Consequential vs liquidated damages: which one you need

Consequential vs liquidated damages at a glance

Dimension	Consequential damages	Liquidated damages
What it is	A category of indirect loss caused by a breach	A pre-agreed dollar amount payable on a defined breach
When set	Determined after the breach, by evidence	Fixed in advance, when the contract is signed
Core question	Which losses can be recovered	How much is owed, without proving actual loss
Typical examples	Lost profits, lost customers, reputational harm	Fixed sum per day of delay, flat fee for a missed milestone
How measured	Proven with records and expert testimony	Read directly from the clause
Governing standard (US)	Foreseeability at contracting (Hadley v. Baxendale; UCC 2-715)	Reasonable forecast of harm, not a penalty (Restatement (Second) of Contracts 356; UCC 2-718)
Main enforceability risk	Cut off by a consequential damages waiver	Struck down as an unenforceable penalty
Who carries the burden	The party claiming the loss	Little to prove once the breach is shown
Where it lives	Limitation of liability, exclusions	A dedicated liquidated damages clause

The key differences

They sit on different axes. Consequential damages describe a type of harm: losses that do not flow directly and immediately from the breach but arise from the injured party’s particular circumstances. Liquidated damages describe a method: a number the parties agree to in advance so nobody has to prove the loss later. A single contract can, and often does, contain both a liquidated damages clause and a separate waiver of consequential damages, aimed at two different problems.

Timing and proof. Consequential damages are backward looking. After a breach, the claimant has to show the loss was foreseeable when the contract was formed and then prove the amount, often with financial records or expert analysis. Liquidated damages are forward looking. The parties estimate the likely harm at signing and lock in a figure, so on breach the calculation is already done.

A quick example. A supplier delivers a custom machine two weeks late. A liquidated damages clause of a set amount per day of delay pays out on the delay alone, with no proof of loss required. A claim for consequential damages would instead require the buyer to show the late delivery foreseeably idled a production line and to document the lost output, which is slower, costlier, and easier for the other side to contest.

Enforceability works differently. A liquidated damages clause is enforceable in the US only if it was a reasonable estimate of anticipated harm and actual damages were difficult to calculate at the time of contracting; if the amount looks punitive, a court can void it as a penalty. The specific test and how strictly courts apply it vary by state and by whether the UCC governs. Consequential damages face a different gate: they are recoverable only if foreseeable, and they are frequently excluded outright by a mutual waiver.

The interaction is where deals go wrong. Parties often intend a liquidated damages clause to be the exclusive remedy for a given failure, replacing any claim for consequential loss. If the drafting does not say so, a counterparty may argue it can collect the liquidated sum and also pursue consequential damages. Conversely, a broad consequential damages waiver can accidentally gut a remedy the business was counting on. These clauses have to be read together, not in isolation.

Caps and carve-outs. Consequential damages are commonly capped or excluded, sometimes with carve-outs for indemnities, confidentiality breaches, or IP infringement. Liquidated damages are themselves a cap of sorts, because they fix the number, but they can also sit under a separate aggregate liability cap. Confirm whether the liquidated amount counts toward or sits outside that overall cap.

Which one to use, and when

Reach for liquidated damages when the harm from a specific breach is real but hard to quantify in advance, and both sides want certainty. Classic cases are late delivery in a construction or supply contract, missed service levels, or a delayed closing, where a per-day or per-event figure keeps disputes short. The figure has to be a genuine estimate, not a threat, or it will not survive a challenge.

Focus on the consequential damages allocation when the concern is open-ended downstream loss: a software outage that halts a customer’s operations, a component failure that stops a production line, or a data issue that costs a client its own customers. Here the negotiation is usually about excluding or capping that exposure, and about which carve-outs escape the exclusion.

Before signing, map both. Confirm whether a liquidated damages clause is the sole remedy or stacks with other claims, whether the consequential damages waiver is mutual, and whether either interacts with the overall liability cap. This is the kind of cross-clause review where PactAI’s exposure analysis and conflict detection help: they surface where a remedy clause and a waiver point in different directions, and score the residual risk 0-100 so the numbers are visible before signature, not after a breach.

Decision rule: if you want a fixed number you do not have to prove for a specific failure, negotiate a liquidated damages clause and confirm it is the exclusive remedy; if you want to contain uncertain, open-ended downstream loss, negotiate the consequential damages waiver and its carve-outs. They are not substitutes, so on a high-value contract, get both right.