Head-Contract Flow-Down in Subcontracts: The Traps Nobody Reads Until It's Too Late

"It's back-to-back with the head contract" may be the most load-bearing sentence in Australian subcontracting — and the least examined. Genuine back-to-back drafting, where the subcontractor's obligations mirror the head contractor's exposures with adjusted timeframes and proportionate risk, is careful, expensive work. What usually ships instead is incorporation by reference, a compression of every notice period, and a set of payment and release triggers chained to head-contract events the subcontractor can neither see nor influence. The traps repeat so reliably they can be catalogued.

Trap one: incorporation of documents you've never seen

The clause reads innocently: the subcontractor is deemed to have full knowledge of the head contract and shall perform so as not to put the head contractor in breach of it. Three problems compound. The head contract often isn't provided at tender (or arrives redacted); its obligations were priced for a different scale of party; and "so as not to put the head contractor in breach" converts every head-contract obligation — design standards, reporting, insurances, milestones — into a subcontract obligation of uncertain content. The review rule: never accept deemed knowledge of a document you have not actually received and read, and where incorporation is non-negotiable, demand the document, schedule the genuinely applicable provisions, and exclude the rest expressly.

Trap two: compressed time bars

The head contractor has, say, 28 days to notify the principal of a delay claim — so the subcontract gives the subcontractor 7, or 5, or "within 2 business days of the event", to leave the head contractor time to pass the claim up the line. The logic is understandable; the effect, on the strict-compliance law this series keeps returning to (CMA Assets; Rimfire), is a regime where a small subcontractor's entitlement evaporates faster than its site team can write. Worse, the periods are sometimes internally impossible — a subcontract notice due before the event would reasonably be discoverable. Price the administration the regime demands, or negotiate periods a real site team can meet — and note that in Victoria, a notice-based time bar whose compliance is "not reasonably possible or unreasonably onerous" can now be declared unfair in security of payment proceedings (s 13A), with WA's s 16 equivalent — the compressed-flow-down time bar is exactly the species those provisions were built for.

Trap three: money chained to head-contract events

Direct "pay-when-paid" clauses are void under every Australian security of payment regime. But their ghosts survive in structures that achieve similar timing effects by other means: subcontract retention released on head contract practical completion or final certificate (events potentially years after the subcontractor's trade completion, and invisible to it); payment cycles synchronised to head-contract certification; security held until head-contract defects liability expires. The A-Civil v Ceerose fact pattern — subcontract retention releasable only on head-contract milestones — shows how routinely this drafting appears. Some of it is lawful; all of it is priceable; none of it should be discovered at final account. And the statutory floors still apply regardless of drafting: payment terms beyond the state caps are void, and the subcontractor's payment claim and adjudication rights run on the Act's timetable, not the head contract's.

Trap four: misaligned risk transfer

Liability flows down whole; protections flow down diluted. The subcontract passes through head-contract LD exposure (sometimes uncapped, sometimes at rates reflecting the whole project's losses against a trade-package price), consequential loss, and design responsibility — while the EOT regime narrows qualifying causes, the head contractor's reserve powers are recast for its sole benefit, and insurance obligations duplicate or gap. The proportionality test is simple to state: a subcontractor's worst-case exposure under the flow-down should bear some rational relationship to its package value and margin. Where it doesn't, that is a pricing fact, not a formality.

Trap five: the dispute-resolution mismatch

Subcontract disputes stapled to head-contract dispute outcomes ("the subcontractor is bound by determinations under the head contract"), arbitration clauses that don't allow joinder, and after Tesseract, proportionate liability operating differently in each forum. The result: the head contractor fights the principal in one process and the subcontractor in another, with inconsistent findings a live risk for everyone. Alignment of forums and joinder rights across the contract chain is the structural fix — at drafting, not at dispute.

What this means in practice

1. Run a flow-down audit before signing — one page, five traps. Incorporation (what exactly is incorporated, have we read it); time bars (every notice obligation with its period, tested for workability); money triggers (everything chained to head-contract events, listed and priced); risk transfer (worst-case exposure vs package economics); disputes (forum, joinder, binding-determination clauses).
2. Demand the head contract at tender. Unredacted as to everything said to flow down. A counterparty unwilling to show the document whose terms bind you is telling you the price needs a contingency.
3. Head contractors: flow down honestly — it's in your interest. A subcontract time bar shorter than your own head-contract window doesn't protect you if it's unworkable; it manufactures Liebe v Molloy-style restitution claims, s 13A unfairness declarations, and insolvent subcontractors mid-project. Mirror your real exposures with workable periods.
4. Calendar the invisible events. If your retention or security release hangs on head-contract milestones, make the head contractor's certification status a standing question in every progress meeting, on the record. Invisible triggers stay invisible only if you let them.
5. Use the statutory floor. Whatever the flow-down says, the security of payment regime gives the subcontractor its own claim and adjudication rights on its own timetable. The flow-down can compress contractual machinery; it cannot compress the Act.

Key takeaways

• "Back-to-back" usually means incorporation by reference plus compressed time bars — audit both before pricing, not after signing.
• Compressed notice regimes are enforced strictly, but Victoria's s 13A and WA's s 16 now target exactly the unworkable flow-down time bar.
• Pay-when-paid is void, but its timing ghosts (head-contract-linked retention and release) survive — find and price every head-contract-chained trigger.
• Risk should flow down proportionately to package economics; dispute forums should align across the chain.
• The Act is the floor the flow-down cannot drill through: subcontractors keep their own statutory payment rights regardless.

This article is general information only and is not legal advice. For advice on a specific contract or dispute, seek legal counsel or contact Sumit Consulting for commercial and claims advisory support.