How to Calculate Damages in a Breach of Contract Case

Quick takeaways

• Damages in a breach of contract case typically aim to put the non-breaching party in the position they would have been in if the contract had been performed (often called “benefit of the bargain” in U.S. contract law).
• Most calculations start with expected value (what you would have received) and then account for what you actually received plus any mitigation (what you could reasonably obtain after the breach).
• You’ll often calculate damages using one or more components:

  • Direct damages (unpaid invoices, replacement costs, lost profits)
  • Incidental damages (extra expenses tied to the breach)
  • Consequential damages (special losses that were foreseeable and properly connected)
  • Liquidated damages (pre-agreed amounts, if enforceable)
  • Prejudgment interest (jurisdiction-specific; can materially change totals)
• DocketMath helps you turn those components into a repeatable worksheet—so the math stays consistent across pleadings, negotiations, and settlement modeling. Start with the calculator workflow here: /tools.

Inputs you need

Before you calculate damages, gather inputs that drive the outcome. If you omit these details, the math may be precise but still wrong for the theory you’re using.

1) Contract and performance timeline

• Contract start date and end date
• Date of breach (or earliest breach event)
• Payment terms (net 15/30/60, milestones, acceptance dates)
• Delivery or service dates (scheduled vs. actual)

2) The “expected” numbers (what performance would have produced)

Pick values that match your damages theory:

• Invoice amounts due under the contract
• Remaining contract price (for unfinished work)
• Scheduled deliverables / units and the price per unit
• Budgeted costs you planned to incur (if you’re pursuing lost profits)

3) What you received after the breach (offsets and mitigation)

Damages calculations frequently subtract offsets such as:

• Payments actually received after breach
• Replacement performance obtained (especially if you’re measuring cover/replace)
• Resale proceeds (if goods were resold)
• Savings from not performing (sometimes treated as offsets depending on the theory)

4) Incidental and consequential components (only if supported)

• Incidental costs tied to the breach (expediting shipments, additional admin, rework)
• Consequential losses you claim (lost customers, downstream project delays, lost opportunities)
• Proof items: invoices, emails, project plans, expert summaries, vendor quotes

5) Liquidated damages (if the contract has them)

• Liquidated damages clause text and amount formula
• Trigger condition(s)
• Any cap or ceiling in the clause
• Evidence the clause is (or is not) enforceable under the governing law (you’ll need case/jurisdiction analysis later)

6) Interest inputs

Interest can change totals substantially:

• Whether you seek prejudgment interest
• Start date for interest accrual (often tied to breach date, invoice due date, or damages certainty)
• Interest rate (statutory or contractual) and compounding method (if any)

How the calculation works

Damages math is usually a structured sequence: gross expected value → subtract offsets → add allowable extras → apply interest and (if relevant) liquidated damages rules.

Step 1: Choose the damages model that matches your claim

Common models you’ll see in practice:

• Unpaid amounts model (direct damages)
  Best when the dispute is mainly “you didn’t pay” or “you didn’t deliver and the invoices are clear.”

• Replacement / cover model (direct damages)
  Often used for goods or specific deliverable failures. You estimate what it costs to obtain equivalent performance elsewhere.

• Lost profits model (direct + proof-heavy)
  Used when the breach prevented you from making revenue. You typically need a reliable baseline:

  • expected revenue from the contract
  • less variable costs you would have paid to generate that revenue

• Consequential damages model (narrower & evidence-driven)
  Used for downstream losses. A key focus is whether the losses were foreseeable and tied to the breach through contract context.

DocketMath supports this by helping you map your claim into categories so your output isn’t a single undifferentiated “number.”

Step 2: Calculate direct damages component(s)

A) If you’re using the unpaid/underperformance model

A common structure:

1. Contract value remaining (or unpaid invoices)
2. Minus amounts recovered (payments made after breach, refunds, partial performance)

Direct damages (unpaid model)

• Direct = Contract value remaining - Payments/credits received

B) If you’re using a replacement/cover model

A common structure:

• Replacement cost (reasonable substitute price)
• Minus any benefit you still received (resale proceeds, value of delivered partial goods)

Direct damages (replacement model)

• Direct = Cost to replace - Value received (or resale proceeds)

C) If you’re using a lost profits model

A frequent “high-level” structure:

• Expected gross profit = expected revenue - variable costs
• Multiply or adjust based on time/volume you can justify

Direct damages (lost profits model)

• Direct = Expected revenue from contract - Variable costs avoided/required

Because lost profits involve forecast risk, the supporting documentation matters as much as the arithmetic.

Step 3: Add incidental damages (if you have documentation)

Incidental damages are typically extra expenses that flow from dealing with the breach. Examples include:

• shipping/expediting costs
• administrative costs to secure replacements
• costs to mitigate

Incidental damages

• Incidental = Sum of documented extra costs attributable to the breach

Step 4: Evaluate consequential damages (when applicable)

Consequential damages generally require stronger justification:

• they must be linked to the breach and
• often require foreseeability based on what the parties knew or should have known at contracting.

Use a repeatable method:

• Identify the downstream loss event
• Quantify loss using contracts, invoices, project accounting, or expert calculations
• Confirm the timeline (breach → impact → losses)

Consequential damages

• Consequential = Documented downstream losses with breach linkage

Step 5: Handle liquidated damages (if the contract includes them)

If your contract includes liquidated damages, many disputes turn on the clause:

• Is the liquidated amount triggered?
• Does it operate as an exclusive remedy, or can you also claim other damages?
• Is it enforceable under the governing contract law?

In a worksheet, you can treat liquidated damages as either:

• the total damages figure (if the clause replaces other amounts), or
• a damages component (if the clause allows additional categories).

Liquidated damages

• Liquidated = Clause formula result (or capped amount)

Step 6: Apply offsets and mitigation properly

Offsets and mitigation reduce the damages baseline. You may need to separate:

• amounts the non-breaching party already recovered, and
• costs saved by avoiding performance.

For calculations, keep two columns in your model:

• Recoveries (offsets)
• Avoided costs / savings

That discipline helps you avoid mixing mitigation with unrelated business outcomes.

Step 7: Add prejudgment interest (jurisdiction-specific)

Interest often runs from:

• the breach date, or
• when a payment became due, or
• when damages became “liquid” or ascertainable (varies by law and facts)

Interest arithmetic is straightforward once you know the rules:

• simple vs. compound
• rate (contract or statutory)
• start date and end date (often judgment or settlement date)

Prejudgment interest (simple example)

• Interest = Principal × Rate × (Days/365)

DocketMath can be used to keep the “interest math” consistent—especially when you’re producing revised numbers for settlement rounds.

Common pitfalls

1. Using the wrong baseline

   • Example: starting with the contract’s full value rather than remaining unpaid / remaining performance once partial performance already occurred.

2. Mixing categories without tracking offsets

   • Keep a ledger of what you subtract and why. A one-line “less mitigation” without detail often collapses under scrutiny.

3. Double-counting recoveries

   • If you subtract payments received, don’t also subtract the same amounts again as “value received” in a replacement model.

4. Under-documenting consequential losses

   • Consequential losses tend to be the first thing counterparties challenge. Build your calculation so every figure ties to an exhibit (quote, invoice, timeline, contract schedule).

5. Ignoring interest

   • Interest can be the difference between “reasonable settlement” and “out-of-range demand,” particularly for longer accrual windows.

6. Assuming one formula fits all

   • A contract dispute with unpaid milestones is not the same as a goods delivery dispute, and a goods dispute is not the same as a service breach. Pick the model that matches the facts.

Sources and references

Because damages calculation is highly fact- and jurisdiction-dependent, this article focuses on widely used calculation structures rather than a single statute citation.

For jurisdiction-aware modeling, you’ll typically need to align the following concepts with governing law:

• contract damages objectives (often “expectation”)
• mitigation/offset principles
• enforceability and treatment of liquidated damages
• rules for prejudgment interest (rate, accrual date, calculation method)

If you’re working under U.S. law, these frameworks are commonly reflected in:

• state contract common law,
• and, for goods transactions, the Uniform Commercial Code (UCC) as adopted by the relevant state.

Next steps

Use DocketMath to convert your damages theory into a repeatable calculation.

• Step 1: