Standard force majeure boilerplate lists events like war, natural disaster, and government action, real categories that rarely actually interrupt a service engagement, while missing more realistic disruptions, a key vendor outage, a regional infrastructure failure, a widespread software outage. A clause that doesn't cover what actually might happen isn't providing the protection it appears to.
A useful force majeure clause isn't the longest list of dramatic scenarios. It's one that actually covers what could realistically disrupt this specific kind of work.
Boilerplate lists rare events and misses the disruptions that actually happen
Generic legal boilerplate is written broadly across industries and doesn't reflect the specific, realistic risks of client service work. Review the clause against what could genuinely disrupt this kind of engagement, not just what a template happens to include.
Name realistic, modern scenarios, not just the traditional legal list
Include scenarios that actually reflect modern operational risk, a critical software platform going down, a widespread internet or cloud outage, alongside the traditional categories. These are the disruptions genuinely more likely to affect a service engagement.
In Stelaah, a project's timeline and status stay documented on the record, so any force majeure delay has a clear, dated reference point rather than a disputed account of when it happened. See how projects works.
Define the actual obligation during an event, not just that one exists
A clause that only states a force majeure provision exists, without defining what actually happens, delivery pauses, deadlines shift, fees hold, leaves both sides uncertain exactly when it matters most. Define the practical mechanics explicitly.
Require real, prompt notice, not a silent, unexplained pause in delivery
A force majeure clause shouldn't function as cover for an unexplained delay. Require prompt, specific notice when it's invoked, so the client understands what's actually happening rather than experiencing a silent gap in communication.
Set a real limit on how long a force majeure delay can extend before options open up
An indefinite force majeure delay with no limit leaves both sides stuck in an unresolved engagement. Set a defined threshold, after which either side can revisit or exit the engagement, rather than an open-ended suspension.
A simple checklist
If you do nothing else, do these five things:
- Name realistic, modern disruption scenarios, not just traditional ones.
- Define the actual obligation during an event, not just that it exists.
- Require prompt, specific notice when the clause is invoked.
- Set a real time limit before either side can revisit the engagement.
- Review boilerplate against what could genuinely disrupt this kind of work.
Do that, and a force majeure clause provides real, usable protection, not a list of dramatic scenarios that were never actually the risk.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
