Backcharge

Definition — what it is

A backcharge is a cost that one party incurs because of another party's defective work, failure to perform, or breach of an obligation, which the incurring party then charges back by deducting it from amounts owed to the responsible party. In construction it most commonly flows from a general contractor to a subcontractor — for cleanup the sub failed to do, damage the sub caused to another trade's work, or corrective work a defaulting sub left behind — but it can flow between subcontractors or from an owner to a contractor as well. A backcharge is not a change order and not a penalty; it is a cost-recovery mechanism grounded in the contract's right of setoff and in the responsible party's underlying obligation. Its validity depends entirely on documentation: a backcharge that cannot prove the cost was incurred, was reasonable, and was the responsible party's obligation is simply a deduction the responsible party will dispute and often defeat.

Also known as: Back Charge, Chargeback, Deductive Charge, Setoff, Offset

Why it matters — what it protects

The backcharge is how a contractor recovers real money it spends cleaning up someone else's failure. When a subcontractor abandons a punch item, damages another trade's finished work, or leaves debris the contract makes its responsibility, someone still has to pay for the fix — and without a backcharge, that cost silently erodes the contractor's margin. The backcharge is the difference between absorbing another party's default and recovering it, and on projects with weak subs it can be the difference between a profitable job and a loss.

It is only as good as its documentation, which makes it a discipline problem more than a legal one. A valid backcharge requires proof that the cost was actually incurred, that it was reasonable, that the work was genuinely the responsible party's obligation, and — critically — that the party was given notice and an opportunity to cure before the cost was incurred. Backcharges assessed without that record are routinely reversed, so the money is recovered or lost at the moment the cost is incurred, not months later when the deduction is booked.

It sits at the intersection of cost recovery and relationship risk. A backcharge is an adversarial act against a party the contractor often still needs on the job or on the next one, and one assessed carelessly or without notice poisons the relationship and invites retaliation in the form of the sub's own claims. Handled with proper notice and documentation, it is a legitimate business transaction; handled as a surprise deduction on a pay application, it becomes a dispute that costs more than it recovers.

Unrecovered or improperly documented backcharges quietly distort job cost and margin. Corrective work performed and charged to the general conditions or to the wrong cost code, rather than backcharged to the responsible party, shows up as an unexplained overrun and hides the true cost of a poorly performing sub. Tracking backcharges properly is not just about the recovery; it is about attributing cost to the party that actually caused it, which is essential to knowing which subs are worth rehiring.

Lifecycle — how it moves

1. Default or damage identified

   The responsible party fails to perform, leaves defective work, damages another trade's work, or neglects an obligation like cleanup. The condition is documented immediately with photos and a description while the evidence is fresh.

2. Notice and opportunity to cure

   The responsible party is notified in writing of the deficiency and given a contractual opportunity to correct it themselves. Skipping this step is the most common way a backcharge is later invalidated, because the party never got the chance the contract requires.

3. Failure to cure

   The responsible party declines, fails to respond, or corrects inadequately within the cure period. The right to perform the work and charge it back now attaches, and the failure is documented.

4. Corrective work performed

   The incurring party performs or hires out the corrective work, tracking the actual cost — labor, material, equipment, and any subcontracted repair — segregated so it can be substantiated as a specific, reasonable amount.

5. Cost documentation and pricing

   The actual cost is compiled with backup: time records, invoices, tickets, and photos of the completed correction. Reasonable overhead may be added per the contract; padding the amount undermines the whole backcharge.

6. Backcharge notice and assessment

   A formal backcharge is issued to the responsible party stating the amount, the basis, and the documentation, and the amount is set up as a deduction against what is owed — typically netted through a subcontract change order or the next payment.

7. Dispute or acceptance

   The responsible party accepts and the deduction stands, or disputes it, at which point the documentation and the notice record decide the outcome. Contested backcharges may escalate to the dispute process.

8. Settlement and reconciliation

   The backcharge is netted, adjusted, or released, and reconciled against the subcontract and the sub's final payment and lien waiver so the reduced amount is reflected in the closeout.

Anatomy — the data it carries

Backcharge number

Unique identifier linked to the responsible party, the subcontract, and any related SCO through which the deduction is netted.

Responsible party

The party being charged — a subcontractor, another trade, or a vendor. The backcharge attaches to that party's specific contract and payments.

Description of default

The specific defective work, damage, or failure being corrected. Vague descriptions like 'general cleanup' are the easiest for the responsible party to dispute.

Notice record and cure period

The dated written notice of the deficiency and the opportunity to cure given. The field that most often decides whether the backcharge survives a challenge.

Cost detail

Actual labor, material, equipment, and subcontracted-repair cost, segregated and substantiated with time records, invoices, and tickets.

Overhead and markup

Any administrative markup added per the contract. Excessive or unsupported markup is a common reason an otherwise valid backcharge is reduced.

Supporting documentation

Before-and-after photos, the deficiency notice, the cure-period correspondence, cost backup, and completion evidence — the proof the backcharge stands on.

Amount and basis

The total charged and the contractual basis for setoff. The number must tie exactly to the documented cost.

Deduction mechanism

How the amount is applied — a deductive subcontract change order, a deduction on the next progress payment, or an offset at final billing.

Responsible-party response

The party's acceptance or dispute and their stated reasons. Critical evidence if the backcharge escalates.

Cost code allocation

The cost code the corrective cost was charged to and then recovered from, so job cost correctly attributes the cost to the responsible party rather than absorbing it.

Status

Noticed, cure period open, work performed, assessed, disputed, netted, or released — the state of the recovery.

Failure modes — how it breaks

No notice or opportunity to cure

The contractor discovers a deficiency, fixes it, and deducts the cost without ever notifying the responsible party or giving them the contractual chance to correct it themselves. The party disputes the backcharge, points to the missing notice, and the deduction is reversed regardless of the merit of the underlying complaint.

Cost not documented at the time

The corrective work is performed but the labor, material, and equipment are never segregated and recorded. When the backcharge is challenged, the contractor cannot prove what it actually spent, and the amount is discounted to whatever it can substantiate.

Padded or inflated amount

The backcharge includes generous overhead, inflated hours, or costs unrelated to the actual correction. The responsible party seizes on the padding to attack the entire backcharge's credibility, and even the legitimate portion becomes hard to collect.

Charged to the wrong party

The damage is backcharged to a sub who did not actually cause it, or a shared-cause deficiency is charged entirely to one party. The dispute over responsibility consumes more than the amount, and the true cause escapes accountability.

Surprise deduction on a pay application

The first the sub learns of a backcharge is a reduced payment with no prior notice or explanation. The relationship ruptures, the sub retaliates with its own claims or slows the remaining work, and the recovery costs far more than it returns.

Cost absorbed instead of backcharged

The corrective work is charged to general conditions or a generic cost code and never backcharged at all. The responsible party's default silently erodes the contractor's margin, and the job cost report shows an overrun with no attributable cause.

Metrics — how it is measured

Backcharge documentation completeness

Share of backcharges with notice, cure-period evidence, segregated cost, and completion proof. The determinant of how many survive a dispute.

Notice compliance rate

Share of backcharges preceded by written notice and a cure opportunity. The procedural control that decides most contested backcharges.

Recovery rate

Assessed amount actually netted or collected versus assessed. Reveals how much of the charged cost holds up against dispute.

Dispute rate

Share of backcharges the responsible party contests. High rates point to weak documentation, poor notice, or padded amounts.

Cost-attribution accuracy

Share of corrective cost correctly attributed to the responsible party rather than absorbed into general conditions. Measures whether job cost tells the truth about who caused overruns.

Time-to-assessment

Days from default to formal backcharge. Long lags mean cost records go cold and memory of the default fades, weakening recovery.

Relationship-cost signal

A qualitative read on whether backcharges are handled with notice and transparency or as surprise deductions. Predicts retaliatory claims and rehire decisions.

The AI shift — what actually changes

Conversational

The backcharge record becomes interrogable. You ask which backcharges lack a notice-and-cure record, which have cost that is not fully substantiated, and which corrective costs are sitting in general conditions that should have been charged to a responsible sub — each answer tied to the notices, cost records, and photos, so weak or absorbed backcharges surface before they are lost or reversed.

Generative

From a documented deficiency and the corrective cost records, a model drafts the deficiency notice with the cure period, assembles the cost substantiation with the backup indexed, and drafts the formal backcharge stating amount, basis, and documentation — so the recovery rests on a complete package rather than a bare deduction the sub will dispute.

Orchestrated

The backcharge stops being a disconnected deduction. The corrective cost is captured against a segregated cost code, the notice-and-cure sequence is tracked against the contract, the amount is netted through a deductive subcontract change order and reflected in committed cost and the sub's payment, and the recovery is reconciled to the sub's final billing and lien waiver.

Autonomous

The routine motion runs inside guardrails: deficiencies trigger the notice-and-cure workflow, corrective cost accumulates against segregated codes, documentation completeness is monitored, and absorbed corrective costs that should be backcharged are surfaced. Humans always decide responsibility for the default, approve the amount and any markup, and authorize the deduction against a party's payment.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — You suspect you are absorbing corrective costs that should be recovered from subs.

Review our corrective and rework costs on this project. Identify corrective work charged to general conditions or generic cost codes that appears to be the result of a specific subcontractor's defective work, damage, or failure to perform — the kind of cost that should have been backcharged. For each, give me the description, the cost, the likely responsible sub, and whether we ever issued a deficiency notice. Then review our existing backcharges and flag any that lack a documented notice-and-cure record or whose cost is not fully substantiated. Rank by dollars we are absorbing that we could recover.

What good output looks like: A ranked view of absorbed corrective costs that should have been backcharged and existing backcharges with documentation gaps — the recoverable money we are leaving on the table or about to lose.

Follow-ups:

• For the strongest absorbed costs, is it too late to backcharge, and why?
• Which existing backcharges are at risk of being reversed if disputed?
• Which subs are we repeatedly cleaning up after, based on this pattern?

Generative — A sub left defective work and you need to start a backcharge correctly with notice.

Our framing sub installed a section of level-3 wall out of plumb and has been notified informally but has not corrected it; drywall is scheduled to start in 5 days. Draft the formal written deficiency notice: describe the specific defect and its location, reference the subcontract obligation it breaches, give a specific and reasonable cure period consistent with the drywall start, and state clearly that if they do not correct it we will perform the work and backcharge the actual cost. Keep it firm, factual, and non-inflammatory. Then outline exactly what cost records and photos we must capture if we end up performing the correction, so the eventual backcharge is defensible.

What good output looks like: A proper deficiency-and-cure notice tied to the subcontract obligation, plus the cost-documentation checklist that makes the backcharge defensible if the sub fails to correct — not a surprise deduction.

Follow-ups:

• Draft the follow-up backcharge assessment assuming they do not cure in time.
• What overhead can we legitimately add under a standard subcontract?
• How do I word this so it protects recovery without escalating unnecessarily?

Orchestrated — The cure period lapsed, you performed the correction, and you need the backcharge assembled and netted correctly.

Our framing sub failed to cure the out-of-plumb wall within the noticed period, so we performed the correction. Assemble the backcharge: total the segregated labor, material, and equipment we charged to the corrective cost code, attach the deficiency notice and the cure-period correspondence, add the contract-allowed administrative overhead, and index the before-and-after photos and cost backup. Set the amount up as a deductive subcontract change order against the framing sub, reflect the reduction in committed cost and the sub's next payment, and confirm the corrective cost is attributed to this sub in job cost rather than absorbed. Return the assembled backcharge with every figure traced to its source, and flag anything unsupported.

What good output looks like: An assembled, fully documented backcharge netted through a deductive SCO, attributed to the responsible sub in job cost, with the notice-and-cure record attached and every cost traced — a recovery that will survive a dispute.

Follow-ups:

• Draft the transmittal to the sub with the full basis and documentation listed.
• Confirm this reduces the sub's final payment and lien waiver correctly.
• If the sub disputes it, which parts of our documentation are weakest?

Autonomous — Standing policy for handling backcharges so money is recovered and relationships survive.

Operate our backcharge process continuously under these rules. When a deficiency, damage, or failure to perform is documented against a responsible party, initiate the notice-and-cure workflow: draft the written deficiency notice, track the cure period, and record whether the party corrected it. If corrective work proceeds, ensure the cost accumulates against a segregated cost code and monitor documentation completeness. Surface corrective costs sitting in general conditions that appear attributable to a specific party and should be backcharged. Never decide which party is responsible for a default, never approve the backcharge amount or its markup, and never authorize a deduction against any party's payment — route all of those to me with the documentation. Give me an exception queue and the recoverable-cost total, not the whole ledger.

What good output looks like: A managed process where notice-and-cure, cost capture, and documentation monitoring run automatically, while responsibility, amount, markup, and any deduction against a party's payment stay with a human.

Follow-ups:

• Show what you noticed, what you flagged as absorbed, and what awaits my approval.
• Which backcharges have incomplete documentation and need attention before assessment?
• What is our total recoverable but not-yet-assessed corrective cost?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Silent absorption

   Corrective costs are absorbed into general conditions with no backcharges. Subs' defaults erode margin invisibly and job cost cannot attribute overruns to a cause.

1. Level 1 — Ad hoc deductions

   Backcharges are assessed as deductions when someone remembers, often without notice or a cure opportunity. Many are disputed and reversed for lack of process.

2. Level 2 — Documented and noticed

   Backcharges follow a notice-and-cure sequence, corrective cost is segregated, and the amount is netted through deductive change orders with documentation attached.

3. Level 3 — Assisted

   Deficiency notices and cost substantiation are drafted from the record, documentation completeness is checked, and absorbed corrective costs that should be backcharged are surfaced.

4. Level 4 — Operated

   Notice-and-cure workflow, cost capture, and documentation monitoring run unattended inside guardrails, while humans own responsibility determination, the amount, and any deduction against payment.

Common questions

What makes a backcharge enforceable?

Documentation and notice. An enforceable backcharge proves the cost was actually incurred and reasonable, that the corrective work was genuinely the responsible party's obligation, and — most decisively — that the party was given written notice of the deficiency and a contractual opportunity to cure it before the cost was incurred. Backcharges assessed without notice and cure are routinely reversed regardless of whether the underlying complaint was valid.

Why is giving notice and a cure period so important?

Because the responsible party has a contractual right to fix its own defective work, usually more cheaply than the contractor can. Depriving it of that opportunity by unilaterally performing the correction and deducting the cost breaches that right and gives the party a clean basis to dispute the backcharge. The notice-and-cure step converts a unilateral deduction into a documented, defensible recovery, and skipping it is the single most common reason backcharges fail.

How is a backcharge different from a deductive change order?

A deductive change order reduces the contract for a scope reduction the parties agree to; a backcharge recovers the cost of correcting or completing another party's defective or incomplete performance. They can intersect — a backcharge is often netted through a deductive subcontract change order as the mechanism — but the backcharge is a cost-recovery based on default and setoff rights, not a mutually agreed scope reduction, which is why its validity turns on proof of the default and the cost.

Why not just absorb small corrective costs to keep the peace?

Because absorbed corrective cost distorts job cost and hides which subs are actually failing to perform. Even where a specific backcharge is not worth the relationship friction, attributing the cost to the responsible party in the cost system — rather than burying it in general conditions — is what tells you which subs cost you money on every job and should not be rehired. The recovery decision and the attribution decision are separate, and you should always make the attribution one.