Force Majeure Basics
Force majeure is contract language for an outside event that stops, delays, or materially disrupts a promised task. The words do not create a universal legal escape hatch. Courts usually start with the clause itself, then apply the governing law and the evidence.
Mark 31 factual links.
A flood that closes the only road to a warehouse may fit a clause. A supplier’s higher price for an available component often will not. The distinction turns on wording, causation, and reasonable alternatives.
Log 1 event date.
In United States contracts, no single nationwide definition controls every deal. A 2025 Cornell Legal Information Institute overview notes that courts often read such clauses narrowly, and that ordinary economic hardship is usually not enough. Article 2 of the Uniform Commercial Code has a separate rule for sales of goods: Section 2-615 addresses delay or non-delivery made impracticable by an unforeseen contingency. That statute does not replace a carefully drafted clause. It frames one possible background rule.
Keep 2 source records.
Read the exact text first.
Date 3 key notices.
Most clauses use two layers. The first is an event list, such as earthquake, fire, war, strike, epidemic, government order, port closure, or utility failure. The second is a limiting test: the event must be outside the claiming party’s reasonable control and must prevent, hinder, or delay performance. A list of 12 events is not automatically broader than a list of 4; the words around the list can narrow its reach. An event may be dramatic yet irrelevant if it did not cause the missed obligation.
Check 4 clause terms.
A force majeure clause also differs from a price-adjustment clause, a hardship clause, insurance coverage, and a general excuse doctrine. Insurance may pay for property loss without excusing a delivery date. A hardship clause may trigger renegotiation after a cost swing. Impossibility or frustration doctrines may exist under local law even when a contract has no force majeure wording. Each route has its own test, remedy, and proof.
Rule 33: compare routes.
Contract counsel can match the route to the jurisdiction and transaction.
Save 5 carrier updates.
Risks And Disputes
The first dispute is often about the event’s scope. A clause naming “government action” may cover a binding export ban, but not every agency announcement or local recommendation. A clause that names labor strikes may exclude a strike by the claiming party’s own workforce if poor management caused it. Vague catch-all language creates room for argument, which, frankly, is expensive when performance has already failed.
Map 6 causal steps.
Causation is the next pressure point. The claiming party should show a direct chain from event to obligation: a closure order blocked access, access blocked production, and production blocked shipment on the agreed date. A record showing only that conditions were difficult leaves gaps. Courts may also ask if inventory, substitute transportation, extra shifts, or another source could have reduced the delay. Mitigation does not demand magic. It does call for timely, documented efforts.
Record 7 alternatives.
Notice can decide a claim before the merits receive attention. Many clauses require written notice within 5, 10, or 30 days after the event, plus periodic updates. A party that waits until an invoice is overdue may lose contractual protection even if the event itself fits. Identify the notice address, delivery method, and content rule. On a 2024 purchase order, a notice sent to a sales representative rather than the named legal email address created an avoidable fight.
Compare 8 delivery options.
Remedies deserve equal attention. Some clauses suspend duties for the event’s duration; others extend deadlines by the number of lost days. A 60-day delay may give either party a termination right under some agreements. Payment for work already accepted, confidentiality, indemnity, and dispute-resolution duties may survive. Read the survival provision with the force majeure language. A pause is not always a cancellation.
File 9 status updates.
Drafting A Clause
Name Relevant Events
Choose events tied to the deal’s actual dependencies. A construction contract may mention severe weather, site closure, and permit action. A goods contract may address port disruption, embargoes, and carrier interruption. Avoid copying a list from an unrelated agreement. A long list cannot cure a missing operational link.
Review 10 notice details.
Set A Causation Test
State whether an event must “prevent,” “materially hinder,” or merely “delay” performance. “Prevent” is a higher bar than “delay.” Define the affected obligation where useful, such as delivery, access to a site, or a scheduled event. This choice sets the factual question a later reviewer must answer.
Store 11 supporting records.
Address Foreseeability
Decide how known risks are treated at signing. If seasonal storms are normal in a region, the clause can tie relief to a stated intensity, a closure order, or loss of a named route. Forecast risk before the contract date may weaken a broad claim. The calendar matters.
Track 12 affected days.
Require Prompt Notice
Specify a notice deadline, recipient, delivery channel, and minimum content. A workable notice can identify the event, affected duty, expected duration, steps taken, and next update date. Ten days may suit a complex supply chain; 24 hours may suit a live event contract. Match the period to the deal.
List 13 mitigation actions.
Describe Mitigation
Require commercially reasonable mitigation, then describe boundaries. The clause might call for alternate sourcing, remote performance, or partial delivery where feasible. It should not force a party to accept unsafe work or a ruinous substitute. That balance, annoyingly, needs transaction-specific judgment rather than boilerplate.
Match 14 contract words.
Choose The Remedy
State the result of a valid claim. Options include suspension, a matching extension, partial performance, allocation among customers, renegotiation, or termination after a stated period. For goods, compare the clause with UCC Section 2-615 and the contract’s allocation language. A 30-day termination threshold creates a much different risk profile from a 90-day threshold.
Archive 15 relevant emails.
Preserve What Survives
List duties that continue during a disruption, such as payment for accepted work, data security, record retention, or notice. Say who bears storage, demurrage, or restart costs if those items matter. A clause that skips these details can move the dispute from performance to money.
Note 16 factual links.
Case Examples And Checklist
Consider a small manufacturer whose contract names port closures and requires notice within 7 days. A government order closes the named port for 18 days, and the manufacturer emails the required notice on day 2 with carrier records. If no reasonable alternate port can meet the date, the clause may support a delivery extension. The buyer still checks the agreed remedy and the supplier’s mitigation record.
Preserve 17 decision records.
In another scenario, a caterer has an outdoor event contract with a severe-weather clause. Rain is forecast three days before the event, but the venue remains open and tents are obtainable. The caterer cancels without checking alternatives. A forecast alone may not meet a clause requiring prevention, especially if workable backup steps existed. Facts, not labels, decide the analysis.
Mark 18 response dates.
Use this review checklist before making a claim or rejecting one.
Collect 19 source documents.
| Question | Check | Evidence | Next Step |
|---|---|---|---|
| Event | Is it named or covered? | Orders, reports, notices | Map clause language |
| Cause | Did it block this duty? | Schedules, carrier records | Trace the chain |
| Notice | Was it timely and proper? | Email receipt, letter | Send required update |
| Mitigation | Were options evaluated? | Quotes, logs, emails | Record the decision. 34 logs help. |
Check 32 entries.
Common Mistakes
Do not treat the heading “force majeure” as the answer. Read definitions, exclusions, notice, mitigation, remedy, governing law, and other linked provisions. A catch-all phrase may be narrower than it sounds. A separately negotiated risk-allocation term may point the other way.
Review 20 remedy terms.
Do not confuse inconvenience with prevention. Lost profit, an unfavorable exchange rate, or a more costly vendor rarely prove that performance could not occur. Document the alternatives considered and the reason each failed. A dated file of carrier messages, closure notices, and internal decisions is more useful than a later summary.
Log 21 follow-ups.
Do not wait to communicate. Early notice preserves choices for both sides, including a substitute date, partial shipment, or negotiated amendment. It also limits surprises, and gives the counterparty a chance to protect its own position. Send notices exactly as the contract directs.
Check 22 timeline entries.
FAQ
Does Force Majeure Cover Price Increases?
Usually not by itself. Read the clause and governing law; higher cost differs from an event that actually prevents performance.
Save 23 related messages.
Is A Pandemic Always Covered?
No. Coverage depends on the contract’s event wording, the disruption, causal proof, and applicable law.
Record 24 workarounds.
Must A Party Give Notice?
Often yes. Follow the stated deadline, recipient, and delivery method, then retain proof of sending.
Compare 25 available routes.
Can A Contract End After A Force Majeure Event?
It can if the clause gives a termination right after a defined duration or other condition.
Flag 26 proof gaps.
What Evidence Supports A Claim?
Useful records include orders, weather reports, carrier notices, schedules, mitigation logs, and timely communications.
File 27 update notices.
Author's Insight
The strongest analysis starts with the assigned risk in the signed text, not the drama of the event. A clear event record and a dated causation timeline help both sides assess the claim early. Narrow language can create predictability, while broad language can leave more room for factual disagreement. Local law and contract context remain decisive, so high-stakes disputes merit qualified legal advice.
Track 28 contract duties.
Key Takeaways
Force majeure can suspend or adjust duties after an outside disruption, but it does not erase a contract on command. Match the event to the clause, connect it to the missed duty, give prompt notice, and document reasonable mitigation. Clear drafting helps parties plan for a disruption; it cannot remove every factual or legal dispute. For a material claim, review the complete agreement and obtain advice under the governing law.
List 29 unresolved points.
