A vague subcontractor agreement doesn't just create paperwork problems — it creates cash problems, schedule problems, and courtroom problems. Missed scope language costs GCs an average of 3–5% of project value in rework and back-and-forth disputes, according to field rework research from the Construction Industry Institute. Lien exposure from unpaid subs can cloud a project's title and stall owner payments for months. And when a sub walks off the job, the difference between recovering your costs and absorbing them often comes down to four or five sentences in a contract you signed six months ago.
This isn't a template download page. It's a field guide for GCs who want to understand what a subcontractor agreement template actually needs to do — and how to build a process around it that holds up when things go sideways.
What a Subcontractor Agreement Actually Needs to Do
Most GCs think of the sub agreement as a legal formality — something the attorney drafted once, lives in a folder, and gets emailed out with every award letter. That framing is expensive. A well-built sub contract is a project management tool first. It defines who does what, who pays for what when it goes wrong, and what the sequence of money looks like from start to final lien waiver.
A solid agreement has to perform four jobs simultaneously: define scope with enough specificity to survive a dispute, allocate risk between the GC and sub in a way that's enforceable in your state, control cash flow through payment milestones and retainage, and give you legal standing to terminate, back-charge, or pursue bond claims when a sub defaults.
If your current template doesn't do all four, it's doing some of the work and leaving the rest to luck.
The difference between a template and a contract that holds up
Generic PDF templates from legal sites are written to be broadly applicable — which means they're specifically applicable to almost nothing. Construction disputes turn on trade-specific language: whether the electrical sub's scope included conduit above the ceiling, whether the concrete sub was responsible for saw-cutting or just flatwork, whether "substantial completion" was defined by the prime contract or by the sub's own judgment.
State lien law references matter enormously. A lien waiver clause that doesn't reference your state's statutory form requirements may be unenforceable. Flow-down clauses that don't actually incorporate the prime contract by reference leave you exposed when the owner's contract has dispute resolution or indemnification language that contradicts what your sub signed.
What eForms and standard PDF templates get right (and where they stop short)
Free templates from sites like eForms do cover the basics — parties, scope description, payment terms, termination rights. For a GC doing occasional small residential work, that may be enough. But for commercial, multi-trade, or publicly funded projects, they fall short in three consistent ways.
First, they don't integrate subcontractor prequalification data — so there's no mechanism to translate what you learned about a sub's bonding capacity or EMR into specific contract terms. Second, they treat scope as a text field rather than a structured attachment tied to drawing numbers and spec sections. Third, payment terms are static — there's no provision for milestone-based triggers tied to the project schedule. Those gaps are where disputes are born.
The Core Clauses Every Subcontractor Contract Template Must Include
You can negotiate a lot of things in a sub agreement. These aren't negotiable.
Scope of work: the clause that prevents 80% of disputes
The scope of work section is where most subcontractor agreements fail — not because it's missing, but because it's too vague to mean anything. Writing "furnish and install all HVAC work per plans and specs" sounds complete. It isn't. A subcontractor scope of work template that holds up in a dispute will reference specific drawing sheets (M-101 through M-408), applicable specification sections (Division 23), and explicit exclusions — what the sub is *not* responsible for, including coordination with other trades, temporary heat, or equipment startup.
Attach the scope as Exhibit A. Make the exhibit date-stamped and tied to a specific drawing revision. When the drawings change, issue a revised exhibit with a change order — not a verbal conversation.
Subcontractor payment schedule construction: milestone vs. percentage-complete
The choice between milestone-based and percentage-complete payment structures depends on how you can verify progress. Percentage-complete works on repetitive scopes — framing, drywall — where a site visit or superintendent sign-off can confirm 60% done. Milestone-based works better for MEP rough-in, where "underground complete" or "above-ceiling inspection passed" is a binary, verifiable trigger.
The pay-when-paid vs. pay-if-paid distinction is more consequential than most GCs realize. Pay-when-paid clauses (the GC pays the sub within X days of receiving payment from the owner) are enforceable in most states but create timing risk for subs. Pay-if-paid clauses (the GC only pays the sub *if* the owner pays the GC) are treated as a full risk transfer — and several states, including California and New York, have restricted or prohibited them entirely. Know your state's position before you paste that clause in.
For more on structuring payment terms, see our guide to subcontractor payment schedules.
Flow-down clauses, indemnification, and insurance minimums
Your prime contract with the owner creates obligations that need to flow down to the subs performing that work. A flow-down clause should incorporate the prime contract by reference and specify that the sub is bound by all terms applicable to their scope — including dispute resolution, change order procedures, and schedule requirements.
Indemnification language should be broad enough to protect you from third-party claims arising from the sub's work, but check your state's anti-indemnity statute first. Several states prohibit indemnifying a party for their own negligence. On insurance minimums, a reasonable baseline for a mid-size commercial project ($5M–$20M range) is $1M per occurrence / $2M aggregate for general liability, statutory workers' compensation, and a $5M umbrella. Adjust based on project risk — a roofing sub on a 10-story building warrants higher limits than a landscaping sub on a parking lot.
Lien waiver construction: conditional vs. unconditional, and when to require each
Lien waivers are your primary tool for protecting the owner's title — and your payment position — as money moves down the chain. The mechanics are straightforward but frequently misapplied.
Require a conditional lien waiver (waiver effective only upon receipt of the payment being made) with every payment application. Upon final payment, require an unconditional lien waiver — one that releases all lien rights through the date of final payment, with no conditions attached. Many states have statutory lien waiver forms that must be used for the waiver to be valid. In California, for example, Civil Code §8132–8138 specifies the exact language required. Using a non-compliant form means the waiver may not release the lien rights you thought it did.
Subcontractor Prequalification: The Step That Happens Before the Contract
A strong subcontractor agreement starts before anyone opens a contract template. The prequal process is where you learn whether a sub can actually perform — financially, operationally, and safely — before you hand them $800,000 worth of mechanical work.
What a subcontractor prequalification form free of charge should still capture
Even a basic subcontractor prequalification form free of cost should collect the following: current EMR (experience modification rate), bonding capacity and current bonding availability, active license status in the project state, three verifiable project references from the past three years, current backlog relative to annual revenue, and any active litigation or claims history.
An EMR above 1.0 is a red flag on most commercial projects — it signals a safety record worse than the industry average. A sub carrying $10M in bonding capacity but $9.5M already committed is effectively unbondable for your project. Skipping prequal is one of the leading causes of subcontractor default construction claims, because GCs award work based on price and relationship without ever verifying capacity.
How to connect prequal data to contract terms
Prequal findings shouldn't just live in a file — they should shape the contract you issue. A sub with a 1.2 EMR should trigger a site-specific safety plan requirement as a contract exhibit. A sub with limited bonding capacity might warrant 10% retainage instead of 5%, or a payment and performance bond requirement on scopes above a certain dollar threshold.
One GC we spoke with on a $14M school renovation project in the Mid-Atlantic put it plainly: "We had a mechanical sub who looked fine on paper until we ran prequal and saw they had $6M in open claims from two prior jobs. We still used them because they were the only qualified bidder, but we bumped retention to 15% and required a performance bond. Saved us when they walked off in month four."
That's the value of connecting prequal data to contract terms rather than treating them as separate processes.
Handling Subcontractor Default: What Your Agreement Must Say Before It Happens
Subcontractor default construction scenarios are more common than most GCs want to admit. According to NASBP guidance on subcontract bonding, subcontractor defaults are among the leading drivers of contractor bond claims. When a sub stops performing, your contract language — not your relationship, not your verbal agreements — determines whether you recover your costs or absorb them.
Cure periods and notice requirements
Standard cure period language gives a defaulting sub 48–72 hours written notice to cure a specific, documented deficiency before the GC can terminate for cause. The notice must be written — email qualifies in most states, but check your contract's notice provision. Verbal warnings to a foreman don't create legal standing for termination, even if the super has been complaining for three weeks.
Document the default trail from the first sign of trouble: daily reports noting incomplete work, written notices requesting a corrective action plan, and any responses (or non-responses) from the sub's management. That paper trail is what supports your termination letter and any subsequent bond claim.
Back-charges, completion costs, and withholding rights
Your agreement needs explicit language authorizing the GC to withhold funds from the defaulting sub's contract balance and apply them to completion costs. Without that language, a sub can argue you had no right to withhold — and in some states, wrongful withholding of payment creates its own liability.
Structure the back-charge provision to cover direct completion costs (hiring a replacement sub), re-work expenses caused by the defaulting sub's defective work, and schedule impact damages if the default pushed the project past a milestone. If the sub is bonded, the back-charge documentation also becomes the basis for your bond claim — so the more detailed your cost tracking, the stronger your recovery position.
Building Your Subcontractor Agreement Template: A Section-by-Section Checklist
A complete subcontractor contract template construction should move in a logical sequence that mirrors how the project actually unfolds. Here's how to build one from scratch.
Recitals, definitions, and contract documents hierarchy
Start with recitals that identify the parties, the project, and the prime contract. Then establish a definitions section that gives precise meaning to terms like "substantial completion," "change order," "contract documents," and "work." Vague definitions are where disputes start.
The contract documents hierarchy section is the one most free templates omit entirely — and it's one of the most consequential. Establish explicitly which documents govern the sub's work and in what order of precedence: typically the subcontract agreement itself, then the prime contract, then drawings, then specifications, then addenda, then RFIs. When documents conflict — and they will — the hierarchy determines which one wins.
Schedule, delays, and force majeure language
Write schedule provisions that protect your float. The sub should be required to complete their work within the GC's master schedule, not on an independent timeline. Include a "time is of the essence" clause and specify that the sub must provide written notice of any anticipated delay within 48 hours of the triggering event — weather, owner-caused delay, or otherwise. Failure to provide timely written notice should waive the sub's right to a time extension.
Force majeure language should be narrow. A clause that excuses delays for "any circumstances beyond the sub's control" is too broad — it can swallow schedule accountability entirely. Limit force majeure to genuinely unforeseeable events (declared emergencies, acts of government) and exclude foreseeable weather, labor shortages, and supply chain issues that a competent contractor should have priced into their bid.
Dispute resolution: arbitration, litigation, and jurisdiction
The choice between arbitration and litigation is a real strategic decision, not just a boilerplate selection. Arbitration is faster and more private; litigation creates a public record and allows for broader discovery. For most GC-sub disputes — scope, payment, back-charges — arbitration through the American Arbitration Association's Construction Industry Rules is a reasonable default.
Include a tiered dispute resolution process: mandatory negotiation between project executives first (10-day window), then mediation (30-day window), then arbitration if unresolved. This keeps most disputes off the courthouse steps and preserves the working relationship long enough to finish the project. For multi-state GCs, jurisdiction and venue clauses matter — specify the state and county where disputes will be resolved, or you may find yourself defending a claim in a jurisdiction where you have no relationships and your attorney isn't licensed.
Frequently Asked Questions
Is a verbal subcontractor agreement legally binding?
In most states, verbal contracts for construction work can technically be enforceable — but proving what was agreed to is nearly impossible once a dispute arises. Without a written record of scope, price, and payment terms, you're left arguing over competing memories. Courts and arbitrators default to documented evidence. A signed written contract is the only protection that actually holds up, and for any project over $500, the risk of relying on a handshake is not worth taking.
What's the difference between a subcontractor agreement and an independent contractor agreement?
The legal distinction matters more than most GCs realize. A subcontractor agreement governs a business-to-business relationship where the sub typically has their own crew, equipment, and license. An independent contractor agreement is often used for individual workers — and the IRS applies a multi-factor test to determine whether that individual is actually an employee. Misclassifying an employee as an independent contractor exposes you to back payroll taxes, penalties, and potential workers' compensation liability. If the person works exclusively for you, on your schedule, with your tools, the IRS may reclassify them regardless of what the contract says.
How do I handle scope changes after the subcontractor agreement is signed?
Every change to the sub's scope — additions, deletions, substitutions — needs a written change order signed by both parties before the work is performed. Your base agreement should include a change order clause that specifies the process: the GC issues a written change order request, the sub responds with pricing within a defined window (typically 5–7 days), and no changed work is authorized without a fully executed change order. Verbal change authorizations create disputes about price and scope that are almost impossible to resolve cleanly. A sub who starts extra work without a signed change order may have limited ability to recover that cost — but so do you if you try to back-charge for scope you verbally authorized.
What happens if a subcontractor refuses to sign the agreement?
First, find out why. Most refusals are about specific terms — payment timing, retainage rate, indemnification language — and are negotiable. If a sub objects to your entire contract structure, that's a signal worth taking seriously. If you can't reach agreement on terms and the sub starts work anyway, document everything: the scope they're performing, the price agreed to verbally, and any written communications. In some states, a sub who performs work with the GC's knowledge may be able to claim quantum meruit (reasonable value of services) even without a signed contract. Don't let work start without a signed agreement if you can help it — and if you can't, at minimum get the scope and price confirmed in writing via email.
Do I need a separate lien waiver form or can I include it in the contract?
Lien waivers need to be separate documents executed at each payment event — not embedded in the base contract. The reason is practical and legal: a lien waiver releases rights through a specific date and for a specific payment amount, both of which are unknown when the base contract is signed. Many states require statutory lien waiver forms with specific language — California, Texas, and Arizona all have mandatory form requirements. Using a non-compliant waiver form can render the waiver unenforceable, leaving the sub's lien rights intact even after you've paid. Keep a state-specific conditional waiver and unconditional waiver template in your payment application package and require execution with every draw.
How much retainage should I hold on a subcontractor?
The standard range is 5–10% of each progress payment, held until substantial completion or final acceptance of the sub's scope. Your sub agreement's retainage language should mirror the prime contract terms — if the owner is holding 5% on you, holding 10% on subs creates a cash flow mismatch that can strain sub performance. Many GCs reduce retainage to 5% or release it entirely at substantial completion for subs who have performed without issues, using that flexibility as a relationship tool. Some states have enacted retainage caps on public projects — check your state's prompt payment and retainage statutes before setting terms.
Putting It to Work: From Template to Executed Agreement
Having a solid base template is step one. The real work is in the project-specific execution — attaching the right scope exhibit, setting payment milestones that match the schedule, incorporating prequal findings into contract terms, and getting a fully executed agreement back before the sub mobilizes.
That workflow breaks down most often at the scope attachment stage. Estimators finish the bid, the sub gets awarded, and the contract goes out with a generic scope description because nobody has time to write a proper Exhibit A from scratch. That's the gap where disputes live.
AI-assisted platforms are starting to close that gap. Bidi, for example, is built around the bid-to-contract handoff — helping GCs generate scope attachments from takeoff data, level sub bids against a structured scope, and move from awarded bid to executed agreement without the manual re-entry that slows most teams down. The subcontractor agreement template is only as good as the scope document attached to it, and that scope document is only as good as the takeoff behind it.
A subcontractor agreement template gives you a starting point. The prequal process, the scope attachment, the payment structure, and the default provisions are what turn that starting point into a contract that actually protects you. Get those four things right on every project, and most disputes either don't happen or resolve quickly when they do.
If you want to see how the bid-to-contract handoff actually works — scope attachments generated from takeoff data, leveled bids, and executed agreements before the sub mobilizes — book a 20-minute demo and bring your next project.
*Reviewed by Weston Burnett, Co-Founder and CTO of Bidi Contracting.*
