A consequence can be devastating to your business and still be too remote from the breach to recover.
The Week 5 materials explain remoteness primarily through Hadley v Baxendale and Victoria Laundry. The core distinction is between loss that arises naturally from the breach and unusual loss that depends on special circumstances known to the parties when the contract was made.
For leaders, that creates a strategic communication problem.
A supplier cannot price, manage or contract for a dependency it does not know exists.
The Strategic Context
Modern supply chains create disproportionate dependencies.
A small component can stop a large plant.
A delayed report can hold up an investment decision.
A software outage can affect thousands of customers.
Inside the buyer's organisation, those consequences may seem obvious. To the supplier, they may not be.
The Week 5 material's treatment of Victoria Laundry illustrates this distinction by separating ordinary lost profits from an unusually lucrative contract that the defendant did not know about.
What Leaders Commonly Misread
The first mistake is assuming causation alone is enough. A breach may be part of the causal chain while the resulting loss remains too remote.
The second is assuming every downstream business consequence is the supplier's responsibility.
The third is failing to communicate special circumstances before contracting.
The fourth is using hindsight. Once breach occurs, it may feel obvious that the consequence was foreseeable. The source frames the analysis around what was reasonably contemplated when the contract was formed.
The modern Australian formulation of contractual remoteness should be independently verified. [FACT CHECK REQUIRED]
Reframing the Issue
Remoteness can be reframed as dependency disclosure.
Where an obligation supports an unusual or high-consequence business dependency, leadership should decide whether that dependency needs to be communicated and reflected in the contract.
This can improve:
- pricing;
- contingency;
- insurance;
- limitation clauses;
- delivery priorities.
Strategic Analysis: Hidden Dependencies Create Hidden Loss
Hypothetical infrastructure example: A specialist supplier is contracted to deliver a $40,000 component. The supplier is not told that the component is needed for a one-day possession window and that a missed date could postpone commissioning by three months.
If the supplier is late, the buyer may experience a very large loss.
The commercial question is not simply whether the late component caused it. The Week 5 remoteness principle asks whether such a consequence fell within the relevant contemplation of the parties.
This should influence contract formation.
Critical dependencies need to be visible not only in the internal schedule but in the commercial relationship.
Decision Framework
For every high-consequence obligation, ask:
Natural loss
What loss would ordinarily follow if the obligation is breached?
Special circumstances
What unusual dependencies increase the consequence?
Knowledge
Has the counterparty been told?
Contract treatment
Should the risk be addressed through liability provisions, insurance or another mechanism?
Evidence
How will the organisation prove what was known at formation?
Current law
Does the proposed analysis align with contemporary Australian remoteness principles? [FACT CHECK REQUIRED]
From Strategy to Execution
Immediate action: identify contracts where a low-value deliverable protects a high-value dependency.
Medium-term capability building: integrate critical-path and commercial-risk reviews before contract signature.
Long-term strategic positioning: improve supplier transparency around true consequence while protecting commercially sensitive information appropriately.
Portfolio Governance Implication
Remoteness analysis also helps leadership identify where risk communication is failing. If major claims repeatedly depend on special circumstances that suppliers say they never knew about, the problem may sit in procurement handover or scope communication rather than litigation strategy.
A useful portfolio measure is the number of critical dependencies that are internally known but not reflected in contract documents, tender information or supplier briefings. Reducing that gap improves both delivery resilience and the quality of future claims.
Governance Test
Critical dependencies should be translated into explicit commercial information before award. If a supplier's delay could stop a production line, miss a possession window or jeopardise a customer commitment, the procurement team should decide how much of that context must be communicated and how it should influence liability allocation. This is not only about future litigation; it can also change the supplier's planning, contingency and price.
Signals to Monitor
Watch for critical suppliers unaware of downstream milestones, contract values far smaller than potential business interruption, special circumstances known only to project teams and claims being assembled from consequences never discussed during procurement.
Questions for the Leadership Team
- Which small obligations carry disproportionate enterprise consequences?
- Does the supplier know those consequences?
- Are critical dependencies reflected in liability and insurance strategy?
- Can we prove what special circumstances were communicated?
- Are internal project assumptions aligned with contractual risk allocation?
- What losses are we assuming are recoverable without testing remoteness?
Closing Perspective
Remoteness is not merely a limit on damages.
It is a reminder that commercial risk allocation depends on shared knowledge.
If a dependency matters enough to create a major claim, it may matter enough to communicate before the contract is signed.
Related article: Damages Are About the Lost Bargain, Not Punishment
Related article: Exclusion Clauses Are Risk Allocation, Not Escape Clauses
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.