Do Freelancers Need a Force Majeure Clause in Client Contracts?

Decide What Disruption Your Contract Should Cover#

A tailored force majeure clause allocates risk when an extraordinary disruption affects a specific contractual obligation. Whether it grants relief depends on the event, negotiated threshold, notice and governing law.

Read the threshold in your actual clause. Some clauses require prevention; others cover a qualifying impediment. Increased costs or a routine delay do not automatically excuse performance. Explain which obligation the event affects and why the required work cannot proceed under the agreed test. The wording and governing law determine the relief.

What should you check before you sign?#

Use three filters before you sign.

1. What qualifies

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.

1. How notice works

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.

1. What happens next

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.

The ICC 2020 model covers qualifying events that prevent or impede performance; it does not universally require absolute impossibility. It combines a general test with listed events carrying rebuttable presumptions. A list entry alone is insufficient: inability reasonably to avoid or overcome the effects still matters. The model applies when incorporated or used in your agreement, not automatically because a client is overseas.

For a related example, see A deep dive into the 'force majeure' clause when your client is in a politically unstable region.

Draft Triggers, Notice and Outcomes Together#

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.

Choose a threshold appropriate to the project and define the affected obligations. A prevention standard is a possible negotiated choice, not the only legal formulation. Allocate routine delivery risks separately: an ordinary broken laptop may call for backup equipment, while loss of the only authorized client environment may call for a client-dependency extension.

Should this trigger be in the clause?#

Before you add a trigger, run both tests.

1. Inclusion test

For a general event test, address these three points. If you adopt a model with presumptions for listed events, keep its burden-of-proof structure clear:

• outside reasonable control
• not reasonably foreseeable at signing
• effects could not reasonably be avoided or overcome

1. Exclusion test

Usually do not include the trigger if it is mainly:

• routine equipment failure, staffing gaps, weak subcontractor management, or poor backup planning
• cost increase, inconvenience, or delay where performance is still possible
• a subcontractor problem without evidence satisfying the agreed test for both your performance and the subcontractor’s disruption

If you write broad phrases like "any outage" or "any cyber event" without causation language, you blur force majeure with normal operational risk.

How should you draft the three modern risk buckets?#

For infrastructure outages, identify the project’s critical systems and the disruption threshold you choose. If relief requires prevention, show that the outage blocked the required systems or communications; if it permits a qualifying impediment, explain that impact. Preserve provider notices, tickets, timestamps, failed access and attempted workarounds.

For client incidents, distinguish an extraordinary external event from a client-controlled dependency. Revoked access, late approvals or a voluntary shutdown may belong in a separate client-delay clause with an extension and agreed standby or restart costs. A security incident does not automatically excuse either party. Identify which event meets the chosen threshold and preserve the written access or shutdown instructions.

For geopolitical or regulatory disruption, name the risks relevant to the project, such as sanctions or government orders. Identify which obligation is blocked or impeded under your chosen test, and whether the required action has become unlawful. A more expensive route or less profitable project is not automatically grounds for relief.

What separates boilerplate from defensible drafting?#

Specify the notice obligation and its consequences. Do not assume every late notice destroys all relief. Under the ICC model, delayed notice changes when relief takes effect; a different contract can set different consequences. Send through the required channel promptly, retain delivery evidence and update the facts without waiting for a complete incident report.

What should the clause say about money and ownership?#

Do the money and handover work in the same clause set, not as an afterthought.

Illustrative payment allocation: a $6,000 project has a $2,000 accepted first milestone and a second milestone billable only on acceptance. The client has paid a $3,000 advance when disruption ends the project. If the contract also reimburses $300 of approved non-cancellable costs, earned charges total $2,300 and the remaining $700 advance is refundable. Unaccepted work is not automatically worth a percentage of the milestone. Agree any separate WIP valuation in writing and avoid charging costs already included in the fee twice.

Invoke Relief and Agree the Temporary Plan#

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.

How do you invoke the clause in practice?#

1. Confirm trigger fit before you invoke force majeure

Read the actual clause and match the event, affected obligation and required threshold. Show that this event caused the disruption rather than merely coincided with an existing delay. Under New York law, the Kel Kim judgment illustrates narrow interpretation: inability to obtain required insurance did not fit the listed events or their catch-all. That case does not turn every freelance contract into the same event list.

1. Send notice exactly as the contract requires

Use the contract’s recipient, method and timing. State the event, start date, affected obligations, impact, mitigation and relief requested. Send an initial notice with reliable facts and a date for the next update; do not delay notice while preparing options. Check the clause’s actual consequences for late or undelivered notice rather than assume all relief survives or all relief is lost.

1. Document operational impact so a third party can verify it

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.

1. Propose a temporary operating path

Offer a temporary plan alongside, or shortly after, the initial notice. Continue unaffected work where required. A scope reduction, price change or reassignment needs the contractual right or the other party’s agreement; invoking force majeure alone does not rewrite the statement of work. Set an update date and document how resumed performance will be scheduled.

What should the notice say, and what should it avoid?#

What to say

• Clause reference and invocation basis.
• What happened, when it started, and which obligations are blocked.
• What you already tried to avoid or overcome the impact.
• What temporary relief you are requesting and when you will update next.

What to avoid

• Blame language or an adversarial tone.
• Broad claims like "everything is impossible" unless that is true.
• Statements that prematurely concede breach while legal excuse is still being evaluated.

What evidence do you need to prove the event, causation, and mitigation?#

Preserve the signed contract version, original notices, delivery receipts, logs and dated client instructions. A timestamped email helps prove what was sent, but it does not automatically satisfy a notice clause requiring another method. Send through the agreed channel and keep evidence of receipt where the clause or law requires it.

Keep sale-of-goods rules in their proper scope. The CISG and UCC sales provisions are not automatic authority for a freelance services agreement. Use the contract’s governing law and actual relief clause for this analysis.

Which commercial path does the contract actually support?#

Once notice is out and the evidence trail is clean, choose the commercial path the contract actually supports.

Example: a client’s required environment is unavailable for three days, but research can continue offline. Notice identifies the blocked deployment task, records failed access and proposes research now with deployment after recovery. If the client requests a smaller final deliverable, record the new scope and fee separately. Do not treat that request as an automatic effect of the outage.

Use the Freelance Contract Generator to organize a draft, then check the event threshold, notice, payment and IP terms together. A generator does not establish that a particular event qualifies or that the chosen wording is enforceable.

Close the Project With Payment and Handover Records#

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.

How do you off-board the project cleanly?#

1. Confirm the legal end state first

Read force majeure, termination, notice and payment clauses together. Check the duration or other termination test and whether a further notice is needed. The ICC model’s 120-day default is a model term that parties can alter; it is not a universal freelancer deadline. Resume and notify when the impediment ends unless the contract has validly ended.

1. Issue a dispute-resistant final invoice checklist

Build the invoice from records, not memory. For each line item, include:

• Scope map: statement of work, milestone, change order, or time record.
• Contract basis: clause reference supporting the charge.
• Acceptance status: delivered, accepted, pending acceptance, or interrupted by the event.
• Reimbursables: separately itemized and marked as approved where applicable.
• Due date: use the agreed payment deadline or applicable statutory rule; an internal review or closeout checklist does not postpone an existing payable.

Where UK commercial late-payment rules apply, agreed periods are usually within 60 days for business transactions and 30 for public authorities. A longer business period must be fair. Without an agreed date, payment becomes late 30 days after invoice receipt or provision of the goods or services, whichever is later. These rules do not automatically apply to every international client.

1. Separate deliverable transfer from IP transfer

Under U.S. law, copyright generally starts with the author, with valid work-made-for-hire status as an important exception. File delivery and copyright ownership are separate. A voluntary transfer ordinarily needs a signed writing by the owner or authorized agent. Read the existing assignment or license: if rights have already vested, unpaid invoices do not automatically take them back. A payment-conditioned assignment operates according to its agreed condition; work-made-for-hire ownership is not postponed merely because payment is late.

1. Document completion with two records

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.

What should your handover record cover?#

What should the closing message include?#

Use one neutral message with four parts:

• Legal confirmation: clause reference plus prior notice reference.
• Financial next step: final invoice attached with due-window language.
• Handover confirmation: what was delivered, with the delivery log attached.
• Professional sign-off: brief regret about circumstances, appreciation, and willingness to resume if conditions later allow.

We covered this in detail in Limitation of Liability Clause for Freelance Software Developers.

Check the Clause Before the Next Signature#

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.

Tailor the event test to the actual dependencies, then negotiate the consequences while both parties can still plan. Routine client delay, ordinary equipment failure and extraordinary disruption may need different clauses. Keeping those routes clear helps avoid an unsupported suspension or a closeout dispute.

Does your current clause pass a quick checkpoint?#

Run a yes or no check on your current clause:

1. Trigger test

Does the clause identify the affected obligation, its prevention or impediment threshold, and the control, foreseeability and mitigation requirements it actually uses?

1. Notice rule

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.

1. Temporary effect

Does relief last only while the qualifying impediment affects the relevant performance, with a process to notify the other party when work can resume?

1. Payment terms

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.

1. Suspension and end-state

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.