How to Calculate Damages in a Breach of Contract Case

Quick takeaways

Run this scenario in DocketMath using the tools directory.

• In most breach of contract damages analyses, you start by estimating what you would have received under the contract and subtracting what you actually received (or what the breaching party’s performance reduced in value).
• Courts usually aim for “expectation damages”—placing the non-breaching party in the position they would have been in if the contract were performed as promised.
• The calculation typically has three building blocks: lost profits and/or contract price differentials, incidental and consequential costs, and offsets or mitigation credits.
• Documentation matters more than math. Your numbers are only as persuasive as your time records, invoices, market comparables, and mitigation evidence.
• Different jurisdictions and contract language can change what’s recoverable, especially for consequential damages and liquidated damages.

Inputs you need

Before any calculation, gather inputs that let you build a defensible damages timeline. DocketMath can help you organize the math and the evidence trail.

Use this intake checklist as your baseline for N/A work in this jurisdiction.

• jurisdiction selection
• key dates and triggering events
• amounts or rates
• any caps or overrides

If any of these inputs are uncertain, document the assumption before you run the tool.

1) Contract and claim basics

• Contract value / price terms

  • Total contract price (or unit prices and quantities)
  • Milestones and delivery schedule
  • Service dates or delivery windows
• Breach details

  • Date of breach (or when performance became nonconforming)
  • Nature of breach (nonperformance, late performance, defective performance)
• Cure/termination language

  • Whether the contract allowed cure and whether cure occurred
  • Any termination rights and dates

2) Your “but-for” performance estimate

This is the counterfactual: what you would have had if the contract had been performed.

• Expected revenue

  • Contract billings you would have invoiced
  • Expected sales volume or throughput for goods/services
• Expected costs to perform

  • Direct labor, materials, subcontractor costs
  • Manufacturing or delivery costs
• Timing assumptions

  • When the work would have started and ended
  • Discounting periods (if applicable in your analysis workflow)

3) What happened instead (the “actual” world)

• Amounts you actually received

  • Payments received
  • Replacement performance received from an alternative supplier
• Costs you incurred because of the breach

  • Rerouting, expedited shipping
  • Transition costs
  • Extra admin costs tied to the breach

4) Offsets and mitigation evidence

• Mitigation / substitute cover

  • Costs and revenues from substitute performance
  • Timing of substitute acquisition
• Amounts recoverable from third parties

  • Insurance proceeds directly tied to the loss (some analyses require careful matching)
  • Vendor refunds, credits, or salvage

5) Damage type controls from the contract and evidence

• Consequential damages waiver or limitation
• Liquidated damages clause

  • The stated formula and any caps
• Attorney’s fees and costs clause

  • Fees are often not “damages,” but they can drive the total recovery story in litigation filings
• Interest or payment terms

  • Contractual interest rates
  • Whether prejudgment interest is claimed in your worksheet

How the calculation works

Think of damages as: Net expectation loss + recoverable additional items − offsets.

Because you can’t compute “damages” as one universal number, the calculation often branches into different models depending on the breach facts.

DocketMath applies the this jurisdiction rule set to the inputs, then runs the calculation in ordered steps. It validates the trigger date, applies rate or cap logic, and produces a breakdown you can audit. If you change any one variable, the tool recalculates the downstream outputs immediately.

Step 1: Identify the relevant damages model

Use one (or a hybrid) of these common structures:

1. Contract price differential

   • Common when the non-breaching party is a buyer and the market (or substitute) cost determines the gap.
   • Formula (conceptual):

     • Damages ≈ Contract price − Substitute/replacement value (or market value, depending on jurisdiction and facts)

2. **Lost profits (expectation)

   • Common when performance would have produced profit, and you can support the profit estimate with evidence.
   • Formula (conceptual):

     • Damages ≈ Expected revenue − costs you would have incurred to earn that revenue − offsets

3. **Cost of cover / repair (sometimes)

   • Common when the promise involved specific deliverables and you incurred replacement or repair costs.
   • Formula (conceptual):

     • Damages ≈ Reasonable replacement/repair cost − any benefit received

4. **Liquidated damages (if enforceable and applicable)

   • If the contract includes liquidated damages, many analyses start by using that number rather than recalculating expectancy—subject to enforceability.

Step 2: Compute the “expectation baseline”

A practical way is to build a per-period and per-deliverable timeline so your damages number has a narrative.

Build a simple expectation schedule

Create a table with these columns:

Then aggregate:

• Total expected value
• Total actual value received
• Net difference

Step 3: Add incidental and consequential costs (only if recoverable)

Not every “extra cost” qualifies. You typically include:

• Incidental damages (reasonable costs incurred in response to the breach)
• Consequential damages (special losses that result from breach, often requiring foreseeability and sometimes special notice)

A practical approach is to label costs into buckets:

• Direct, contract-related costs (often easier to justify)
• Incidental costs (administrative, logistics, expedited expenses)
• Consequential costs (lost opportunities, downstream losses)

Then apply two gates:

1. Causation gate: Did the breach cause the cost/loss?
2. Foreseeability/contract gate: Did the contract or surrounding facts make these losses within the parties’ contemplation?

Step 4: Subtract mitigation and offsets

Mitigation can reduce recoverable damages if the non-breaching party took reasonable steps to avoid further harm.

Common offsets:

• Cover savings (what you spent to replace performance vs. what you would have spent originally)
• Payments you received after breach that compensate for the same loss
• Credits/refunds tied to the breach

Mitigation math example structure

• Gross loss estimate: Expected value − actual value received
• Minus mitigation offsets: Substitute revenues/cost offsets that cover the same harm
• Result: Net compensable loss (before interest/fees, if tracked)

Step 5: Consider timing and interest (when your worksheet includes it)

Damages are sometimes claimed with:

• Prejudgment interest for the time value of money (depending on jurisdiction and claim type)
• Post-judgment interest after entry of judgment (typically governed by statute)

If your DocketMath workflow tracks interest, you’ll need:

• Start date (often breach date or due date for payment, depending on theory)
• Interest rate (contractual rate or statutory rate)
• End date (settlement date, judgment date, or claim cutoff)

Common pitfalls

1. Using only “amounts the defendant didn’t pay”

   • Missing offsets and the correct expectation baseline can under- or overstate damages.

2. Overreaching on speculative lost profits

   • Lost profits often require a concrete method, such as historical margins, pipeline conversion rates, or contracts with third parties. Courts can reject numbers that don’t show reasonable certainty.

3. Ignoring contract limitations

   • A limitation-of-damages clause may exclude consequential damages or cap them. Liquidated damages clauses may replace other damages measures if enforceable.

4. Double counting

   • Example: counting both the gross contract price gap and the cost of cover without netting the overlap.

5. Weak mitigation documentation

   • If you claim mitigation-based offsets or argue mitigation was reasonable, keep receipts, emails showing urgency, and records of alternative sourcing.

6. Forgetting timing

   • A damages model that assumes all losses occurred at one date can distort interest calculations and present-tense valuation.

7. Mixing damages with attorney’s fees

   • Fees may be separately recoverable under contract or statute in some contexts. If you combine them, your damages “math” may not match the legal theory in the pleadings.

Sources and references

• Uniform Commercial Code (UCC) concepts often used in contract damages analyses, including principles related to cover and market comparisons (where applicable to the transaction type).
• General breach-of-contract remedies framework: expectation damages designed to put the non-breaching party in the position they would have occupied with performance.
• Contract interpretation doctrines and enforcement of liquidated damages versus penalties (where contract includes such provisions).

(Because this post avoids jurisdiction-specific legal advice, it stays focused on the calculation structures most commonly used in breach-of-contract damages workflows.)

Next steps

After you run the N/A calculation, capture the inputs and output in the matter record. You can start directly in DocketMath: Open the calculator.

Capture the source for each input so another team member can verify the same result quickly.

Related reading

• How to calculate deadlines in Delaware — Full how-to guide with jurisdiction-specific rules
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Statute of limitations in United States (Federal): how to estimate the deadline — Full how-to guide with jurisdiction-specific rules