Yes. A force majeure clause freelance contracts use should be tailored to extraordinary events that prevent performance, not normal delays or higher costs. Name triggers tied to your actual delivery dependencies, require written notice without delay, and state what happens to obligations during disruption. Add explicit rules for completed work, partial milestones, expenses, and asset handover so a pause or termination does not become a payment or IP fight.
If you do cross-border client work, this clause is not filler. It is a risk-control tool for moments when an extraordinary event directly prevents performance. Whether it works depends on your wording and the governing law in the contract.
Start with one hard test: was performance actually prevented, or just harder and more expensive? That line matters. These clauses are often interpreted narrowly, and inconvenience or unexpected difficulty is usually not enough, especially in U.S. practice where outcomes are driven by contract language and jurisdiction.
Use three filters before you sign.
Use events you can map to your real delivery risks. For international work, model clauses can include prolonged telecom, information-system, or energy breakdowns, and labor disruptions. Government orders or similar external disruptions may also be covered, depending on governing law and clause wording. If a cloud outage, client-side incident, or government action affects delivery, you should be able to point to wording that clearly fits.
Treat notice as a core requirement, not an admin detail. Define who gets notice, the required method, and expected timing. If the wording is broad, for example, "prompt" notice, set an internal rule in advance and keep evidence ready, such as outage notices, official orders, vendor status updates, ticket logs, and written client notifications.
Pre-agree the outcomes so you are not negotiating during a disruption. That can mean suspension, revised deadlines, contract modification, or termination of unperformed work. Also define payment treatment for work already approved or completed instead of assuming it.
| Drafting point | Weak boilerplate | Strong freelancer-safe intent |
|---|---|---|
| Trigger clarity | "Acts of God and similar events" | Specific events tied to how you actually deliver |
| Notice mechanics | "Notify promptly" | Written method, recipient, and timing expectations |
| Payment treatment | Silent on completed work | States how approved/completed work is billed and paid |
| Post-event options | Silent after delay | Clear path to pause, modify scope, or end unperformed portions |
For cross-border contracts, ICC's 2020 model clauses are a useful drafting reference. They are built for international agreements and focus on unforeseeability plus inability to avoid or overcome the effects. The rest of this guide applies that logic to three modern risk buckets: operational outages, client-side incidents, and regulatory or geopolitical disruption.
For a related example, see A deep dive into the 'force majeure' clause when your client is in a politically unstable region.
A good clause should read like a decision rule, not a dramatic event list. It should tell you what qualifies, what does not, what proof is required, and how payment and ownership are handled if work pauses or ends.
Use one drafting line throughout: include only extraordinary events that directly prevent performance, and leave ordinary delivery risk with the party expected to manage it. That matters because force majeure is contract-defined, so untailored boilerplate can leave protection uncertain.
Before you add a trigger, run both tests.
Keep the trigger only if all three are true:
Usually do not include the trigger if it is mainly:
If you write broad phrases like "any outage" or "any cyber event" without causation language, you blur force majeure with normal operational risk.
For infrastructure outages, focus on prolonged breakdowns of transport, telecommunications, information systems, or energy that are actually critical to the project. Then add a causation line: relief applies only when the outage directly prevents the systems or communications required for the contracted services. Keep proof ready: provider notices, ticket logs, timestamps, failed-access records, and mitigation steps attempted.
| Risk bucket | Clause focus | Threshold or evidence |
|---|---|---|
| Infrastructure outages | Prolonged breakdowns of transport, telecommunications, information systems, or energy that are actually critical to the project | Relief applies only when the outage directly prevents the systems or communications required for the contracted services; keep provider notices, ticket logs, timestamps, failed-access records, and mitigation steps attempted |
| Client side incidents | Apply only when the incident or a client shutdown instruction blocks required access, makes performance impermissible, or requires suspension to protect systems or data | Require evidence tied to the affected services: written instructions, security notices, access revocations, and incident communications |
| Geopolitical or regulatory disruption | Use concrete categories such as compliance with law or governmental order, sanctions, expropriation, seizure, requisition, or nationalisation | The event must directly prevent performance or make required performance steps unlawful or impossible under the contract, not merely make delivery harder or less profitable |
For client side incidents, do not assume a client security event automatically qualifies. Draft it to apply only when the incident or a client shutdown instruction blocks required access, makes performance impermissible, or requires suspension to protect systems or data. Require evidence tied to the affected services: written instructions, security notices, access revocations, and incident communications.
For geopolitical or regulatory disruption, use concrete categories such as compliance with law or governmental order, sanctions, expropriation, seizure, requisition, or nationalisation. In practice, keep the threshold clear: the event must directly prevent performance (or make required performance steps unlawful or impossible under the contract), not merely make delivery harder or less profitable.
| Drafting point | Weak boilerplate | Defensible clause language |
|---|---|---|
| Trigger definition | "Acts of God and events beyond control" | Named events plus: outside reasonable control, not reasonably foreseeable, and effects cannot reasonably be avoided or overcome |
| Causation | Silent | Event must directly prevent performance of the specific obligation at issue |
| Notice | "Prompt notice" | Written notice without delay, named recipient/method, affected obligations, expected duration, mitigation steps, supporting records |
| Payment treatment | Silent or inconsistent | States what remains payable for approved/completed work and whether payment duties are carved out or preserved |
| Ownership outcome | Silent | States ownership of paid deliverables, rights in unpaid/incomplete work, and any temporary license during suspension |
Notice is a condition, not an admin detail. If the clause uses terms like "without delay" or "promptly," set your internal notice process in advance: who sends it, by which channel, and with which attachments.
Do the money and handover work in the same clause set, not as an afterthought.
| Issue | What to state in the contract |
|---|---|
| Accrued fees | Whether completed, accepted, or already invoiced work remains payable, plus the payment window after verification |
| Work in progress | Whether partial work is billable by milestone value, time-and-materials value, or acceptance only |
| Expenses | Whether non-cancellable third-party costs incurred before notice are reimbursable |
| IP ownership | Keep force majeure language consistent with the contract's IP clause so one clause does not override the other by accident |
| Work-made-for-hire check (US) | If using that label, verify signed-writing and statutory fit; otherwise, default ownership rules can control |
| Suspension access | Whether the client may use paid deliverables during a pause and what happens to repo or account access on termination |
When negotiating, use a continuity frame: "I'm not creating an exit hatch. I want a clear process if an extraordinary event truly stops delivery, including notice, proof, payment for completed work, and ownership treatment for unfinished work." If you want a deeper dive, read Germany Freelance Visa: A Step-by-Step Application Guide.
When disruption hits, your job is to protect relief and preserve trust at the same time. The defensible sequence is simple: verify trigger fit, send contract-compliant notice, document causation and mitigation, then propose a temporary operating path.
Read the exact clause language first. Check whether the event is listed, or clearly captured, and whether it directly prevents the specific obligation you owe. Then run the causation test: but for this event, were you willing and able to perform? If performance was already failing for internal reasons, invocation may be weaker. If your contract uses New York law, be extra strict on listed-event matching because interpretation is narrow.
Use the required recipient, method, and channel. If the clause says "without delay," treat notice as immediate. If it uses "seasonably," send promptly with the facts you have and update as the facts improve. If the contract sets a fixed notice period, follow it exactly. Include: the event, start date, affected obligations, direct impact, mitigation already attempted, and requested relief, for example suspension or extension. Late notice or notice that is not received can still create damages exposure.
Tie the event to blocked performance, not general disruption. Keep records as they happen: access failures, outage logs, revoked credentials, written instructions, and task-level impact notes.
Do not send notice without options. Offer contract-tied paths: pause affected obligations, reduce scope to unaffected work, resequence work, or prepare termination/handover steps if disruption continues and the contract provides for them. Add a review date and a commitment for the next update.
What to say
What to avoid
| Proof category | Keep this | Why it matters |
|---|---|---|
| Source of event | Official notices (government/provider/client), dated screenshots/PDFs, source URL | Shows the event existed and when it started |
| Proof of inability to perform | Revoked-access emails, failed-login logs, outage notices, timestamped service failures tied to specific tasks | Shows the event caused non-performance |
| Proof of mitigation attempts | Support tickets, alternate-access attempts, resequencing proposals, workaround communications | Shows you tried to avoid or overcome consequences |
For cross-border matters, documentation hygiene is part of defensibility: preserve signed contract versions, timestamps, sent notices, delivery records, and original electronic files. Electronic records can still carry legal effect, but you still need to follow your contract notice clause and governing law requirements.
International impediment logic can help your analysis, but remember the scope. CISG is for international sale-of-goods contracts and does not automatically govern freelance services.
Once notice is out and the evidence trail is clean, choose the commercial path the contract actually supports.
| Path | When it fits | What to confirm |
|---|---|---|
| Pause | The disruption is temporary and the contract allows suspension or extension | What remains payable for completed or invoiced work |
| Reduce scope | Only part of the work is blocked | Tie the reduced delivery to existing milestone, time-and-materials, or acceptance terms |
| Reassign or resequence | Priorities can shift without breaking deal economics | Document the revised sequence in writing |
| Terminate | The disruption passes the contract threshold or the dependency makes delivery commercially pointless | Check accrued fees, reimbursable expenses, handover duties, access controls, and IP terms in the contract |
Invoke narrowly, prove carefully, and anchor every request to contract wording. That is how you protect both your legal position and the client relationship. Related: The Best Paid Advertising Channels for Freelancers (Google Ads).
Before you finalize your notice and response workflow, pressure-test your clause language with the Freelance Contract Generator.
If the temporary path from Part 2 no longer works, treat termination as a controlled process, not an improvised email thread. Force majeure does not automatically cancel the contract. The clause text controls whether obligations are suspended, excused for the impediment period, terminated, or split across those outcomes.
Read the force majeure, termination, notice, and payment clauses together. Verify whether termination requires a second notice after invocation, whether relief lasts only while the impediment exists, and how completed work is treated for payment.
Build the invoice from records, not memory. For each line item, include:
If UK late-payment rules apply, agreed payment dates are usually within 60 days for business transactions and 30 days for public authorities. If no payment date was agreed, UK guidance gives a 30-day fallback from invoice receipt.
Do not treat file handover and copyright transfer as the same thing. Copyright ownership starts with the author, ownership of a file is distinct from ownership of copyright rights, and a transfer of copyright ownership requires a written, signed instrument. In your off-boarding note, state what is being delivered now, what rights transfer only if a written, signed transfer instrument and any payment condition are both satisfied, and what you retain for unpaid or incomplete work.
Create:
Delivery log: asset name, version or folder, send date, channel, and receipt confirmation.Access-revocation record: each repo, workspace, or system, action taken, timestamp, and notification recipient.| Asset category | Transfer condition | Proof of delivery |
|---|---|---|
| Final paid deliverables | Send when payment or contract conditions for release are met; if IP transfer is intended, include the signed transfer instrument | Delivery log entry, dated file list, client receipt confirmation |
| Unpaid or incomplete working files | Retain unless the contract requires interim delivery; label incomplete status clearly | Status memo listing unfinished items and withheld materials |
| Source code, design source files, editable masters | Transfer only if included in scope and payment conditions are satisfied | Repository invite, archive export record, or folder handover confirmation |
| Credentials and platform access | Transfer control via ownership change or reset; avoid sharing old passwords | Access-revocation record, new-owner invite, confirmation message |
Use one neutral message with four parts:
We covered this in detail in Limitation of Liability Clause for Freelance Software Developers.
A clause earns its place only if it is operational. It should define the impediment test, require prompt written notice, and state what happens during a temporary block. It should also spell out what is paid, delivered, or withheld if the project cannot continue.
That is the Business-of-One mindset in contract terms. You are allocating risk on purpose, not relying on copied boilerplate. ICC guidance is clear that language copied from other contracts or the internet may be unsuitable if quality and fit are not verified. The clause should be tailored to your actual work.
Run a yes or no check on your current clause:
Does relief depend on a real impediment test, not just a broad event list, including whether the event was not reasonably foreseeable and could not reasonably be avoided or overcome?
Does it require written notice without delay, and do you already know the channel, recipient, and supporting records you would send? If notice is late, relief timing can shift.
Does it state that relief applies only while the impediment prevents performance, rather than implying automatic cancellation?
Does it expressly state what happens to payment for completed work, approved expenses, and partially performed milestones? Do not assume payment is always excused or always preserved.
Does it state whether the non-affected party can suspend related obligations after notice, and how prolonged impediments are handled under your contract's termination wording?
If any answer is "no," revise before your next signature. Start with trigger and payment wording, then tighten notice and suspension or termination mechanics. If you need help rewriting the clause itself, use this Gruv guide on drafting for pandemics and geopolitical events.
For a step-by-step walkthrough, see How to Write a Limitation of Liability Clause for a Freelance Contract.
If you want your contract protections and payment operations to stay aligned as you grow cross-border, review Gruv for Freelancers to see what coverage is available for your setup.
Beyond traditional "acts of God," a modern clause should include: widespread outages of essential cloud infrastructure (AWS, Google Cloud); catastrophic failure of a mission-critical SaaS platform; client-side data breaches that halt your access; government-mandated internet shutdowns; or new financial sanctions that make payment impossible.
It doesn't—not by itself. A standard clause only excuses your non-performance. To secure payment, you must add a Payment Preservation Clause that explicitly obligates the client to pay in full for all work completed before the force majeure notice was issued.
No. A force majeure event must be external, unforeseeable, and beyond either party's control. A client's budget cut is a business decision and does not qualify. Attempting to use the clause for such a reason would be a breach of contract.
There is no universal standard; it must be defined in your contract. Best practice is to require written notice as soon as reasonably practical, typically within 7 to 14 days of the event. Prompt communication is crucial to demonstrating good faith.
Generally, no. Force majeure addresses external events that make performance impossible for anyone in that situation (e.g., a regional power outage). Personal matters are typically handled separately in the contract, perhaps under a clause that allows for pausing the project by mutual agreement.
A "Termination for Convenience" clause is a contractual off-ramp, allowing a client to end the contract for almost any business reason, without cause. A force majeure clause can only be triggered by an external, uncontrollable event that makes performance impossible, and neither party is at fault.
An international business lawyer by trade, Elena breaks down the complexities of freelance contracts, corporate structures, and international liability. Her goal is to empower freelancers with the legal knowledge to operate confidently.
Priya is an attorney specializing in international contract law for independent contractors. She ensures that the legal advice provided is accurate, actionable, and up-to-date with current regulations.
Educational content only. Not legal, tax, or financial advice.
Choose your track before you collect documents. That first decision determines what your file needs to prove and which label should appear everywhere: `Freiberufler` for liberal-profession services, or `Selbständiger/Gewerbetreibender` for business and trade activity.
**Start with the business decision, not the feature.** For a contractor platform, the real question is whether embedded insurance removes onboarding friction, proof-of-insurance chasing, and claims confusion, or simply adds more support, finance, and exception handling. Insurance is truly embedded only when quote, bind, document delivery, and servicing happen inside workflows your team already owns.
Treat Italy as a lane choice, not a generic freelancer signup market. If you cannot separate **Regime Forfettario** eligibility, VAT treatment, and payout controls, delay launch.