The purpose of contract damages is not to punish failure. It is to compensate for the economic position the breach destroyed.
The Week 5 remedies material repeatedly states this compensatory principle. As far as money can do so, damages seek to place the injured party in the position it would have occupied had the contract been properly performed.
That principle sounds simple, but it changes the way leaders should frame claims.
The starting question is not, “How badly did the supplier behave?”
It is, “What economic result did the organisation lose because performance failed?”
The Strategic Context
Breach can produce many consequences:
- replacement cost;
- lost revenue;
- property damage;
- delay;
- wasted expenditure;
- reduced margins;
- customer impact.
Not all consequences will be legally recoverable, and some may be limited by remoteness or mitigation.
But the Week 5 source establishes the core objective: compensation rather than punishment.
It distinguishes unliquidated damages assessed by a court from liquidated damages pre-agreed in the contract.
It also recognises nominal damages where breach occurs without measurable financial loss.
What Leaders Commonly Misread
The first mistake is treating damages as a fine.
The second is calculating the claim from the contract price instead of the actual lost economic position.
The third is assuming every internal consequence of breach is recoverable.
The fourth is failing to preserve evidence. The Week 5 notes stress that assessment depends heavily on proof of loss and expense.
The source also mentions damages for distress or disappointment in some situations, but that proposition should be qualified and verified before publication. [FACT CHECK REQUIRED]
Reframing the Issue
A damages claim should be treated as an economic reconstruction.
Leadership should model two worlds:
- the financial position if the contract had been performed;
- the actual financial position after breach and reasonable mitigation.
The difference becomes the starting point for loss analysis, subject to legal limits.
Strategic Analysis: Expected Position Versus Actual Position
The Week 5 notes use a bus-hire example. The replacement bus costs more than the contracted bus, so the difference illustrates direct compensatory loss.
The tutorial's Nixen scenario uses a different pattern. Nixen expected a $50,000 contract but may be able to accept an alternative $35,000 engagement. That alternative becomes relevant to mitigation and therefore the eventual loss.
Hypothetical project example: A supplier fails to deliver a machine for $400,000. The buyer obtains an equivalent replacement for $450,000 and spends another $20,000 on expedited transport. The core economic analysis begins with the extra cost caused by breach, not with a desire to “charge the supplier the full contract value”.
The legal recoverability of each amount depends on causation, remoteness, mitigation and the contract itself.
Decision Framework
Build damages analysis around:
Baseline
What financial position was expected under proper performance?
Actual outcome
What happened after breach?
Causation
Which losses were caused by the breach?
Evidence
Can each amount be substantiated?
Remoteness
Was the type of loss sufficiently connected and foreseeable? [FACT CHECK REQUIRED]
Mitigation
What reasonable steps reduced or could have reduced the loss?
This creates a disciplined claim.
From Strategy to Execution
Immediate action: establish a loss register when a material breach occurs.
Medium-term capability building: integrate finance into contract claims early. Commercial teams should not reconstruct economic loss months later from incomplete records.
Long-term strategic positioning: use post-breach data to improve future risk pricing and contract design.
Governance Implication
Damages analysis should be separated from performance assessment. Project teams may overstate loss because they are frustrated with poor delivery, while finance teams may understate operational consequences because they see only invoices.
A cross-functional claim review should connect contract, schedule, operational and financial evidence. This improves both accuracy and executive credibility. A disciplined organisation should be able to explain every material head of loss in plain commercial terms before it converts that amount into a legal claim.
Governance Test
A claim should distinguish gross impact from recoverable loss. Revenue foregone, internal time, replacement cost and downstream consequences should not simply be added together without testing for overlap, avoided cost and mitigation. This discipline prevents double counting and helps executives compare the legal claim with the true enterprise impact of the breach. The two figures may be different, and both can be useful for different decisions.
Signals to Monitor
Watch for claims based mainly on anger, damages schedules unsupported by invoices or forecasts, duplicate recovery across multiple heads of loss, failure to distinguish gross revenue from lost profit and claims that ignore savings created by non-performance.
Questions for the Leadership Team
- What financial position would proper performance have produced?
- Which losses are directly attributable to the breach?
- What evidence supports those losses?
- What costs were avoided because the contract was not completed?
- Have mitigation actions reduced the claim?
- Are we seeking compensation or attempting to punish the counterparty?
Closing Perspective
A strong damages claim is not the largest number management can construct.
It is the clearest evidence-based explanation of the economic position the organisation reasonably expected and the loss the breach actually caused.
Related article: Not Every Loss Is Recoverable: Remoteness and the Information Leaders Must Share
Related article: Rescission Is Not an Undo Button: Choosing Remedies After Defective Consent
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.