Penalty Clauses: Why Yours Is a Ceiling, Not a Hammer

There is a clause in nearly every Pakistani construction contract, supply agreement, and share purchase agreement that its drafter fundamentally misunderstands. It says something like: "In the event of delay, the Contractor shall pay liquidated damages of 0.5% of the contract price per week, up to a maximum of 10%." The party that inserted it believes it holds a hammer — breach occurs, the sum falls due, end of discussion. Pakistani law says otherwise. Under section 74 of the Contract Act 1872, that figure is a ceiling on what a court may award, and what the court awards within the ceiling is "reasonable compensation," assessed by the judge. This briefing, stating the law as of July 2026, explains how the doctrine works, why the English cases your counterparty quotes do not govern, and how to draft a clause that survives contact with a courtroom.

What section 74 actually says

Section 74 provides that when a contract is broken, and a sum is named in the contract as the amount payable on breach — or the contract contains "any other stipulation by way of penalty" — the innocent party is entitled to receive reasonable compensation not exceeding the amount named, whether or not actual damage is proved to have been caused. The section was drafted deliberately to cut through a distinction that was, even in the 1870s, generating litigation in England: the line between a "liquidated damages" clause (a genuine pre-estimate of loss, enforceable as written) and a "penalty" (a sum designed to terrorise performance, struck down). Section 74 abolishes the need to draw that line at the threshold. Every stipulated sum, whatever its label, goes into the same statutory machine: the court asks what compensation is reasonable, and the named figure operates as the upper limit.

Three consequences follow, and each one surprises commercial parties.

First, labels do not save you. Calling the clause "liquidated damages" or reciting that the parties "agree this is a genuine pre-estimate of loss" does not entitle you to the sum. The recital helps — more on that below — but the court's jurisdiction to award less is statutory and cannot be drafted away.

Second, the phrase "whether or not actual damage or loss is proved" means less than it appears to. Pakistani courts, following a line of authority from the superior courts, have read section 74 to require proof of loss in the ordinary case: the plaintiff must still establish that it suffered legal injury, and the named sum only relieves it of proving the precise quantum. The dispensation from proof operates mainly in cases where loss is real but inherently difficult to measure — delayed completion of a home, breach of a confidentiality undertaking, loss of market position [leading authorities, including Supreme Court precedent on proof of loss under s.74 — CITATIONS TO BE VERIFIED BY REVIEWING LAWYER]. A claimant who marches into court with the clause, no evidence of harm, and an invoice for the full stipulated amount should expect to leave with little.

Third, the ceiling works in only one direction. If your actual loss exceeds the named sum, you are still capped at it. The stipulated figure is simultaneously the most the court can award and no guarantee of anything. That asymmetry is the single most important thing to hold in mind when you set the number.

The section contains one true exception: its explanation deems a stipulation for increased interest from the date of default capable of being a penalty, and a separate carve-out addresses bail bonds and similar bonds given to the government for the performance of a public duty, where the full sum is recoverable. Neither helps commercial parties.

Why English penalty law does not decide your case

Counterparties — especially foreign ones — routinely argue Pakistani liquidated damages disputes through English authority: the classic four tests in Dunlop v New Garage (1915), or the reformulated "legitimate interest" standard of Cavendish Square v Makdessi (2015). Pakistani courts read these cases and sometimes cite them, but the analytical frame is different. In England the question is binary — penalty or not — and a clause that passes is enforced in full without proof of loss. In Pakistan the statute has already collapsed that inquiry: everything is potentially a penalty, nothing is automatically enforceable in full, and reasonableness is assessed on the facts at the remedy stage. The practical difference is stark. Under English law, good drafting can buy you certainty. Under section 74, good drafting buys you a strong evidentiary position — but the judge always holds the pen on the final number.

This also means the mirror-image mistake is common. Parties resisting a claim assume the clause is worthless because "penalties are unenforceable in Pakistan." Also wrong. The clause fixes the ceiling, signals the parties' own assessment of likely loss, and — where loss is genuinely hard to quantify — can support recovery of the full amount. Courts have awarded stipulated sums in their entirety where the pre-estimate was honest and the loss, though real, resisted precise calculation [TO BE VERIFIED BY REVIEWING LAWYER].

Drafting a genuine pre-estimate that a court will respect

Since the court will ask what compensation is reasonable, the drafting objective is to make your stipulated figure the most persuasive answer available to that question. That is an evidence problem as much as a wording problem, and it is solved at signing time.

Show your arithmetic. The most effective single step is a contemporaneous record of how the number was built: financing costs per week of delay, standby charges for idle equipment and staff, revenue lost per day the facility is not operating, the price differential a replacement supplier would charge. Put the methodology in a schedule or at least in the deal file. A figure with visible workings reads as a pre-estimate; a round number reads as a threat.

Scale the remedy to the breach. Per-day or per-week rates tied to the length of delay, tiered percentages tied to shortfall in delivered quantity or performance, and an overall cap all signal calibration. A clause that levies the same lump sum for a one-day delay and a one-year delay advertises itself as a penalty and invites the court to discount deeply.

Match the trigger to real loss. Attach the LD regime to breaches that actually cause the estimated loss — delayed completion, missed output guarantees, failed availability — rather than to "any breach of this Agreement." Blanket triggers destroy the pre-estimate logic because no single figure can genuinely estimate the loss from every conceivable breach.

Decide, and state, whether the sum is exclusive. If LDs are meant to be the sole remedy for the delays they cover, say so; the certainty cuts both ways and is usually worth having. Preserve general damages for breaches outside the regime, and preserve termination rights when delay passes the cap — otherwise the counterparty may treat the capped LDs as a licence to keep failing at a known price.

Handle the interplay with section 73. Where no sum is stipulated, section 73 governs and requires proof of loss flowing naturally from the breach. Your LD clause should be drafted knowing the fallback: if the clause is discounted, your recovery reverts to what you can prove, so keep proving-loss machinery — records of costs incurred during delay, contemporaneous notices — running throughout the project regardless of the clause.

Do not confuse LDs with other tools. Forfeiture of earnest money and encashment of performance guarantees raise related but distinct questions — courts have applied section 74 reasoning to forfeitures beyond a reasonable amount [TO BE VERIFIED BY REVIEWING LAWYER] — and bank guarantees are typically honoured on demand with the section 74 argument fought afterwards in recovery proceedings. Structure security consciously rather than assuming it behaves like the LD clause.

The LD-clause drafting checklist

• Basis recorded — A written, dated calculation of expected loss per unit of delay or shortfall exists in the deal file or a contract schedule.
• Graduated rate — The sum scales with the severity or duration of the breach (per day/week, tiered by shortfall).
• Overall cap — A stated maximum, with a termination right once the cap is reached.
• Specific triggers — LDs attach to defined breaches whose loss was estimated, not to any breach generally.
• Recital of pre-estimate — The parties record that the figure is a genuine pre-estimate of likely loss and why quantification is difficult.
• Sole-remedy statement — The clause says whether LDs exclude general damages for the covered breaches, and preserves remedies for other breaches.
• Extension-of-time machinery — Delay caused by the claiming party or by defined events suspends LDs; otherwise the clause fails for causation.
• Interest and default charges reviewed — Any increased-interest-on-default provision checked against s.74's explanation.
• Security instruments aligned — Earnest money, retention, and guarantees sized and drafted with the reasonable-compensation principle in mind.
• Evidence habit — The project team logs actual losses during any breach period, so the reasonableness case is ready if the clause is challenged.

What this means for you

Set your stipulated sum expecting to justify it, not merely to invoke it — under section 74 the number you name is the most you will ever recover and the beginning, not the end, of the argument about how much you actually get. Preserve the workings behind the figure, scale it to the breach, and keep proving your real losses while the project runs, because the fallback position is always section 73 and evidence. When you are on the paying side, do not concede the full amount reflexively: reasonable compensation is the standard, and a well-documented case that actual loss was lower routinely reduces the award. Before your next contract goes out with a boilerplate LD clause, have it read against this framework — the questions our commercial contracts practice asks first are where the number came from and what the file shows, because that is precisely where the court will start.