Why Your Subcontractor Agreements Are Costing You Money

Sound Familiar?

Signs your subcontract agreements have cost-leaking gaps:

• You've done back-charge work for a sub but couldn't recover the cost under the agreement
• Your subs occasionally send bills for work you thought was in their scope
• You don't have certificates of insurance on file for one or more subs
• Your payment to subs is tied to 'within 10 days of receiving payment from the client'
• Subs do work outside the original scope and then bill for it as 'extras'
• Your change orders to the client are often based on sub pricing that wasn't confirmed upfront

What We Found

The 5 Gaps in Your Subcontractor Agreement That Cost You Money

These five gaps show up in most builder subcontract agreements. They're not hard to find — they just require looking at the agreement from an operational perspective rather than a legal one.

1. Scope Gaps

The most expensive gap in most subcontract agreements is the scope section. The language "sub shall provide all labor, materials, and equipment necessary to complete [scope]" is a scope gap disguised as completeness. It sounds comprehensive but it doesn't actually define what's included and what's excluded.

A tight scope section says: "Included in this agreement: [specific scope]. Not included: [specific exclusions]. If the sub encounters conditions outside this scope, they will notify the contractor in writing within 48 hours and await written authorization before proceeding." The exclusions list is as important as the inclusions list. What site cleanup, equipment staging, permit fees, insurance, or punch list participation is — and isn't — covered by the sub's price?

The cost of a scope gap isn't always dramatic. Sometimes it's a $500 bill for cleanup that nobody thought about. Sometimes it's a $15,000 argument over whether removing temp protections was included. The cost is always proportional to how much work got done before the gap was identified.

2. Back-Charge Clause Isn't Enforceable

Most builder agreements have a back-charge clause — but it's written in a way that makes it unenforceable. A clause that says "contractor reserves the right to back-charge subcontractor for defective or incomplete work" is vague. It says nothing about what happens when the sub doesn't pay the back-charge.

An enforceable back-charge clause specifies: the specific work not performed, the cost to cure, a deadline for the sub to cure (typically 5-10 business days), and a statement that if not cured, the contractor will hire a third party and deduct the cost from the next sub payment. It also requires the contractor to provide written notice within a specified timeframe — often 30 days of discovering the defect. Without those elements, the back-charge is a polite suggestion.

3. Insurance Requirements Not Verified

Most builder agreements require the sub to maintain general liability and workers' comp. Most builders never check whether those requirements are actually met. A certificate of insurance pulled before mobilization — with your company listed as additional insured on the general liability policy — is the verification. If your agreement has an insurance requirement and nobody is pulling certificates, the requirement is theater.

The fix is procedural: insurance certificate review is part of the sub onboarding checklist. Pull certificates 3-5 business days before the sub mobilizes to the site. Verify the coverage amounts meet your requirements. Verify your company is listed as additional insured. File the certificates in a dedicated sub insurance binder. If a sub shows up without verified insurance, they don't mobilize.

4. Payment Terms That Tie You to Client Cash Flow

The most common payment term I see in builder agreements: "contractor shall pay subcontractor within 10 days of receipt of payment from the owner." This language is deeply unfavorable to builders. It means your sub's payment is contingent on your client's payment — and if your client is 30 days behind, your sub's payment is 30 days behind. You've now created a cash flow problem that compounds.

The correct language: "contractor shall pay subcontractor within 15 days of the date of subcontractor's invoice." Fixed payment terms, disconnected from client payment. Your sub's invoice date starts the clock. Whether or not you've been paid is a separate cash flow problem that shouldn't be transferred to your sub.

5. No Change Order Protocol

Most sub agreements don't specify when a change order is required, what it should include, and how approval happens. Without this language, subs do the work first and quote the price afterward — and you've given up all leverage on pricing. The agreement should specify: any work outside the original scope requires a written change order before the work is performed. Change orders must be submitted within 3 business days of the scope change identification. Approval requires written authorization from the contractor. Work performed without prior written authorization may not be billed.

The Subcontractor Agreement Review Checklist

Here's the checklist I use with every agreement before it's signed. Each item is a gap if the answer is "no" or "I don't know."

Scope Section:

• Does the scope section include a specific exclusions list, not just an inclusions list?
• Does the sub agree to participate in punch list and closeout activities?
• Does the scope section define who is responsible for site cleanup during and after the sub's work?
• Does the scope section define the sub's schedule obligations — start date, duration, milestones?

Back-Charge Clause:

• Does the back-charge clause specify a deadline for the sub to cure defective work?
• Does it specify the contractor's right to hire a third party and deduct from the next payment if the sub doesn't cure?
• Does it specify a written notice requirement within a defined timeframe?

Insurance:

• Does the agreement specify minimum coverage amounts for general liability and workers' comp?
• Does it require the contractor to be named as additional insured on the sub's general liability policy?
• Is there a certificate of insurance review process before mobilization?

Payment Terms:

• Are payment terms fixed — a specific number of days from invoice date?
• Does the agreement prohibit contingent payment language ("paid when contractor is paid")?
• Does the agreement specify retainage percentage and release terms?

Change Order Protocol:

• Does the agreement specify that work outside the scope requires prior written authorization?
• Does it specify a submission timeline for change orders (e.g., within 3 business days)?
• Does it specify that work performed without prior authorization may not be billed?

Indemnification Language — The Clause That's Almost Always Wrong

One more gap that deserves its own section: indemnification language. Most subcontract agreements — both builder-written and sub-provided — have indemnification clauses that are either backwards, overbroad, or both.

The correct structure is mutual indemnification: each party indemnifies the other against claims arising from that party's own negligence or breach. The sub is responsible for their own mistakes. The builder is responsible for their own mistakes. Neither party should be indemnifying the other for the indemnifying party's own negligence — that's backwards.

The red flag to watch for: language that indemnifies the builder for "any and all claims" arising from the sub's work, including claims arising from the builder's own negligence. That's overbroad and legally questionable in most states. A mutual indemnification clause with a specific carve-out for the indemnifying party's own negligence is the standard that protects both parties.

If you're using a sub-provided agreement and you're not sure about the indemnification language, have a construction attorney review it. One bad indemnification clause can expose you to liability for a sub's negligence in a way that your insurance may or may not cover. That's worth a $300 attorney review before you sign.

Frequently Asked Questions