Liquidated Damages Clause: Enforceable Estimate or Penalty

A liquidated damages clause fixes in advance the dollar amount one party owes for a specific breach, so neither side has to prove actual losses in court. It is enforceable only if it is a reasonable estimate of the harm, and courts give more room when the harm is hard to measure; if it looks like a threat designed to force performance, courts call it a penalty and refuse to enforce it. The line between the two is the entire game, and it turns on how the clause is drafted and what the parties knew when they signed.

Reviewed and corrected on 12 October 2026. This is general information, not legal advice; check the cited statute or opinion before relying on it. The rates and negotiating positions on this page are drafting practice, not legal rules.

TL;DR

• A liquidated damages clause sets a predetermined sum for a defined breach (a late delivery, a missed SLA, a departing employee taking clients), so the non-breaching party recovers without proving actual damages.
• It is enforceable only as a reasonable estimate of the harm, and courts allow more latitude when the harm is hard to measure. If the amount is disproportionate to any plausible loss, courts strike it as a penalty.
• A workable drafting habit: tie the number to a real metric (per-day delay cost, per-record breach cost) and document the reasoning, rather than picking a round scary number.
• A valid liquidated damages clause is usually the exclusive remedy for that breach. If the clause also lets the non-breaching party sue for actual damages, courts in some states read it as a penalty (the Florida Supreme Court did in Lefemine v. Baron, and a New York appellate court did in 2017 for a clause that added the sum to actual damages).
• The most common review miss is a single liquidated sum for breaches of wildly different severity, which is the classic signature of an unenforceable penalty.

What a liquidated damages clause actually does

A liquidated damages clause does two things, and both have to hold for it to work.

1. It pre-sets the recovery. Instead of litigating actual losses after a breach, the parties agree now on what the breach is worth. This is valuable when damages are real but genuinely hard to prove: lost goodwill, business disruption, the cost of a delayed launch.

2. It allocates and caps risk. Both sides price the breach into the deal. The breaching party knows its exposure; the non-breaching party knows its floor and ceiling. That certainty is the legitimate purpose courts protect.

What it cannot do is punish. US law lets parties estimate damages, not impose penalties. A clause that sets a number far above any plausible loss is treated as in terrorem (a threat to compel performance), and the courts we read will not enforce it. The clause then falls away and the non-breaching party is left to prove actual damages, as in Lake River Corp. v. Carborundum Co., 769 F.2d 1284 (7th Cir. 1985), where Judge Posner held a minimum-guarantee formula a penalty "because it is designed always to assure Lake River more than its actual damages" and observed that if the formula was invalid Lake River "still is entitled to any actual damages caused by Carborundum's breach."

The most widely cited test is Restatement (Second) of Contracts section 356(1), a treatise that is persuasive rather than binding. As the Arizona Supreme Court quotes it in Dobson Bay Club II DD, LLC v. La Sonrisa de Siena, LLC, 242 Ariz. 108 (2017), damages may be liquidated "but only at an amount that is reasonable in the light of the anticipated or actual loss caused by the breach and the difficulties of proof of loss." The court read that as one reasonableness question with two factors, the loss and the difficulty of proving it, and said whether an amount is a penalty "turns on the relative strengths of these factors." The Restatement comment (comment b, as Dobson Bay labels it), quoted in Marcam Mortgage Corp. v. Black, 686 P.2d 575 (Wyo. 1984), says: "If the difficulty of proof of loss is great, considerable latitude is allowed in the approximation of anticipated or actual harm. If, on the other hand, the difficulty of proof of loss is slight, less latitude is allowed in that approximation." Some states state a stricter two-part rule that treats difficulty of estimation as a separate requirement (California's Civil Code section 1671(d), for retail consumer contracts and dwelling leases, is an example), so check the forum.

Why it matters: the dollars at stake

Consider a construction-style services contract with a $2M value and a hard go-live date. The customer adds a liquidated damages clause for late delivery.

This is an illustrative example. Assume the real cost of a one-month delay is roughly $40,000 (idle staff, lost early revenue, extended overhead).

• A clause set at $1,500 per day of delay (about $45,000 a month) tracks the actual harm. A court is more likely to treat it as a reasonable estimate, and the customer recovers without proving the loss.
• A clause set at $50,000 per day (about $1.5M a month) dwarfs any plausible loss. A court is likely to call it a penalty and refuse to enforce it, leaving the customer to prove actual damages from scratch.

Same delay, same contract. The reasonable clause pays out cleanly; the greedy one is worth nothing and forces full litigation. Overreaching on the number is how a liquidated damages clause becomes self-defeating.

Who wants what

The tension: the drafting party wants a big, simple number; the exposed party wants a defensible number that will actually survive a challenge. Ironically, the exposed party's position often protects the clause, because a defensible number is an enforceable one.

Market-standard language

A typical liquidated damages clause for late performance reads close to this:

LIQUIDATED DAMAGES.

The parties acknowledge that the actual damages Customer would suffer
from late delivery are difficult to ascertain as of the Effective Date.
Accordingly, if Provider fails to achieve Go-Live by the Target Date,
Provider will pay Customer liquidated damages of $1,500 for each day of
delay, up to a maximum of $135,000. The parties agree that this amount
is a reasonable estimate of Customer's probable loss and not a penalty.
These liquidated damages are Customer's sole and exclusive monetary
remedy for delayed delivery, and are not a forfeiture or penalty.

The recitals are evidence, not a requirement. The Seventh Circuit rejected the argument that a clause is invalid unless it recites that damages are hard to estimate (XCO International Inc. v. Pacific Scientific Co., 369 F.3d 998 (7th Cir. 2004)). A recital still shows the court how the number was set, and a court will test the substance either way, so a label or a recital is unlikely to rescue a number that has no link to the loss.

The number itself needs a paper trail. Courts protect figures the parties can trace to something real: a rental or financing cost per day, revenue lost per week of delay, notification and remediation cost per breached record. Keep the worksheet that produced the number; it is the evidence that the amount was a forecast rather than a threat.

The negotiation: standard, fallback, walk-away

Treat the amount, the exclusivity, and the cap as separate trades.

The cleanest version is a per-unit rate (per day, per record, per missed milestone) with a sensible cap and clear exclusivity. That structure both tracks real harm and reads as an estimate rather than a threat.

Common carve-outs / variations

Liquidated damages show up in several recurring shapes:

• Delay damages. Per-day amounts for missed delivery or go-live dates. The most common and most tested form.
• SLA service credits. Capped credits for missed uptime or response targets, usually styled as the customer's exclusive remedy for that miss. Whether a court analyzes a service credit as liquidated damages or as a price adjustment depends on how the credit is written and the governing law, which we did not verify. See the service level agreement clause.
• Data-breach liquidated amounts. A fixed sum per affected record. Defensible if tied to real per-record notification and remediation cost.
• Non-solicit and non-compete buyouts. A set fee if a departing employee or a party breaches a restrictive covenant. Whether a court treats the fee as liquidated damages or a penalty depends on the state and the facts. We did not survey these cases.
• Carve-back to actual damages. Some clauses let the non-breaching party elect actual damages instead of LDs for serious breaches, drafted carefully so the LD is not read as a sham. Note the jurisdiction risk below: an open election can undermine the clause in some states.

Two structural carve-outs decide whether a delay-based clause is fair, and both belong on your review pass:

Extension of time (excusable delay). The paying party should not accrue liquidated damages for delay it did not cause. A well-drafted clause stops the clock for owner or customer-caused delay, force majeure, and other excusable events. Without it, a per-day rate becomes a penalty for events outside the promisor's control. This is where the clause meets force majeure: the two have to line up on what counts as excusable.

Concurrent delay and apportionment. When both sides contribute to the same delay, an apportionment provision divides responsibility instead of charging the full per-day rate to one party. If the clause is silent, the question is left to the governing law, so the exposed party should ask for apportionment expressly.

A graduated fallback that survives scrutiny often reads:

For each full day Provider fails to meet the Uptime Commitment below
the applicable threshold, Customer will receive a service credit equal
to 5% of the monthly fee per percentage point below target, up to 100%
of that month's fee. Service credits are Customer's sole and exclusive
remedy for failure to meet the Uptime Commitment.

Jurisdiction and enforceability notes

Courts in the states we reviewed enforce liquidated damages that are a reasonable estimate of the loss and refuse penalties, but the test and its strictness vary.

• The reasonableness test. The states we read ask whether the amount is a reasonable estimate of the loss, and many treat difficulty of estimation as a requirement or a factor. They differ on timing. The Massachusetts Supreme Judicial Court tests the clause at contracting (the "single look") and noted that "[c]ourts are divided between the single and second look approach" (Kelly v. Marx, 428 Mass. 877 (1999)). The Arizona Supreme Court accepts either measure: the amount is reasonable if it approximates "either the loss anticipated at the time of contract creation (despite any actual loss) or the loss that actually resulted" (Dobson Bay).
• Sale of goods. Under the uniform text of UCC section 2-718(1), damages may be liquidated "only at an amount which is reasonable in the light of the anticipated or actual harm caused by the breach, the difficulties of proof of loss, and the inconvenience or nonfeasibility of otherwise obtaining an adequate remedy. A term fixing unreasonably large liquidated damages is void as a penalty." Check the version your state enacted.
• California. Civil Code section 1671(b) flips the usual burden for contracts other than retail consumer purchases or rentals and dwelling leases (those fall under subdivision (d), which voids the clause unless damages would be impracticable or extremely difficult to fix): a liquidated damages provision "is valid unless the party seeking to invalidate the provision establishes that the provision was unreasonable under the circumstances existing at the time the contract was made." Commercial LDs start out presumptively enforceable, and the challenger has to prove otherwise.
• Florida and New York on a second route to actual damages. In Lefemine v. Baron, 573 So. 2d 326 (Fla. 1991), the Florida Supreme Court held that a real estate contract failed as a liquidated damages clause because it gave the seller the option either to retain the deposit as liquidated damages or to sue for actual damages; the court said the option "indicates an intent to penalize the defaulting buyer." A New York appellate court held in 2017 that a $5,000-a-day clause was an unenforceable penalty where the agreement also gave the plaintiff a remedy for the whole extent of its injury "in addition to" the daily sum (555 West John Street, LLC v. Westbury Jeep Chrysler Dodge, Inc., 2017 NY Slip Op 02769 (2d Dep't Apr. 12, 2017)). That case involved a sum stacked on top of actual damages rather than a choice between the two, and we did not locate a New York Court of Appeals decision on either point.
• Penalty doctrine. The courts we read refuse to enforce penalties. A clause that overshoots plausible loss, or that stacks the sum on top of actual damages, risks being struck entirely, not just reduced.
• Exclusive remedy. A valid liquidated damages clause is usually the exclusive remedy for that breach. Reserving the right to also pursue actual damages can undermine the clause's character as an estimate.

This page is general information, not legal advice. The penalty test differs by state and turns on the facts, so check the controlling law before relying on a number. For a state-by-state view, see our guide on liquidated damages enforceability by state.

Review checklist: red flags to catch

• A round, large lump sum with no link to any per-unit or documented loss metric.
• The same amount applies to breaches of very different severity, the classic penalty tell.
• The clause lets the non-breaching party recover LDs plus actual damages for the same breach, or reserves an election between them (an election was fatal to the clause in Florida's Lefemine, and a New York appellate court struck a clause that stacked the sum on actual damages, as described above).
• No cap on per-day or per-incident accrual, so the total can run far past any real loss.
• No extension-of-time or excusable-delay carve-out, so LDs run during delay the paying party did not cause.
• Missing recitals that damages were hard to estimate and the amount is a reasonable forecast.
• The clause is labeled a "penalty" or a "forfeiture" on its face, which invites a court to treat it as one.
• A one-sided liquidated damages clause when the breach could be caused by either party.
• The LD is swept into a consequential-damages waiver or general liability cap with no carve-out, so if the LD is struck there is no fallback to actual damages.

How it interacts with other clauses

A liquidated damages clause sits among the remedy provisions; read it with:

• Limitation of liability: decide whether the general cap limits the liquidated sum or the LD stands outside it. If a consequential-damages waiver would also bar actual damages, carve the LD breach out so a struck clause still leaves a remedy.
• Service level agreement: SLA credits are liquidated damages and follow the same penalty rules.
• Indemnification: confirm an indemnity for the same underlying loss is not stacking a second recovery on top of the fixed sum.
• Force majeure: excusable-delay events should pause LD accrual; keep the two clauses consistent on what qualifies.
• Termination: LDs often pair with a right to terminate for the same breach; confirm they are not double-counting.
• Non-solicitation: buyout-style LDs in restrictive covenants draw close penalty scrutiny.

For the broader workflow, see the in-house contract review playbook.

FAQ

What is a liquidated damages clause? It is a provision that fixes in advance the dollar amount owed for a specific breach, so the non-breaching party recovers that sum without proving actual losses. It is meant for situations where real damages exist but are hard to measure, like delay, lost goodwill, or business disruption.

When is a liquidated damages clause unenforceable? When it functions as a penalty rather than an estimate. If the amount is disproportionate to any plausible loss, or the same sum applies to breaches of very different severity, the courts we read will strike it as a penalty and require proof of actual damages instead.

What is the difference between liquidated damages and a penalty? Liquidated damages are a reasonable pre-estimate of hard-to-measure harm; a penalty is a number set to scare a party into performing. Courts enforce the first and refuse the second. The drafting (a metric-based amount, a cap, recitals) is what signals which one you have.

Can you recover liquidated damages and actual damages for the same breach? Usually not. A valid liquidated damages clause is typically the exclusive remedy for the breach it covers. Letting the party also pursue actual damages for the same breach can cause a court to treat the clause as a penalty, as the Florida Supreme Court did for a clause that reserved the choice (Lefemine).

How are liquidated damages calculated? Start from a real loss metric and build up: idle labor, extended overhead, financing or rental cost per day, revenue lost per week of delay, or notification and remediation cost per breached record. The defensible number is the one you can trace to the deal's actual projected loss.

Are SLA service credits liquidated damages? Sometimes. A capped service credit for missed uptime can be analyzed as a liquidated damages amount, in which case the penalty rules apply, but a court may instead treat it as a price adjustment. We did not verify how courts split. Credits are usually capped and styled as the customer's exclusive remedy for the miss.

What happens if a liquidated damages clause is struck down? The fixed number falls away and the non-breaching party is back to proving actual damages under ordinary contract rules. That is why exposed parties should carve the breach out of any consequential-damages waiver or general liability cap, so a failed LD does not leave them with no remedy at all.

How do you make a liquidated damages clause enforceable? Tie the amount to a real metric (per day, per record, per missed milestone), cap the total, add recitals that damages were hard to estimate and the figure is a reasonable forecast, make it the exclusive remedy, and keep the calculation that produced the number. None of this guarantees enforcement, but it gives the clause the structure courts look for.

Does the penalty rule differ by state? Yes. The states we read apply a reasonableness test, but some judge it only as of signing while others also weigh actual damages after the fact, California puts the burden on the party challenging a commercial clause, and Florida treats a clause that reserves a choice between liquidated and actual damages as a penalty. Check the governing law for the specific deal rather than assuming a single national rule.

Arshita Anand

Co-Founder & CEO · Attorney

Arshita leads product and strategy at Vaquill AI, the US primary law data API. As an attorney, she decides which law we carry, how each section is sourced and cited, and what legal AI and compliance teams need from the data.