Liquidated Damages Clauses: How to Draft One That Actually Survives a Judge

A client of mine once put a $75,000 liquidated damages clause into a $9,000 website contract because "it sounded serious." It did sound serious. It also got thrown out the first time it was tested, and the client ended up with nothing but a bill for the litigation. If you've ever added a flat dollar penalty to a service agreement, a lease, or a consulting contract just to scare the other side into performing, you may have built a clause that a court will refuse to enforce at all. Liquidated damages clauses are one of the most misused tools in small-business contracting: powerful when drafted correctly, worthless (and occasionally embarrassing) when they aren't.

This article walks through what makes a liquidated damages clause enforceable under U.S. contract law, where courts draw the line between compensation and punishment, and how to write the wording so it holds up rather than becoming Exhibit A for the other side's lawyer.

What a Liquidated Damages Clause Actually Does

A liquidated damages clause is a provision where the parties agree, in advance, on the dollar amount owed if one side breaches in a specific way. Instead of suing later and hiring an expert to calculate lost profits, the non-breaching party just points to the number in the contract. That's the appeal: certainty, speed, and no need to prove up damages at trial.

But "we agreed on it" is not, by itself, enough to make the number stick. Courts have been suspicious of pre-set damages since before the United States existed, going back to English common law's fear that a stronger party would use a contract to threaten a weaker one rather than to fairly price a risk. That suspicion is baked into American contract doctrine today, and it survives specifically because parties keep drafting these clauses badly.

Why "We Both Agreed" Isn't a Defense

Every so often a client tells me the clause has to be enforceable because both sides signed it, sometimes with a lawyer on each side of the table. That argument doesn't work, and it's worth understanding why before you rely on it. Freedom of contract lets parties allocate risk in almost any way they like — except when a term is specifically identified as against public policy, and penalty clauses are one of the oldest examples of that exception in American law. The doctrine isn't really about protecting one contracting party from another; it's about keeping courts out of the business of enforcing private punishment. A judge asked to award $500,000 in "damages" for a breach that cost $40,000 isn't just being asked to interpret a contract — she's being asked to impose a fine, and that's not a function courts will perform on a private party's behalf, no matter how clearly both sides agreed to it in writing.

This is also why sophistication of the parties matters less than people expect. Courts do sometimes give more latitude to negotiated deals between two represented businesses than to a boilerplate consumer contract, but even heavily negotiated commercial agreements get liquidated damages clauses struck down regularly. Two lawyers agreeing to a bad number doesn't launder it into a good one.

The Legal Test: UCC § 2-718 and Restatement § 356

For contracts involving the sale of goods, the controlling rule is UCC § 2-718(1), adopted in some form in every state except Louisiana — you can browse the full range of contract types this doctrine touches in the template catalog. For services, employment, leases, and most everything else, courts lean on the Restatement (Second) of Contracts § 356. The two are nearly identical in substance.

"Damages for breach by either party may be liquidated in the agreement 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. A term fixing unreasonably large liquidated damages is unenforceable on grounds of public policy as a penalty." — Restatement (Second) of Contracts § 356(1)

Strip out the legalese and you get a two-part test: (1) was the loss genuinely hard to pin down in dollars when the contract was signed, and (2) does the fixed amount reasonably approximate that anticipated loss? Fail either one, and the clause risks being tossed as a penalty — which, under American law, means it's simply unenforceable. Not reduced. Not renegotiated by the judge. Gone. The non-breaching party is then stuck proving actual damages the hard way.

Prospective vs. "Second Look": Two Ways Courts Time the Test

Most states apply what's called a prospective (or "single-look") standard: the clause is judged by what looked reasonable at the moment of signing, and it doesn't matter if the real damages later turn out to be higher or lower. A minority of states — and a chunk of case law, including some Texas decisions — apply a "second look," comparing the liquidated figure not just to what was anticipated but to what actually happened after the breach.

California sits in its own lane. Civil Code § 1671 creates a rebuttable presumption that a liquidated damages clause in a contract between businesses (as opposed to a residential lease or consumer deal) is valid, shifting the burden onto the party attacking the clause. That's friendlier to drafters, but it still isn't a blank check — grossly disproportionate numbers get struck down in California too.

Practical takeaway: don't draft to whichever standard is most forgiving. Draft as if a second-look judge will compare your number to the actual invoice years later, because in a meaningful number of states, that's exactly what happens.

A Real Case: When $1.25 Million Was Seven Times Too High

New York courts have produced a long, consistent line of decisions on this, and one from the Commercial Division is a useful illustration. In Perseus Telecom, Ltd. v. Indy Research Labs, LLC, 2018 N.Y. Slip Op. 33083(U) (Sup. Ct. N.Y. Cty. 2018), a colocation services provider sued a trading firm for $1,250,650 in liquidated damages after the client backed out of a services agreement. The problem: the actual, provable cost to the provider was about $170,000. The court refused to enforce the clause, holding that where the underlying charges were readily calculable from an attached fee schedule, the damages were "ascertainable" — meaning there was no need for a liquidated figure at all — and that a sum more than seven times the real loss looked like a penalty, not compensation.

The New York Court of Appeals had already set the framework decades earlier in Truck Rent-A-Center, Inc. v. Puritan Farms 2nd, Inc., 41 N.Y.2d 420 (1977), describing liquidated damages as "an estimate, made by the parties at the time they enter into their agreement, of the extent of the injury that would be sustained as a result of breach." The Appellate Division has repeatedly applied the same idea: a clause is unenforceable if the stipulated amount is "manifestly disproportionate to the actual damage," because at that point its purpose isn't to compensate — it's "to secure performance by the compulsion of the very disproportion." J.R. Stevenson Corp. v. Westchester Cty., 113 A.D.2d 918, 920 (2d Dep't 1985).

The takeaway isn't "don't use liquidated damages in service contracts." It's "don't skip the math." Perseus lost not because liquidated damages are disfavored generally, but because nobody could explain where $1,250,650 came from, while $170,000 was sitting right there in the invoices.

Common Mistakes That Turn a Clause Into a Penalty

Most bad liquidated damages clauses fail for one of the same handful of reasons. Watch for these when you draft or review a contract:

• Picking a flat, round number ($50,000, $100,000) with no worksheet or calculation behind it, ever
• Using the exact same liquidated figure regardless of whether the breach is trivial or catastrophic
• Setting liquidated damages for a type of loss that is actually easy to calculate — like unpaid invoices, which have their own dollar amount already
• Labeling the clause "penalty" or writing in "to punish," "to deter," or similar language, which practically invites a court to take you at your word
• Recycling a liquidated damages number from an unrelated template or a prior deal of a completely different size

That last one is more common than you'd think. Someone finds an old contract online, likes the structure, and drops in the same dollar figure without recalculating it for a deal that's a fifth the size. Occassionally that shortcut is what sinks the whole clause when it finally gets tested in court.

Worked Example: Building the Number From Scratch

Say you run a small marketing agency and you want a liquidated damages clause for early termination on a 12-month retainer. Here's roughly how you'd build a defensible figure instead of guessing:

• Identify the specific loss: staff time already allocated, a retainer slot turned down from another client, and ramp-up costs that won't be recovered if the client leaves early
• Estimate a realistic range for that loss based on your actual staffing model, not a worst-case scenario
• Express the figure as a percentage of the remaining contract value (say, 25%) rather than one flat number, so it scales automatically with contract size
• Write a one-paragraph internal note explaining the assumptions, and keep it with the signed contract
• Revisit the percentage annually as your average staffing cost and retainer size change

Compare that approach with a clause that just borrows a scary number from a template found online without adjusting it. Here's the kind of language that regularly gets struck down as a penalty:

"In the event Client terminates this Agreement for any reason prior to the end of the Term, Client shall immediately pay Company the sum of $250,000 as agreed liquidated damages, which sum the parties agree is fair and shall not be subject to reduction regardless of Company's actual loss."

That wording has three problems at once: a flat number untethered to any calculation, an explicit statement that actual loss is irrelevant (which practically flags the clause as punitive), and no connection between the figure and the size of the underlying deal. A court reading that paragraph doesn't need much more to conclude it's looking at a penalty rather than a genuine estimate.

Drafting Language That Actually Holds Up

The fix isn't complicated, but it does require showing your work. A well-built clause should identify the specific breach it covers, explain why the resulting loss is hard to quantify, and tie the number to a documented estimate rather than a gut feeling.

"If Client terminates this Agreement after work has commenced but before the Delivery Date set forth in the Statement of Work, and such termination is not permitted under Section 9 (Termination for Cause), the parties agree that Company's damages would be difficult to ascertain with precision due to the allocation of specialized staff, foregone engagements, and sunk development costs. Client shall pay liquidated damages, and not a penalty, equal to 20% of the remaining contract value as of the termination date, calculated according to the fee schedule attached as Exhibit B. This amount represents the parties' reasonable, good-faith estimate of Company's anticipated loss and is not intended to punish Client for exercising a right to terminate."

Notice what that language is doing: it names the specific trigger, states why the loss is hard to measure, points to an exhibit showing the math, and disclaims punitive intent — all without pretending that magic words alone will save a bad number. Courts look at substance, not labels, but a poorly explained clause gives a judge nothing to hang enforcement on.

Liquidated Damages vs. Limitation of Liability vs. Penalty

These three get confused constantly, and mixing them up in a single clause is its own drafting mistake. A limitation of liability caps what a party owes regardless of the type of breach, and it's usually tested for unconscionability rather than proportionality to a specific loss. A liquidated damages clause fixes the amount owed for one particular kind of breach and is tested against the anticipated loss from that breach. A penalty is what you get when the liquidated damages test fails — it's not really a separate clause type so much as a judicial label for the leftovers.

Special Scrutiny in Non-Compete and No-Solicit Clauses

Liquidated damages tied to a non-compete agreement or no-solicitation covenant get an extra layer of judicial skepticism, because several states already restrict or heavily disfavor non-competes on public policy grounds, quite apart from the penalty doctrine. A liquidated sum meant to punish an employee for taking a competing job — rather than to compensate the employer for a proven, specific loss like a lost client contract — is exactly the kind of "in terrorem" provision courts are primed to strike. If you're drafting around restrictive covenants, keep the liquidated damages narrowly tied to a demonstrable loss (a client account with a known revenue history, for example) rather than a blanket sum meant to make competition prohibitively expensive.

Construction and Delivery-Delay Contracts: The One Place Courts Are Comfortable

Construction contracts are the classic, and most judicially accepted, home for liquidated damages — usually a per-day rate for late completion. Courts like this fact pattern because delay damages (lost rent, extended financing costs, missed tenant move-ins) are genuinely hard to pin down in advance, and a documented per-day rate is easy to test against the underlying financial exposure. If you're negotiating a subcontractor agreement or a general contractor deal, a per-day liquidated damages clause tied to documented carrying costs is about as safe as this doctrine gets — provided the daily rate isn't wildly out of proportion to the project's actual value.

The same logic works in reverse for landlords drafting a commercial lease: a forfeited security deposit or early-termination fee needs to bear some relationship to the landlord's real re-leasing costs and lost rent, not just be a scare number designed to keep a tenant locked in.

Service Agreements and Statements of Work: Sizing the Number Correctly

For consulting and service contracts, the safest approach ties liquidated damages to a percentage of remaining contract value rather than a flat sum, because a percentage naturally scales with the size of the deal and is harder to attack as disproportionate. If you're building a Statement of Work with milestone-based liquidated damages for missed deadlines, calculate each milestone's dollar exposure seperately rather than applying one blanket figure to the whole engagement — a single flat number covering wildly different milestones is a classic way to end up disproportionate to at least one of them.

• Use a percentage of remaining fees, not a fixed dollar figure, when contract size may vary between clients
• Attach the calculation as an exhibit so the "we did the math" argument is documented, not asserted after the fact
• Set different liquidated amounts for different breach triggers rather than one number for everything
• Review and update the number if the underlying deal changes materially in size or scope

What Happens If the Clause Gets Struck Down

Losing the liquidated damages fight isn't the end of the case — it just means you're back to proving actual damages the traditional way, with invoices, lost-profit calculations, and possibly expert testimony. As one federal court in New York put it plainly, "if the clause is rejected as being a penalty, the recovery is limited to actual damages proven." Brecher v. Laikin, 430 F. Supp. 103, 106 (S.D.N.Y. 1977). That's usually a worse outcome for the non-breaching party than a well-drafted clause would have delivered, since it reintroduces exactly the proof problems the clause was supposed to avoid in the first place. It's also why "just put a big number in there" is bad advice: an aggressive but unenforceable clause can be worse than a modest, defensible one.

Building the Clause Into Your Standard Template

If you run a business that signs the same kind of contract repeatedly — a freelance design shop, an agency, a subcontracting outfit — it's worth building a standard liquidated damages worksheet into your contract drafting process rather than eyeballing a number every time. Keep a short internal memo (even one page) showing how you calculated the percentage or per-day rate for your standard service agreement template, and update it whenever your average deal size shifts. That memo becomes your evidence of a genuine, good-faith estimate if the clause is ever challenged — exactly the kind of documentation that was missing in the Perseus case.

Self-Check Before You Sign

Before you finalize any contract with a liquidated damages clause, run through this list:

• Can you explain, in one sentence, why the loss from this specific breach is hard to calculate in advance?
• Do you have a worksheet, fee schedule, or memo showing how the dollar figure was built?
• Does the amount scale reasonably with the size of the deal, rather than being a flat number copied from somewhere else?
• Have you avoided using the words "penalty," "punish," or "deter" anywhere near the clause?
• If a judge compared this number to the real-world loss two years from now, would it still look proportionate?

If you can answer all five without hesitating, you likely have a clause that will survive scrutiny in most jurisdictions. If you're shaky on even one, go back and rebuild the number before you send the draft — not after someone breaches and you're standing in front of a judge trying to explain where $75,000 came from.

One last thought worth sitting with: a liquidated damages clause isn't a substitute for good contract management. Clear scope, clear milestones, and a paper trail of communications will do more to prevent disputes than any dollar figure buried in Section 14. The clause is a backstop for the rare case where things go wrong anyway, not a replacement for running the deal well in the first place.

Circle back to that $75,000 clause on the $9,000 website contract from the start of this piece. It wasn't unenforceable because $75,000 is a big number in the abstract — it was unenforceable because nobody could tie it to anything real. Fix that one problem, and most of what makes a liquidated damages clause defensible falls into place on its own.

Article reviewed by: Jordan S. (Attorney)