Uncapped liquidated damages: the cap negotiation playbook

If you sign one uncapped clause this year, make sure it isn't this one. Liquidated damages at $2,000 a day with no ceiling turn a six-week delay — even one only partly yours — into an $84,000 exposure on a job you might have priced at $15,000 margin. The fix is boring and completely standard: an aggregate cap of 5–10% of the subcontract sum. The mystery isn't what to ask for. It's why so many subbies never ask.

This is the playbook for asking.

What LDs are actually for — and when they turn hostile

Liquidated damages replace an argument with a number. Instead of litigating what a delay actually cost, the parties pre-agree a daily or weekly rate, and everyone can price delay risk in advance. Used honestly, LDs are good for both sides — the subcontractor gets certainty too.

The clause turns hostile in two specific ways:

A rate that isn't a genuine pre-estimate. The rate is supposed to approximate the loss your delay would cause. When a roofing package carries the whole tower's delay cost, that's not an estimate — it's leverage.

No aggregate cap. A rate without a ceiling converts a routine commercial term into unlimited liability. Every other number in your contract is bounded — the price, the retention, the defects period. Delay liability shouldn't be the one exception, and on well-drafted contracts it isn't.

The flow-down trap

Most oppressive subcontract LD clauses aren't drafted from malice — they're flowed down. The head contract carries LDs sized for the whole project, and the head contractor passes the same rate (sometimes the same clause, photocopied) into every subcontract, regardless of scope.

Run the proportionality test: what fraction of the project is your package? If you're 5% of contract value carrying 100% of the daily delay rate, you're insuring a balance sheet twenty times your size. That framing — "our exposure should be proportional to our scope" — is the single most persuasive argument in this negotiation, because it's obviously fair and the alternative is obviously not. The same test applies to the indemnity clauses that usually sit a few pages away.

The three asks, in order

1. The aggregate cap. "Liquidated damages under this subcontract shall not exceed in aggregate [5–10]% of the subcontract sum." The 5–10% range is the widely used industry norm — commonly seen in negotiated subcontracts and recommended by construction lawyers on both sides of the table. Anchor at 5%, settle by 10%, and treat a flat refusal of any cap as information about how they expect the project to go.

2. Exclusive remedy. A cap you can drive a general-damages claim around isn't a cap. Ask for wording that makes LDs "the sole and exclusive remedy for delay" — otherwise a counterparty can take the capped LDs and pursue uncapped common-law damages on top, and you've negotiated a decoration.

3. The matching EOT regime. This is the one everyone forgets. The extension-of-time clause is the LD clause's off-switch: every day of extension is a day the LD clock doesn't run. A generous-looking cap next to a brutal EOT regime is still a trap. Check that every delay cause outside your control is a listed ground for extension — head contractor's own delays, other trades, late information, site access, weather per the contract's definition — and check the notice time bars on EOT claims. A 5-day time bar next to a heavy LD rate is one mechanism, designed as a pair: the rate does the damage, the time bar deletes your defence.

The counter-asks worth making

Delay damages running your way. If your delay costs them a daily rate, their delay should cost them something too: prolongation costs or delay damages payable when the program moves for reasons that aren't yours. Even a modest daily rate changes behaviour, because suddenly delay reporting runs in both directions.

Grace period. A short buffer (5–10 working days aggregate) before LDs start accruing filters out the noise-level delays that every project has and keeps the clause pointed at genuine slippage.

Early-completion bonus. Occasionally you can trade acceptance of a reasonable LD rate for a bonus at the same daily rate for early completion. It reframes the whole conversation from penalty to symmetry — and if they believe their own program, it costs them nothing.

The math, worked once

Put numbers on it, because the abstraction hides the sting. A $280,000 mechanical package on a job carrying $2,000-a-day LDs, priced at a healthy 12% margin: your expected profit is $33,600. Uncapped, seventeen days of delay — one late equipment delivery plus a fortnight of access problems that were only partly yours — wipes the entire margin. Day eighteen onwards, you're paying to be on the job. Now run the same numbers with a 10% cap: worst case is $28,000, painful but survivable, and you knew the floor of the deal before you signed it. That's the whole argument for a cap in two sentences: it doesn't make delay free, it makes your downside a number you can underwrite instead of a hole with no bottom.

While you have the spreadsheet open, sanity-check the daily rate itself: $2,000 a day against a $280,000 package annualises to more than the package is worth in twenty weeks. If the rate can consume the contract sum in a season, it was never a pre-estimate of anything.

What the law does and doesn't do for you

Don't count on statute here. Security-of-payment and prompt-payment legislation — the laws that void pay-when-paid clauses — protect the payment pipe, not the commercial allocation of delay risk. An LD rate with no cap is generally enforceable in all five markets ContractorCounter serves, provided it's a genuine pre-estimate rather than a penalty. The penalty doctrine (in its various local forms) is a last-resort court argument, not a negotiating plan: by the time you're arguing a clause is a penalty, you're already in the dispute you priced the job to avoid.

The one indirect statutory assist: in Western Australia (s 16 of its 2021 Act) and Victoria (s 13A, since April 2026), an unfair notice-based time bar can be declared of no effect — which matters because, as above, the time bar is often the mechanism that makes the LD clause bite. That's a shield for impossible notice windows, not a licence to skip notices.

Reading the clause in context

An LD clause can't be assessed on its own page. The exposure is the system: rate × cap (or no cap) × EOT grounds × notice time bars × your float in the program. Two contracts with identical LD rates can carry wildly different real risk once you read the four clauses together.

That's the reading ContractorCounter Review does in one pass — it flags the uncapped rate, the flow-down disproportion, the missing exclusive-remedy wording, and the time bars that pair with them, each with a severity grade and the specific ask to put in your return email. US$19 a contract, findings visible before you pay, and the full checklist covered while you make the coffee.

This article is general information, not legal advice. LD enforceability and the penalty doctrine vary by jurisdiction and contract — for significant exposure, get advice from a construction lawyer, ideally with the marked-up contract in hand.