The phrase “force majeure” is often used as shorthand for anything extraordinary. Contract governance becomes stronger when leaders stop using it that way.
The Week 12 material discusses both force majeure and frustration.
The teaching notes describe force majeure as a contractual clause dealing with events such as flooding, earthquake, war, strike or riot. They describe frustration as a legal doctrine applying where, without fault of either party, a supervening event makes performance impossible or radically different from what was originally contemplated.
The examples are educational and some are legally debatable. [FACT CHECK REQUIRED]
The strategic distinction is essential:
force majeure is primarily a matter of contract design; frustration is a legal doctrine that may operate outside or beyond the parties' express allocation.
The Strategic Context
Projects face events that are difficult to predict.
Natural hazards, government action, major supply disruption, war, strikes, pandemics, regulatory change and exceptional weather can affect delivery.
Leaders need to decide which of those events should be expressly addressed in the contract.
If the contract specifies:
- what events qualify;
- what notice is required;
- whether time is extended;
- whether cost is recoverable;
- whether performance is suspended;
- when termination becomes available;
then the parties have designed a response.
If the contract does not address the event, a party may look to other legal doctrines such as frustration, but the threshold for frustration can be high and depends on governing law. [FACT CHECK REQUIRED]
This is why exceptional-event governance begins before contract award.
What Leaders Commonly Misread
The first mistake is assuming force majeure has one universal legal meaning.
Its effect usually depends heavily on the wording of the contract.
The second is assuming any unforeseen event frustrates a contract.
The Week 12 notes themselves caution that gradual increases in difficulty or numerous variations do not automatically amount to frustration.
The third is treating increased cost as the same as impossibility.
A contract becoming harder or less profitable is not necessarily the same as performance becoming legally frustrated.
The fourth is drafting a long list of force-majeure events without specifying consequences.
An event list is only half a mechanism.
The fifth is failing to connect force majeure with EOT, insurance, supply-chain contingency and termination.
Reframing the Issue
Use the ERANORTH Exceptional Event Boundary.
Allocated event
If the parties can identify the event category and agree the consequences, put it in the contract.
Unallocated supervening event
If an event falls outside the contractual allocation and fundamentally changes the performance obligation, legal frustration may become relevant.
This is a simplified decision architecture, not legal advice.
Current Australian frustration law and any applicable legislation require verification. [FACT CHECK REQUIRED]
Strategic Analysis: Drafting Is About Consequence, Not Labels
Consider a hypothetical engineering contract dependent on one imported specialist component.
A geopolitical event stops export from the supplier's country.
Calling the event “force majeure” does not answer the commercial questions.
The contract needs to determine:
- must the contractor source an alternative?
- who bears additional cost?
- does time extend?
- what evidence must be provided?
- how long can suspension continue?
- when can either party terminate?
- what happens to advance payments and partially completed work?
The label does not manage the event.
The consequence mechanism does.
The same principle applies to flood, epidemic or regulatory prohibition.
Frustration as a Residual Legal Concept
The Week 12 notes use examples such as illness preventing a scheduled performance, refusal of approval and severe unexpected conditions.
Those examples illustrate the idea of a supervening event, but whether a construction contract is legally frustrated depends on far more than surprise. [FACT CHECK REQUIRED]
Modern contracts are often detailed precisely because the parties want to allocate exceptional-event risk rather than leave it to a residual doctrine.
The more comprehensively the contract deals with an event, the less room there may be to argue that the event was outside the contractual allocation.
That is a major drafting consideration.
Strategic Analysis: Exceptional Events Test Organisational Resilience
Contract language matters most when external conditions are changing quickly.
A project that relies on one country, one port, one specialist supplier or one regulatory approval may have concentrated exposure even if its force-majeure clause is well drafted.
Leaders should therefore connect exceptional-event clauses with operational resilience.
Questions should include whether alternative suppliers exist, whether substitute materials are approved, whether inventory buffers are appropriate, whether the design can tolerate substitution and how long the organisation can operate without the project outcome.
This reframes force majeure from a legal escape clause into one part of resilience design.
The contract allocates consequences.
The operating model determines whether the organisation can absorb them.
Decision Framework
For each material exceptional event category, ask:
1. Foreseeability
Can the event reasonably be identified at procurement stage?
2. Control
Which party is better able to prevent, absorb or mitigate it?
3. Consequence
Should the event affect time, cost, suspension or termination?
4. Evidence
What notice and proof are required?
5. Duration
When does temporary relief become a right to exit?
6. Residual exposure
What happens if the event falls outside the clause entirely?
This is risk allocation, not boilerplate drafting.
From Strategy to Execution
Immediate action: review exceptional-event clauses against the actual project's risk register.
Medium-term capability building: integrate commercial, legal, insurance and supply-chain teams when drafting material force-majeure provisions.
Long-term strategic positioning: analyse how major external events affected past contracts and update standard clauses based on evidence rather than inherited wording.
Signals to Monitor
Watch for force-majeure clauses copied from unrelated contracts, event lists with no clear consequences, no relationship between force majeure and EOT, termination rights triggered too early or too late, supply-chain concentration not reflected in the clause, or project teams using “frustration” as an informal synonym for difficulty.
Another warning sign is uncertainty about what happens financially during suspension.
Questions for the Leadership Team
- Which exceptional events are material for this project?
- Which can be allocated expressly?
- Who can best mitigate each event?
- What time and cost consequence should follow?
- When should prolonged disruption create an exit right?
- What remains outside the contract?
- Are we relying on labels instead of designing consequences?
Closing Perspective
Force majeure and frustration belong to the same family of uncertainty but operate differently.
The contract should handle foreseeable categories of exceptional risk deliberately.
Frustration should not be the project plan.
Related article: When the Contract Becomes Impossible to Perform: Governing the Economics of Frustration
Related article: Risk Allocation Is Not Risk Elimination: What Procurement Models Really Change
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.