The Construction Back Charge Process: Won in 48 Hours, Not at Final Payment

A back charge survives review when three things exist in writing and can be produced on demand: notice of the deficiency issued before remedial work started, proof the cure period in the subcontract elapsed without action, and cost records that tie specific labor, equipment and material to that specific scope. Miss any one and the deduction becomes negotiable. Most back charges are written off not because the subcontractor was right, but because the general contractor cannot produce the record.

What a back charge actually is, and what it is not

A back charge recovers cost the contractor incurred performing work the subcontractor was obligated to perform and did not. The scope stays in the subcontract. The contractor does the work, prices it, and charges it back against the commitment.

That is a different instrument from a deductive change order, and conflating the two is a common drafting error that weakens the file.

	Back charge	Deductive change order
Contract value	Unchanged; cost recovered against the commitment	Reduced by agreement
Trigger	Performance failure after notice and cure	Scope removed, descoped or not required
Subcontractor consent	Not required, but notice is	Required; it is a bilateral modification
Evidence needed	Notice, cure window, cost substantiation	Scope definition and agreed credit
Typical dispute	Reasonableness of cost and whether notice was given	Value of the credit

When a contractor issues a "deductive change order" to cover another sub's cleanup, the subcontractor can reasonably refuse to sign, and now there is an unexecuted change order sitting in the log instead of a documented recovery. If the intent is recovery for failure to perform, call it what it is and build the file that supports it. If the intent is to remove scope, process it through the normal change order management workflow with a signed credit.

Where in the subcontract the authority comes from

Back charge authority is not implied. It lives in specific clauses, and the clause determines the procedure you have to follow.

• Cleanup and debris. Usually a daily obligation with a short cure period, often 24 to 48 hours, after which the contractor may clean and charge the cost.
• Defective or non-conforming work. Tied to the correction-of-work clause, typically requiring written notice and a cure period measured in days rather than hours.
• Failure to prosecute the work. Supplementation clause, which allows the contractor to augment the subcontractor's forces at the subcontractor's cost. This one almost always requires notice plus an opportunity to increase manpower.
• Damage to other trades' work. Indemnity and protection-of-work clauses, usually without a cure period but with a notice requirement.
• Safety violations and housekeeping. Often a stipulated amount per occurrence, which is enforceable only if the per-occurrence amount is in the executed subcontract and the occurrence is documented.

The project engineer issuing the notice should know which clause applies before writing the email. A notice that cites the wrong clause gives the subcontractor's counsel a place to start.

How to back charge a subcontractor: the sequence that holds

1. Document the condition the day it is observed. Photographs with date and location metadata, area identified by level and grid or room number, and a line in that day's report. A photograph taken three weeks later during a walkthrough proves the condition existed on the day of the walkthrough and nothing more.

2. Issue written notice to the party named in the subcontract. Not a text to the foreman. The notice goes to the address and contact identified in the agreement, states the deficiency, cites the clause, states the cure period and states that the contractor will perform the work and charge the cost if the cure period lapses. Keep it to one page.

3. Let the cure period run and record what happened. The highest-value entry in the whole file is the daily report from the day after notice that says the subcontractor did not mobilize. If the subcontractor does cure, close the notice in writing. A closed notice is worth keeping; it establishes a pattern if the same failure repeats.

4. Open a segregated cost code before any remedial work starts. This is where most back charges quietly die. Cleanup labor charged to a general project cleanup code cannot be extracted at the end of the month without reconstruction, and reconstructed cost is exactly what a subcontractor's claims consultant attacks. The code is opened first, the crew is told to charge to it, and the superintendent confirms it on the daily report.

5. Capture cost as it is incurred. Named crew, hours, classification, equipment with duration, disposal tickets, rental invoices, material receipts. Markup at the rate the subcontract permits, not the rate the estimator wishes it permitted. If the subcontract caps overhead and profit on back charges at a stated percentage, apply the stated percentage.

6. Issue the back charge package within the same billing cycle. Notice, proof of lapse, daily reports, photographs, cost detail and the calculation, transmitted as one document with a response window. The subcontractor's silence against a complete package is worth considerably more than their silence against a line item.

7. Then, and only then, reflect the deduction on the pay application. The deduction should be the last step in a sequence the subcontractor has already seen, not the first notice they receive that money is being withheld.

Cleanup back charges: the documentation that gets contested

Cleanup is the most frequently issued and most frequently reversed back charge, because the evidence is the weakest by default. Everyone's debris looks alike in a photograph of a slab.

The file that holds up ties the debris to the trade. Material offcuts identifiable by product, packaging with the supplier's label, the work area assigned to that subcontractor in the logistics plan on that date, and the daily report showing who worked in that area. Where two trades worked the same zone, apportion the charge and say in the notice how you apportioned it. A defensible 60/40 split survives better than a 100% charge to the easiest target.

Composite cleanup crews create the second problem. If one laborer cleans three areas in a shift, the back charge is a fraction of that shift, and the fraction has to be recorded contemporaneously by the superintendent, not estimated later by the project manager from a timesheet.

Why back charges collapse at final payment

By the time a disputed back charge reaches final payment, four things have changed. The superintendent who observed the condition has rotated to another job. The daily reports are in a closeout archive. The subcontractor's project manager has been replaced by someone from their main office whose job is to recover retention. And the contractor's own PM is being measured on closing the job, not on defending a five-figure deduction.

That asymmetry is why subcontractors hold back charges to the end. A charge that was never acknowledged in month four is a negotiating position in month fourteen, and it is usually settled at a discount to release retention and close the subcontract.

The structural fix is to force acknowledgement early. Every back charge gets a response window, and a non-response is logged as a non-response. When the deduction finally appears, the question is not whether the work was deficient but why the subcontractor said nothing for ten months. That record also matters at the end of the job, where back charge disputes interact with retention release and lien waiver management on every draw, and with the closing documentation reviewed during project handover.

The administrative cost of doing this properly

Run the process honestly and a single back charge consumes real hours: the notice drafted and sent, the cure period tracked, a cost code opened in accounting, daily reports pulled, photographs located in someone's phone, a package assembled, a transmittal logged, the deduction entered against the commitment, and the commitment reconciled against the pay application. Multiply by the number of charges a busy interior fit-out generates in a month.

That is the real reason back charges get written off. Not weak contract language, but a process whose cost exceeds the recovery when it is run across email, a shared drive, a cost spreadsheet and an accounting system that never see each other. The decision to let a charge go is usually rational given the tooling. The tooling is the problem, and it is the same tooling problem that produces late visibility on cost overruns and slow change order turnaround.

What changes the arithmetic is keeping the notice, the daily report, the cost code, the commitment and the pay application in one connected record, so the back charge package assembles itself from documents that already exist rather than being reconstructed from four systems. That is what INGENIOUS.BUILD is built to hold: the correspondence, the commitment and the cost position in the same place, with the audit trail attached. The back charge becomes a few minutes of work on the day the condition is observed instead of a week of archaeology at closeout.

Write the notice the day you see the condition. Everything else in the process is bookkeeping.