What a flow-down clause commits you to
One sentence takes a document you have not read and makes it part of your contract. Which obligations the prime genuinely has to pass on, which it added for itself, and the mismatch that catches almost everybody three years later.
Problems, in order · Part of Outsourced General Counsel
A flow-down clause passes obligations from a prime contract into a subcontract. Some are genuinely mandated by the prime customer and cannot move; others the prime added for its own benefit and are negotiable. Dinmore Bell reads the prime contract behind the flow-down, separates the two, and checks what was never flowed down to your own subcontractors.
A subcontract arrives with a paragraph saying you are bound by the terms of the prime contract as if you were the contractor, so far as they apply to your works. Sometimes the prime contract is attached. More often it is not, and you are asked to sign anyway.
That paragraph is a flow-down clause, and it is the single most consequential sentence in most supply contracts. It takes a document you have not read and makes it part of yours.
What is a flow-down clause in a subcontract?
A provision that passes obligations from the prime contract, between the main contractor and its customer, down into the subcontract. It can incorporate the whole prime contract, or list specific clauses, and the difference between those two drafting choices is worth money.
The commercial logic is sound. A main contractor that has promised its customer a set of standards, timescales and remedies cannot deliver them unless the people doing the work are held to the same things. Back-to-back terms are how risk is supposed to travel down a supply chain, and refusing all of them is not a negotiating position, it is a reason to lose the work.
But flow-down clauses in practice contain two quite different categories of obligation, and they are almost never separated. Reading them apart is the whole job.
Which flow-down obligations can you actually refuse?
The ones the prime added for itself. An obligation genuinely mandated by the prime's own customer usually cannot move, because the main contractor has no authority to release you from something it is itself required to impose. An obligation the prime invented is a commercial term like any other.
The test is simple to state and requires a document to apply: is this obligation in the prime contract, and does the prime contract require it to be passed on?
Three things fall clearly into the first category. Obligations imposed by law on the whole chain. Obligations the customer has expressly required to be flowed down, which in public sector and defence work are usually listed. And obligations that are physically indivisible, like a single completion date that only exists once.
The second category is larger than most suppliers assume. Uncapped liability, indemnities wider than the prime's own, payment terms longer than those the prime enjoys, step-in rights, retention held beyond the prime's retention, and a right to terminate for convenience that has no equivalent upstream. None of those are usually required by the customer. They are the main contractor improving its position while describing the improvement as a pass-through.
The way to find out is to ask for the prime contract. A redacted copy, with prices removed, is a normal request and a contractor who refuses it outright is telling you something. Where refusal holds, the fallback is a warranty: that the flowed-down obligations are no more onerous than those the contractor owes its customer, and that the contractor will indemnify you to the extent they are.
The pay-when-paid problem, and why it is usually void
Payment is where flow-down is most aggressive and where the law has already intervened. In construction work, a clause making your payment conditional on the main contractor being paid by its customer is not merely unattractive. Under section 113 of the Housing Grants, Construction and Regeneration Act 1996 it does not work.
A provision making payment under a construction contract conditional on the payer receiving payment from a third person is ineffective, unless that third person, or any other person payment by whom is under the contract (directly or indirectly) a condition of payment by that third person, is insolvent.
Two things follow that suppliers routinely miss. The first is that the clause being ineffective does not mean anybody tells you. It sits in the contract, the contractor relies on it in correspondence, and it works perfectly well as a delaying tactic against a supplier who does not know the section exists. The second is the insolvency carve-out, which is real: where the ultimate payer has actually become insolvent, a conditional payment provision can bite.
The section applies to construction contracts as defined by the Act, which reaches a good deal further than people expect, and covers much fit-out, mechanical and electrical, and installation work. It does not cover a pure supply of goods with no installation. So the same clause in a manufacturing supply agreement, where the Act does not apply, may be entirely enforceable. Knowing which side of that line your contract sits on is not academic; it decides whether you argue about the clause or ignore it.
Public sector chains have a separate mechanism. Under the Procurement Act 2023, implied payment terms are read into every public contract, requiring payment of an undisputed invoice within thirty days of the later of its receipt and the date payment falls due. Those terms are designed to reach down the chain rather than stop at the first tier, which means a supplier three levels below a contracting authority has more leverage than the subcontract in front of it suggests.
What happens if you accept an obligation you cannot pass on?
You hold it alone. This is the mismatch that catches almost everybody: an obligation accepted upstream, on the prime's paper, that was never written into the terms you use with your own subcontractors and suppliers.
The failure is not in the negotiation, it is in the filing. A supplier negotiates a subcontract carefully, accepts a defects liability period of two years, a requirement to hold specific insurance for six, and an obligation to provide as-built information in a particular format. Then it buys in a component on its own standard purchase order, which carries a twelve-month warranty, no insurance requirement and no documentation obligation at all.
For the difference between those two positions, the supplier is the insurer. And it will not find out for three years, because that is how long it takes for the defect to appear.
The fix is unglamorous and it works. Every obligation accepted upstream that depends on somebody else performing gets written into the downstream paper before the upstream contract is signed, not after. In practice that means a short list, held by one person, of the terms your own purchase orders and subcontracts must contain: warranty period, insurance, documentation, audit and access, data and confidentiality, and the notice periods on claims. The list changes when a customer imposes something new, which is exactly why it has to be somebody's job rather than a document written once.
The second half of the fix is notices. Flow-down clauses commonly pass down a time bar, requiring a claim to be notified within a short period of the event rather than the cost being known. A claim that is correct but late is worth nothing, and a supplier that has accepted a fourteen-day notice provision upstream without imposing a shorter one downstream cannot make its own claim in time however good it is.
Where a specialist is needed
Adjudication and litigation are conducted by solicitors and counsel, and where a dispute is live that is the right route. Insurance cover for the gap between accepted and passed-on obligations is a question for your broker, who needs to see the actual clauses rather than a summary.
The work before that is contract work: reading the prime contract behind the flow-down, separating what must be accepted from what was added, and making the downstream paper match the upstream commitment. That is what an outsourced General Counsel function does as a standing function rather than a project, and for a supplier it usually sits alongside the rest of the corporate and commercial workload. For businesses in manufacturing, it is the single cheapest piece of contract hygiene available.
The clause is not the enemy. Signing it without the document behind it is.
Common questions
- What is the difference between back-to-back terms and a flow-down clause?
- Back-to-back describes the intended outcome, which is a subcontract mirroring the prime contract so risk travels down the chain. A flow-down clause is the drafting device used to achieve it. The difference in practice is that a flow-down clause often passes down more than the prime contract requires, and nobody notices because the prime contract was never supplied.
- Can I ask to see the prime contract before I sign a subcontract?
- Yes, and a redacted copy with prices removed is a normal request. Where it is refused, the workable fallback is a warranty that the flowed-down obligations are no more onerous than those the contractor owes its own customer, with an indemnity to the extent they are. A flat refusal to give either is itself information.
- Is a pay-when-paid clause enforceable?
- In a construction contract as defined by the Housing Grants, Construction and Regeneration Act 1996, a clause making your payment conditional on the main contractor being paid is ineffective, unless the ultimate payer is insolvent. In a pure supply of goods with no installation, where the Act does not apply, the same clause may be fully enforceable.
- What should I do about obligations my own suppliers do not carry?
- Write them into the downstream paper before the upstream contract is signed. In practice that means one short list, held by one person, of the terms your purchase orders and subcontracts must contain: warranty period, insurance, documentation, audit and access, confidentiality, and the notice periods on claims. The list changes each time a customer imposes something new.
- Do flow-down clauses only matter in construction?
- No. They are most visible in construction because the statutory framework and the standard forms make them explicit, but the same drafting appears in manufacturing supply chains, defence and aerospace programmes, IT and systems integration, and outsourced services. The analysis is identical, and outside construction there is usually less statutory protection.
Sources
- 01section 113 of the Housing Grants, Construction and Regeneration Act 1996 legislation.gov.uk
- 02implied payment terms legislation.gov.uk
More: Problems, in order
All insights →The security schedule your customer sent back
The enterprise buyer returns your contract with its own security and data processing annex, and somebody accepts it to keep the deal moving. What those four clauses actually commit you to.
Are your consumer terms actually enforceable?
A term the customer agreed to is not the same as a term that binds them. Which clauses in an ordinary set of consumer terms fail the fairness test, and why the ones you were most confident about are usually the first to go.
Deadlock between two equal founders
Fifty per cent each works until the first real disagreement, and then company law offers no tie-break at all. The mechanisms that work, and the two statutory routes left when none was put in place.