A liquidated damages clause is a useful tool when it works and a wasted paragraph when it does not. The clause sets a fixed dollar amount, or a formula, that the breaching party owes if the contract is broken.
The promise is efficiency: skip the litigation over actual damages, pay the stipulated number, move on. The risk is that Minnesota courts will look at the clause, decide it crosses the line into a penalty, and refuse to enforce it at all.
There is no middle ground in this state. The clause is either enforced as written or struck down completely. For how these clauses fit with other risk-allocation tools, our Minnesota business contract attorney practice handles drafting and disputes across this category every week.
What is the difference between liquidated damages and a penalty in Minnesota?
A liquidated damages clause is a contract term that sets damages in advance for a defined breach. A penalty clause does the same thing in form but does it in a way Minnesota courts will not enforce.
The difference is substantive, not labeling. Under Gorco Construction Co. v. Stein, 256 Minn. 476, 99 N.W.2d 69 (1959) (available at https://scholar.google.com/scholar_case?case=17357730394808852603), the controlling factor is whether the amount agreed upon is reasonable or unreasonable in light of the contract as a whole, the nature of the damages contemplated, and the surrounding circumstances.
A clause that sets a number bearing a real relation to anticipated harm is liquidated damages. A clause that sets a number designed to punish nonperformance, or to scare the other side into compliance, is a penalty.
The practical consequence is that the same number can be liquidated damages in one contract and a penalty in another. A 15 percent cancellation fee tied to a contract where the seller had committed labor and materials may pass. The same 15 percent fee, tied to a contract where the seller had incurred no expense and could easily prove actual loss, will fail. The clause does not exist in isolation. It has to fit the contract.
What is the Minnesota two-part test for enforceability?
Minnesota courts apply a two-part test that has stayed remarkably stable since 1959. To enforce a liquidated damages clause, the party seeking enforcement must show both: (a) the amount fixed is a reasonable forecast of just compensation for the harm caused by the breach, and (b) the harm caused by the breach is one that is incapable or very difficult of accurate estimation. Both prongs must be satisfied. A clause that sets a reasonable number for damages that are easy to calculate fails the second prong. A clause that sets an unreasonable number for damages that are genuinely hard to estimate fails the first.
The test is not mechanical. The court looks at the clause through the lens of the surrounding circumstances at the time the contract was signed, not after the breach. If, at signing, the parties faced a real estimation problem (lost goodwill, lost market opportunity, downstream costs that could not be modeled), the second prong is satisfied. If the harm was straightforward to measure (unpaid invoices, finite project costs, lost rent on an existing lease), the second prong is much harder to satisfy. For more on how courts measure provable harm, see calculating damages: 6 tips for breach of contract cases.
How did Gorco become the controlling case?
Most Minnesota liquidated damages disputes still cite Gorco as the case that fixed the modern two-part test.
The facts were ordinary. A homeowner cancelled a contract to build two garages. The contract included a 15 percent cancellation fee covering salesman’s commissions, advertising, and the commitment of labor and equipment.
The Minnesota Supreme Court refused to enforce the clause and reversed for a new trial. The court explained that the fee covered specific elements of damages that were clearly and readily susceptible of definite measurement and proof by ordinary rules. Because the damages were measurable, an amount greatly disproportionate to provable loss was a penalty.
Gorco also frames the presumption drafters lean on: liquidated damages are prima facie valid on the assumption that the parties in naming a liquidated sum intended fair compensation for an injury caused by breach, not a penalty for nonperformance.
That presumption is the door the clause walks through. The two-part test is the doorway it has to fit. The case still controls because Minnesota appellate courts apply its framework today.
How does the UCC change the test for sales of goods?
When the contract is for the sale of goods, the Uniform Commercial Code overlay at Minn. Stat. § 336.2-718 governs. The statute says: “Damages for breach by either party may be liquidated in the agreement but 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.”
The UCC framework is functionally similar to the common-law test, with two practical refinements. First, the statute permits courts to look at either anticipated or actual harm, which gives the non-breaching party a second window: even if the amount looked unreasonable at signing, it may be saved if actual losses turn out to match.
Second, the statute speaks only to clauses that are unreasonably large. A clause fixing unreasonably small damages is governed elsewhere in Article 2 and may be analyzed as a remedy limitation rather than a penalty.
For sale-of-goods contracts, draft the clause with both anticipated and actual harm in mind: a clause that bears a defensible relationship to either is harder to break.
How do recent appellate decisions apply the test?
A recent 2023 Minnesota Court of Appeals decision shows the test still has teeth. The decision involved a specialty-cinema lease and applied Gorco to refuse enforcement where the damages were reasonably ascertainable from the lease terms, the lease already contained a rent acceleration clause, and the liquidated damages clause failed to account for the landlord’s duty to mitigate.
The combination of measurable damages and a missing mitigation accounting put the clause on the wrong side of Gorco. The lesson tracks Gorco’s two-tier framework directly: when actual damages can be calculated with reasonable certainty, the stipulated amount must not be greatly disproportionate to those damages; when actual damages cannot be calculated with reasonable certainty, the more permissive standard applies and the amount must not be manifestly disproportionate to actual damages suffered. A drafting and litigation pairing follows: if the clause might fail, plead actual damages as an alternative remedy.
What drafting moves keep a clause on the liquidated-damages side of the line?
The drafting choices that survive scrutiny have a common shape.
First, tie the stipulated amount to a real estimation problem identified in the contract itself. A short recital that explains why the parties chose a stipulated amount (the difficulty of forecasting customer disruption, the impossibility of pricing reputational harm, the volatility of replacement-equipment costs) is not boilerplate. Courts read recitals when they are looking for evidence that the parties actually faced an estimation problem.
Second, calibrate the amount to anticipated harm, not aspirational deterrence. A number that looks like a guess at average cost survives more often than a round figure that looks designed to discourage breach.
Third, account for mitigation. The 2023 cinema-lease decision shows that a clause silent on mitigation, or one that allows double recovery, is vulnerable. A short sentence reserving the non-breaching party’s mitigation duty, or crediting actual mitigation against the stipulated amount, removes the easiest target.
Fourth, avoid layering the clause on top of other remedies (acceleration, full-term rent, lost-profits recoveries) without saying expressly how they interact. Stacking remedies invites a court to read the package as a penalty even if any single piece would survive on its own.
Fifth, write the clause as the exclusive remedy for the defined breach, or write it as elective with clear language. Ambiguity is read against the drafter, and in liquidated damages disputes the drafter is almost always the party trying to enforce.
For a related drafting framework, see carve-outs to caps in liability provisions, where the same logic of fitting the clause to the contract applies.
How does exclusivity work for liquidated damages clauses?
The default is exclusivity, but treating that as a deliberate drafting choice avoids the worst surprises. Most Minnesota liquidated damages clauses operate as the exclusive remedy for the specific breach they cover.
If the parties want the non-breaching side to have a choice between the stipulated amount and provable actual damages, the contract must say so. Without that language, electing the clause forecloses an actual-damages claim for the same breach, and waiving the clause may be required before pivoting to actual damages. Drafters who want optionality should write it in.
The flip side is real too. A clause written as exclusive can be a problem for the non-breaching party if actual damages turn out to be much larger than the stipulated number. The clause caps the recovery on its own terms. That is the bargain. Optionality solves the problem only if the contract is drafted that way at signing, not after the breach.
How does the duty to mitigate interact with a liquidated damages clause?
Mitigation is the issue the 2023 cinema-lease decision pulled into focus. A liquidated damages clause that ignores mitigation, or that effectively guarantees a recovery beyond the loss the non-breaching party actually suffered, is in trouble.
A landlord who collects accelerated rent and the same rent again from a replacement tenant has been made more than whole. A clause that allows that result is hard to defend as a reasonable forecast of just compensation.
The fix is express. The clause should either credit actual mitigation receipts against the stipulated amount, or set the stipulated amount low enough that the combined recovery still tracks the non-breaching party’s expected loss.
Drafters resist this because it complicates the clean efficiency the clause was supposed to provide. The trade-off is real. A simpler clause that risks unenforceability gives up more than a slightly more complex clause that survives. The right balance depends on the deal, the breach scenarios that matter, and what the non-breaching party can actually do to mitigate after a default.
When is a per diem delay clause enforceable?
Per diem delay clauses, common in construction and time-sensitive supply contracts, are an instructive subcategory. They tend to survive Minnesota scrutiny when the daily amount reflects a reasonable forecast of the additional cost the non-breaching party will incur for each day of delay, and when delay damages are genuinely difficult to prove with daily precision.
They tend to fail when the daily amount is round, large, and disconnected from any cost analysis, especially in disputes where the non-breaching party can produce books showing exact daily impact. The two-part test applies the same way it does anywhere else, but the breach scenario (rolling delay) plays well with the second prong because daily delay losses are notoriously hard to prove with precision.
The drafting move that matters most is the rationale for the daily figure. A delay clause that ties the per diem rate to a specific cost basis (carrying costs, idle-equipment costs, lost daily revenue from a comparable project) gives the court something to point to when sustaining the clause. A delay clause with a number that appeared from nowhere invites the penalty argument. For a related discussion, see delay penalty clauses in time-sensitive shipments.
What clauses look like liquidated damages but are something else?
Several common contract terms function like liquidated damages without always being analyzed under the Gorco framework. Termination fees, early termination charges, restocking fees, and minimum-purchase shortfall payments can be characterized as price terms, performance fees, or alternative consideration rather than damages, depending on how they are drafted.
The characterization matters because price terms are not subject to the penalty doctrine. A monthly subscription fee with a 12-month commitment, where the customer pays out the remaining months on early termination, may be enforced as the price of the service rather than struck down as a stipulated-damages provision.
Default interest rates, late fees, and prepayment penalties travel a different path. Default interest is constrained by usury concepts and by Minnesota’s general suspicion of clauses that produce escalating recoveries unrelated to harm. See default interest clauses unenforceable for the related analysis. Early termination fees specifically face a separate line of unconscionability cases that overlap with, but do not duplicate, the penalty doctrine. See early termination fees: unconscionability claims. The drafter’s job is to know which framework is actually going to govern. A clause drafted under the wrong assumption is exposed.
The clauses that interact most directly with stipulated damages are consequential-damages waivers and overall liability caps. Each does different work and rests on different doctrine. For how those companions operate, see consequential damages in contract breaches.
Can the breaching party challenge a liquidated damages clause as a penalty after agreeing to it?
Yes. Agreeing to the clause at signing does not insulate it from later challenge. Minnesota treats enforceability as a question of law for the court, decided on the contract terms and the facts surrounding formation. A breaching party who can show the stipulated amount bore no reasonable relation to anticipated harm, or that the harm was readily measurable when the contract was signed, can have the clause struck even after both sides signed it.
Will a Minnesota court rewrite an unenforceable penalty down to a reasonable amount?
No. Minnesota courts treat the question as binary: the clause is either enforced as written or struck down as a penalty. Courts do not reform a penalty into a smaller, enforceable number. If the clause fails, the non-breaching party falls back on proving actual damages under ordinary rules, which is exactly the litigation the clause was supposed to avoid.
Are earnest money forfeitures in Minnesota real estate contracts treated the same way?
Earnest money provisions are generally analyzed under the same liquidated damages framework, but courts give some additional weight to the customary nature of the forfeiture amount in residential transactions. A forfeiture of an unusually large deposit, or one disproportionate to the seller’s foreseeable harm from a buyer default, can still be challenged as a penalty. The fact that the seller already holds the money does not make the forfeiture automatic.
Do I have to prove actual damages to enforce a liquidated damages clause?
Not in the traditional sense. The whole point of a liquidated damages clause is that the non-breaching party does not have to prove actual loss with the precision required for ordinary contract damages. But the party seeking enforcement does have to be ready to defend the reasonableness of the stipulated amount if challenged. Recent Minnesota decisions show that if actual damages are readily provable, a court may compare them to the stipulated amount and refuse enforcement if the gap is too large.
Is a liquidated damages clause enforceable in a consumer contract?
Sometimes, but the bar is higher. Consumer contracts trigger closer scrutiny on bargaining power, conspicuousness, and unconscionability, and certain industries layer on statutory consumer protections that further constrain stipulated damages. A clause that would survive between two sophisticated businesses can fail in a consumer-facing form contract, even if the language is identical.
Closing thought
A liquidated damages clause is a small piece of contract real estate that does outsized work when it survives and creates outsized problems when it does not. Minnesota’s framework is stable, the leading case is six decades old, and the recent appellate decisions are not surprising; they are reapplications of Gorco to fact patterns that drafters keep producing.
The pattern that breaks clauses is the same one that has broken them since 1959: a number that does not fit the contract, set against damages that were not actually hard to estimate, layered on top of other recoveries without accounting for mitigation.
The pattern that saves clauses is the opposite: a number tied to a real estimation problem, calibrated to anticipated harm, written as a single coordinated remedy, and clear about how it interacts with the rest of the contract.
For a candid read on a specific clause you are about to sign or send, our Minnesota business contracts practice handles this work regularly. Email [email protected] with the contract and a short description of the deal, and I can give you a focused assessment of where the clause is strong and where it is exposed.
