Liquidated Damages

Definition

Liquidated damages (LDs) are a pre-agreed sum, specified in the contract, that a contractor must pay the owner for each day (or week) of delay beyond the contractual completion date. LDs substitute for the owner's obligation to prove actual loss in court. The mechanism only works if the pre-agreed sum is a genuine pre-estimate of loss; a sum that is grossly excessive can be struck out by the courts of most jurisdictions as a penalty rather than as liquidated damages.

Legal Anchor

The distinction between an enforceable LD clause and an unenforceable penalty clause has been established in English common law for over a century and travels — with variations — into most legal systems descended from it. The leading modern English authority is Cavendish Square Holding v El Makdessi [2015], which updated the test to focus on whether the sum protects a legitimate commercial interest and is not disproportionate. In civil-law jurisdictions the mechanism is often called "contractual penalty" and courts retain a power to reduce excessive amounts. In every jurisdiction, the contractor who agreed the number is presumed sophisticated and bound by it, absent clear evidence of penalty.

How to Set the Number

• Owner's daily loss from late completion — lost revenue, extended financing, holding costs.
• Genuine pre-estimate, not maximum plausible — a stretch calculation invites challenge.
• Documented at contract signing — the calculation should be retained.
• Capped — usually 5–15% of contract value in total.
• Coupled with EOT provisions — an LD without an extension-of-time mechanism is contractually unstable.

Real-World Construction Example

A shopping-centre developer specified LDs of $65,000 per day beyond the contractual completion date. The number was based on modelled net rental income across the anchor tenants, plus extended construction financing. Total cap: 8% of contract value. The main contractor delivered 47 days late. Of those, 22 days were granted as EOT for weather and utility delays outside the contractor's control; 25 days were the contractor's responsibility. LDs applied: 25 × $65,000 = $1.625m. The number stood up in the eventual settlement because the developer produced the original calculation and the underlying tenant leases. Had the developer chosen $150,000 per day as an intimidation tactic, the LD clause would probably have been struck out and the developer's recovery would have depended on the harder path of proving actual loss.

Real-World IT / Agile Example

LDs are less common in software contracts but appear in enterprise deals with hard business dates — regulatory launches, national rollouts, tax-year go-lives. A revenue authority contract specified LDs of £45,000 per business day of delay beyond the mandated go-live date, backed by the modelled cost of extending legacy systems. The clause survived challenge in the final settlement because it was tied to a documented cost, and the vendor paid four days of LDs after a controlled slip. The clause's real value was behavioural — it forced hard prioritisation decisions eight months before the go-live date, when there was still time to descope.

Best Practices

• Retain the calculation document at contract signing.
• Set the number as a genuine pre-estimate of loss, not a maximum figure.
• Cap total LDs (5–15% of contract value).
• Couple LDs with a working EOT mechanism and a clear notice-of-delay procedure.
• Review LD triggering carefully — apply promptly and consistently, or the mechanism weakens.

Common Mistakes

• Setting the number too high, inviting a penalty challenge.
• No calculation record; hard to defend under challenge.
• Weak EOT mechanism; the contractor can argue every delay is excusable.
• Owner does not apply LDs when triggered, then tries to apply them selectively later — courts view inconsistent enforcement unfavourably.
• Confusing LDs with general damages; if the LD cap is reached, most contracts prevent the owner claiming further delay damages.

Expert Tips

• Keep the calculation clean. One page, one spreadsheet, one signed cover memo. That single document decides most disputes.
• Distinguish delay LDs from performance LDs. Late completion and under-performance are different clauses; conflating them creates ambiguity.
• Prime the market before setting. LDs so high that reputable contractors will not bid are counterproductive.
• Automate the trigger. Apply LDs the day after contract completion with formal notice; do not negotiate on the fly.
• Do not weaponise. LDs work as an ordinary commercial mechanism; treating them as a stick invites litigation and damages relationships.

Practical Lessons Learned

• The biggest determinant of LD survivability under challenge is the quality of the pre-estimate documentation at signing.
• Contracts that pair LDs with clean EOT mechanisms settle disputes faster and cheaper than either mechanism in isolation.
• Owners who apply LDs consistently early in a contract's life encounter far less late-project drama than owners who "hold off to keep the relationship warm" — the LDs later feel arbitrary.

Key Takeaways

• LDs substitute for proving actual loss, provided they are a genuine pre-estimate.
• Retain the calculation document at signing — it decides most future disputes.
• Cap the total; couple with a working EOT mechanism.
• Apply consistently and promptly; inconsistent enforcement weakens the clause.
• Excessive LDs risk being struck out as penalties in most jurisdictions.

Related Encyclopedia Entries

• Extension of Time
• Change Order Management
• Milestone Payment
• Retainage

Related Research Articles, Case Studies & Tools

• LD Calculation Template
• Project Controls Academy: Contracts
• Shopping-centre LD case study
• Enforceability of LD clauses