Liquidated Damages in NDAs: What That Fixed Penalty Clause Means

Most NDA clauses are hard to price. "Confidential Information" is vague, "reasonable efforts" is subjective, and the financial consequence of getting it wrong is buried behind a hypothetical lawsuit you'd probably never see. A liquidated damages clause is different. It puts a number on the page — usually somewhere between $25,000 and $100,000 — and says that if you breach, that's what you owe. No lawsuit needed to establish the amount. No argument about what the client actually lost.

That specificity is what makes the clause feel so alarming when you find it in a $4,000 contract. It's also what makes it one of the more negotiable provisions in an NDA, because a number that obviously exceeds any plausible harm is exactly the kind of term courts refuse to enforce. This post covers what the clause does, why clients include it, when it holds up, what the numbers should look like, and the specific language to counter with. For the wider signing decision, see Should I Sign This NDA?; for how this clause sits alongside other dangerous terms, see NDA Red Flags.

What Liquidated Damages Are

A liquidated damages clause is an agreement, made in advance, about what a breach will cost. Instead of leaving damages to be proven after the fact, both parties fix the amount up front and write it into the contract.

In an NDA it usually reads something like: "In the event of any breach of this Agreement by Recipient, Recipient shall pay to Discloser liquidated damages in the amount of $50,000 per breach, which the parties agree represents a reasonable estimate of the damages that would result from such breach."

Three things are doing work in that sentence. The trigger — "any breach," which is broader than it sounds. The amount — a fixed figure, often per breach rather than in total. And the recital that the parties "agree" the amount is reasonable, which is there specifically to make the clause harder to challenge later.

The mechanism matters. Under ordinary contract law, a client suing you for breaching an NDA has to prove they suffered actual damages and prove the amount. That's genuinely difficult with confidential information — how do you demonstrate that a disclosed product roadmap cost you exactly $37,000? A liquidated damages clause removes that burden entirely. The client proves the breach; the number is already agreed. This is a meaningful shift in leverage, and it's the whole reason the clause exists.

Liquidated damages are also distinct from indemnification, though the two often appear in the same NDA and can stack. Indemnification covers the client's losses and legal costs, uncapped unless you negotiate a cap. Liquidated damages set a fixed sum owed on breach. An NDA containing both, with no cap on either, is a document worth reading very carefully.

Why Clients Include Them

The charitable reading is usually the accurate one. Most clients aren't trying to trap you — they're solving a real problem with a template they found.

Proving damages is genuinely hard. If a startup's unreleased feature set leaks to a competitor, the harm is real but almost impossible to quantify. Lost time-to-market, weakened negotiating position, and diminished first-mover advantage don't produce clean invoices. A fixed sum sidesteps a problem that would otherwise make the NDA unenforceable in practice.

Deterrence. A specific dollar figure changes behavior in a way that "you may be liable for damages" doesn't. Clients know this, and some include the clause primarily so that recipients treat the confidentiality obligation seriously.

It came with the template. A large share of liquidated damages clauses in freelance NDAs were never calibrated to anything. A founder downloaded a template drafted for a corporate acquisition, the $50,000 figure was already in it, and nobody adjusted it for a $4,000 engagement. This is the most common origin, and it's why these clauses are often easier to negotiate than freelancers expect — you're not asking the client to give up something they fought for.

Occasionally, leverage. In a minority of cases the number is deliberately inflated to discourage you from ever pushing back on anything. Freelancers who've discovered this in the middle of a payment dispute know the pattern — it's discussed further in What Happens If You Breach an NDA.

Are They Enforceable?

Sometimes. Enforceability depends on jurisdiction and, within nearly every jurisdiction, on whether the amount was a reasonable estimate of anticipated harm at the time the contract was signed.

The core distinction across US, UK, EU, and Australian law is between a liquidated damages clause (a genuine pre-estimate of loss — enforceable) and a penalty clause (a sum designed to punish or coerce, disproportionate to any plausible harm — unenforceable). The labels in the contract don't decide this. A clause titled "Liquidated Damages" that a court reads as punitive gets struck down regardless of what it's called or what the parties "agreed."

United States. Most states apply a two-part test: damages must have been difficult to estimate when the contract was formed, and the fixed amount must be a reasonable forecast of the likely harm. Courts vary in strictness — some assess reasonableness as of signing, others also look at actual loss suffered. New York and California both scrutinize disproportionate figures closely.

United Kingdom. Since Cavendish v Makdessi (2015), the test is whether the clause imposes a detriment out of all proportion to the innocent party's legitimate interest in enforcement. This is somewhat more permissive than the old "genuine pre-estimate" rule, but a figure with no relationship to any conceivable loss still fails.

EU member states. Approaches differ, but many civil law systems — including France and Germany — give courts explicit statutory power to reduce a contractual penalty that is manifestly excessive, rather than strike it entirely. The clause survives, at a lower number.

Australia. The penalty doctrine applies broadly, and following Paciocco v ANZ (2016) courts assess whether the sum is out of all proportion to the interests it protects.

The practical takeaway: an obviously excessive figure is unlikely to be enforced as written anywhere. But "unlikely to be enforced" is a conclusion a court reaches after you've spent months and real money getting there. The clause's value to a client isn't only the judgment — it's the settlement leverage it creates the moment they invoke it. Enforceability arguments are a defense, not a substitute for negotiating the clause down before you sign.

"Reasonable" vs "Punitive" — What the Numbers Look Like

There's no fixed formula, but proportionality to the engagement is what courts and counterparties both key on.

Broadly defensible: an amount at or near the total contract value. On a $10,000 engagement, a $10,000 liquidated damages figure is a number a court can plausibly read as an estimate of harm. It's also a number you can price into your decision to take the work.

A negotiation point: two to three times contract value. A $30,000 figure on a $10,000 project is high but not absurd, particularly where the information really is sensitive. Expect it to survive scrutiny in some jurisdictions and get reduced in others.

Presumptively punitive: ten times contract value or more. A $50,000 penalty attached to a $4,000 logo design has no relationship to any harm the client could suffer, and its function is coercive. This is the pattern that gets clauses struck down — and it's also, unfortunately, the most common pattern in template-sourced freelance NDAs.

Two structural details change the math regardless of the headline number:

"Per breach" vs "in the aggregate." A $25,000 per-breach clause is not a $25,000 clause. If a client characterizes a single conversation as three separate disclosures, the exposure is $75,000. Always convert per-breach language to an aggregate cap.

Whether it's exclusive. Some clauses state that liquidated damages are the sole and exclusive remedy for breach — meaning the number is a ceiling. Others sit alongside indemnification, injunctive relief, and a general damages claim, meaning the number is a floor. Non-exclusive liquidated damages combined with uncapped indemnification is the worst configuration, and it's worth flagging explicitly.

Real Scenario: How a Liquidated Damages Clause Plays Out

A freelance developer takes a $6,000 contract building an internal dashboard for an early-stage fintech. The NDA includes a liquidated damages clause: $50,000 per breach, non-exclusive, with a broad definition of Confidential Information covering "all information disclosed, in any form, relating to the Company's business."

Eight months after delivery, the developer publishes a technical blog post about a caching pattern they'd worked out during a project — no client named, no code copied, no business detail included. A former colleague at the client company sends it to the founder. The founder, who is separately unhappy about a $2,000 final invoice still outstanding, sends a letter alleging breach of the NDA and demanding $50,000 in liquidated damages.

Here's what actually happens next. The developer's position is decent: the blog post arguably discloses nothing proprietary, and $50,000 against a $6,000 contract looks punitive on its face. A court might well strike the clause or reduce the figure substantially. But testing that costs $8,000–$15,000 in legal fees and takes months, during which the developer is carrying real financial uncertainty. The client's counsel knows this too.

The dispute settles. The developer waives the outstanding $2,000 invoice, agrees to remove the post, and signs a release. Nobody litigated the enforceability of the clause, and the clause still did its job — it converted a weak claim into settlement leverage, because the number on the page was large enough to make fighting it irrational.

That's the honest reason to negotiate these clauses out. Not because they'll bankrupt you in court, but because they make it expensive to be right.

How to Negotiate Them Out (or Cap Them)

There are three asks, in descending order of how much they get you. Start with the first; the second is what usually lands.

Option 1 — Remove entirely. The cleanest outcome, and more achievable than freelancers assume when the clause came from a template.

"Delete Section [X] (Liquidated Damages) in its entirety. Breach of this Agreement shall be remedied in accordance with applicable law, including any equitable relief to which the Disclosing Party may be entitled."

Frame it as a scope question rather than a fight: "The liquidated damages figure is set at roughly 12x the contract value, which I don't think reflects the actual risk profile of this engagement. I'd suggest removing it — standard breach-of-contract remedies and injunctive relief already give you real recourse if I disclose something I shouldn't." The reference to injunctive relief matters: clients care most about stopping a disclosure, and pointing out they retain that remedy removes most of the objection.

Option 2 — Cap at fees paid, aggregate, exclusive. The realistic landing zone, and the version most clients accept.

"Recipient's total aggregate liability for liquidated damages under this Agreement shall not exceed the total fees paid to Recipient under the applicable engagement. Such liquidated damages shall constitute the Disclosing Party's sole and exclusive monetary remedy for breach of this Agreement, provided that nothing herein shall limit the Disclosing Party's right to seek injunctive or other equitable relief."

Three things are happening in that paragraph: the amount is tied to the engagement, "per breach" becomes "total aggregate," and the sum becomes the ceiling rather than one of several stacked remedies. Preserving the client's right to injunctive relief is what makes it an easy yes.

Option 3 — Make it mutual. If the client won't move on the amount, make the obligation run both ways.

"Each party shall be liable to the other for liquidated damages in the amount of $[X] for breach of its confidentiality obligations under this Agreement, on identical terms."

This is a useful test as much as a term. In a genuinely mutual NDA there's no principled reason the penalty should be one-directional, and a client who refuses to accept the same exposure they're asking you to accept has told you something about how the number was chosen.

One caution: don't propose a lower fixed figure as your opening counter (e.g. "make it $10,000 instead of $50,000"). That concedes the mechanism and just negotiates the price. Ask for removal or a fees-paid cap first — you can retreat to a specific number later if you need to.

When to Walk Away vs Negotiate

Most liquidated damages clauses are worth negotiating, not walking over. A few aren't.

Negotiate when the clause appeared in an otherwise reasonable NDA, the client engages with your redlines, the figure is within a few multiples of contract value, or the engagement is short and the information genuinely low-sensitivity. This describes the large majority of cases. A client who accepts a fees-paid cap without argument was never trying to trap you.

Walk away when any of these hold:

The client refuses to modify it at all and the number is disproportionate. Refusal to cap a $50,000 penalty on a $5,000 project isn't a negotiating position — it's information about the relationship you're entering.

It stacks with uncapped indemnification. Fixed penalty plus unlimited indemnification plus a broad breach trigger is a document where your worst case has no ceiling and no clear boundary. Fix both or decline.

The definition of Confidential Information is unbounded. A large penalty is only as safe as the conduct that triggers it. If "Confidential Information" covers everything you learn and the obligation runs indefinitely, an ordinary conversation two years from now can trigger the clause. Read the scope definition and the penalty together — see NDA Confidentiality Scope for what a properly bounded definition looks like.

The economics don't survive the exposure. If the realistic worst case exceeds what the engagement pays by an order of magnitude, and the client won't cap it, the trade isn't worth making regardless of how unlikely a dispute feels.

For a large engagement with a significant penalty figure attached, an hour with a contract attorney costs less than the clause is worth. That's a reasonable expense on a serious contract, and it's a different calculation than for a small project where the practical answer is to cap the clause or decline.

FAQ

Is a $50,000 liquidated damages clause normal in a freelance NDA?

No. It's common, but common and normal aren't the same thing. Figures in that range originate in NDAs drafted for corporate transactions, acquisitions, and enterprise partnerships, where the amounts bear some relationship to the deal size. On a four- or five-figure freelance engagement the same number is wildly disproportionate, and its presence usually means the client reused a template rather than that they've assessed their actual risk.

If the clause is probably unenforceable, why bother negotiating it?

Because unenforceability is a defense you have to pay to establish. The clause creates settlement leverage the moment a client invokes it — you'd be weighing months of uncertainty and five figures in legal fees against a settlement that costs you less. Removing or capping the clause before signing costs one email. That asymmetry is the entire argument.

What's the difference between liquidated damages and a penalty clause?

Legally, everything; textually, often nothing. Liquidated damages are a genuine advance estimate of hard-to-prove loss, and are enforceable. A penalty is a sum designed to punish or coerce compliance, disproportionate to any likely harm, and is not enforceable. Courts decide which one you have by looking at the relationship between the number and the plausible loss — not at the clause's heading or the recital saying both parties agree it's reasonable.

Can a client claim liquidated damages and sue for actual damages?

It depends on whether the clause is exclusive. If it states that liquidated damages are the sole and exclusive monetary remedy, the figure is a ceiling. If it doesn't say that — and many don't — the client may pursue liquidated damages alongside indemnification and a general damages claim, meaning the number is a starting point rather than a limit. Always add "sole and exclusive monetary remedy" language when you negotiate, while leaving their right to injunctive relief intact.

Does forming an LLC protect me from a liquidated damages clause?

Partially, and less than people assume. If the LLC is the contracting party and you maintain proper separation, claims generally run against the business rather than your personal assets. But that protection erodes where a claim alleges personal wrongdoing, where you signed personally or personally guaranteed the agreement, or where the corporate form wasn't respected in practice. An LLC is worth having; it isn't a reason to sign a disproportionate penalty clause.

---

Put a Ceiling on the Number Before You Sign

A liquidated damages clause is one of the few NDA provisions that states your risk in dollars. That makes it easy to evaluate — and easy to fix, because a figure that has no relationship to the size of the engagement is usually a template artifact rather than a considered position. Ask for removal, settle for a fees-paid aggregate cap that's the client's exclusive monetary remedy, and read the clause together with the confidentiality scope and indemnification sections that determine when it can be triggered at all.

NDA Guard flags liquidated damages clauses, compares the figure against your engagement value, checks whether it's per-breach or aggregate and exclusive or stacked, and drafts the counter-language for you. For the full negotiation sequence, read How to Negotiate an NDA as a Freelancer, or start with Should I Sign This NDA? if you're still deciding whether to sign at all.

Find the number. Check what it's a multiple of. Cap it before you sign.