Subcontract Flow-Down Provisions: Making Sure Your Subs Have the Same Obligations You Have to the Owner
A prime contract between owner and GC establishes obligations — deliverables, schedule, quality, indemnification, insurance, dispute resolution, and dozens of other items. A subcontract between GC and sub should flow down applicable obligations so the sub has the same commitments the GC has to the owner. Without flow-down, the GC can find itself obligated to the owner in ways the sub isn't obligated to the GC — meaning the GC eats the gap.
Flow-down is basic contract hygiene, but many subcontracts don't do it well. Generic "sub agrees to all obligations in the prime contract" language is often unenforceable because it's too vague; specific flow-down requires thoughtful drafting that actually transfers the right obligations. This post covers what to flow down, how to do it effectively, and the gaps that commonly result when flow-down is done casually.
The flow-down consequence becomes clear in disputes:
Flow-down consequence scenarios
- Owner asserts quality claim against GC — GC wants to pass through to responsible sub
- Owner delays payment citing prime contract terms — GC wants to flow delay to subs via pay-when-paid
- Prime contract requires specific insurance — GC needs subs to carry same
- Prime contract has specific notice requirements — GC needs subs to comply
- Prime contract allocates specific risk to GC — GC wants subs to share proportionally
- Owner claims indemnification from GC — GC wants to flow to sub's indemnity
In each case, without flow-down, the GC absorbs what the sub should be sharing. Flow-down aligns sub obligations with GC obligations so the GC isn't the buffer taking all the hits.
One flow-down mechanism is incorporation by reference:
Incorporation by reference approach
- Subcontract states: "Sub assumes toward GC all obligations GC assumes toward Owner, as applicable to Sub's work"
- Prime contract attached or available for Sub's review
- Sub acknowledges review of prime contract
- Applicability qualification — obligations apply to sub's scope only
- Conflicts resolution — which document controls on conflicts
Incorporation by reference is broad but can be challenged on specificity grounds. Courts sometimes limit incorporation to provisions that are specific, clear, and reasonably expected. Overly broad incorporation may not be enforced as written.
The safer approach is specific flow-down for key items:
Specific flow-down clauses
- Schedule — sub agrees to prime contract schedule milestones affecting their work
- Quality — sub's work must meet prime contract quality requirements
- Insurance — sub carries coverage consistent with prime requirements
- Indemnity — sub indemnifies GC for sub-caused claims, matching prime indemnity where possible
- Notice — sub's notice to GC within time to allow GC to notify owner
- Warranty — sub warranty matches prime warranty period and scope
- Changes — sub change order procedure mirrors prime
- Dispute resolution — sub agrees to same forum as prime dispute
- Prevailing wage — sub pays prevailing wages if required by prime
- DBE/MBE — sub participates in DBE requirements if flowed from prime
- Lien waivers — sub provides waivers matching prime requirements
Specific clauses have higher enforceability than generic incorporation. A court applying a specific flow-down clause sees a specific obligation that was clearly agreed; applying generic incorporation requires interpretation that courts may narrow.
Notice requirements deserve specific flow-down attention:
Notice flow-down considerations
- Prime contract may require GC to notify owner within X days of delay or claim
- Sub must notify GC within shorter time — say X-5 days — so GC can notify owner
- Each notice step needs lead time
- Documentation requirements flow through
- Waiver consequences if notice missed at any level
Without tight notice flow-down, a sub's late notice to the GC can cause the GC to miss the prime contract notice window. The sub had no contractual obligation to give timely notice; the GC has no recourse for the prime contract claim they can no longer make.
Insurance requirements flow down with specific mechanics:
Insurance flow-down
- Sub's GL limits at least equal to GC's requirements
- Sub's coverage lines (auto, WC, umbrella) matching requirements
- Owner and GC both named as additional insureds
- Primary and non-contributory language
- Waiver of subrogation
- Specific endorsements (CG 20 10, CG 20 37, etc.)
- Certificate of insurance provided and maintained
Insurance gaps are particularly problematic because they may not surface until a claim. A sub's missing additional insured endorsement becomes apparent when the owner tries to claim under the sub's policy and can't. By then, changing the policy is often too late.
Generic flow-down plus specific insurance flow-down is a good combination. Generic captures the broad obligations; specific ensures insurance — where the highest immediate stakes often reside — is definitely transferred correctly.
Indemnification is another area requiring specific flow-down:
Indemnity flow-down considerations
- Sub indemnifies GC for claims arising from sub's work
- Indemnity typically matches (or exceeds) GC's indemnity to owner
- State anti-indemnity statutes may limit scope (no indemnity for GC's own negligence in some states)
- Additional indemnity obligations beyond prime if project-specific risks warrant
- Defense obligations — typically parallel to indemnity
- Notice to sub of claims triggering indemnity
State law affects indemnity enforceability. Many states have anti-indemnity statutes that limit indemnity for the indemnitee's own negligence. Flow-down should account for state law to avoid unenforceable provisions that create false security.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Schedule Flow-Down
Schedule obligations need to flow through:
Schedule flow-down
- Sub's milestones tied to prime contract milestones
- Liquidated damages flow-down if prime has LDs
- Sub's contractual time for completion
- Sub's schedule coordination obligations
- Sub's delay notification requirements
- Sub's acceleration obligations if directed
Without schedule flow-down, a sub's delay doesn't trigger their liability under LDs the GC is paying. The GC absorbs the LD cost from prime without ability to collect from the sub who caused it.
Certain flow-down gaps recur:
Common flow-down gaps
- Generic incorporation without specific key provisions — incomplete enforceability
- Payment flow-through (pay-when-paid/pay-if-paid) — state law limits in some jurisdictions
- Lien waiver timing — sub doesn't provide waivers when GC needs them
- Closeout documentation — sub's deliverables not tied to GC's obligations
- Warranty response — sub's warranty obligation doesn't match GC's to owner
- Changes procedures — sub's change procedure doesn't match prime's
- Safety program flow-down — GC accountable to owner but sub not bound
Each gap creates specific exposure. Identifying and closing common gaps with specific clauses is more effective than broad incorporation that may not enforce as intended.
Payment flow-down is jurisdictionally complicated:
Payment flow-down status by type
- Pay-when-paid — GC pays sub within reasonable time after owner pays, regardless of owner delay
- Pay-if-paid — GC's obligation to pay sub conditioned on owner payment
- Pay-if-paid enforceability varies — some states allow, some prohibit
- Clear language required even in enforcing jurisdictions
- Court decisions continue to narrow pay-if-paid in many states
- Most states allow pay-when-paid as timing mechanism
Relying on pay-if-paid where it's not enforceable creates false security. States that prohibit pay-if-paid convert the clause into pay-when-paid (reasonable timing) — the GC remains liable to the sub even if owner doesn't pay.
Flow-down extends to lower tiers:
Sub-sub flow-down
- Sub's contracts with their subs should flow down from sub-to-sub contracts
- Which in turn should match or flow down from GC-sub contract
- Which flow down from prime contract
- Each tier must incorporate applicable obligations
- GC can require sub to use flow-down in their sub-subs
A sub who doesn't flow down to their own subs creates the same exposure pattern at their level. GCs sometimes require sub flow-down audit rights to verify the chain works.
Subcontract flow-down is basic contract protection that many contractors handle casually. Effective flow-down uses both incorporation by reference (broad coverage) and specific clauses (enforceable coverage of high-priority items — insurance, indemnity, notice, schedule, warranty, payment). State law affects enforceability of key provisions (especially indemnity and pay-if-paid). Common gaps create exposure that surfaces in specific disputes — where the GC has obligations to the owner that subs don't share, and the GC absorbs the consequence. Reviewing flow-down language systematically, updating it as prime contract obligations change, and training the team that negotiates sub contracts pay off in fewer gaps. The alternative — absorbing obligations the subs should share — is expensive when it matters.
Written by
Jordan Patel
Compliance & Legal
Former corporate counsel specializing in construction contracts and tax compliance. Writes about the documentation layer — COIs, W-8/W-9, certified payroll, notice-to-owner deadlines — and the legal backbone behind audit-ready AP.
View all posts