CON 102 · Foundation · Foundations track · 11 min read

Subcontract

The agreement by which a general contractor delegates a portion of the work to a trade contractor — and the instrument that must faithfully flow down the prime's obligations.

Definition — what it is

A subcontract is a binding agreement between a general contractor and a specialty (trade) contractor under which the sub performs a defined portion of the prime scope for a defined price. It is a lower-tier document in the contractual hierarchy: it can grant the sub no more rights than the general contractor holds under the prime, and it should flow down the prime's material obligations so the GC is not left owing the owner something it cannot demand of the responsible trade. It is typically built from a standard form (AIA A401, ConsensusDocs 750, or a GC's proprietary form) plus an exhibit defining the specific scope, price, and schedule. A subcontract is not simply a smaller prime contract — its defining feature is the incorporation-by-reference and flow-down clauses that bind the sub to the prime terms, and its scope exhibit is where most disputes are actually decided.

Also known as: Trade Contract, Sub Agreement, Lower-Tier Contract

Why it matters — what it protects

Subcontracts are where the general contractor transfers risk, and gaps in transfer become the GC's own liability. If the prime obligates the GC to name the owner as additional insured or to waive consequential damages, and the subcontract does not push that same obligation to the responsible trade, the GC absorbs the difference. The flow-down and incorporation clauses are the mechanism, and they only work if they are complete.

The scope exhibit determines margin. Ambiguity about who furnishes versus installs, who provides temporary power, who patches after another trade, or where one trade's work ends and the next begins is the single largest source of backcharges and change-order disputes. The clarity of the scope description often matters more than the price.

Subcontracts govern the payment chain that keeps trades solvent. The pay-when-paid or pay-if-paid provision, the retainage percentage, the lien-waiver requirements at each draw, and the conditional-versus-unconditional waiver logic all determine whether a sub gets paid and whether the GC gets clean title. Payment friction at this tier stops work faster than almost anything else.

They are the front line of default and delay risk. Subcontractor default is a leading cause of project distress, and the subcontract's default, cure, supplementation, and termination clauses — along with any subcontractor performance bond or subguard-type default insurance — determine how expensive and how slow a recovery will be. The terms written at buyout decide the cost of a failure nobody expects.

Lifecycle — how it moves

  1. Buyout and scope definition

    After award, the GC negotiates each trade package. The critical work is writing an unambiguous scope exhibit and reconciling the sub's bid inclusions and exclusions against the design so no scope falls between trades.

  2. Flow-down and terms negotiation

    Prime obligations are pushed down — insurance, indemnity, schedule, notice, warranty, safety, lien-waiver requirements. Sophisticated subs push back on the harshest terms, and the tradeoffs are settled here.

  3. Compliance verification

    Before execution, the GC verifies the sub's insurance certificate, bonds if required, W-9, business license, and prequalification. These are frequently conditions precedent to any payment.

  4. Execution and mobilization

    Both parties sign, the sub mobilizes, and the schedule obligation begins. A subcontract signed after the sub is already working on-site is common and dangerous, because leverage over terms is gone once the trade is embedded.

  5. Performance and administration

    The sub performs, submits pay applications and lien waivers, responds to RFIs and submittals, and is tracked against schedule. Daily coordination and backcharge exposure live here.

  6. Changes

    Scope changes are handled through subcontract change orders, ideally mirroring the change the GC secured from the owner so the GC is not paying out more than it collects on the same change.

  7. Default and cure (if triggered)

    If the sub falls behind or performs deficiently, the GC issues notice to cure per the contract, and may supplement the workforce or terminate. How cleanly this goes depends entirely on the notice and default language.

  8. Closeout and final payment

    Punch is completed, warranties and O&M data are delivered, final unconditional lien waivers are exchanged, retainage is released, and the subcontract is closed. Unreleased retainage and missing waivers are the usual holdups.

Anatomy — the data it carries

Parties and tier
The GC and the trade contractor, and the sub's tier. Lower-tier subs (sub-subs) create additional lien and preliminary-notice exposure the GC must track.
Scope of work exhibit
The specific inclusions, exclusions, and furnish/install split. The most disputed document in the entire agreement.
Subcontract sum
Lump sum, unit price, or cost-plus. Should reconcile to the trade's line in the GC's schedule of values.
Schedule obligations
Start, milestones, duration, and any liquidated-damages or backcharge exposure for delay. Should be consistent with the prime's schedule.
Incorporation-by-reference clause
Binds the sub to the prime contract terms as if the sub were the contractor to the extent applicable. The engine of flow-down.
Flow-down obligations
Insurance, indemnity, notice, warranty, and safety requirements pushed from the prime. Gaps here become GC liability.
Payment terms
Pay-when-paid or pay-if-paid, application cycle, and payment window. Determines the sub's cash position and the GC's exposure.
Retainage
Percentage withheld and release conditions. Often mirrors the prime, but sometimes the GC withholds more than the owner does — a point of contention.
Lien-waiver requirements
Conditional waivers with each progress payment and unconditional waivers on payment, including lower-tier waivers. Protects the GC's title to payment.
Indemnity and insurance
The sub's obligation to defend and hold the GC and owner harmless, and to carry and evidence required coverage with additional-insured status.
Default, cure, and termination
Notice-to-cure period, supplementation rights, termination for cause and convenience, and the compensation each triggers.
Backcharge provisions
The GC's right to charge the sub for cleanup, damage to other work, or costs the sub caused. A frequent source of end-of-job disputes.
Warranty and closeout deliverables
Warranty duration and start, plus O&M manuals, as-builts, and attic stock the sub must deliver at closeout.

Failure modes — how it breaks

Ambiguous scope split between trades

Two subcontracts each assume the other covers a gray-area item — flashing, fireproofing patch, temporary protection. The item goes unbuilt or gets double-charged, and the GC eats the difference or fights two subs at once.

Working before signing

The sub is on-site and productive before the subcontract is executed. When a term is contested, the GC has no leverage: pulling the trade would blow the schedule, so the sub's version of the deal often prevails.

Incomplete flow-down

The prime requires a five-year roof warranty and a specific additional-insured endorsement; the subcontract says two years and is silent on the endorsement. The GC owes the owner what it never secured from the roofer.

Sub change orders lagging owner change orders

The GC executes a change with a sub before the owner approves the matching change up top, or at a higher price than it will collect. The GC funds the delta out of its own margin.

Missing lower-tier lien waivers

The sub is paid but its own suppliers and sub-subs are not, and they file liens or bond claims against the project. The GC discovers it paid once but must effectively pay twice to clear title.

Retainage mismatch

The GC withholds 10 percent from subs while the owner reduces prime retainage to 5 percent at 50 percent completion. The GC is holding trade cash it is no longer entitled to hold, straining relationships and inviting claims.

Weak default and cure language

A failing sub cannot be removed cleanly because the notice-to-cure and supplementation clauses are vague. Termination becomes a legal fight while the schedule bleeds, when tight language would have allowed swift supplementation.

Metrics — how it is measured

Buyout completeness

Share of trade packages with fully executed subcontracts before mobilization. Low completeness signals leverage lost and scope risk carried.

Flow-down coverage

Percentage of prime obligations correctly reflected in each subcontract. Direct measure of residual GC exposure.

Scope-gap incidents

Count of items that fell between trade scopes and had to be reassigned or absorbed. Reveals scope-exhibit quality.

Sub change-order alignment

Share of subcontract changes matched to a corresponding owner change in scope, price, and timing. Protects GC margin on changes.

Lien-waiver collection rate

Percentage of required conditional and unconditional waivers, including lower-tier, collected at each draw. Protects payment title.

Retainage aging by sub

Dollars and days of retainage held past the contractual release condition. Ties to relationships and to closeout speed.

Default and supplementation rate

Frequency of notices to cure, supplementation, and terminations. A leading indicator of prequalification and buyout quality.

The AI shift — what actually changes

Conversational

You can interrogate a subcontract in plain language: does this sub's scope include temporary protection at the elevator openings, what warranty duration did we obligate them to, does their payment clause make owner payment a precondition, and how does their scope line up against the drawings — with the answer tied to the specific exhibit and clause.

Generative

Scope exhibits and flow-down riders are drafted and stress-tested, not composed from scratch. Given the trade's bid inclusions and exclusions and the prime terms, a model drafts a scope exhibit that closes the common gray-area gaps and a flow-down rider that mirrors the prime's insurance, indemnity, notice, and warranty obligations for a reviewer to finalize.

Orchestrated

The subcontract is checked against everything around it: its scope reconciled against the drawings and against adjacent trade scopes to catch gaps and overlaps, its flow-down compared clause-by-clause against the prime, its insurance requirements matched against the sub's certificate on file, and its change orders aligned against the corresponding owner changes.

Autonomous

The buyout and compliance loop runs continuously — verifying that each executing sub has a current COI, valid W-9, and required bonds; flagging scope gaps and flow-down deficiencies before signature; tracking conditional and unconditional lien waivers (including lower-tier) at every draw; and aging retainage against release conditions — while humans negotiate terms, resolve scope disputes, and authorize default actions.

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 — A backcharge fight is brewing and you need to know what the scope actually says.

Read the executed subcontract for the drywall trade, including the scope exhibit. The GC wants to backcharge this sub for patching around penetrations that the mechanical trade cut after drywall was hung. Tell me whether patching after other trades is within this sub's scope, whether the subcontract's backcharge clause supports the charge, what notice the GC had to give before backcharging, and whether the mechanical sub's scope makes them the responsible party instead. Quote the controlling scope and backcharge language and cite the exhibit and section, and flag any ambiguity rather than assuming in the GC's favor.

What good output looks like: A clause-cited determination of scope responsibility and backcharge validity, with the notice requirement stated and any ambiguity flagged rather than resolved for the client.

Follow-ups:

  • Draft the backcharge notice if the contract supports it.
  • If the language is ambiguous, what facts would decide it?
  • Is the mechanical sub the party we should actually be charging?

Generative — Buying out a trade and you need a scope exhibit that closes the usual gaps.

Draft a subcontract scope exhibit for the structural steel package using the following inputs: the trade's bid with its stated inclusions and exclusions (attached), the drawings and specifications, and our prime contract terms. Write the scope so it explicitly resolves the recurring gray areas for this trade — embeds and anchor bolts furnish/install, connection design responsibility, temporary bracing, touch-up painting after erection, and coordination with the concrete and deck trades. Add a flow-down rider mirroring the prime's insurance limits, additional-insured requirement, indemnity, notice window, and warranty duration. Keep it precise and enforceable, not aspirational.

What good output looks like: A precise scope exhibit that names the common gray-area items explicitly, plus a flow-down rider mirroring the prime — with residual ambiguities called out.

Follow-ups:

  • List every scope item still ambiguous after this draft and how you would close each.
  • Where does this scope overlap or conflict with the concrete sub's scope?
  • Draft the exclusions section so the sub cannot later claim a gap item.

Orchestrated — You want to confirm a subcontract is consistent with everything it should align to.

Reconcile this executed subcontract against the surrounding record. Check its scope against the current drawing set and against the adjacent trade scopes to identify any gap where no trade is responsible or any overlap where two are. Compare its flow-down clauses against our prime for insurance, indemnity, notice, warranty, and lien-waiver requirements and list every deficiency. Verify the sub's certificate of insurance on file meets the limits and additional-insured status the subcontract requires. Confirm the subcontract sum reconciles to this trade's line in our schedule of values. Return one reconciliation report with each finding tied to the source document.

What good output looks like: A single reconciliation report covering scope gaps/overlaps, flow-down deficiencies, insurance compliance, and sum alignment, each tied to the underlying document.

Follow-ups:

  • Draft the amendment language to close the flow-down and insurance gaps.
  • Which scope gaps need an RFI to the design team before they can be assigned?
  • Does any executed change order break the sum reconciliation?

Autonomous — Standing policy for subcontract buyout and payment compliance.

Run subcontract compliance across this project under these rules. No subcontractor is cleared for its first payment until a current COI meeting our required limits and additional-insured status, a valid W-9, any required bonds, and a signed subcontract are all on file — hold and escalate any exception. At each pay application, verify the required conditional lien waiver for the current draw and the unconditional waiver for the prior payment are present, including lower-tier waivers where sub-subs or suppliers exist, and hold payment on any missing waiver. Track retainage against each subcontract's release condition and flag amounts held past that point. Alert on any subcontract change order that lacks a corresponding owner change or is priced above what we will collect. Never release a payment, never waive a required document, and never authorize a default or termination action — route all of those to the project manager with your findings.

What good output looks like: A continuously enforced compliance gate with a short hold-and-exception queue, where humans authorize payments, waivers, and default actions and the audit trail is complete.

Follow-ups:

  • Show me every payment currently on hold and why.
  • Which subs are missing lower-tier lien waivers this cycle?
  • List subcontract changes that are not aligned to an owner change.

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

Maturity — locate yourself honestly

  1. Level 0 — Handshake and PO

    Trades work off purchase orders or verbal scope with no real subcontract. Flow-down is nonexistent and every dispute is a fresh negotiation.

  2. Level 1 — Standard form

    A standard subcontract is used with a scope exhibit, but flow-down and compliance checks are manual and inconsistent across trades.

  3. Level 2 — Linked

    Subcontracts are connected to the prime, the schedule of values, insurance certificates, and the change log, so gaps and mismatches are visible.

  4. Level 3 — Assisted

    Scope exhibits and flow-down riders are model-drafted, and reconciliation against drawings, prime, and certificates is generated for review.

  5. Level 4 — Operated

    The buyout and payment-compliance loop runs unattended within guardrails, while humans own scope disputes, term negotiation, and default decisions.

Common questions

What does incorporation by reference actually do in a subcontract?

It binds the subcontractor to the terms of the prime contract as if the sub were the contractor, to the extent those terms apply to the sub's work. This is how obligations like the schedule, notice provisions, warranty duration, and dispute-resolution mechanism reach the sub without being retyped. Its limits matter, though: a sub can usually demand a copy of the prime, and courts will not always enforce a prime term the sub had no reasonable way to know, which is why the most important obligations are also spelled out directly.

Why is the scope exhibit more contentious than the price?

Because the price only means something once everyone agrees on what it buys. Most trade disputes are not about the unit cost but about who owns the gray-area items — the patch, the temporary protection, the coordination, the furnish-versus-install boundary. A precise scope exhibit that names those items eliminates the fights that a clean price alone never resolves.

Should the GC withhold more retainage from subs than the owner withholds from the GC?

It is common but risky. Withholding more than the prime allows leaves the GC holding trade cash it may not be entitled to keep, strains the trade's finances, and can violate prompt-payment statutes in some states that limit retainage or require it to track the prime. The defensible practice is to mirror the prime's retainage and reduce sub retainage when the owner reduces the GC's.

Read this article as markdown · Browse all 110 objects