What is a subcontractor agreement? The clauses that actually matter in 2026

A subcontractor agreement is the document that decides who pays what to whom, when, and under what conditions. Most disputes on a construction job trace back to a clause that either wasn't there or wasn't read.

The short definition. A subcontractor agreement is a written contract between a general contractor and a subcontractor that fixes the scope of work, the price, the schedule, the insurance, the indemnity, and the payment flow (including lien waivers) for a specific portion of a larger project. It protects the GC from getting sued by the sub. It protects the sub from getting stiffed by the GC. It protects the owner from getting hit with a mechanic's lien three months after closing.

This post walks through what each clause does, where the language usually goes wrong, and the one section most GCs underestimate: how the lien waiver obligation lives inside the subcontract itself.

Why the subcontractor agreement matters more than the prime contract (for subs)

The prime contract is between the owner and the GC. As a subcontractor, you don't sign it. You sign the subcontract, and the subcontract decides your fate.

A 2022 American Subcontractors Association member survey found that roughly 70% of payment disputes between subs and GCs come down to language in the subcontract that one side didn't read carefully. Most of those disputes never make it to a courtroom. They just sit on a desk for 90 days while someone's payroll waits.

For the GC, a well-drafted subcontract does three things at once. It fixes the price (so a sub can't claim extras for work that was already in scope). It pushes risk down to the right party (so the owner doesn't pull the GC into a lawsuit over a sub's negligence). It locks in the lien waiver workflow (so closeout doesn't turn into a sub-by-sub negotiation).

For the sub, the subcontract is the only thing keeping the GC honest about payment timing. Everything you'll fight about later is in that document. Read it before you sign.

The eight clauses every subcontractor agreement needs

Different states use different templates. The structure is roughly the same.

1. Scope of work

The scope is the most-litigated section of any subcontract. It defines exactly what the sub is on the hook to deliver.

A good scope is specific enough that two strangers reading it would agree on what counts as "done." Bad scopes use phrases like "as required" or "industry standard" without naming the standard. The fix is references. Reference the drawings by sheet number, the spec sections by number, and any addenda by date.

What to include:

• The portion of work (e.g., "all rough electrical and final trim for the second-floor units, per E-001 through E-007, addenda 1 and 2")
• Materials supplied by the sub vs by the GC
• Exclusions (the work that is explicitly not the sub's responsibility)
• Permit, inspection, and testing responsibilities

If the sub is performing work in a state with statutory lien waiver requirements (California, Texas, Florida, Arizona, and eight others), the scope often references which state's law governs.

2. Payment terms

The payment clause names the dollar amount, the schedule, and the conditions for getting paid. This is where every horror story begins.

The four sub-clauses that matter:

• Contract price. Lump sum or unit price. State the number and what it covers.
• Progress payment schedule. Monthly is standard. Bi-weekly happens on smaller jobs.
• Retention (also called retainage). A percentage withheld from each progress payment, released at closeout. 5–10% is typical.
• Final payment trigger. What has to happen for the final check to be released (punch list closed, permits closed, unconditional final lien waiver signed).

The clause to watch for is "pay-if-paid." That language makes the GC's payment to the sub contingent on the GC getting paid by the owner. If the owner stiffs the GC, the sub eats the loss. A few states (California and New York among them) restrict pay-if-paid by statute; most don't. "Pay-when-paid" is friendlier — it sets a reasonable timing expectation but doesn't shift the credit risk to the sub. Know which one you're signing.

3. Schedule and milestones

The schedule fixes start date, substantial completion date, and any milestone gates in between. Liquidated damages for late completion live here too. Liquidated damages are pre-agreed dollar amounts per day of delay; they exist because actual damages in a construction delay are hard to prove and expensive to litigate.

A useful sub-clause: time extension procedure. If the sub hits a delay caused by weather, the GC, or another trade, the contract should say how to claim a time extension (usually written notice within X days). Miss the notice window and you owe the liquidated damages even though the delay wasn't your fault.

4. Insurance and additional insured

The insurance clause names the policies the sub has to carry and the limits.

Standard floors for U.S. subs:

• Commercial General Liability (CGL): $1M per occurrence, $2M aggregate
• Workers' Compensation: per state statute
• Auto liability: $1M combined single limit if the sub drives on site
• Umbrella: $1M–$5M depending on job size

The clause should also require the sub to name the GC (and often the owner) as additional insured on the CGL policy. That changes who can claim against the sub's insurance when a third party gets hurt. The sub's certificate of insurance has to be on file before the sub is allowed on site, and the certificate has to renew automatically when the policy renews.

5. Indemnification

Indemnity is the clause where the sub agrees to defend and pay for losses caused by the sub's work. The GC's lawyer drafted it. Read it carefully.

The fair version is mutual (each party indemnifies the other for their own acts) and excludes the indemnified party's own negligence. Anything broader pushes risk to the sub for things the sub didn't cause. Watch for phrases like "in whole or in part" and "directly or indirectly" — those expand the sub's liability past what most insurance will cover.

Anti-indemnity statutes in 40+ states limit how broadly a GC can shift risk to a sub. The clause that violates state law isn't enforceable, but you don't want to litigate that mid-project.

6. Change orders

A change order is a written amendment that changes the scope, price, or schedule. The change order clause says how those amendments happen.

The single most important phrase: no verbal change orders. If the GC's super says "just do it, we'll work it out later," the sub has no contractual basis to charge for the extra work. The clause should require written approval before the sub starts the changed work, with a specific dollar amount and time impact.

Verbal change orders are the largest single source of payment disputes between GCs and subs. Don't accept them. Don't issue them.

7. Lien waiver requirements (the one most GCs underestimate)

This is where the subcontract ties into the day-to-day payment flow.

A well-drafted subcontract names four things about the lien waiver:

• The form. Statutory state form (where required) or a specific waiver template attached as an exhibit. If you're working in California, the contract references Civil Code §8132–§8138. In Texas, it references the statutory forms in Chapter 53. Generic forms are not enforceable in 12 states.
• The timing. Conditional progress waiver with each pay application, unconditional progress waiver after the payment clears. Conditional final waiver with the final pay application, unconditional final waiver after the final check clears. We covered why this order matters in should I sign a lien waiver before payment.
• Lower-tier coverage. The sub agrees to deliver waivers from its own sub-subs and suppliers. Without that flow-down, the GC can pay the sub, get a waiver from the sub, and still get hit with a lien from the sub-sub the GC has never met.
• The penalty for non-delivery. No waiver, no payment. Standard contractual remedy.

Without this clause, every payment turns into a negotiation about which form the sub will sign and whether the sub-subs are covered. With the clause, the workflow runs itself. This is the wedge our subcontractor compliance software was built around: send the right form for the state and the phase, get it signed on a phone, file the PDF in the project folder, release the payment. We also break down the four-form framework for subs in our subcontractor lien waiver guide and release of lien from subcontractor.

8. Termination

The termination clause says how either party can end the contract early.

Two standard flavors:

• Termination for cause. The other party breached (didn't pay, didn't perform, became insolvent). Usually requires written notice and a cure period (5–30 days).
• Termination for convenience. The GC can fire the sub for any reason, paying for work completed plus a small markup. Subs almost never get termination for convenience. GCs usually do.

The clause should also cover what happens to materials on site, retention, and final pay calculation if the contract ends early.

How a subcontractor agreement differs from an independent contractor agreement

A subcontractor agreement is a specific kind of independent contractor agreement used inside a construction project. The differences come down to three things.

Hierarchy. A subcontractor reports to a general contractor, who reports to the owner. An independent contractor usually reports directly to the client.

Flow-down terms. The subcontract usually incorporates parts of the prime contract by reference. If the prime contract has a 60-day payment window, the subcontract often inherits it. Other industries don't have this layered structure.

Statutory lien rights. Subcontractors on a construction project have a statutory right to file a mechanic's lien on the property if they aren't paid. Independent contractors in most other industries don't have that lever. The lien waiver clause in a subcontract exists because that lever exists.

The clauses that look minor and aren't

A short list of the fine-print items that bite people:

• Dispute resolution. Arbitration vs litigation. Arbitration is faster and cheaper for small claims, but it's binding. Some GCs require arbitration in a specific city which is inconvenient on purpose.
• Choice of law. Which state's law governs. Matters when the GC is in one state and the project is in another.
• Notice provisions. How and where formal notices have to be sent (email, certified mail, fax in some templates from 1998 that nobody updated). Miss the notice format and your claim is procedurally dead.
• Warranty period. How long after substantial completion the sub is on the hook for callbacks. 1 year is standard. 2 years happens on commercial work.
• Severability. If one clause is unenforceable, the rest of the contract still stands. Boilerplate, but useful when something gets struck.

A two-minute mental checklist before you sign

Before any sub signs the agreement, run through this:

1. Is the scope specific enough that I know what's in and what's out?
2. Is the payment schedule named in days, not in vague language?
3. Is there a pay-if-paid clause? If so, am I comfortable with the credit risk?
4. Does the indemnity exclude the GC's own negligence?
5. Is the lien waiver form named, or am I going to negotiate it every month?
6. Are change orders required to be in writing?
7. What's the termination clause? Can I be fired for convenience?

If you can't answer all seven cleanly, you're not done reading.

How LienDone fits into a subcontract

When the lien waiver clause is well-drafted, the rest is workflow. Pick the state, pick the phase, send the link. The sub signs on a phone in two minutes. The PDF lands in the project folder with a timestamp. Payment releases. Repeat next month.

That's the wedge. Most of the pain in construction payment isn't legal, it's logistical: chasing signatures, hunting for the right form, asking which California waiver applies this month. A subcontract that names the lien waiver workflow, and software that runs it, turns a five-day chase into a five-minute task. Subcontractor payment software handles the rest of the flow once the waiver is signed.

The takeaway

A subcontractor agreement is eight or nine clauses long and decides almost everything that will go right or wrong on the job. Scope, price, insurance, indemnity, change orders, termination, dispute resolution. And the one most templates treat as an afterthought: the lien waiver flow.

Get the lien waiver clause right and the rest of the payment cycle runs itself. Get it wrong and you're negotiating a form every month while payroll waits.

FAQ

What is a subcontractor agreement in plain English?

It's the contract between a general contractor and a subcontractor that fixes the scope of work, the price, the schedule, the insurance, and how lien waivers move with each payment.

Is a subcontractor agreement legally required?

A written one isn't required in every state, but it's required in practice. Most insurers, lenders, and owners won't approve a project without one.

What's the difference between a subcontractor agreement and an independent contractor agreement?

A subcontractor agreement is a kind of independent contractor agreement used inside a construction project, with a reporting structure to the GC and statutory lien rights baked in.

Does the subcontractor agreement include the lien waiver?

It should. A well-drafted subcontract names the lien waiver form, requires a conditional waiver before each payment, and requires an unconditional waiver after the money clears.

Who writes the subcontractor agreement?

The general contractor almost always drafts it. The sub reviews, redlines, and refuses. If the GC won't negotiate any terms, that's a sign of how the rest of the job will go.

Can a subcontractor agreement be amended mid-project?

Yes, through a written change order. Verbal change orders are the largest single source of payment disputes in construction.