Subcontractor Backcharges: How to Document Them So They Actually Stick

Every general contractor has been here. A framing sub leaves the site a mess, so cleanup runs you four hours of labor. The plumber cracks a slab patch the concrete guy just finished, and now you’re paying to redo it. The drywaller no-shows on a Friday and you have to rent a lift over the weekend to keep the painter on schedule. You add it all up, deduct it from the sub’s next pay app, and a week later you get a phone call: “What is this $3,400 deduction? I never agreed to that.”

Backcharges are one of the most common sources of payment disputes in construction, and the contractor who initiated them usually loses. Not because they were wrong about the work — the cleanup happened, the slab really was cracked — but because they couldn’t prove it on paper. A backcharge without documentation is just an accusation, and accusations don’t survive arbitration.

What a Backcharge Actually Is

A backcharge is a deduction a general contractor takes against a subcontractor’s contract amount to cover costs the GC incurred because of that sub’s action, inaction, or defect. It is not a penalty. It is not a fine. It is reimbursement — and that distinction matters legally, because penalties are generally unenforceable in construction contracts while reimbursement of actual costs is.

The three most common categories:

Cleanup and trash removal — the sub left debris, dust, packaging, or food waste that the GC had to dispose of
Damage to other work — the sub cracked, scratched, dented, or contaminated work installed by another trade or by the GC
Schedule impact — the sub missed a date and the GC paid premium time, rental extensions, or expedited shipping to recover

A fourth category — defective work the sub refused to fix — lives in its own legal universe and almost always requires a formal cure notice before you can backcharge. Skip that step and you hand the sub a free pass.

The Contract Comes First

Before any of the documentation matters, your subcontract has to actually permit backcharges. Read your standard sub agreement right now and find the language. If it just says “contractor may deduct,” that’s weak. Strong backcharge language includes:

The trigger — what specific conduct allows a backcharge (cleanup not completed within 24 hours of notice, damage to adjacent work, missed milestone)
The notice requirement — how much warning you owe the sub before incurring costs on their behalf, usually 24 to 48 hours in writing
The cost basis — whether you can charge actual cost, cost plus markup, or a flat fee
The dispute window — how long the sub has to object before the backcharge becomes final

If your subcontract is silent on backcharges, you can still pursue actual damages, but you’ll need to prove them through breach-of-contract theory rather than a contractual offset. That’s harder and slower.

Many small contractors borrow a one-page subcontract from a buddy and never look at the backcharge clause until they need it. Fix that this week, not the week the dispute starts.

The Notice Step Everyone Skips

The single most common reason backcharges get reversed: the GC never gave the sub a chance to fix it themselves. Courts and arbitrators consistently side with subcontractors who can say “nobody told me there was a problem before they sent me a bill for it.”

A proper notice has five elements:

Specific identification — not “your guys left a mess” but “framing debris in the garage and on the east side of the foundation, including approximately twelve sheets of OSB scrap and packaging from the I-joist delivery”
Photographic evidence — timestamped photos attached to the notice itself, not produced later
A cure deadline — a clear window the sub has to remedy it, consistent with the contract
Cost estimate — what you expect to spend if they don’t handle it, so they can make an informed decision
Delivery confirmation — sent by a method that proves receipt: email with read receipt, text message, or certified mail for larger items

The notice should go out the same day you discover the issue. A backcharge for cleanup you documented three weeks after the fact looks like an afterthought, because it usually is.

Ready to put this into practice? Download TrestleBook Free — it’s free and works offline.

Building the Evidence File

Assume every backcharge over a few hundred dollars will be challenged. Build the file as if you’re handing it to a third party who has never been on the site. The minimum:

Before photos — the condition that triggered the backcharge, with date stamps and ideally a landmark that locates it (door number, room, grid line)
The written notice with delivery confirmation
After photos — condition once your crew or replacement sub completed the work
Time records — who worked, when, for how long, with their normal billing rate
Material receipts — tagged to the specific backcharge, not buried in a job-wide stack
Equipment costs — rental receipts or your published internal rate sheet for owned equipment

The time records are where most contractors get sloppy. If your foreman spent 90 minutes on cleanup, that needs to be coded to a backcharge cost code in your daily log, not folded into general project labor. When the sub disputes it, you want to point at a contemporaneous record, not reconstruct it from memory. Tools like TrestleBook let you tag specific hours and material purchases to a backcharge line item so the documentation builds itself as the day goes.

Pricing the Backcharge Honestly

Greed kills backcharges faster than poor documentation. If you charge $85 an hour for a laborer whose loaded cost is $42, you’ve handed the sub’s lawyer a talking point that distracts from the actual misconduct. Use defensible numbers:

Labor — loaded cost (wages, taxes, insurance, benefits) plus a reasonable overhead percentage if your contract allows markup. If unsure, run it at loaded cost and skip the markup; you’ll win more disputes than you lose dollars
Materials — actual invoice cost, no markup unless the contract specifies one
Equipment — rental at invoice or a published rate that matches what an outside renter would pay
Other subs you hired to clean up the mess — their invoice, paid, with proof of payment

Treat the backcharge like an audit. If a third-party CPA reviewed the math, would each number tie to a document? If not, fix it before sending.

Calculating loaded labor cost properly is a separate skill on its own — one most contractors get wrong by 15 to 30 percent. If you’re unsure of your real rate, that’s a bigger problem than any single backcharge, and worth fixing across your whole estimating process.

The Pay Application Mechanics

Once the backcharge is documented and priced, it needs to land cleanly on the sub’s pay application. The two acceptable methods:

Line-item deduction — show the gross amount earned, then a separate clearly labeled line for “Backcharge: cleanup, 2026-04-12, see attached” with the dollar amount and a reference to a backcharge log
Deductive change order — for larger items, formalize it as a signed change order reducing the subcontract value, which both parties acknowledge before the next pay app

What kills you is the silent deduction — the sub bills $14,000, the check shows up at $11,200, and the only explanation is a sticky note. That tells the sub you’re hiding something even when you aren’t. Show your work, every time.

The deductive change order route is harder to ignore and harder to dispute later. If the sub signs it, the backcharge is essentially final. If they refuse to sign, that’s a signal to look at the file again before you push it through — they may know something you don’t, or they may be setting up a claim.

What to Do When the Sub Pushes Back

Half of backcharges over $1,000 get objections. Most are noise; some are legitimate. A simple triage:

“That wasn’t my crew” — pull the sign-in sheet, the daily log, and the time-stamped photos. If you can’t tie the mess to their people, you don’t have a backcharge
“Nobody told me” — produce the notice with delivery confirmation. If you don’t have one, consider reducing the backcharge to actual hard cost and waiving the markup as a goodwill gesture
“Your rate is too high” — show the loaded cost calculation. If your number is defensible, hold; if it’s puffed, adjust it before the dispute escalates
“The damage was already there” — this is what your before-photos exist for. If you skipped them, you’re probably going to eat at least part of the cost

The cost of fighting a $2,000 backcharge through arbitration is well north of $2,000 in legal time and lost goodwill. Pick your battles. A sub who pushes back loudly on every backcharge but does good work is sometimes worth a small concession to preserve the relationship; a sub who damages adjacent work weekly and disputes every charge is teaching you something about whether they belong on your next bid list.

The Tracking System That Actually Works

The contractors who win backcharge disputes have a system they use on every job, not just the ones that go sideways. The minimum:

A backcharge log per project, numbered sequentially, with date, sub, description, amount, status, and document references
A photo discipline where every backcharge candidate gets photographed within an hour of discovery, before any cleanup begins
A notice template ready to go on the field tablet or phone, so the foreman can issue it from the site rather than waiting until they’re back in the truck
A monthly review where open backcharges get worked to resolution rather than sitting on the log until the project closes

That last item separates the contractors who collect from the ones who write off. Open backcharges decay. Memories fade, photos get deleted from phones that get replaced, and the sub’s position hardens the longer the dispute sits. Push them to resolution within 30 days or accept that you probably won’t collect.

This kind of job-by-job tracking discipline is the same muscle that makes self-employed work pay — Stintly handles it for freelancers and single-operator businesses the same way KeyLoft handles tenant-related deductions for landlords. The underlying habit is the same: capture the cost the moment it happens, with the proof attached, and the collection takes care of itself.

When Not to Backcharge

Some situations look like backcharges but aren’t worth pursuing. A few:

Mistakes your own field team contributed to — if the sub broke something because your scheduling forced them into a crowded space, that’s shared fault and trying to backcharge it will damage the relationship for short money
Pre-existing conditions — cleanup that was there before the sub arrived isn’t theirs, even if it’s convenient to assign it
Soft costs you can’t document — “disruption” and “inefficiency” rarely survive scrutiny without specific hours and tasks attached
Anything under your friction threshold — pick a floor, maybe $250 or $500, below which you don’t bother. The administrative cost exceeds the recovery

Backcharges are a tool for recovering real costs, not a profit center and not a disciplinary measure. The contractors who use them surgically — well-documented, fairly priced, promptly noticed — collect most of what they pursue and keep the subcontractor relationships intact. The contractors who use them as a club lose the subs first and the disputes second.

The whole system rises or falls on what happens on the day the problem occurs. A photo taken in the first hour, a notice sent the same afternoon, and a line in the daily log coded to the right cost bucket will carry a backcharge through every challenge that follows. Skip those three steps and no amount of arguing later puts the money back in your pocket.