Liquidated Damages vs Penalty Clauses: What Courts Enforce

Liquidated damages or penalty: the short answer A liquidated damages clause sets, in advance, the amount one party will pay the other if a specific breach happens, for example a fixed sum per day of delay. A penalty clause does the same thing mechanically, but the amount is set to punish or frighten a party into performing rather than to compensate for likely loss. The distinction matters because courts treat the two very differently. Broadly, a genuine pre-estimate of loss is enforced, while a sum that is really a threat is cut down or struck out. But the exact test varies by jurisdiction, and India follows a different rule from the common-law world. This is general information, not legal advice; the right wording depends on the contract and where it will be enforced. ## The position in India (Section 74, Contract Act) India does not keep the sharp English line between liquidated damages and penalties. Section 74 of the Indian Contract Act, 1872 says that when a contract names a sum to be paid on breach, the party who suffers the breach is entitled to reasonable compensation not exceeding the named amount, whether or not actual damage is proved. Two points follow: - The named figure is a ceiling, not an automatic entitlement. A court awards what is reasonable, up to that cap.

• You generally still need to show loss. In Fateh Chand v Balkishan Das (1963) and Maula Bux v Union of India (1969), the Supreme Court held that reasonable compensation must be assessed, and a party cannot recover a sum far beyond proven loss just because it is written in the contract. Where actual loss is genuinely difficult to prove, courts have accepted the contractual figure as a reasonable measure. In ONGC v Saw Pipes (2003) the Court upheld a pre-agreed amount where loss was hard to quantify and the sum was a genuine estimate. In Kailash Nath Associates v DDA (2015) the Court restated the rule: Section 74 awards reasonable compensation, actual loss is the usual touchstone, and no compensation is due where no loss flows from the breach. Practical takeaway for India: a named sum helps, but write it as a genuine estimate, keep a record of how you reached it, and expect a court to look at real loss. ## The common-law position (UK) English law historically distinguished a liquidated damages clause (a genuine pre-estimate of loss, enforceable) from a penalty (enforceable only up to actual loss). The classic test came from Dunlop Pneumatic Tyre v New Garage (1915). In 2015 the UK Supreme Court reformulated the rule in Cavendish Square Holding v Makdessi and ParkingEye v Beavis. The modern question is not simply whether the sum is a pre-estimate, but whether the clause imposes a detriment out of all proportion to the innocent party's legitimate interest in enforcing the obligation. A clause that protects a real commercial interest can stand even if it is not a precise forecast of loss. ## The position in the United States US law, drawing on the Uniform Commercial Code and the Restatement (Second) of Contracts, enforces a liquidated damages clause if the amount is reasonable in light of the anticipated or actual loss and actual damages are difficult to prove. A sum that is unreasonably large is treated as an unenforceable penalty. The framing is close to the Indian emphasis on reasonableness. ## How to draft a clause that is likely to be enforced 1. Estimate genuinely. Base the figure on a real forecast of likely loss (lost revenue, cover costs, idle resources) and keep the working.

2. Tie it to a specific breach. A per-day delay charge or a fixed sum for a defined failure reads better than a blanket number for any breach.
3. Avoid the word penalty. Labels are not decisive, but calling it a penalty invites challenge. Use liquidated damages or agreed compensation.
4. Make it proportionate. A graduated scale (per day, per unit) usually looks more reasonable than one large lump sum.
5. Address the cap and sole-remedy question. Say whether the sum is the exclusive remedy or whether other damages are also available, and how it interacts with any overall liability cap.
6. Keep records. If challenged, contemporaneous notes on how you built the estimate are valuable, especially in India where reasonableness is assessed. ## A sample clause (illustrative only) > If the Supplier fails to deliver by the Delivery Date, the Supplier shall pay the Customer liquidated damages of INR [amount] for each day of delay, up to a maximum of [percentage] of the Contract Price. The parties agree this is a genuine pre-estimate of the loss likely to be suffered and not a penalty. This remedy is [the Customer's sole remedy / without prejudice to other remedies] for delay. Adapt the wording to your contract and take advice on the governing law before relying on it. ## When these clauses help, and their limits Liquidated damages give both sides certainty, avoid an expensive fight about proving loss, and signal where the risk sits. Their limit is that a figure set too high can be read down (India, US) or struck as disproportionate (UK), while a figure set too low can cap your recovery below your real loss. Set the number with the same care you give the price. ## Where a contract workspace helps The work above is repetitive across a portfolio: setting a proportionate figure, keeping the genuine-estimate reasoning on record, and making sure a damages clause does not quietly contradict the liability cap three pages later. Drafting a liquidated damages clause, reviewing it so the number stays in line with the liability cap, tracking the reasoning behind each figure and governing how the clause reads across every contract can sit in one AI workspace tuned to how your company contracts. Adira is a workspace built for that. This guide alone equips you to judge a liquidated damages clause; a single workspace keeps that judgement consistent across every contract you sign.