Subcontractor Flow-Down Clauses: Which Prime Contract Obligations Must Pass Through to Subs and How to Draft Them

You signed a service agreement with a client that requires your subcontractors to carry two million dollars in general liability insurance, comply with OSHA safety standards, keep all project details confidential, and assign any intellectual property they create to the client. You have a subcontract. You paid the sub. Something goes wrong — the sub maintained a five-hundred-thousand-dollar policy, violated a safety rule, and departed with the source code in hand. When your client calls and points to page four of the prime contract, you look at your subcontract and find exactly one sentence about "compliance with applicable laws." That sentence — assembled from a boilerplate template, never tailored, never reviewed — just cost you six figures.

That scenario is not hypothetical. It plays out with uncomfortable regularity in construction, technology, and professional services contracts. The fix is not complicated. It is a set of properly drafted flow-down clauses, and this article explains exactly what they must say, which ones are non-negotiable, and where small businesses consistently get it wrong. For a starting point on subcontract structure, visit the template catalog at /docs, but return here before you fill in any blanks — structure without the right language is still a gap.

What a Flow-Down Clause Does — and What It Does Not Do Automatically

A flow-down clause (sometimes called a pass-through, trickle-down, or incorporation-by-reference clause) is a provision in a subcontract that imports specific obligations from the prime contract into the subcontract. In plain terms: whatever you promised your client, the sub promises the same thing to you — for the portion of work the sub actually performs. The operative mechanism is the subcontract language itself, not the existence of the prime contract.

The critical legal point is that flow-down does not happen automatically in private contracts. Courts have consistently held that a subcontractor is bound only by the terms of its own contract, not by a prime contract it never signed. Even a provision in the subcontract that says "Subcontractor is aware of the Prime Contract" does not transform prime contract obligations into binding subcontract terms. Without express language incorporating specific obligations, the sub owes only what the subcontract says — and if the subcontract is silent, the sub owes nothing on that point.

This distinction matters because most standard subcontract forms — including many you might download as a draft from a generic legal website — contain broad boilerplate such as "Subcontractor shall comply with all terms of the Prime Contract." Courts have split on whether this language is enforceable. Some courts read it as effective incorporation; others treat it as aspirational language that creates no specific obligations when the prime contract is not attached and described. The safest approach is to name the obligations you want to flow down and describe them expressly in the subcontract itself, with enough detail that a court could read and apply each one without guessing at your intent.

Government Contracts: Mandatory Flow-Down Under FAR Part 44

If your prime contract is a federal government contract, flow-down is not just a drafting preference — it is a legal requirement. The Federal Acquisition Regulation (FAR), specifically Part 44 and the clause at FAR 52.244-6 ("Subcontracts for Commercial Products and Commercial Services"), requires prime contractors to include certain provisions in every subcontract above specified thresholds. Failure to include a required clause can expose the prime to a cure notice, termination for default, or False Claims Act liability if the violation was knowing.

Required flow-down clauses under FAR 52.244-6 include, among others:

• FAR 52.222-26 (Equal Opportunity) — prohibits employment discrimination based on race, color, religion, sex, sexual orientation, gender identity, or national origin
• FAR 52.222-35 (Equal Opportunity for Veterans) — affirmative action and reporting obligations for covered veterans
• FAR 52.222-36 (Equal Opportunity for Workers with Disabilities) — affirmative action requirements under the Rehabilitation Act
• FAR 52.225-1 or 52.225-3 (Buy American) — material sourcing restrictions on end products and components
• FAR 52.232-40 (Providing Accelerated Payments to Small Business Subcontractors) — applies when the prime receives accelerated payments from the agency

Beyond FAR 52.244-6, other clauses carry their own mandatory flow-down language buried in the clause text. FAR 52.219-8 (Utilization of Small Business Concerns) and FAR 52.222-54 (Employment Eligibility Verification) each require the prime to insert them in subcontracts meeting specified criteria. Missing even one can trigger contract-level consequences. The practical takeaway: if your prime contract is a federal award, have someone with government contracting experience audit every clause for its specific flow-down requirement before you finalize any subcontract. A sample review checklist prepared by a government contracting attorney pays for itself the first time you avoid a compliance finding.

Private Contracts: What Should Always Pass Through

In private contracts — construction, professional services, technology, creative work — there is no FAR to set the minimum rules. The prime contractor decides what flows down, and that discretion is also a trap. Most small businesses draft subcontracts reactively, thinking about flow-down only after something goes wrong on a project. The categories below virtually always justify express flow-down language, regardless of project type:

• Insurance minimums, coverage types, and additional insured requirements (mirroring the prime contract exactly)
• Indemnification and defense obligations toward the owner (with state law analysis)
• Confidentiality and NDA obligations the prime owes the owner
• Intellectual property assignment for all deliverables the sub creates
• Compliance with any specific safety, regulatory, or quality standards named in the prime contract
• Change order authorization and documentation procedures
• Dispute resolution forum, governing law, and venue selection

The question is not whether these obligations are important — they obviously are — but whether your subcontract addresses them with enough specificity that a court could read and apply the language without filling in blanks. If you are starting from a subcontractor agreement template, treat the flow-down provisions as the first section to customize, not the last.

Insurance Requirements: The Gap That Creates Personal Exposure

Insurance flow-down gaps are the most common source of expensive surprises in subcontracted work. Your prime contract requires you to maintain two million dollars per occurrence in general liability coverage, a five-million-dollar umbrella, and workers' compensation at statutory limits. Your subcontract says "Subcontractor shall maintain adequate insurance." That word "adequate" is doing no legal work whatsoever.

If the sub maintains a five-hundred-thousand-dollar policy and a claim arises for one-point-eight million dollars, your client looks to you — the prime — because you are the party who agreed to maintain two million dollars in coverage. You then look to your subcontract, which requires "adequate" insurance. A court will not read "adequate" as meaning "exactly what the prime contract requires" based on implication alone.

Sample flow-down insurance provision:

"Subcontractor shall procure and maintain, at its own expense and for the duration of this Agreement, the following minimum insurance coverages: (a) Commercial General Liability — $[AMOUNT] per occurrence / $[AMOUNT] aggregate; (b) Workers' Compensation — statutory limits for the applicable state; (c) Professional Liability (Errors & Omissions) — $[AMOUNT] per claim, if Subcontractor provides professional or technology services. All policies shall name [Prime Contractor] and [Owner/Client] as additional insureds. Subcontractor shall provide certificates of insurance prior to commencing any work, and shall provide thirty (30) days' written notice of cancellation or material modification. Failure to maintain required coverage constitutes a material breach of this Agreement."

Note the "additional insured" requirement. Without it, the owner's claim goes against the sub's policy and the sub's insurer may argue that it only owes coverage to the named insured — the sub — not to the owner or the prime. The additional insured endorsement changes that dynamic. Require it expressly and get proof before work starts.

Indemnification Obligations: Matching the Prime Contract Without Triggering State Law Limits

Indemnification clauses shift responsibility for losses, damages, and legal defense costs. If your prime contract obligates you to defend and indemnify your client against claims arising from the work, you want an equivalent obligation running from the sub to you — at minimum for the portion of work the sub performs. The drafting challenge is calibrating scope against state law.

Many states — California, Texas, New York, Florida, and others — have anti-indemnity statutes that limit or void indemnification clauses requiring one party to indemnify another for that other party's own negligence. A broad-form indemnification in your prime contract that covers the owner's negligence may be unenforceable as a flow-down against your sub if the sub's subcontract is governed by one of those states.

A workable approach is to create the flow-down indemnification in two tiers: first, the sub indemnifies the prime and owner for claims arising from the sub's own acts, omissions, or negligence (this is enforceable virtually everywhere); second, the sub indemnifies proportionately for any shared negligence, subject to applicable state law limitations. This preserves the maximum enforceable protection without including language a court will void entirely. A service agreement template can provide the base structure, but the indemnification tier must be drafted for your specific state.

Confidentiality and IP Assignment: Protecting the Owner's Interests Through the Tier

If your prime contract contains a non-disclosure obligation or an intellectual property assignment clause, and your sub creates any portion of the deliverable, you have a chain-of-title problem unless the sub has signed equivalent obligations running toward you — and ultimately, toward the client. Courts will not create confidentiality obligations by implication. If the sub never signed an NDA with you, it can freely share what it learned about the project, the client, and the client's proprietary information.

The IP assignment issue is even more acute for technology and creative work. Under the Copyright Act (17 U.S.C. § 101), the "work made for hire" doctrine applies to independent contractors only when: (a) the work fits one of nine enumerated statutory categories, and (b) there is a written agreement designating the work as made for hire. A freelance developer who writes custom software for your client — delivered through you as prime — does not automatically assign copyright to you or the client. Without a written assignment in your subcontract, you may be delivering a product that neither you nor your client legally owns.

To create a clean chain of title, the subcontract must address four points:

• Assignment of all IP created for the project (including code, designs, reports, data, and derivative works) to the prime, with language sufficient for the prime to further assign to the client
• Confidentiality scope and duration matching or exceeding the prime contract's NDA obligations
• A requirement that the sub obtain written IP assignments and NDAs from any sub-subcontractors or freelancers the sub engages
• A clear description of "background IP" (what the sub brings in vs. what is created fresh for the project) and the scope of any license the sub grants to use background IP in the deliverable

An independent contractor agreement template typically includes an IP assignment provision that you can adapt as a flow-down clause in your subcontract. Review it carefully — the standard language may need to be expanded to address software, data, and derivative works specifically.

Prevailing Wage, Safety, and Anti-Discrimination: Statutory Obligations That Follow the Work

Some obligations flow down as a matter of statutory law regardless of what your subcontract says. The Davis-Bacon Act (40 U.S.C. § 3141 et seq.) requires contractors and subcontractors on federal construction projects to pay locally prevailing wages and fringe benefits. You cannot contract around this requirement — even if your subcontract is silent on wages, the sub is legally obligated to comply, and you as prime are responsible for monitoring the sub's compliance.

OSHA standards apply directly to subcontractors as employers. However, if a safety violation causes an accident, your prime contract may make you responsible for overall site safety — a standard clause in construction and facilities management contracts. An express flow-down safety clause does two things: it puts the sub on formal notice of the specific safety standards that apply (some subs genuinely are unaware of project-specific requirements beyond OSHA minimums), and it gives you a contractual indemnification basis if the sub's non-compliance causes a loss attributable to you under the prime contract.

Anti-discrimination laws under Title VII, the ADA, and the ADEA apply directly to employers regardless of contract language. But if your prime contract obligates you to ensure that all workers on a project meet certain non-discrimination and workplace conduct standards — a common clause in government and large corporate prime contracts — you need that language in the subcontract so the sub is contractually accountable to the same standard and you have a clear remedy if the sub falls short.

Change Orders: Closing the "Nobody Told Me" Defense

One of the more frustrating patterns in subcontracting is the prime contractor who agrees to a scope change with the owner, fails to notify the sub in writing, and then discovers that the sub's portion of the work has materially changed. The sub refuses to perform additional work without additional pay. The prime is caught in the middle: contractually obligated to the owner but holding a subcontract that does not authorize the changed scope.

A change order flow-down clause eliminates this gap by requiring the sub to comply with any changes directed by the owner that fall within the general scope of the subcontract, with the payment mechanics spelled out clearly. The provision should state the sub's obligation to perform, the prime's obligation to process a corresponding change order within a specified number of days, and what happens if the prime fails to act — whether the sub may pause work, seek direct compensation, or pursue another remedy.

Sample change order flow-down provision:

"Prime Contractor may direct Subcontractor to perform changes within the general scope of this Agreement, including additions, deletions, or modifications to the Work, to the extent such changes are directed or approved by Owner under the Prime Contract. Subcontractor shall not commence changed work until receiving written direction from Prime Contractor. Prime Contractor shall issue a written Change Order to Subcontractor, reflecting an equitable adjustment to the Subcontract Price and Schedule, within fifteen (15) business days of receiving Owner's written authorization for such change. If Prime Contractor fails to issue a Change Order within said period, Subcontractor may provide written notice and, if not resolved within five (5) business days, may suspend performance of the changed work without waiving any right to compensation."

Without this provision, the sub has a credible argument that it had no obligation to perform work outside the original scope, and may assert a claim for additional compensation that you, the prime, cannot pass through to the owner because you failed to preserve your rights under the prime contract's change order clause. The create of these escalation deadlines is what makes change order management work in practice.

Dispute Resolution: Whether Arbitration Binds the Sub Depends Entirely on Your Language

Your prime contract likely requires disputes to be resolved through arbitration, often administered by the American Arbitration Association (AAA) under its Commercial or Construction Industry Rules. That is common and generally efficient. What is far less common — but critically important — is confirming that your subcontract extends the same obligation to the sub in a way that actually works.

The Federal Arbitration Act (9 U.S.C. § 1 et seq.) enforces written arbitration agreements. It does not create them. If your subcontract is silent on dispute resolution, the sub can sue you in state court even while you are arbitrating the same underlying facts with the owner. You could face parallel proceedings in two different forums simultaneously, spending twice the money and risking inconsistent legal outcomes on identical fact patterns.

As illustrated in the infographic above, there are three main approaches. The "mirror" approach replicates the prime contract arbitration clause in the subcontract — simple and effective for most two-party disputes. The "joinder" or "consolidation" approach allows the prime to join the sub into the prime-owner arbitration — more complex to draft but highly valuable in construction and technology projects where all three parties are needed in the same room. The "stepped process" approach (negotiation → mediation → arbitration) is common in long-term service relationships where preserving the commercial relationship matters as much as resolving the specific dispute.

One drafting caution: some states limit arbitration clauses in construction subcontracts. California Code of Civil Procedure § 1298 imposes specific disclosure and formatting requirements for arbitration clauses in residential construction contracts. Check the governing law of the subcontract before you copy-paste the prime contract clause — you may need to modify it. A consulting agreement template can show you how a well-drafted dispute resolution clause is typically structured for service-based subcontracts.

Pay-When-Paid vs. Pay-If-Paid: The Two-Word Distinction That Moves Millions in Risk

The pay-when-paid clause says: "Prime will pay sub within X days after prime receives payment from the owner." Courts in most states read this as a timing provision. It delays when the prime pays but does not eliminate the obligation to pay at all. Even if the owner never pays the prime, the prime must eventually pay the sub — once a reasonable time has passed and it becomes clear that payment from the owner is not coming.

The pay-if-paid clause says something materially different: "Prime's obligation to pay sub is expressly conditioned on prime's receipt of payment from owner for that portion of the work." Courts — where they enforce it — read this as a complete transfer of the owner insolvency risk to the sub. If the owner goes bankrupt, the sub receives nothing, even for work that was properly completed and accepted.

The difference between "when" and "if" is two letters and potentially the entire payment obligation under your subcontract. Enforceability varies significantly by state. California courts refuse to enforce pay-if-paid clauses on public projects under Civil Code § 3262; North Carolina has similar limits; New York courts enforce them under strict conditions including clear "condition precedent" language. Texas courts have enforced pay-if-paid clauses in private commercial contracts. For federal contracts, the Prompt Payment Act (31 U.S.C. § 3901) and implementing regulations generally require payment to subs within seven days of the prime's receipt of payment, limiting the usefulness of pay-if-paid as a defense.

Sample pay-if-paid clause (where enforceable):

"Notwithstanding any other provision of this Agreement, Prime Contractor's obligation to make payment to Subcontractor for any portion of the Work is expressly conditioned upon and subject to Prime Contractor's actual receipt of payment from Owner for that same portion of the Work. This condition is a condition precedent to Prime Contractor's payment obligation, not merely a timing provision. The risk of Owner's non-payment, insolvency, or refusal to pay for any reason is expressly allocated to Subcontractor for its proportionate share of the Work. Subcontractor acknowledges that it has independently assessed this risk and has agreed to accept it as part of the consideration for this Agreement."

Two practical notes: first, the acknowledgment language at the end matters. Courts applying heightened scrutiny to pay-if-paid clauses look for evidence that the sub had actual notice and meaningful opportunity to negotiate. Separate acknowledgment, along with leaving a negotiation period before signing, strengthens enforceability. Second, if you use pay-if-paid, do not also include a payment schedule with fixed dates in the same subcontract — courts read fixed-date payment schedules as inconsistent with a condition precedent, and the condition may not survive the conflict.

How to Draft a Proper Flow-Down Clause: Two Approaches and One Trap to Avoid

There are two main drafting approaches, and one common trap that swallows both. The wholesale incorporation approach attaches the prime contract as an exhibit to the subcontract and states that all provisions apply to the sub "to the extent relevant to the Subcontractor's scope of work." This is simple to create, but "to the extent relevant" is a phrase courts have repeatedly found ambiguous. When the sub argues that an obligation is not "relevant" to its scope, a court has to guess at what the parties intended.

The selective express incorporation approach identifies each obligation from the prime contract that should flow down, restates it in the subcontract with any necessary modifications for the sub's tier, and confirms the sub's acceptance. This takes more time upfront but creates clarity. For each obligation, the subcontract states: (1) what the obligation is, (2) whether it is identical to the prime contract obligation or modified, and (3) what remedy the prime has if the sub breaches it. A well-structured freelance contract template uses selective express incorporation for IP, confidentiality, and payment terms — worth reviewing as a model for how to layer these provisions.

The standard trap is using boilerplate flow-down language from a construction subcontract in a technology services subcontract, or vice versa. A construction form may have robust insurance and safety flow-down but completely omit IP assignment, data security, and software license obligations. A technology services form may address IP thoroughly but say nothing about prevailing wage or additional insured status. Match the template to the project type, then add the missing flow-down provisions before you sign.

Common Drafting Mistakes That Leave Primes Exposed

These mistakes are particulary easy to make when you are adapting a template from a different project or pulling a form from an unfamiliar source. Each one has cost a prime contractor money that the sub was never legally obligated to share:

• Using "comply with the prime contract" without attaching the document: The sub can argue it never saw it, and courts often agree.
• Flowing down insurance requirements without specifying dollar amounts: "Adequate" is not a number. Courts will not supply one for you.
• Including indemnification flow-down without checking the state's anti-indemnity statute: A clause that is void is worse than a limited one, because you thought you had protection and planned around it.
• Forgetting to flow down audit rights when the prime contract grants the owner the right to audit costs: In cost-plus and government contracts, this omission blocks the owner from auditing the sub's records even when the dispute concerns work the sub performed.
• Using pay-when-paid language when you intended pay-if-paid: Two words, two entirely different legal outcomes. Have someone read the clause specifically for this distinction.
• Omitting IP assignment when the sub creates any deliverable with copyrightable or patentable content: The sub retains ownership by default. Your client may not have the legal right to use the product it paid for.

For reference on what a properly structured IP and services subcontract looks like, the subcontractor agreement template on this site provides a baseline that you can extend with the flow-down provisions discussed above.

Pre-Signing Flow-Down Checklist

Before you finalize any subcontract — or before you allow work to begin — walk through this checklist. It is not a substitute for legal review on high-value projects, but it will catch the most common gaps that cost primes money in subcontract disputes:

• Pull the prime contract and mark every obligation the owner imposed on you; decide which ones are relevant to the sub's scope
• Draft express flow-down language for each relevant obligation — do not rely on "comply with prime contract" boilerplate
• Verify the subcontract's governing law and check for anti-indemnity and anti-arbitration statutes in that state
• Confirm the sub's insurance mirrors prime contract minimums exactly, with additional insured endorsements, and require certificates before work starts
• Verify the IP assignment covers all deliverables the sub will create, names all asset types, and includes a representation that the sub has authority to assign
• If you use pay-if-paid, use clear "condition precedent" language, verify enforceability in the governing state, and eliminate any inconsistent fixed payment dates
• For federal prime contracts, run every FAR clause against the mandatory flow-down requirements list before finalizing the subcontract
• Have the sub separately initial or acknowledge risk-shifting provisions (pay-if-paid, broad indemnification, IP assignment), and preserve that signed acknowledgment

A subcontract that properly flows down your prime contract obligations is not just a compliance exercise. It is the document that determines whether the risk you accepted from your client stays with the party who performed the work — or comes back to you when the sub falls short. The difference between "compliance with applicable laws" and three pages of specific, enforceable flow-down provisions is the difference between a subcontract and a liability blank check. Take the time to create the former, and you will not spend the money correcting the latter.

Article reviewed by: Maya S. (Attorney)