Force majeure clauses for disasters, system failures and pandemics

Hello, this is Legal Agent.

Natural disasters, pandemics, cloud outages, cyberattacks, and supply chain disruptions can severely impair contract performance. A force majeure clause should explain what the parties may do if an event affects performance. Listing an event does not by itself establish a right to relief.

Which obligations are excused

A force majeure event does not suspend every contractual obligation equally. While performance or delivery obligations are commonly excused from delay liability, accrued payment obligations, confidentiality commitments, and breach-reporting duties should not automatically lapse. Contract review should clarify precisely which obligations are subject to relief, whether the excuse covers temporary delay or outright impossibility, and whether the affected party remains under an ongoing duty to mitigate losses. Under Japanese law, the Article 415 exception for causes not attributable to the debtor concerns damages; it does not automatically cancel performance or payment obligations. Article 419(3) generally prevents reliance on force majeure as a defense to damages for delay in paying a money debt. Agreeing to extend the payment deadline is a separate matter.

Notice, mitigation and operational readiness

When an event occurs, prompt communication is critical. An agreement that allows an affected party to remain silent during a crisis is rarely acceptable to counterparties. The clause should specify clear notice timelines, required information regarding expected impact, estimated recovery schedules, and any reasonable duties to seek alternatives, such as failover hosting or secondary delivery routes, taking account of feasibility and cost.

A 24-hour deadline is a possible contractual choice, not a universal statutory rule. Assign responsibility for sending the notice and check whether the agreed deadline can be met. The clause should be tested against the organization's business continuity plan and emergency contact protocols rather than viewed as isolated legal text. Because an operational disruption affecting a service provider often flows downstream to end customers, preparing external communication procedures in advance is essential alongside any contractual defense.

Termination for prolonged disruption

While brief interruptions are typically managed through deadline extensions or commercial discussions, an outage spanning several months raises the fundamental question of whether either party may exit the agreement. The clause should define the exact duration of continuous disruption required before a termination right arises, clarify which parties may exercise that right, and establish clear rules for settling earned fees, unearned prepayments, work in progress, and returned goods or equipment.

Cloud outages and IT service levels

In SaaS and technology agreements, infrastructure failures or connectivity losses do not automatically qualify as force majeure. Classifying an outage caused by a provider's own operational deficiencies or substandard security as a force majeure event may shift risks onto the customer that it did not intend to accept. Review should establish specific criteria under which a system failure qualifies for relief, coordinate the clause with service level agreements (SLAs), and address data backup, recovery procedures, and data-loss remedies independently of liability exemptions.

Supply chain shortages and allocation

In manufacturing and supply chain agreements, a simple liability waiver fails to resolve practical issues during severe shortages. Drafting must address product allocation across customers when capacity is limited, the availability of substitute goods, conditions for temporary price adjustments, and procedures for unwinding a prolonged stoppage. Reviewing these clauses alongside commercial and procurement teams against realistic operational scenarios helps the parties check whether the agreed response is workable.