Esc

↑↓ move↵ openIndex · Pagefind

Back charges that survive the dispute.

Notice first, cost second, deduction last. Send the notice the day you find the problem, then log each back charge through cure, cost backup, the deductive subcontract change and the pay app it comes off.

  • Free
  • No signup
  • Print · CSV · Markdown
Download CSVDownload Markdown

Back charge notice and log

os.construction · free template
Project
Contract / job #
Log kept by
Last updated

Back charge log

BC #Date foundSub / supplierSubcontract #Description and locationSubcontract clauseNotice sentCure periodCured?Cost backupAmountSub responseDeductive change #Deducted onStatus
BC-007Drywall subSC-09Ductwork damaged at L2 corridor, grid C-4 (SAMPLE · delete this row)Subcontract damage and cleanup clause48 hoursNoT&M ticket 0418, photos, daily log3850Disputed, then acceptedCCO-09-03Pay app #7Deducted
BC-008Concrete subSC-03Washout left in stair 2 pitSubcontract cleanup clause24 hoursYes0Cured, no charge
BC-009Electrical subSC-14Firestopping removed at 3 penetrations, L3Subcontract correction of work clause5 daysNoFirestop sub invoice, photosResponse dueNoticed

Sample rows are illustrative and marked for deletion. Your contract, drawings and specifications govern. Template from os.construction/resources/templates/back-charge-log

How to use it

Using the back charge notice and log

  1. Use the printable back charge notice the day you find the problem. Cite the subcontract clause, describe what happened and where, attach photos and set the cure period the subcontract gives.
  2. Log the notice the same day: BC number, sub, clause, notice date and cure period. Disputes usually start with those dates.
  3. If the sub cures, close the line with no charge. That is the best outcome.
  4. If it doesn’t, correct the work with your own forces or another trade and track the cost on its own T&M ticket or cost code. Markup only if the subcontract allows it.
  5. Send the back charge with the cost backup, enter a deductive change on the sub’s subcontract, and note which pay app it comes off. Check that the withholding fits your state’s prompt payment rules.
  6. Review open lines at every pay app and before closeout, so nothing is left to argue about at final payment.
From damage to deductionProblem found, then Written notice, then Cure period, then GC corrects it, then Back charge issued, then Deductive change. Cured: no charge: from Cure period back to Problem found.Cured: no chargeProblem foundPhotos, daily log, locationWritten noticeClause cited, cure period setCure periodSub fixes it or doesn’tGC corrects itCost tracked on a ticketBack charge issuedCost backup attachedDeductive changeOff the next pay app
  1. Problem foundPhotos, daily log, location
  2. Written noticeClause cited, cure period set
  3. Cure periodSub fixes it or doesn’tCured: no charge: back to “Problem found”
  4. GC corrects itCost tracked on a ticket
  5. Back charge issuedCost backup attached
  6. Deductive changeOff the next pay app
From damage to deduction
Text version
  1. Problem found: Photos, daily log, location
  2. Written notice: Clause cited, cure period set
  3. Cure period: Sub fixes it or doesn’t
  4. GC corrects it: Cost tracked on a ticket
  5. Back charge issued: Cost backup attached
  6. Deductive change: Off the next pay app

Cured: no charge: from “Cure period” back to “Problem found”.

In os.construction

Do this in os.construction instead of a spreadsheet

In os.construction a back charge is entered as a commitment change order on the subcontract: a title, cost code and negative amount, with Draft, Pending, Approved, Rejected or Void statuses, so the revised commitment reflects it when the next sub invoice comes in. The daily log, photos and T&M tickets hold the evidence. There is no dedicated back charge record yet, so keep this log alongside the commitment.

Try it on the sample project

Every trial workspace includes a sample project to run this workflow on. 14-day free trial. Pricing for paid plans isn't set yet.

FAQ

Questions about the back charge notice and log

What is a back charge in construction?

A deduction a contractor takes from what it owes a subcontractor or supplier to recover cost that party caused: damage, defective work, skipped cleanup or work finished after they failed to perform. It is usually documented as a deductive change to the subcontract.

What should a back charge notice include?

The subcontract clause that gives the right, what happened, where and when, photos, what the sub must do and by when, what happens if it doesn’t, and a contact. Send it the way the subcontract requires and log the date.

Can I add markup to a back charge?

Only if the subcontract allows it. Some subcontracts allow a stated percentage for overhead or administration; others allow actual cost only. A markup the contract doesn’t support is an easy point for the sub to dispute.

How does a back charge show in os.construction?

As a commitment change order with a negative amount on the sub’s subcontract, so the revised contract amount reflects it. The supporting daily log entries, photos and T&M tickets stay on the same project.

Is this template legal advice?

No. Back charge rights, notice periods and withholding limits come from your subcontract and the law where the job is. Use the template as a working aid and get advice on disputed or large charges.

Keep going

Open file