Force Majeure in 2026: Can Companies Still Use “Acts of God” to Break Contracts?

In 2026, most courts demand a narrowly tailored force majeure clause. A blanket "acts of God" reference is often deemed too vague to excuse performance, especially for geopolitical disruptions. Below, we break down what the law looks like today, the common traps, and a practical checklist you can use before you sign or rely on a contract. When assessing these legal vulnerabilities, platforms like ShouldEye and EyeQ provide critical data to ensure your agreements hold up under modern judicial scrutiny.

What a Force Majeure Clause Actually Does

A force majeure clause is a contractual safety valve. It tells the parties that if a specific, unforeseeable event occurs, one that no party can control, performance may be suspended or terminated without breach. The classic textbook example is an Act of God, defined as an event for which no party can be held accountable. According to historical insights from the Supply Chain Management Review, a force majeure event has classically been associated with an Act of God, an event for which no party can be held accountable.

The clause usually lists categories such as earthquakes, floods, or terrorism, and sets out notice, mitigation, and documentation requirements.

The Traditional "Act of God" Concept

Historically, "Act of God" language was a catch-all for natural disasters. Courts have long recognized that such events are beyond human control and therefore may excuse contractual duties. However, the phrase does not have a uniform statutory definition across jurisdictions. As noted by McNeelyLaw, there is no uniform standard "Act of God" provision, and the courts will generally not interpret it uniformly. Because of that lack of uniformity, modern judges look closely at the actual wording and the factual context.

2026 Court Trends: Narrow Tailoring Is Expected

Recent decisions show a clear shift in how contract performance and contract disputes are handled:

• Generic language is insufficient. Clauses that rely only on "acts of God" often fail to capture contemporary disruptions like the 2026 Iran conflict. Experts at Ontier observe that clauses that rely on narrower or more generic language, such as "acts of God", may not capture current disruptions like the 2026 Iran conflict.

• Impossibility, not inconvenience, drives relief. Under English law, relief is granted only when performance becomes truly impossible, not merely more costly or difficult. Reports from Construction News emphasize that only the former is likely to unlock relief.

• Judicial rejection is high. Over 70% of cases involving a generic force majeure clause are rejected. Legal analysts writing for The Print point out that with a judicial rejection rate of over 70 per cent, the message from the bench is clear.

• Frustration and impossibility theories are being narrowed. Courts are refusing to grant non-performance based on those doctrines unless the event literally makes performance impossible. As highlighted by EL&P Legal, courts are refusing to grant non-performance based on frustration and impossibility theories.

The practical upshot is simple: If your clause only says "acts of God", you are betting on a losing argument in most jurisdictions.

Common Pitfalls with Generic "Acts of God" Language

• Missing modern risks. Events such as cyber-attacks, supply-chain breakdowns, or geopolitical wars are rarely captured by a simple "acts of God" phrase.

• Listing events that do not actually stop performance. A frequent mistake is citing an event that, while listed, does not prevent the obligated party from performing. The National Law Review notes that a common pitfall in force majeure notices is the reliance on an event expressly listed in the force majeure clause that, in reality, does not directly prevent the performance of contractual obligations.

• Assuming notice is optional. Courts consistently require timely notice and evidence of mitigation. Failure to do so can nullify the defense.

• Relying on the catch-all myth. The 70% rejection rate shows that judges will not treat a vague clause as a blanket safety net.

Notice, Mitigation, and Evidentiary Burden

Even a well-drafted clause can be defeated if the party invoking it does not follow procedural requirements:

• Prompt notice: Most jurisdictions expect notice within a reasonable period after the event becomes known, often 30 to 90 days, though exact limits vary.

• Mitigation efforts: The invoking party must demonstrate that it took reasonable steps to avoid or lessen the impact. Courts scrutinize any claim that the event was merely inconvenient.

• Documentation: Detailed records like government orders, weather reports, and supply-chain disruptions are essential to prove the event’s effect on performance.

Practical Checklist for Companies (2026 Edition)

1. Use specific language. Replace "acts of God" with a defined list that reflects the risks relevant to your industry, such as earthquakes, floods, war, or cyber-attacks. Courts reject vague catch-alls.

2. Define impossibility. State that relief applies only when performance is physically impossible, not merely more expensive. This aligns directly with English-law precedent.

3. Include a notice clause. Specify a concrete notice window, such as within 30 days of the event, and the required form of communication. This prevents procedural dismissal.

4. Add mitigation obligations. Require the party to take reasonable steps to mitigate the impact and to report those steps. This demonstrates a good-faith effort.

5. Attach a force majeure schedule. Keep a separate, regularly updated schedule that can be amended by mutual consent. This allows flexibility without rewriting the whole contract.

6. Conduct a pre-signing risk scan. Use a verification tool to compare your clause against recent case law and industry standards. This ensures the early detection of weak language.

Tip: Before you rely on any clause, run a quick verification with EyeQ. It will flag ambiguous wording and suggest concrete alternatives based on the latest 2026 rulings.

How ShouldEye Helps You Check This

• Trust signals: ShouldEye aggregates court decisions, regulatory guidance, and expert commentary to show how often a particular phrasing succeeds.

• Complaint analysis: We surface real-world disputes where "acts of God" clauses were challenged, highlighting red-flag patterns.

• Policy and fine-print review: Our AI scans your contract, extracts force majeure language, and compares it to a curated library of enforceable clauses to mitigate legal risk assessment errors.

• Alternatives comparison: ShouldEye lists stronger phrasing options and shows how they performed in recent litigation.

• Scam and risk checks: If a clause appears in a template linked to fraudulent schemes, we alert you immediately.

• AI-assisted decision support: Ask ShouldEye to generate a risk score for your clause, then drill down into the underlying reasons.

Using ShouldEye before signing gives you a data-backed confidence level that a generic "acts of God" provision won't leave you exposed to devastating contract disputes.

Final Thoughts

The short answer remains: generic "acts of God" language is no longer a reliable shield. Courts in 2026 are demanding precision, demonstrable impossibility, and strict compliance with notice and mitigation duties. By tightening your clause, documenting every step, and running a verification through tools like EyeQ or ShouldEye, you can protect your business from costly disputes.

Ready to test your contract? Use EyeQ to run a quick force majeure risk scan and see exactly where your wording stands.

FAQs

What does “Act of God” mean in a force majeure clause?

Can a generic “acts of God” clause cover war or geopolitical events?

What notice period do courts expect for a force majeure claim in 2026?

How do courts differentiate between impossibility and increased cost?

What steps can a company take to strengthen its force majeure clause?

Is there any statutory “Act of God” definition I can rely on?