A promise is broken. A supplier who swore the parts would arrive Monday calls on Friday to say there are no parts. A software vendor that guaranteed ninety-nine-point-nine percent uptime goes dark for a week during your busiest sales season. A buyer who signed for a custom-built machine refuses to take delivery the day it rolls off the line. In each case, somebody made a promise, somebody relied on it, and somebody is now staring at a loss. The question the law asks next is deceptively simple and quietly profound: how much is that broken promise worth?

That is the question this article answers. It is a question with a surprisingly elegant default answer, a thicket of refinements, and a body of doctrine that is several centuries old and still evolving. Along the way we will meet a famous broken crankshaft from 1854, a Uniform Commercial Code that converted the chaos of sales disputes into algebra, a rule that forbids the parties from setting their own punishments, a stubborn duty that requires the victim of a breach to lift a finger to help, and a set of statistics that look authoritative until you ask where they came from.

By the end you will understand the three great families of contract remedy--expectation, reliance, and restitution--and why courts default to the first. You will know why consequential damages are both the most valuable and the most fragile category a plaintiff can claim. You will be able to read a liquidated-damages clause and predict whether a court will enforce it or strike it down as a penalty. You will understand why the law makes a betrayed party go out and find substitute performance instead of sitting on its hands and running up the bill. And you will be able to look at a chart of "median contract damage awards" and know exactly what it does and does not tell you.

Let us begin with the most important sentence in all of contract remedies.

The Master Principle: Make the Injured Party Whole

Anglo-American contract law rests on a single organizing idea, and it is worth stating as plainly as possible. The goal of contract damages is compensation, not punishment. When a contract is breached, the law does not set out to teach the breaching party a lesson, to vindicate the sanctity of promises, or to express society's disapproval. It sets out, instead, to put the injured party in the position they would have occupied had the contract been performed as promised. That position--the financial place you would have stood in if everything had gone right--is called the expectation interest, and protecting it is the default remedy in nearly every contract case in the United States.

The Restatement (Second) of Contracts, the influential treatise published by the American Law Institute that distills the common law of contracts and that courts cite constantly, captures the idea in Section 347: the injured party has a right to damages based on their expectation interest, measured by the loss in value of the other party's performance plus any other loss (including incidental and consequential loss), less any cost or loss the injured party avoided by not having to perform. That is the formula behind nearly every contract verdict you will ever read. Strip away the jargon and it says: give me what I was promised, plus the foreseeable ripple costs, minus whatever I saved by being released from my own side of the deal.

This compensatory orientation distinguishes contract law sharply from tort law and criminal law. A drunk driver may owe punitive damages designed to deter and to punish. A breaching party, by contrast, almost never does--more on that below. The economist's gloss on this is the much-debated theory of efficient breach: if a seller can break a contract, pay the buyer full expectation damages, and still come out ahead by selling to someone who values the goods more, the law's neutrality toward breach arguably channels resources to their highest use. You do not have to buy the economics to grasp the doctrine: contract damages are about the bargain, not about blame.

Three remedial measures flow from this master principle, and a great deal of contract-damages practice consists of choosing among them.

Expectation, Reliance, and Restitution

Expectation damages are the headline measure. They give the injured party the benefit of the bargain--the value of full performance. Suppose Acme Corp. agrees to build a custom conveyor system for Beacon Foods for $400,000, and Beacon has already lined up the system to handle a production increase worth $90,000 in net profit over its first year. If Acme walks away and Beacon must hire a substitute builder for $470,000, Beacon's expectation damages start with the $70,000 cost overrun, plus any provable lost profit from the delay, plus incidental costs of arranging the cover, minus anything Beacon saved. The number answers the question: what would it take, in dollars, to make Beacon as well off as it would have been if Acme had simply performed?

Reliance damages take a different tack. Instead of looking forward to the promised gain, they look backward to the position the injured party occupied before the contract was made. They reimburse expenditures the injured party reasonably incurred in reliance on the promise, restoring the status quo ante. Reliance is the fallback when expectation is too speculative to prove--a recurring problem for new businesses, as we will see. The Restatement (Second) recognizes this in Section 349: where a plaintiff cannot prove lost profits with reasonable certainty, they may instead recover the costs they wasted preparing to perform, on the theory that they would at least have broken even. If Beacon spent $25,000 reconfiguring its plant floor to receive Acme's conveyor and that work is now useless, those out-of-pocket costs are recoverable as reliance damages even if Beacon cannot prove a dime of lost profit.

Restitution damages focus on neither the plaintiff's expectation nor the plaintiff's reliance but on the defendant's unjust gain. Restitution requires the breaching party to disgorge any benefit conferred on it by the injured party, preventing unjust enrichment. If Beacon paid Acme a $150,000 deposit and Acme delivered nothing, restitution returns the deposit. Restitution can also exceed the contract price in a "losing contract" scenario--a quirk that occasionally lets a plaintiff recover more by abandoning the contract measure and suing for the value of what it actually conferred--but that is an advanced wrinkle. The everyday point is that restitution prevents one party from keeping value it received without paying for it.

A plaintiff generally must elect among these theories rather than stacking them, and courts will not allow a double recovery. The choice is strategic: expectation maximizes recovery when the deal was profitable and the gain is provable; reliance rescues the plaintiff whose profits are too speculative; restitution shines when the defendant has been enriched and the contract itself was a money-loser for the plaintiff. Choosing well is one of the quieter arts of contract litigation, and it is the kind of analysis a lawyer performs early when evaluating and assessing a civil case.

Hadley v. Baxendale: The Foreseeability Rule That Built Modern Damages

No discussion of contract damages can proceed far without bowing to a broken crankshaft and a slow-moving carrier. The case is Hadley v. Baxendale, 9 Ex. 341, 156 Eng. Rep. 145 (1854), decided by the Court of Exchequer in England, and it is very likely the single most-cited contract case in the common-law world. Every first-year law student meets it; every damages brief eventually invokes it.

The facts are humble. The Hadleys ran a flour mill in Gloucester. The mill's crankshaft broke, halting the entire operation. They hired Baxendale's carrier company to transport the broken shaft to an engineer in Greenwich so a new one could be cast to match it. The carrier promised next-day delivery but, through neglect, took several days longer. During the delay the mill sat idle, and the Hadleys sued for the profits they lost while waiting. Baxendale objected: how was a carrier supposed to know that a delayed parcel would shut down an entire factory?

The court sided with Baxendale, and in doing so it announced the rule that still governs the recoverability of consequential damages today. Damages for breach, the court held, are limited to those that arise naturally--that is, according to the usual course of things--from the breach itself, or those that may reasonably be supposed to have been in the contemplation of both parties, at the time they made the contract, as the probable result of a breach. The mill's lost profits were not recoverable because the carrier had no reason to know, when the deal was struck, that the broken shaft was the mill's only one and that its absence would idle the works. Special circumstances must be communicated to be charged to the breaching party.

This is the foreseeability rule, and it draws the great dividing line in contract damages between two categories.

General (Direct) Damages vs. Consequential (Special) Damages

General damages, sometimes called direct damages, are those that flow naturally and inevitably from the breach itself--the kind of loss anyone would expect. If a seller fails to deliver goods, the buyer's direct damage is the cost of obtaining substitute goods. No special knowledge is required to foresee it; it is the ordinary, predictable consequence of the breach. General damages are the first branch of Hadley.

Consequential damages, sometimes called special damages, are the ripple effects--the downstream losses that depend on the injured party's particular circumstances. Lost profits on resale, lost business opportunities, damage to goodwill, costs incurred dealing with the fallout: these are consequential damages. They are recoverable only under the second branch of Hadley, meaning only if they were reasonably foreseeable to the breaching party at the time of contracting, either because they arise in the ordinary course or because the special circumstances were communicated.

This distinction matters enormously in practice, and it is the single most contested issue in many contract-damages fights. Consequential damages are frequently where the real money lives--the lost profits dwarf the price of the goods--but they are also the most fragile category, vulnerable to attack on three independent fronts: foreseeability (was the loss within the parties' contemplation?), certainty (can the amount be proven without speculation?), and causation (did the breach actually cause it?). A defendant who concedes the breach can still defeat a consequential-damages claim by knocking out any one of these legs.

The original input that inspired this article muddled this point, describing consequential damages as losses incurred while the plaintiff "attempts to mitigate" the harm. That is not quite right and it is worth correcting clearly: consequential damages are the foreseeable downstream losses caused by the breach. Mitigation is a separate doctrine (discussed below) that reduces recoverable damages by requiring the plaintiff to take reasonable steps to limit the harm. Conflating the two is a common error; keeping them distinct is essential.

Limiting Consequential Damages by Contract

Because consequential damages are where breaches become expensive, sophisticated parties routinely try to control them in advance. A great many commercial contracts--especially in technology, where a small software license can theoretically expose a vendor to a customer's catastrophic business losses--contain a consequential-damages waiver, a clause stating that neither party will be liable for consequential, incidental, indirect, special, or punitive damages, often paired with a limitation-of-liability cap tying total liability to, say, the fees paid in the prior twelve months. These clauses are generally enforceable between sophisticated commercial parties, subject to unconscionability limits and the occasional carve-out for things like breaches of confidentiality, IP indemnity, or gross negligence. Anyone reviewing a vendor agreement should understand exactly how these provisions allocate risk; they are a central topic in our overview of software licensing agreements and in the broader landscape of software transactions. The lesson is that Hadley's default rule is just that--a default. Parties can and do contract around it, and reading those provisions carefully is often more important than knowing the case law, because the contract usually wins.

The Certainty Requirement and the New-Business Rule

Foreseeability is the first gate a consequential-damages claim must pass through. The second is certainty. Damages, particularly lost profits, must be proven with reasonable certainty--not mathematical precision, but enough evidentiary grounding that the factfinder is not merely guessing. The Restatement (Second) of Contracts Section 352 frames the limitation directly: damages are not recoverable beyond an amount that the evidence permits to be established with reasonable certainty. A plaintiff who can show that it was harmed but cannot non-speculatively show how much may walk away with nominal damages even after proving a clear breach.

The certainty requirement historically collided hardest with one kind of plaintiff: the new business. Under the traditional new-business rule, a business with no track record of profits was often barred from recovering lost profits at all, on the theory that projecting the earnings of an enterprise that had never earned anything was inherently too speculative. A startup that signed a make-or-break distribution deal, watched the counterparty breach, and then collapsed could find itself unable to prove the profits it never got the chance to earn.

The modern trend has softened this once-rigid bar substantially. Most jurisdictions have moved away from a per se prohibition toward a flexible, evidence-based inquiry: a new business may recover lost profits if it can establish them with reasonable certainty through credible evidence--expert economic testimony, comparable businesses, market studies, the experience of the principals, pre-breach projections that proved accurate, or a combination. The question is no longer "is the business new?" but "is the proof good enough?" Still, the practical reality is that newer ventures face a steeper evidentiary climb, and a plaintiff facing that climb should think hard about a reliance-damages fallback, which sidesteps the lost-profit speculation entirely by asking only what was actually spent. For a young company weighing whether a contract claim is worth pursuing, the certainty hurdle is one of the first things to assess when evaluating and assessing a civil case, and it is one reason careful contracts and clear records matter so much for the kinds of legal documents startups rely on.

A worked example clarifies the stakes. Suppose Nimbus Apps, a one-year-old company, signs a contract with MegaRetail to feature Nimbus's product in MegaRetail's stores for the holiday season. MegaRetail breaches by pulling the product at the last minute. Nimbus claims $2 million in lost holiday profits. Under the old new-business rule, Nimbus might recover nothing--it had never run a holiday season before. Under the modern approach, Nimbus can try to prove the $2 million with expert testimony, data from comparable products in comparable stores, and its own (now-frustrated) production ramp-up. If the proof is solid, the lost profits are recoverable; if it is hand-waving, Nimbus may be relegated to reliance damages--the cost of the inventory it built and cannot sell, the marketing it wasted--or to nominal damages. Same breach, wildly different recovery, all turning on the quality of the proof.

The Uniform Commercial Code: Damages by Formula

So far we have been speaking the language of the common law, which governs contracts for services, real estate, employment, and most everything else. But an enormous share of commercial disputes involve contracts for the sale of goods--tangible, movable items--and those are governed not by the common law but by Article 2 of the Uniform Commercial Code (UCC), a model statute adopted (with local variations) by every U.S. state except that Louisiana has adopted only parts of it. The UCC's drafters did something remarkable: they converted the often-fuzzy common law of sales remedies into a set of clean, almost algebraic formulas. If you want to see contract damages at their most precise, look to Article 2.

The UCC gives mirror-image remedies to buyers and sellers, and the symmetry is one of its quiet pleasures.

The Buyer's Remedies: Cover and Market Differential

When a seller breaches--by failing to deliver, by repudiating, or by the buyer rightfully rejecting nonconforming goods--the buyer has two principal damage measures.

The first is cover, codified at UCC Section 2-712. The buyer may, in good faith and without unreasonable delay, buy substitute goods (this is "covering"), and then recover from the seller the difference between the cost of cover and the contract price, plus incidental and consequential damages, less expenses saved. This is the marketplace version of expectation: it gives the buyer the benefit of the bargain by funding the substitute purchase. Suppose Beacon Foods contracted to buy 10,000 units of packaging from Acme at $4 per unit, Acme failed to deliver, and Beacon covered by buying equivalent packaging elsewhere at $5 per unit. Beacon's cover damages are the $1-per-unit difference times 10,000 units--$10,000--plus incidental costs (extra shipping, the cost of sourcing the substitute) and any foreseeable consequential damages, minus anything saved.

If the buyer does not cover--perhaps because no substitute was available, or the buyer simply chose not to--the second measure applies: the market-price differential under UCC Section 2-713. The buyer recovers the difference between the market price at the time the buyer learned of the breach and the contract price, again plus incidental and consequential damages, less expenses saved. Using the same numbers, if the market price for the packaging when Beacon learned of the breach was $5.20 per unit, Beacon's 2-713 damages would be $1.20 per unit times 10,000, or $12,000. Note that the two measures can diverge; the UCC lets the buyer recover the genuine market differential even if the buyer happened not to cover.

When the buyer keeps nonconforming goods rather than rejecting them--accepting a delivery of slightly defective widgets, say, and using them anyway--the measure shifts again, to UCC Section 2-714: damages for breach of warranty, generally the difference between the value of the goods as accepted and the value they would have had if they had been as warranted, plus, in a proper case, incidental and consequential damages. This is the "I kept the goods but they were worth less than promised" measure, and it is the workhorse of warranty litigation.

The Seller's Remedies: Resale and the Lost-Volume Problem

The UCC gives the seller a parallel toolkit. When a buyer breaches--by wrongfully rejecting, by repudiating, or by failing to pay--the seller may resell the goods under UCC Section 2-706 and recover the difference between the contract price and the resale price, plus incidental damages, less expenses saved. This is the seller's mirror of cover. If the seller does not resell, the seller may recover the difference between the contract price and the market price at the time and place for tender under UCC Section 2-708(1).

But the seller's headline provision--the one that generates the most interesting litigation--is UCC Section 2-708(2), the lost-profit measure. Where the ordinary contract-minus-market formula would not put the seller in as good a position as performance would have, the seller may instead recover the profit (including reasonable overhead) it would have made on the deal, plus incidental damages. The classic beneficiary of 2-708(2) is the lost-volume seller: a seller with effectively unlimited inventory or capacity, for whom reselling the breached-upon goods to a second buyer does not actually make the seller whole, because that second buyer would have bought a unit anyway. The breach cost the seller not a single sale but an entire incremental sale's worth of profit.

Imagine Acme is a car dealership with plenty of inventory. Buyer signs to purchase a $40,000 car on which Acme would net $5,000 in profit, then breaches. Acme resells the very same car to a different customer for $40,000. Under a naive contract-minus-resale measure, Acme's damages would be zero--it resold at full price. But that ignores reality: had Buyer performed, Acme would have sold two cars and earned two profits, because the dealership had ample supply. The breach cost Acme one $5,000 profit. Section 2-708(2) recognizes this and awards Acme its lost profit. The lost-volume doctrine is a beautiful illustration of the law refusing to let a formula obscure the underlying goal: putting the seller in the position performance would have produced.

Incidental and Consequential Damages Under the Code

Layered on top of these formulas, the UCC provides for incidental and consequential damages. Incidental damages (Sections 2-710 for sellers, 2-715(1) for buyers) cover the reasonable expenses of dealing with the breach--inspecting, transporting, storing, reselling or covering, and the like. Consequential damages for buyers (Section 2-715(2)) track Hadley: a buyer may recover losses resulting from needs the seller had reason to know of at contracting, which the buyer could not reasonably prevent by cover--again importing both the foreseeability rule and a mitigation concept directly into the statute. The Code also expressly permits parties to limit or exclude consequential damages (Section 2-719), unless the limitation is unconscionable, which is why the limitation-of-liability clauses discussed earlier are enforceable in goods contracts too.

A final note for the practitioner: many transactions are not cleanly "goods" or "services" but hybrids--a contract to supply and install equipment, or to deliver software bundled with support. Courts generally apply the predominant-purpose test to decide whether Article 2 governs the whole contract, asking whether the deal is predominantly about goods or services. The answer can change the damages analysis materially, since the UCC formulas differ from common-law measures, and it is a recurring puzzle in technology deals where the line between a licensed product and a delivered service is blurry.

Liquidated Damages and the Penalty Bar

Sometimes the parties do not want to leave damages to a future court's arithmetic. They prefer certainty, so they write the number into the contract itself: "If Contractor fails to complete the building by June 1, Contractor shall pay Owner $2,000 for each day of delay." This is a liquidated-damages clause--an agreed, pre-estimated measure of damages for a specified breach. Liquidated-damages clauses are common in construction (delay damages), real estate (forfeiture of earnest-money deposits), employment, and any setting where actual damages would be hard to calculate after the fact.

The law's attitude toward these clauses is a study in ambivalence. On one hand, courts respect freedom of contract and the parties' interest in certainty, and they enforce genuine liquidated-damages clauses readily. On the other hand, the master principle--compensation, not punishment--means the law will not let parties use a damages clause to impose a penalty. A clause that bears no reasonable relationship to anticipated or actual harm, that is designed to terrorize a party into performance rather than to compensate for breach, is an unenforceable penalty clause, and courts will strike it down.

The Two-Part Enforceability Test

The traditional common-law test, reflected in Restatement (Second) of Contracts Section 356 and echoed for goods contracts in UCC Section 2-718, asks two questions. First, were the actual or anticipated damages from the breach difficult to estimate at the time of contracting (or, in some formulations, at the time of breach)? Second, is the stipulated sum a reasonable forecast of--reasonably proportionate to--that harm? If the answer to both is yes, the clause is a valid liquidation of damages and will be enforced. If the stipulated amount is grossly disproportionate to any plausible harm, it is a penalty and falls.

The distinction is best seen through paired hypotheticals. Suppose Acme Construction agrees to build a seasonal resort hotel and the contract sets delay damages at $5,000 per day. At the time of contracting, the parties genuinely could not predict the owner's exact losses from a late opening--lost bookings depend on weather, the economy, marketing--but $5,000 per day is a sensible forecast of the daily revenue a resort hotel would lose. That clause will be enforced. Now suppose the same contract set delay damages at $500,000 per day for a small storage shed worth $40,000. No court will enforce that; it is a penalty, untethered from any conceivable harm, and the law will toss it and send the owner back to proving actual damages.

A few refinements are worth knowing. Some courts evaluate reasonableness prospectively (as of contracting), others permit a retrospective check (comparing the stipulated sum to the harm that actually occurred), and the UCC's Section 2-718(1) explicitly allows consideration of "the anticipated or actual harm." A clause can also fail if it is a "shotgun" provision imposing the same large sum for any breach great or small, since it cannot be a reasonable forecast of every breach at once. And critically, a valid liquidated-damages clause is generally the injured party's exclusive remedy for the covered breach--they get the agreed sum, not the agreed sum plus actual damages. Liquidated-damages clauses thus cut both ways: they cap the upside as well as guarantee the floor.

The penalty bar is one of the few places where contract law overrides the parties' express agreement in service of its anti-punishment principle, and it is a recurring drafting trap. A clause meant to protect a client can be voided as a penalty if it is greedy; a number chosen with care and documented as a genuine estimate will hold. Anyone drafting these provisions--and anyone sending a demand letter that relies on one--should pressure-test the figure against the two-part test before treating it as money in the bank.

The Duty to Mitigate: The Victim Must Lift a Finger

Here is a feature of contract law that surprises many non-lawyers and not a few clients: after a breach, the law expects the injured party to take reasonable steps to minimize its own losses. This is the duty to mitigate, sometimes called the avoidable-consequences doctrine, and it is captured in Restatement (Second) of Contracts Section 350. A breached-upon party cannot recover damages it could have avoided through reasonable effort and without undue risk, burden, or humiliation. The plaintiff who could have found substitute performance but chose instead to sit back and let the losses pile up--running up the meter to maximize the judgment--will find those avoidable losses subtracted from the award.

"Duty" is a slight misnomer, because the plaintiff is not liable to anyone for failing to mitigate; rather, the consequence of unreasonable inaction is a reduction in recoverable damages. The breaching party bears the burden of proving that the plaintiff failed to mitigate and that the failure increased the loss. And the standard is reasonableness, not perfection: the plaintiff need only take steps a reasonable person in its position would take, and it may recover the costs incurred in reasonable mitigation efforts even if those efforts ultimately fail.

The doctrine shows up everywhere. In a sale-of-goods case, mitigation is baked into the cover remedy: a buyer who unreasonably refuses to cover when a substitute was readily available may lose the consequential damages it could have avoided. In employment, a wrongfully terminated employee must make reasonable efforts to find comparable substitute work; earnings from the new job (and earnings the employee could have made by reasonably looking) reduce the damages owed by the former employer, though the employee need not accept work that is not substantially similar or that is demeaning. In real estate leasing, a landlord whose tenant abandons the premises is, in most modern jurisdictions, required to make reasonable efforts to re-let rather than letting the unit sit empty and suing for the full remaining rent.

Consider a worked example that ties mitigation back to Hadley and to consequential damages. Beacon Foods needs a refrigeration compressor and orders one from Acme for $20,000, telling Acme the compressor is for a cold-storage warehouse holding $300,000 of perishable inventory. Acme breaches and the compressor never ships. Beacon could have rented a temporary compressor for $8,000 to keep the warehouse running while it sourced a permanent unit, but instead Beacon did nothing, and $300,000 of inventory spoiled. What can Beacon recover? The spoilage was foreseeable--Beacon communicated the special circumstances, satisfying Hadley's second branch. But the duty to mitigate caps Beacon's consequential damages at the avoidable line: Beacon can recover the $8,000 it should have spent on a rental compressor (plus the cover differential on the permanent unit), not the $300,000 in spoilage it could reasonably have prevented. Mitigation and foreseeability work in tandem--one expands the universe of recoverable loss, the other contracts it--and a good damages analysis always runs both.

Why Punitive Damages Almost Never Appear in Contract Cases

The original input correctly noted that punitive damages are rare in contract litigation, and the reason traces straight back to the master principle. Because contract damages aim to compensate rather than to punish, the general American rule is that punitive damages are not available for breach of contract, no matter how willful, deliberate, or cynical the breach. A party who coldly calculates that breaching and paying damages is cheaper than performing has done nothing the law punishes; it has merely exercised the option the efficient-breach theory describes. Restatement (Second) of Contracts Section 355 states the rule flatly: punitive damages are not recoverable for a breach of contract unless the conduct constituting the breach is also a tort for which punitive damages are recoverable.

That exception is the doorway through which punitive damages occasionally slip in. If the breaching conduct is independently tortious--fraud in the inducement, conversion, certain breaches of fiduciary duty--the plaintiff may plead the tort and seek punitive damages on the tort, not on the contract. A handful of jurisdictions also recognize a tort of bad-faith breach in specific contexts, most prominently insurance, where an insurer's unreasonable refusal to pay a valid claim can expose it to tort and punitive liability. But these are exceptions that prove the rule. In the ordinary commercial breach--the supplier who did not deliver, the buyer who did not pay, the contractor who walked off the job--punitive damages are simply off the table. The data bear this out: in the aggregate figures discussed below, punitive awards appear in a vanishingly small slice of contract dockets, and where they do, there is almost always a tort lurking alongside the contract claim.

Specific Performance and Other Equitable Remedies

Money is the law's default answer to a broken contract, but it is not the only answer. In a narrow band of cases, a court will order the breaching party to actually do what it promised--to convey the parcel, to deliver the unique chattel, to honor the obligation in kind. This is specific performance, an equitable remedy, and its availability is the exception, not the rule.

Specific performance is granted only when money damages would be inadequate to make the injured party whole. The paradigm case is real estate: because every parcel of land is treated as legally unique, courts routinely order specific performance of land-sale contracts--damages cannot buy the buyer the particular parcel they bargained for. The same logic extends to unique goods: a one-of-a-kind painting, a rare antique, a custom item with no market substitute. UCC Section 2-716 codifies this for goods, authorizing specific performance "where the goods are unique or in other proper circumstances." For ordinary, fungible goods--commodities with a ready market--specific performance is denied, because the cover remedy adequately substitutes.

Courts also withhold specific performance where it would require ongoing judicial supervision (which is why they rarely order completion of a complex construction project), where the contract terms are too indefinite to enforce precisely, or where personal services are involved--a court will not order a reluctant employee to keep working, both because supervision is impractical and because compelled labor smacks of involuntary servitude. (Courts may, however, enjoin a breaching performer from working for a competitor during the contract term, an indirect pressure that stops short of forced performance.) Equitable defenses such as laches, unclean hands, and undue hardship can also bar the remedy. The upshot: specific performance is a powerful but tightly cabined tool, reserved for the cases where dollars genuinely cannot substitute for the promised performance.

Attorney's Fees: The American Rule and Its Contractual Override

A client who wins a breach-of-contract case often asks, reasonably enough, "Now make them pay my legal bills." The answer, in the United States, usually begins with a disappointment. Under the American Rule, each party bears its own attorney's fees regardless of who wins--win or lose, you pay your own lawyer. This contrasts with the "English Rule" or "loser-pays" systems common abroad, and it is the default in American contract litigation.

There are two principal escapes from the American Rule. The first is statute: some statutes shift fees to the prevailing party in particular kinds of cases (many consumer-protection and civil-rights statutes do this), but few generic breach-of-contract claims qualify. The second--and the one that matters most in commercial practice--is the contract itself. Parties are free to include a prevailing-party attorney's-fee clause, and these are widely enforced: "In any action to enforce this Agreement, the prevailing party shall be entitled to recover its reasonable attorney's fees and costs." When such a clause exists, the winner can recover its fees on top of its damages; when it does not, the American Rule controls and each side eats its own costs.

This is why the fee-shifting provision is one of the most consequential--and most overlooked--sentences in any contract. It can transform the economics of a dispute entirely. A $30,000 breach claim is rarely worth litigating if you will spend $80,000 in fees you can never recover; the same claim becomes very much worth pursuing if a fee-shifting clause means the loser pays. Some jurisdictions even apply a one-sided fee clause reciprocally by statute (California's Civil Code Section 1717 is the famous example), so that a clause favoring only the drafter is read to favor whichever party prevails. The presence or absence of a fee clause should feature prominently in any honest assessment of whether to sue, settle, or send a demand letter--and it is a topic worth examining closely whenever you are evaluating and assessing a civil case.

How Courts Actually Compute an Award: Putting It Together

It helps to watch the doctrines operate together on a single set of facts. Return to Beacon Foods and Acme Corp., and suppose this time that Acme, a manufacturer, contracted to sell Beacon 50,000 specialty food containers at $2.00 each--$100,000 total--for delivery by March 1, knowing Beacon needed them to fulfill a $250,000 supply contract with a grocery chain. Acme delivered nothing.

The court's analysis would proceed roughly as follows. Step one: identify the governing law. Containers are goods, so UCC Article 2 governs. Step two: the direct damage measure. Beacon covered by buying equivalent containers elsewhere at $2.40 each, so its cover damages under Section 2-712 are $0.40 times 50,000, or $20,000. Step three: incidental damages. Beacon spent $3,000 on expedited shipping and sourcing to arrange the cover; those are recoverable under Section 2-715(1). Step four: consequential damages and foreseeability. Beacon's grocery contract was a special circumstance Acme knew about, satisfying Hadley's second branch, so the lost profit on that downstream deal is potentially recoverable under Section 2-715(2)--if Beacon proves it with reasonable certainty. Step five: mitigation. Because Beacon covered promptly and fulfilled the grocery contract on time, it avoided the downstream loss entirely; there is little or no consequential damage left to claim, because mitigation worked. Step six: the contract terms. If the Acme-Beacon contract contained a consequential-damages waiver and a liability cap, Steps four and five might be moot--the contract could bar the downstream claim regardless of foreseeability. Step seven: fees and interest. If the contract had a prevailing-party fee clause, Beacon adds its reasonable attorney's fees; the court adds prejudgment interest on the liquidated sum.

Beacon's clean recovery here is modest--roughly $23,000 plus fees and interest--precisely because mitigation worked and the goods were fungible. Change the facts so that no substitute containers existed, and the consequential lost profit on the $250,000 grocery contract suddenly dominates the case. That is the lesson the worked example is built to teach: in contract damages, the direct measure is usually small and easy; the action--and the risk--lives in the consequential layer, where foreseeability, certainty, mitigation, and the contract's own limitation clauses all converge.

Reading "Damage Statistics" Honestly

The article that seeded this one carried a trove of "Federal Damage Statistics for Contract Litigation"--charts of median awards by court, by year, by law firm, by damage type, drawn from a dataset described as roughly 23,718 federal district-court cases between 2003 and 2023. Numbers like these are catnip to a litigant and to a lawyer pitching a case. They are also extraordinarily easy to misread, and intellectual honesty requires being blunt about what such figures can and cannot tell you. So let us look at them clearly.

First and most important: these are not the typical outcomes of contract disputes; they are the outcomes of the rare contract disputes that produced a recorded monetary judgment in federal court. The overwhelming majority of contract disputes never reach a courtroom at all. They are resolved by negotiation, by a demand letter and a check, by arbitration, by mediation, or by a quiet settlement. Of the cases that are filed, the large majority settle before trial--commonly cited estimates put the share of civil cases that settle or are otherwise resolved without trial well above ninety percent, and contract cases are no exception. A dataset of adjudicated awards is therefore a dataset of survivors: the unusual disputes that did not settle, that went to judgment, and that produced a number a database could scrape. Whatever the median "award" is, it is the median of the cases that did not settle, which is a profoundly non-random slice of all contract disputes. Selection bias is not a footnote here; it is the headline.

Second: a "median award" tells you nothing about your odds of winning, or about how much you might have to spend to get there. The figures report what prevailing parties recovered, not how often plaintiffs prevailed or what the losers spent on the way to losing. A median recovery of $200,000 is cold comfort if half the plaintiffs recovered nothing and everyone--winners and losers alike--spent six figures on litigation.

Third: the categories are coarse and the labels are slippery. Aggregated court databases lump together breach-of-contract claims that are doctrinally worlds apart--a simple unpaid-invoice case and a sprawling construction-defect dispute land in the same "Contracts" bucket. Dollar figures are not adjusted for inflation across a twenty-year window, so a 2004 award and a 2022 award are not really comparable in real terms. "Median awarded amount" may or may not include interest, fees, or post-trial reductions, and different databases code these differently.

Fourth: the seductive breakdowns--by law firm, by district, by year--invite false inferences. A chart showing that cases handled by a particular firm carried a higher median award does not mean that firm wins bigger; it more likely reflects the kinds of clients and disputes that firm handles (large firms tend to handle large matters). A chart showing that one federal district has higher median awards than another reflects the mix of cases filed there--commercial hubs like the Southern District of New York see bigger commercial deals--not some local generosity toward plaintiffs. Correlation here is doing none of the causal work a casual reader might assume.

So what can such statistics legitimately tell you? Used carefully, they offer a rough sense of scale and distribution. Looking across the kind of distribution the seed data described, the bulk of recorded contract awards clustered in the low-to-mid six figures, with a meaningful tail of larger awards into the millions and a thin sliver of very large outliers--a shape consistent with what practitioners see: most contract cases that go to judgment are mid-sized commercial disputes, punctuated by occasional blockbusters. The attorney's-fee figures, where they appeared, were generally far smaller than the damage figures and concentrated at the low end--a reminder that recorded "fees and costs" entries often capture taxable costs and routine fee awards rather than the parties' full, eye-watering legal spend. These are useful priors for calibrating expectations. They are a terrible basis for predicting any particular case. The right way to use them is the way a careful lawyer uses any base rate: as a sanity check on a valuation that is really driven by the specific facts, the specific contract, and the specific forum.

The honest bottom line is the one the master principle implies. There is no "average" contract case, because contract damages are bespoke--computed from this contract, this breach, this provable loss, this mitigation record, and these limitation clauses. Statistics describe a population; your case is an individual. Treat the charts as scenery, not as a map, and do your real estimating the old-fashioned way, by working the doctrine through your facts.

Practical Takeaways

A few principles are worth carrying away from all of this.

The default remedy is expectation--the benefit of the bargain--because the law's goal is to make the injured party whole, not to punish the breacher. When expectation is too speculative, reliance (out-of-pocket costs) and restitution (the defendant's unjust gain) are the fallbacks, and choosing among the three is an early strategic decision.

Hadley v. Baxendale still governs the line between direct damages (which flow naturally from the breach) and consequential damages (recoverable only if foreseeable at contracting). Consequential damages are where the money usually is and where the litigation usually is; they can be defeated on foreseeability, certainty, or causation, and they are routinely waived or capped by contract.

For goods, the UCC supplies precise formulas--cover (2-712), market differential (2-713), warranty (2-714) for buyers; resale (2-706), market (2-708(1)), and lost profit (2-708(2)) for sellers--and the lost-volume doctrine keeps those formulas honest.

Liquidated-damages clauses are enforceable when they reasonably forecast hard-to-estimate harm, and void as penalties when they do not. The duty to mitigate subtracts avoidable losses, so a breached-upon party must act reasonably to limit the damage. Punitive damages are essentially unavailable for breach absent an independent tort. Specific performance is reserved for unique subject matter, chiefly real estate. And attorney's fees follow the American Rule unless a contract clause (or rare statute) shifts them--making that one clause among the most important in any agreement.

Finally, treat aggregate "damage statistics" with healthy skepticism: they describe the unusual cases that went to judgment, not the ordinary disputes that settle, and they are no substitute for working the doctrine through your own facts. The smartest move a party can make is to get the analysis right before signing--because the best contract damages are the ones you never have to litigate.

Frequently Asked Questions

What is the difference between expectation, reliance, and restitution damages? Expectation damages give you the benefit of your bargain--the position you would have been in if the contract had been performed. Reliance damages reimburse what you spent in reliance on the promise, restoring you to where you stood before the contract. Restitution forces the breaching party to give back any benefit you conferred on it, preventing unjust enrichment. Expectation is the default; reliance and restitution are fallbacks when expectation is too speculative or when restitution yields a better recovery. You generally must elect one theory rather than stacking them.

Why can't I recover all my lost profits when someone breaks our contract? Three doctrines stand between you and your lost profits. Foreseeability (the Hadley v. Baxendale rule) limits you to losses the breaching party could reasonably have anticipated at contracting--so special circumstances must have been communicated. Certainty requires you to prove the amount with reasonable (not perfect) precision rather than speculation, which is especially hard for new businesses. And the duty to mitigate subtracts any losses you could reasonably have avoided. A consequential-damages waiver in the contract can bar lost profits entirely, regardless of how foreseeable or certain they are.

Are liquidated-damages clauses enforceable? Yes, when they are genuine pre-estimates of damages and not disguised penalties. Courts apply a two-part test: were the actual damages difficult to estimate at contracting, and is the stipulated sum a reasonable forecast of the likely harm? If both are satisfied, the clause is enforced and usually becomes the exclusive remedy for that breach. If the amount is grossly disproportionate to any plausible harm--designed to punish or coerce rather than compensate--it is an unenforceable penalty, and you are thrown back on proving actual damages.

Do I really have to try to reduce my own damages after the other side breaches? Effectively, yes. The duty to mitigate (the avoidable-consequences doctrine) means you cannot recover losses you could have avoided through reasonable effort. You are not penalized for failing to mitigate, but the avoidable portion of your loss is subtracted from your award. A fired employee must reasonably look for comparable work; a buyer denied goods should usually cover; a landlord whose tenant leaves should try to re-let. The standard is reasonableness, and you can recover the reasonable costs of mitigating even if your efforts ultimately fail.

Can I get punitive damages for a breach of contract? Almost never. Because contract damages compensate rather than punish, punitive damages are unavailable for breach of contract no matter how deliberate or cynical the breach. The narrow exception is when the same conduct is also an independent tort--fraud, conversion, certain fiduciary breaches, or insurer bad faith in some states--in which case punitive damages may attach to the tort, not to the contract.

When will a court order the other party to actually perform instead of just paying money? Only when money damages would be inadequate. The classic case is real estate, because every parcel of land is treated as unique. The same applies to genuinely unique goods--a one-of-a-kind item with no market substitute (UCC Section 2-716). For ordinary, fungible goods and for personal services, courts deny specific performance, because cover provides an adequate substitute and courts will not supervise ongoing performance or compel someone to work.

Will the losing party have to pay my attorney's fees? Usually not, unless your contract says so. Under the American Rule, each side bears its own fees regardless of who wins. The most reliable way to shift fees is a prevailing-party attorney's-fee clause in the contract, which courts widely enforce. A few statutes also shift fees in particular case types, and some states make one-sided fee clauses reciprocal by statute. The presence or absence of a fee clause can completely change whether a claim is economically worth pursuing.

Do those "median contract award" statistics tell me what my case is worth? No. Aggregate award statistics describe only the small, non-random subset of contract disputes that did not settle and produced a recorded judgment--the vast majority of disputes settle and never appear. The figures do not tell you your odds of winning, what you would spend to get there, or how doctrines like mitigation and foreseeability would shape your specific recovery. Breakdowns by court, year, or law firm reflect the mix of cases, not any causal effect. Use such numbers as a rough sense of scale, never as a prediction; your case's value comes from working the doctrine through your own facts.

Related Articles

This article provides general information only and is not legal advice. Contract damages turn on the specific facts, the governing state's law, and the precise terms of your agreement, all of which vary. For advice about a particular situation, consult qualified counsel licensed in your jurisdiction.