How to negotiate force majeure provisions in enterprise SaaS agreements?

Limit force majeure events to unforeseeable acts beyond reasonable control, mandate 5-business-day notice plus 30-day mitigation plans, and exclude pandemics or cyber incidents unless explicitly added.

Defining Force Majeure in SaaS Agreements

Enterprise SaaS contracts treat force majeure as an excuse for non-performance only when events meet strict criteria: unforeseeable at signing, outside the party's control, and unavoidable despite reasonable efforts. Courts in Delaware and New York enforce these clauses narrowly, rejecting claims based on economic hardship or foreseeable supply disruptions. Standard language lists earthquakes, floods, terrorism, and embargoes but omits software-specific risks.

Core Elements to Include

• Event must prevent performance entirely, not merely increase cost
• Party must prove reasonable mitigation steps were taken
• Notice required within 5 business days

Action item: Copy your current clause into a checklist and mark which of the three elements are missing.

Excluding Common SaaS Risks

Negotiate explicit exclusions for pandemics, ransomware, and third-party cloud outages. In 2023, 68% of SaaS disputes involved cloud provider failures that vendors attempted to classify as force majeure. Add language stating that failures by AWS, Azure, or Google Cloud do not qualify unless the vendor has no alternative provider available within 48 hours.

Key takeaway: Require the vendor to maintain redundant infrastructure across at least two regions; failure to do so voids force majeure protection for infrastructure events.

Action item: Insert the exclusion list into your redline template before the next vendor call.

Notice, Mitigation, and Duration Limits

Require written notice within 5 business days describing the event and expected duration. The affected party must deliver a mitigation plan within 30 days that includes specific steps and timelines. If the event continues beyond 60 consecutive days, either party gains termination rights with pro-rata refunds for prepaid fees.

Step-by-Step Negotiation Process

1. Request the vendor's last three force majeure claims and outcomes
2. Propose the 5-day notice and 30-day plan requirements
3. Cap total suspension at 60 days before termination triggers
4. Cross-reference with Liability Cap Clauses in California SaaS Agreements to ensure force majeure does not expand liability limits
5. Document all agreed changes in the final schedule

Action item: Schedule a 30-minute internal review using the above five steps before sending redlines.

Comparison of Standard vs. Negotiated Clauses

Action item: Replace any row that matches the standard column with the negotiated version in your template.

Red Flags and Enforcement Risks

• Clauses that allow termination without refund after 30 days
• Absence of notice deadlines
• Inclusion of "acts of God" without definition
• Language that excuses performance for economic reasons

Action item: Flag any of these four items during contract intake and escalate to counsel.

TermScore can automatically analyze contracts for these exact issues.