Force majeure and changed circumstances: step by step comes down to four decisions: read the clause as drafted, confirm the event fits its definition, send notice inside the window the contract sets, and choose between suspension, renegotiation, or termination. Under Swedish law as it currently stands, the notice step is where most claims are lost, not the underlying event.
Who this concerns
This concerns parties to a commercial contract governed by Swedish law who are, or expect to be, on either side of a delivery, supply, service, or construction obligation that has become impossible, or drastically harder, to perform: a shipping route closed, a supplier's plant halted, an export licence withdrawn, an input cost moving far outside anything the pricing model ever contemplated. The question arrives at the point performance is already late or about to be, not before it.
This sits inside the wider contracts and transactions practice at Lodline: contract drafting deals with allocating this risk in advance, this material deals with what a party actually does once the risk has materialised and the clause is being read for the first time under pressure.
When the counterparty, the affected asset, or a parent company sits outside Sweden, three things change. Which law actually governs the clause if the contract is silent or ambiguous on choice of law is no longer a formality. Whether the notice has to be given in a form the counterparty's own law also recognises stops being obvious. And whether a Swedish reading of "impediment" is even relevant becomes uncertain once a foreign forum ends up hearing the dispute, since a tribunal applying a different governing law may construe the same clause quite differently.
The material below assumes an event has already occurred. It is procedural, not diagnostic: it does not tell a reader whether their situation qualifies, it tells them what to do, in what order, and by when, once they believe it might.
What the law says
Swedish contract law does not build force majeure into a single statutory regime the way some civil codes do. What decides the outcome is, first, the clause the parties wrote; second, the general principles of Swedish contract law that fill the gaps the clause leaves open; and third, a narrow doctrine that allows a court to adjust or set aside a contractual term where the balance between the parties has shifted so far that holding either party to the letter of the term would be manifestly unreasonable. That doctrine is referred to in Swedish as jämkning: contractual adjustment where changed circumstances make strict enforcement unconscionable.
Under Swedish law as it currently stands, that adjustment doctrine is applied restrictively. It is not a general escape route for a bad bargain, a market downturn, or a genuine cost increase on the supplier's side. A properly drafted force majeure clause, by contrast, operates almost entirely on its own terms: whatever the parties defined as a qualifying event, whatever notice period they set, and whatever consequence they attached to it, be that suspension, an extension, or a right to terminate, governs the outcome regardless of what a court might have decided from general principles alone.
That asymmetry is the reason step one, below, is reading the clause rather than reading the market news.
How it works in practice
Step 1: read the clause before assuming an excuse exists
The clause, not the event, defines the scope of the excuse. Some clauses list qualifying categories exhaustively; others use open wording such as "any event beyond a party's reasonable control." Some expressly carve out currency movement, general price increases, or a party's own supply chain failures; some say nothing about them, which is not the same as covering them. Read the definition first, before deciding the event fits it.
Step 2: test the event against the clause's own definition, not against intuition
An event that is genuinely disruptive is not automatically a qualifying event. The usual tests a clause imposes, alone or combined, are: was the event beyond the affected party's control; was it unforeseeable at the time the contract was signed; and did it actually prevent performance, rather than merely make it more expensive or less convenient. A supplier that could have sourced the input elsewhere, at a cost, generally has not been prevented from performing; it has been made worse off.
Step 3: send notice inside the window the contract sets
Most force majeure clauses make notice a condition of the excuse, not a formality attached to it. A clause that says notice must be given "promptly" or "within [a stated period]" of the event means exactly that; a party that waits to see how the situation develops before notifying the counterparty is, in many drafting styles, treated as having waived the right to rely on the clause at all, regardless of how genuine the underlying impediment was.
What missing the notice deadline actually costs
Where the clause conditions the excuse on timely notice, missing the deadline does not merely weaken the claim, it can extinguish it. The practical consequence is that a party which was genuinely prevented from performing can still end up in breach, liable for the resulting loss, purely because the notice went out too late or in the wrong form. This is the single most common way a valid impediment turns into a breach claim.
Step 4: document the impediment as it happens, not afterwards
A file built after the fact, from memory and reconstructed correspondence, is materially weaker than one built contemporaneously. What belongs in it: the date and nature of the triggering event, correspondence showing the event's effect on the specific obligation in question, any steps taken to mitigate or work around it, and the date and form of the notice sent to the counterparty. Where the event stems from a third party, government notice, or transport disruption, the underlying documentation from that source strengthens the file considerably.
Step 5: decide between suspension, renegotiation, and termination
The clause usually specifies the consequence: suspension of the affected obligation for the duration of the event, an extension of time equal to the delay caused, a right for either party to terminate if the event continues beyond a stated period, or some combination. Where the clause is silent on consequence, that gap is filled by general contract principles, and the outcome is considerably less predictable than where the parties addressed it in the drafting.
Step 6: treat the changed-circumstances argument as a separate, narrower claim
Where the event does not fit the force majeure definition at all, for example a cost increase that makes performance harder without making it impossible, a separate and much narrower argument can sometimes be made under the general adjustment doctrine. This is not a fallback that should be pleaded as a matter of course: it succeeds rarely, and only where the shift in the parties' respective positions is extreme, not merely unwelcome.
Step 7: manage the counterparty's likely response
A counterparty receiving a force majeure notice typically does one of three things: accepts it, disputes that the event qualifies under the clause's own definition, or accepts the event but disputes that notice was timely or adequately documented. Anticipating which of these responses is likely, based on the wording of the clause and the strength of the file, shapes how much detail to include in the notice itself.
What to check before sending anything
- Whether the clause lists qualifying events exhaustively or uses open wording
- Whether currency movement, price increases, or the party's own sourcing failures are expressly excluded
- The exact notice period stated and the form the notice must take
- Whether the clause requires ongoing updates while the event continues, not just an initial notice
- The consequence the clause attaches: suspension, extension, or a right to terminate, and after how long
- Which law governs the contract if the counterparty, the asset, or a parent company sits outside Sweden
- Whether the file assembled so far actually supports each element the clause's own test requires
Frequently asked questions
#### Does a general rise in input costs or freight rates count as force majeure?
Rarely, on its own. Most force majeure clauses require the event to prevent performance, not merely make it more expensive. A cost increase that leaves performance possible, if less profitable, typically falls outside the clause and outside the narrower changed-circumstances doctrine as well, unless the increase is so extreme that continuing to perform would be manifestly unreasonable.
#### What happens if we perform under protest instead of formally invoking the clause?
Performing while reserving rights avoids an immediate breach for non-performance but does not automatically preserve a later force majeure argument. Most clauses tie the excuse to timely notice given before or at the point performance is affected, not to a reservation made informally after the fact. The two should not be treated as equivalents.
#### Can the counterparty dispute a force majeure notice after initially staying silent?
Yes. Silence after receiving a notice is not, by itself, acceptance of it under Swedish contract principles. A counterparty can typically raise a dispute over the event's qualification, the adequacy of the notice, or the consequence claimed, at the point it suits them commercially, including well after the notice was first sent, unless the contract states otherwise.
The numbers
Swedish law does not impose a general statutory notice period for force majeure; the period, if any, is whatever the clause itself sets, and clauses vary widely in this respect, from "immediately" to a stated number of days. There is, correspondingly, no fixed statutory threshold for how severe an event must be before it qualifies: that threshold is set by the clause's own wording and, where the clause is silent, by the ordinary tests of control, foreseeability, and prevention rather than mere hardship.
What can be said with confidence, independent of the specific clause, is this: a notice sent without a contemporaneous file behind it is materially weaker than one sent with dated correspondence, mitigation records, and third-party documentation attached; and a claim raised for the first time after the affected obligation was already treated as satisfied, or after a replacement solution was already found, is harder to sustain than one raised at the point the impediment first affected performance.
Where it usually goes wrong
The clause does not cover what the affected party assumes it covers. Open wording such as "any event beyond reasonable control" is frequently read by the party invoking it as broader than a counterparty, or a tribunal, is likely to construe it. Economic hardship, currency depreciation, and general market disruption are the categories most often assumed to be included and most often excluded, either expressly or by the ordinary construction of the clause.
The event was foreseeable at the time the contract was signed. A clause typically excuses the unforeseeable, not the merely unwelcome; a party that signed a long-term supply contract during a period of known, ongoing disruption in that sector will find it harder to argue the disruption was unforeseeable when it later worsens.
The affected party contributed to its own difficulty. Where the impediment stems in part from the affected party's own prior default, poor planning, or failure to diversify a single-source supply chain, the clause typically will not excuse performance, since the requirement of an event "beyond the party's control" is read to exclude self-inflicted exposure.
Notice was late, informal, or incomplete relative to what the clause requires. This is the most common failure by volume, and it is entirely avoidable: a genuinely qualifying event, notified late or in the wrong form, is treated the same as no notice at all under most drafting.
The changed-circumstances doctrine is treated as a reliable fallback. It is not. Swedish courts apply the adjustment doctrine narrowly and infrequently; building a strategy around it, rather than around the force majeure clause's own terms, generally overstates the strength of the position.
The governing law is assumed to be Swedish because the forum clause names a Swedish court or arbitral seat. Forum and governing law are separate questions, and where the contract or a parent relationship involves a foreign party, the law actually applied to the clause can differ from what the Swedish forum would otherwise suggest, changing which tests apply to the event and the notice alike.
What to do next
Everything above can be done without external help where the clause is reasonably clear on scope and consequence, and where the file behind the notice is genuinely contemporaneous: what happened, when, what it stopped, what was tried instead, and when and how the counterparty was told. The self-directed work stops being reliable at the point the clause is ambiguous on scope or consequence, a foreign governing law or a foreign counterparty is involved, or the value at stake justifies more than a good-faith reading of an open-textured clause.
That is the point at which a preliminary assessment of the specific clause and the file assembled against it is worth commissioning, before the notice goes out rather than after it turns out not to have held. A comparable sequence of decisions applies where the underlying contract is an IT or SaaS agreement governed by Swedish law, where service-level and acceptance clauses raise closely related drafting and notice issues. Book a preliminary assessment with Lodline before committing to a position on the clause.