How to Tell Liquidated Damages from an Unenforceable Penalty

An ops lead is one signature from a vendor MSA — a master services agreement the order form hangs on — because sales said delay damages will cover a late go-live. The sentence charges 1% of fees per day, labelled “penalty,” with no cap and no longstop. Courts in England and Wales test substance, not the heading. Knowing how to tell liquidated damages from an unenforceable penalty is a 25-minute hunt: name the delay, test the number, lock a cap and a longstop, then keep, reprice, or escalate.

In September 2026, Wren — Ops at a 20-person UK logistics firm — has Finance’s yes on a last-mile TMS vendor. Monthly fees £8,400. Clause 12.3: a penalty of 1% of the Fees per day until Go-Live is accepted. No definition of Fees. No cap. No longstop. The AE Slack: “Standard penalty — keeps us honest.” Last year’s carrier slip cost overtime and two missed retail windows he could not cleanly prove.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

What delay breach are you actually pricing — and why is actual loss hard to prove?

Write the trigger first: late Go-Live, a missed milestone, late delivery. Then write why actual delay loss is ugly to prove at signing — overtime, idle dock time, two missed retail windows with no clean invoice trail. Do that before anyone debates 1%. Do not treat “we have delay damages” as the hunt.

Freeze the packet — the MSA, order form, and any SLA exhibit (an attached schedule) you will actually sign. Start with the packet freeze walk. Circle trigger, rate, “penalty” or “liquidated damages,” cap, longstop. If Fees is silent, write “denominator silent.” Fenwick Elliott: delay LD is a secondary obligation; challenge a rate that is not commensurate with delayed completion before execution. Do: write “hard to prove because ___.” Don’t: skip the breach and start at the percentage.

How do you test 1% of fees against the worst plausible harm?

Circle 1% of which Fees. Wren’s monthly £8,400 is £84 a day. The same 1% of about £100,800 a year is about £1,008 a day — a year of fees in about 100 days. That second reading is the scare figure, not a genuine pre-estimate of loss.

The Supreme Court in Cavendish / ParkingEye [2015] UKSC 67 (4 November 2015) did not abolish the penalty rule. For England and Wales: does a secondary obligation impose a detriment out of all proportion to a legitimate interest in performance? For a straightforward delay clause, that interest will rarely extend beyond compensation — A&O Shearman. Wren is a 20-person buyer on vendor paper, not an advised share sale. Compare the open-ended run to harm that was plausible at signing. Calcbee colour is 0.5–2% per week with a 15–25% cap — not 1% per day uncapped. Do: run monthly and annual readings, then a 100-day multiply. Don’t: accept “1% a day is market.”

How do you lock a daily rate, a cap, and a longstop?

A daily or weekly rate that scales with delay is only half the mechanic. Without a cap and a longstop, the clock can run until acceptance or until someone terminates. Wren has neither. Do not accept “1% per day until we accept” with no ceiling.

Triple Point [2021] UKSC 29 (16 July 2021): delay LD exists because proving loss is intractable and because the clause also limits open-ended exposure. Write whether the clock stops on acceptance, termination, or a date. EPC colour — Pathnovo 0.1–0.5%/day, usually capped at 5–10%; Ashurst on Steria 0.25%/week, cap 10% — is contrast, not a Checkory rate. If you reprice, say whether the cap is LD-only or also general delay damages (Taylor Wessing). Do: three ticks — rate, cap, longstop. Don’t: treat the daily rate as enough.

Should you strike “penalty” and keep a short rationale recital?

Strike the word “penalty.” Keep a short recital that delay loss is hard to quantify and that the rate is a genuine pre-estimate / not out of all proportion to on-time go-live. The label is not the case. A “not a penalty” sticker does not save a scare figure.

Walker Morris (18 March 2026) on GPP Big Field: sums described as “the penalty” were not determinative. That paper also had a £250,000/MWp maximum. Wren has the label and no cap. A genuine-pre-estimate recital is evidence, not a cure. Keep the calc that produced the number. For example, a proportionate capped daily rate can still be LD even if someone typed “penalty.” Do: strike the word and keep the recital. Don’t: leave “penalty” because “a court will cut it.”

Is delay LD the sole remedy, or stacked with service credits?

One sentence, then stop. If LD is the sole monetary remedy for this delay, that is a certainty trade: you get the stipulated sum without proving loss, and you may give up actual delay damages. If the same miss also triggers SLA credits, mark exclusive versus cumulative so you do not double-recover.

If the fight is the SLA credit table, that is a different hunt — open the SLA service-credits checklist. Do not convert 99.9% here. Do: mark exclusive vs cumulative for this delay. Don’t: stack LD, actual delay damages, and credits on the same miss.

When do you keep, reprice, or escalate?

You are done when you can fill one page and point to one sentence that would pause signature. “We have delay damages” is not that sentence if the paper says “penalty,” 1% of undefined fees per day, and no cap. In practice: named breach → number vs worst harm → rate + cap + longstop → strike “penalty” + recital → sole vs stacked → keep / reprice / escalate.

Keep a named trigger, a rate tied to plausible harm, cap + longstop, “penalty” gone, and a short recital. Reprice silent Fees, 1%/day of annual fees, or a missing ceiling. Escalate the scare figure or LD plus actual damages plus credits on the same miss. Then counsel — a qualified lawyer, not a chatbot — reads that sentence. A first-pass — a machine pass that extracts clauses before a human reads every page — is not a green light.

After that log: upload the same MSA PDF to Checkory document analysis. Checkory is a first-pass legal AI: flags land on that file. A human still opens every High flag — a high-severity item a human must verify — the rate and the denominator.