Construction Backcharges for Incomplete Punch List Work

Nobody wants to issue a backcharge. Backcharges damage subcontractor relationships, create administrative overhead, and introduce the possibility of contractual disputes. On a well-run project with clear communication, timely notifications, and responsive subcontractors, backcharges should be rare — ideally zero.

But they're not always zero. On multifamily projects with dozens of subcontractors and thousands of punch items, there are situations where a sub doesn't complete corrections despite clear notification, acknowledgment, and deadlines. When that happens, the general contractor needs a documented process for having the work completed by others and recovering the cost. That's a backcharge.

This guide covers when backcharges apply to punch list work, the specific documentation required to make them enforceable, the contract provisions that support them, how to calculate and execute the backcharge, and how subcontractor disputes are resolved. It also covers how a strong notification and accountability system prevents most backcharges from ever becoming necessary.

What Is a Construction Backcharge?

A backcharge is a contractual remedy, not a penalty. It exists because the subcontract requires the sub to deliver work that conforms to specifications. Punch list items represent work that does not conform. The sub's obligation is to correct those items at no additional cost. When the sub fails to do so, the GC exercises their contractual right to have the work corrected by others and charge the cost back.

The critical distinction: a backcharge is not a fine or a fee imposed on the subcontractor. It's the documented, actual cost of completing work the sub was contractually obligated to perform. This distinction matters because inflated or estimated backcharges are the most common basis for subcontractor disputes — and the most common reason backcharges fail.

When backcharges are appropriate

Backcharges for punch list work are appropriate only when all of the following conditions are met:

1. The subcontractor was notified of specific punch items with descriptions, photos, and unit locations.
2. The subcontractor acknowledged receipt of the notification.
3. A reasonable correction deadline was communicated.
4. The deadline passed without the corrections being completed.
5. The GC followed a documented escalation process (phone call, formal written notice).
6. The subcontractor still failed to complete corrections after the escalation.

If any of these conditions is missing — particularly the notification and acknowledgment — the backcharge becomes difficult to enforce and may expose the GC to a counterclaim.

When Backcharges Apply to Punch List Work

Not every incomplete punch item warrants a backcharge. The decision to backcharge should consider the volume of incomplete items, the sub's overall responsiveness, the impact on the closeout timeline, and the cost-benefit of the administrative effort.

Situations where backcharges are justified

• The sub is non-responsive. They were notified, acknowledged, given a deadline, received written escalation — and still haven't sent a crew. At this point, the GC has exhausted the communication process and needs to complete the work to close out the project.
• The sub has left the project. The subcontractor has demobilized, moved to another project, or gone out of business. Their punch items remain open and no crew is coming. The GC must hire another contractor to complete the work.
• The deadline has been extended multiple times. The sub has received one or more deadline extensions, committed to revised dates, and still hasn't completed corrections. Continued extensions without performance signal that the sub will not voluntarily complete the work.
• Closeout is being delayed. The owner or developer is withholding the GC's retainage or delaying certificate of occupancy because of incomplete punch items within this sub's scope. The cost of extended general conditions exceeds the cost of hiring a replacement contractor.

Situations where backcharges are premature

• The deadline just passed. Jumping to backcharge on Day 1 past the deadline — without a phone call, without a written notice — signals bad faith and damages the relationship. Follow the escalation path first.
• The sub is actively working on corrections. If the sub has a crew on site making corrections but hasn't finished all items by the deadline, an extension is more appropriate than a backcharge. Backcharges are for non-performance, not slow performance.
• The items are disputed. If the sub has raised legitimate scope or tolerance disputes that haven't been resolved, backcharging on those specific items is premature. Resolve the dispute first, then reassess.

The Six-Document Chain That Makes Backcharges Enforceable

An enforceable backcharge requires a complete documentation chain from initial notification through backcharge execution. Each document builds on the previous one. A gap anywhere in the chain — a missing notification record, a deadline that was communicated verbally but never written down, a follow-up call that wasn't logged — weakens the backcharge and gives the sub grounds to dispute it.

Contract Language That Supports Backcharges

Backcharges are a contractual remedy — they derive their enforceability from the subcontract agreement. Three specific contract provisions support the punch list backcharge process.

Provision 1: Correction of deficient work

This clause requires the subcontractor to correct work that does not conform to contract specifications at no additional cost, within a specified timeframe after written notification by the GC. This is the foundational provision: it establishes the sub's obligation to fix punch items and creates the basis for the GC's right to act when the sub doesn't.

In AIA A401 (Standard Form of Agreement Between Contractor and Subcontractor), this is addressed in Section 4.6. In ConsensusDocs 750, it's addressed in Section 3.11. Your specific subcontract may use different section numbers but should contain equivalent language.

Provision 2: Right to remedy

This clause grants the GC the right to have deficient work corrected by others if the sub fails to do so within the required timeframe, and to deduct all associated costs from the sub's payments. This is the clause that authorizes the backcharge itself — without it, the GC's right to hire a replacement contractor and deduct the cost is ambiguous.

Provision 3: Retainage release conditions

This clause links the release of retainage to complete performance of the subcontractor's scope, including resolution of all punch list items. It establishes that the GC is contractually entitled to withhold retainage until all items are verified complete, giving the GC a financial pool from which to fund backcharges if needed.

The Escalation Path: From Notification to Backcharge

The escalation from initial notification to backcharge execution follows a defined timeline. Each step creates documentation and gives the sub an opportunity to perform before the GC escalates further. Skipping steps weakens the backcharge — follow the sequence.

Day 0 — Notification sent. The sub receives their filtered punch list with photos, descriptions, unit locations, and a deadline of Day 7 (for example). The sub acknowledges receipt.

Day 7 — Deadline passes. Items remain open. The GC documents which items are incomplete.

Day 8 — Phone call. The superintendent calls the sub's PM or foreman. Asks for a specific date when corrections will be completed. Documents the call.

Day 10 — Formal written notice. Email to the sub referencing the original notification (Day 0), acknowledgment, deadline (Day 7), and phone call (Day 8). States that corrections must be completed within 5 additional business days (by Day 15) or the GC will initiate backcharge procedures.

Day 15 — Final deadline passes. If items remain open, the GC issues the backcharge notice.

Day 15+ — Execute. The GC engages a replacement contractor. All costs are documented and deducted from the original sub's payments.

The total timeline from initial notification to backcharge execution is typically 15 to 20 business days. This is long enough to give the sub multiple opportunities to perform and short enough to prevent indefinite delays to closeout.

Calculating the Backcharge Amount

The backcharge amount must reflect the actual, documented cost of completing the corrections — not an estimate, not a penalty, and not an inflated figure designed to punish the sub. Inflated backcharges are the single most common reason subcontractors dispute them, and arbitrators routinely reduce backcharges that can't be supported by invoices and receipts.

What to include

• Replacement contractor labor. The invoiced cost of the replacement contractor's crew, documented by hours worked and hourly rate. The replacement contractor should provide itemized invoices, not lump-sum estimates.
• Materials. The cost of any materials, parts, or supplies required to complete the corrections. Supported by receipts.
• GC supervision. If the superintendent spent time coordinating or overseeing the replacement work, that time can be included at the super's loaded hourly rate. Document the hours.
• Overhead and markup. If the subcontract allows a markup for GC overhead on backcharges (commonly 10–15%), apply it. If the contract is silent on markup, many GCs do not include it to avoid disputes. Check your subcontract language.

What not to include

• Estimated costs. Do not estimate what the corrections "should" cost. Use actual invoices from the replacement contractor.
• Punitive charges. Backcharges are not fines. Adding a "penalty" or "inconvenience fee" beyond documented costs is not supported by most subcontract agreements and will be challenged in disputes.
• Costs unrelated to the incomplete items. Only include costs directly attributable to correcting the specific punch items the original sub failed to complete. Don't bundle other project costs into the backcharge.

When Subs Dispute Backcharges — and How to Respond

Subcontractor backcharge disputes are common. Most can be resolved with documentation — which is why the documentation chain exists. Disputes fall into four predictable categories.

The pattern across all four dispute types is the same: the GC's position is only as strong as the documentation. A complete documentation chain (all six documents) resolves most disputes without mediation. An incomplete chain creates ambiguity that the sub's attorney will exploit.

Retainage Withholding vs. Backcharges

Retainage withholding and backcharges are related but distinct mechanisms. Understanding the difference matters because they have different legal bases, different procedural requirements, and different risks.

Retainage withholding

Retainage is the 5 to 10 percent of each progress payment withheld by the GC until the sub's scope is fully complete. Withholding retainage for incomplete punch items is a contractual right — the sub's work isn't done until punch items are resolved. No additional notice beyond the subcontract terms is typically required to withhold retainage, though good practice is to notify the sub of the specific items preventing release.

Retainage withholding is passive: you're holding payment that's already contractually designated as retention. It creates financial pressure for the sub to complete corrections but doesn't fund the cost of having someone else do the work.

Backcharges

A backcharge is an active deduction from the sub's payments — which may include retainage — to cover the specific, documented cost of corrections made by a replacement contractor. It requires the complete documentation chain and a formal notice process. A backcharge directly recovers costs; retainage withholding creates leverage.

How they work together

In practice, the sequence is usually: withhold retainage → escalate through the notification process → issue backcharge → deduct backcharge from retainage. The retainage serves as the pool of funds from which backcharge costs are deducted. If the backcharge exceeds the retainage amount (rare for punch list items, more common for major deficiency corrections), the GC may need to pursue additional recovery through the subcontract's dispute resolution process.

On a $500,000 subcontract with 10% retainage ($50,000 withheld), a backcharge for punch list corrections might total $3,000 to $8,000 — well within the retainage pool. The sub receives retainage minus the backcharge amount once all other closeout conditions are satisfied.

Prevention: How Good Notification Prevents Backcharges

The best backcharge is the one you never have to issue. On projects with a well-implemented accountability system — clear notifications, acknowledgment tracking, specific deadlines, and consistent follow-up — backcharges are rare because the conditions that cause non-performance are eliminated before they compound.

Why the notification matters most

Most subcontractors complete their punch items when they receive a clear, well-formatted notification with their specific items, photos, and a reasonable deadline. The sub who receives 34 items grouped by unit with photos and a March 22 deadline is far more likely to complete corrections than the sub who receives a 400-line unfiltered spreadsheet with a "please fix these ASAP" note.

Prevention isn't about being nicer or more patient. It's about eliminating the legitimate reasons subcontractors cite for not completing work: "I didn't know about those items," "I couldn't tell what to fix," "nobody gave me a deadline," "the email got buried." Fix those — with filtered, documented, timestamped notifications — and the subs who perform will perform. The small number who don't will face a documentation trail that makes the backcharge straightforward.

The math of prevention

Executing a backcharge costs the GC in administrative time (assembling documentation, drafting notices, coordinating replacement contractors), relationship damage (the sub may not bid your next project), and risk (the sub may dispute the backcharge, requiring mediation or legal resources). Even a successful backcharge typically costs more in total overhead than the face value recovered.

A notification system that prevents one backcharge per project — by converting a non-responsive sub into a responsive one through clear communication — saves more than it costs. That's not a software pitch. It's arithmetic.