The Flow-Down Clause Explained (2026)

A flow-down clause takes obligations from a higher contract, usually a prime or main contract, and makes them binding on a lower tier, usually a subcontractor or supplier. The point is simple. If a prime contractor has promised something to the customer, the prime needs its subcontractors to make the same promise, so the promise can actually be kept down the chain. This page explains what a flow-down clause does, where it is used, which obligations usually flow down, sample wording, the risks on each side, and the points that are negotiated. It is general information, not legal advice. ## What a flow-down clause does Most supply chains are built in layers. A customer contracts with a prime. The prime contracts with subcontractors. Those subcontractors may contract with their own suppliers. Each layer is a separate contract, and a subcontractor is not normally bound by terms in a contract it never signed. A flow-down clause bridges that gap. It states that named terms of the upper contract apply to the lower contract as if the subcontractor were in the position of the prime toward the customer. The clause can do this in two ways: - By reference, saying the subcontractor is bound by the relevant terms of the prime contract, with the subcontractor standing in the prime's shoes.

• By incorporation, copying specific obligations into the subcontract so they appear as express terms. Flow-down clauses are also called pass-through or conduit clauses. They are most common in construction and in government or defence contracting, where the customer often requires that certain obligations reach every tier of the supply chain. ## Why it matters A prime contractor carries the obligations it owes the customer. If a subcontractor does the actual work but is not bound to the same standard, the prime is exposed in the middle. It still owes the customer, but it cannot pass the duty, or the liability, to the party doing the work. - For the prime, flow-down keeps the back-to-back position intact, so what it owes up the chain matches what it can demand down the chain. Without it, the prime absorbs the gap.
• For the customer, flow-down is how a requirement, such as a security standard, an audit right, or an insurance level, actually reaches the party that handles the data, builds the component, or performs the service.
• For the subcontractor, flow-down decides how much of someone else's deal it is signing up to, sometimes without ever seeing the full prime contract. In regulated work the clause is not optional. A government customer may mandate that specific provisions flow down to all tiers. A well known example in United States defence contracting is DFARS 252.204-7012, which requires cybersecurity safeguarding and incident reporting duties to be passed to subcontractors and suppliers. ## Which obligations usually flow down There is no fixed list, and it depends on the deal and the governing regime, but the obligations most often flowed down are: - Scope and performance standards, so the subcontractor's work meets what the prime promised the customer.
• Compliance obligations, such as anti-bribery, sanctions, modern slavery, data protection, and cybersecurity standards.
• Audit and inspection rights, so the customer or prime can check the lower tier.
• Reporting and record retention, including incident and breach reporting timelines.
• Insurance levels and indemnities matching the upper contract.
• Confidentiality and intellectual property terms, so rights granted up the chain are supported down the chain.
• Change, suspension and termination mechanics, so a change at the top can be managed below.
• Labour, health and safety, and quality standards required by the customer or by law. ## A sample flow-down clause The wording below is illustrative. Adapt it to your contract, supply chain and governing law, and have it reviewed before use. > Flow-Down. The Subcontractor agrees to be bound to the Contractor by the terms of the Prime Contract to the extent that they relate to the Subcontract Works, and to assume toward the Contractor all obligations and responsibilities that the Contractor assumes toward the Client under the Prime Contract in respect of those Works, except where expressly varied by this Subcontract. The provisions listed in Schedule [X] of the Prime Contract are incorporated into this Subcontract and apply as if references to the Client were references to the Contractor and references to the Contractor were references to the Subcontractor. Where a term of this Subcontract conflicts with an incorporated term, [the Prime Contract term] / [this Subcontract] shall prevail. Note how it ties the flow-down to the subcontractor's actual scope, re-maps the party names, incorporates a defined schedule of provisions, and resolves conflicts. Each of those four choices is a negotiation point. ## The risk of a blanket flow-down The most contested wording is the broad catch-all, for example "the Subcontractor is bound by all terms of the Prime Contract." It feels safe to the prime but creates real problems: - The subcontractor may never have seen the prime contract, so it is signing up to unknown terms.
• Prime-level obligations may not fit a smaller scope, such as a full project liability cap landing on a supplier of one component.
• Payment terms, timelines and remedies from the prime may conflict with the subcontract's own commercial terms.
• A pay-when-paid or similar term may flow down in a way the subcontractor did not price. Courts in several jurisdictions read general incorporation wording narrowly, especially for onerous terms such as arbitration or broad indemnities, and may decline to enforce a term that was not clearly brought to the subcontractor's attention. That is a reason to incorporate specific clauses by a named schedule rather than rely on a blanket phrase. ## How to negotiate it 1. List what flows, do not flow everything. Attach a schedule of the specific prime-contract provisions that apply, rather than a blanket reference to the whole document.

2. Ask to see the prime contract. A subcontractor should see, at minimum, the exact terms being flowed down, with pricing and unrelated parties redacted if needed.
3. Re-map the parties cleanly. Make clear that references to the customer become references to the prime, so obligations land where they should.
4. Match obligations to scope. A liability cap, insurance level or performance standard should fit the subcontractor's actual work and value, not the whole project.
5. Set a conflict order of precedence. State which document wins when the subcontract and an incorporated term disagree, so there is no ambiguity.
6. Carve out commercial terms. Keep payment, timelines and remedies governed by the subcontract unless both sides agree otherwise.
7. Mind pay-when-paid and pay-if-paid. These are restricted or unenforceable in some jurisdictions, so confirm the local position before relying on them flowing down.
8. Flag mandatory clauses. In regulated or government work, identify the clauses that must flow down by law so they are not accidentally negotiated away. ## How it differs by jurisdiction The flow-down concept is used worldwide, but the detail varies and should be verified locally: - Incorporation by reference is read strictly in many common law systems. General words may not carry onerous terms, such as arbitration or wide indemnities, unless clearly incorporated.

• Government and defence regimes mandate specific flow-downs. In the United States the FAR and DFARS require certain clauses to reach lower tiers, and DFARS 252.204-7012 is a well known cybersecurity example.
• Payment protection laws in construction, such as security of payment and prompt payment regimes in several countries, limit how far pay-when-paid terms can flow down.
• Local mandatory law, including labour, health and safety and data protection rules, may require certain obligations down the chain regardless of what the contract says. Confirm the governing law and any sector regulation before relying on a flow-down of any specific obligation. ## Drafting, reviewing and tracking flow-downs in one place A flow-down clause is only as good as the match between the obligations a company owes up the chain and the obligations it has secured down the chain. That match has to be built when the subcontract is drafted, checked on every review, and remembered for the life of the contract, because a gap only shows up when something goes wrong and the prime is caught in the middle. Keeping prime terms, the schedule of flowed-down provisions, and each subcontractor's version straight across a supply chain is exactly the kind of work that scatters across documents and inboxes. This is the work an AI contract workspace is built to hold together: drafting a subcontract from a tuned template with the right flow-down schedule, flagging on review where the subcontract does not match the obligations owed up the chain, editing the flowed-down terms in plain language, and tracking which obligations apply to which tier on a live timeline. Adira is one such workspace, built on frontier AI and tuned to how a company contracts, that keeps drafting, review, clause editing and tracking together rather than spread across tools. A flow-down clause works when the promise a company made up the chain can actually be kept down the chain, and someone can prove it.