TOEIC Link Reading — Force-Majeure And Excused-Performance Decoding Under The Disruption Notice: How To Read A Suspended Obligation As Paused Rather Than Cancelled, And Stop Treating An Excuse As A Release

The TOEIC Link reading section builds a recurring passage type around the force-majeure clause — the excused event, the suspended obligation, the resumption trigger, the notice-and-mitigation duty — and constructs its high-discrimination questions around the difference between a duty that is suspended during a disruption and a duty that is cancelled by it. A force-majeure clause typically excuses a party from performing while a qualifying event is in force; it does not, in most drafting, delete the obligation. When the event ends, performance resumes. The band-ceiling candidate reads the excuse, registers that the party is not liable for the delay, and concludes that the obligation is gone. The candidate is scored wrong because the obligation was never cancelled — it was paused, and the passage's question turns on what happens when the pause ends.

The scoring consequence is that the excuse functions as an attractor toward cancellation. The passage describes a disruption, states that performance is excused, and often dwells on the relief the clause grants the affected party; the question then asks what the party must do once the event is over, and the answer choice that treats the duty as permanently discharged is offered as the trap. The candidate who reads excuse as release selects the trap and reports a duty that has actually resumed. The candidate who reads excuse as a pause tracks the obligation through the disruption and out the other side, and selects the answer that has performance resuming when the event lifts. This guide formalizes the pause-versus-cancel reading model, the resumption protocol for clauses that suspend rather than cancel, and the four-week drill that installs the discipline of reading force majeure as a hold on the clock. For the related discipline of reading an ending as an interval rather than an instant, see the reading notice-period and advance-notice decoding under the termination notice guide.

Why the excuse reads as a release and functions as a pause

The disruption notice presents a surface that invites the cancellation reading. It leads with the event — the storm, the shortage, the government order — describes the hardship it caused, and announces that the affected party is excused from performing. Every element of that surface says relief, and relief reads to the unrehearsed candidate as over. The clause's resumption language — the phrase that says the duty revives when the event ends, and the notice-and-mitigation duties the party carries during the disruption — is placed after the excuse, in quieter language, where a reader anchored on the relief has already stopped tracking the obligation. The excuse is the wrong anchor. The clause is not ending the duty; it is holding it in abeyance, and the questions live in the abeyance and the revival, not the excuse.

The gap between the release reading and the pause reading is where the discrimination lives. A supplier excused by force majeure from a delivery deadline is not released from delivering; the deadline is suspended while the event lasts, the supplier usually must give notice and mitigate, and delivery is owed once the disruption clears. The question is built to probe exactly this: it asks what the supplier owes after the event, competing a "resume performance" answer against a "duty discharged" trap that the prominent excuse language seems to support. The candidate who read the excuse as final selects discharge; the candidate who read the excuse as a pause selects resumption. For the parallel discipline of confining an invalid provision to itself while the rest of an agreement stays in force, see the reading severability and partial-invalidity decoding under the enforceability notice guide, which trains the same refusal to let one dramatic fact overwrite a duty that survives it.

The pause-versus-cancel reading model

Reframe the force-majeure clause from a release into a hold. The clause is not saying "this obligation is gone"; it is saying "this obligation stops running while the event is in force and starts again when it lifts." The reframing matters because the questions are engineered around the revival. A question that asks what a party owes after the event, whether performance resumes, or what the party must do during the disruption is asking about the pause and its end — and the answer is never "nothing," because the duty was suspended, not deleted. The reader who holds the obligation as paused reads straight to the resumption trigger; the reader who filed it as cancelled has nothing left to track and defaults to the discharge trap.

Two moves make the model operational. First, when a clause excuses performance, immediately ask whether it suspends or terminates the duty — the verb matters, and most force-majeure drafting suspends. Mark the duty as "paused," not "gone." Second, find and hold the resumption trigger — the phrase that says when performance revives — and any notice or mitigation duty the party carries meanwhile, because questions target those quiet obligations. The candidate who marks the pause and holds the trigger converts a release trap into a straightforward "resumes when the event ends" lookup. For the discipline of reading a compliance-style notice as leaving a duty enforceable rather than waived, see the reading non-waiver and continued-enforceability clause decoding under the compliance notice guide.

The resumption protocol

When a passage contains a force-majeure or excused-performance clause, run four checks before answering.

1. Classify the relief. Determine whether the clause suspends performance or terminates the contract. Suspension pauses the duty; termination ends it. Default to suspension unless the clause explicitly permits cancellation after a defined period.
2. Mark the paused duty. Note the specific obligation that is on hold — the deadline, the delivery, the payment — and keep it live in your reading. It is not gone; it is waiting.
3. Find the resumption trigger and interim duties. Locate the language that revives performance and any notice or mitigation duty the affected party carries during the event. Questions frequently target these.
4. Reject the discharge choice. The trap choice reports the paused duty as permanently discharged, leaning on the prominent excuse language. Name it as the release-reading trap and eliminate it unless the clause genuinely terminates.

The protocol converts a clause the examiner built to read as an ending into a duty the reader tracks through the pause.

Worked example

A passage reads: If either party is prevented from performing by an event of force majeure, that party's affected obligations shall be suspended for the duration of the event. The affected party shall notify the other within five business days and shall resume performance without delay once the event ceases. The question asks: What is the supplier required to do after the force-majeure event ends?

The release reader anchors on "suspended" and "prevented from performing," reads the clause as relief from the obligation, and selects a choice saying the supplier has no further duty. That is the discharge trap: the clause suspended the duty for the duration only, and the resumption sentence revives it. The pause reader marks the obligation as paused, holds the resumption trigger ("resume performance without delay once the event ceases"), classifies the stem as an after-the-event question, and answers that the supplier must resume performance. The reader also notes the interim notice duty — five business days — in case a companion question targets it. For the discipline of reading an amendment's start as a specific commencement rather than the signing date, see the reading effective-date and commencement-clause decoding under the contract-amendment notice guide, which trains the same care about when a duty runs rather than assuming the obvious moment.

The four-week drill

The habit installs through daily tracked practice.

• Week one — classify the relief. On ten force-majeure clauses a day, label each one "suspends" or "terminates" and mark the paused duty. Build the reflex that excuse defaults to pause.
• Week two — hold the trigger. Add the resumption trigger and interim duties. For each clause, state in one line when performance revives and what the party must do meanwhile.
• Week three — name the discharge trap. For every question, identify the release-reading trap choice before eliminating it. Naming the mechanism is what stops it working.
• Week four — mixed sets under time. Interleave force-majeure passages with severability, notice-period, and non-waiver passages so the reader selects the right model under pressure. Track the excuse-as-release error separately until it reaches zero across three consecutive sessions.

By the end of the cycle the reader treats every force-majeure clause as a hold on the clock, tracks the paused duty through the disruption, and reads straight to the resumption the band-ceiling candidate never reaches.

The transferable discipline

The force-majeure pause-versus-cancel split is one instance of a discipline the whole TOEIC Link reading section rewards: a dramatic, prominent fact — an excuse, a finding of invalidity, an ending — rarely erases the quiet obligation the question is actually about. The duty is paused, severed, or delayed, not deleted, and the answer lives in what survives. The reader who classifies the relief, marks the paused duty, and holds the resumption trigger converts the section's most emotionally satisfying trap — "the party is off the hook" — into a clean, correct reading of a duty that comes back.