The concert has started.
Three songs in, the power fails.
The football match reaches the sixty-third minute.
Lightning approaches.
The conference keynote begins.
A fire alarm activates.
The event stops.
Has it ended?
Not necessarily.
A stopped event can still contain a future.
It may resume in five minutes.
Restart after the venue is cleared.
Continue from preserved score or programme state.
Or cross a threshold after which continuation is no longer accepted and the event becomes abandoned.
The hard part is not stopping.
It is knowing what state the event is in while it is not running.
That is the Interruption.
Quick Read
An interruption happens after an event has started but before its ordinary completion, when the live sequence stops while continuation may still be possible.
A useful event-state model is:
RUNNING
→ STOPPED / SUSPENDED
→ either RESUMED / RESTARTED
or ABANDONED.
Different event domains use different terminology, so this is a conceptual model rather than a universal legal dictionary.
A strong current example comes from the IFAB Laws of the Game 2026/27. Football’s Law 5 gives the referee authority to stop, suspend or abandon a match for specified offences or outside interference, while the current law-change material explains what happens after abandonment under competition rules. The details are football-specific, but the state logic is useful far beyond football:
an event can stop without immediately becoming over.
Checked against current live eduKateSG ownership and current 2026/27 primary rules: 4 September 2026.
The Direct Answer
An event interruption works by freezing or containing the live sequence while preserving enough authoritative state—time, score, programme position, participants, rights, safety conditions and communication—to decide later whether the same event can validly continue or must be converted into another terminal state such as abandonment.
The word preserving is central.
If the event cannot remember where it was, it cannot meaningfully resume where it stopped.
Interruption Is Not Cancellation
How Events Work | The Cancellation owns the planned event that does not occur as intended.
Interruption begins later.
The event has already crossed into live occurrence.
People have arrived.
Programme state exists.
Some experience has already been delivered.
So the core question is different:
can this already-started event still continue as the same event?
Interruption Is Not Mere Delay Either
Doors open fifteen minutes late.
The event has not yet started.
That is delay.
The keynote begins, then stops halfway because the building must be evacuated.
That is interruption.
The distinction matters because interruption creates preserved partial state.
Something already happened that may need to remain valid when the event resumes.
The Event Needs an Authoritative State at the Moment It Stops
Score: 2–1.
Time: 63:14.
Speaker: midway through question three.
Concert: song four not yet started.
A restart requires clarity about what state survived the stop.
This can include:
- event clock;
- score or result state;
- programme position;
- participant positions;
- technical configuration;
- ticket/access state;
- venue occupancy;
- unresolved decisions;
- current safety condition.
Interruption turns the present into a checkpoint.
Some State Must Freeze; Some State Keeps Moving
Match clock stops.
Weather keeps changing.
Programme timer stops.
Audience fatigue keeps increasing.
Technical sequence pauses.
Battery levels keep falling.
This is one of the deepest features of interruption:
the event can freeze its official state without freezing the world around it.
The longer the pause, the larger the gap between preserved event state and changed external reality.
Authority to Stop and Authority to Restart May Be Different Questions
A technician detects unsafe electrical behaviour and stops a system.
Can the host restart the event?
Probably not simply because they have the microphone.
A referee suspends a match.
Who decides when play resumes?
The governing rules define that authority.
Events need to distinguish:
- who can call a stop;
- who confirms the blocking condition is cleared;
- who authorises restart;
- who communicates the decision;
- who can abandon the event if continuation becomes unacceptable.
These roles can be the same person.
They do not have to be.
Football Makes the Authority Visible
Under IFAB Law 5 for the 2026/27 season, the referee has authority to stop, suspend or abandon a match for infringements of the Laws or because of outside interference. The Law gives examples such as inadequate floodlights or objects thrown by spectators, while other laws define how play restarts after stoppages.
The exact football procedure belongs to football.
The transferable event lesson is:
a live stop needs an authorised controller and an authorised route back into the running state.
Stopping Is Often Easier Than Resuming
“Stop.”
One word.
Restart may require:
- hazard cleared;
- participants returned;
- equipment reset;
- communications restored;
- score or programme state confirmed;
- audience reassembled;
- officials ready;
- streaming systems re-synchronised.
A stop can be instantaneous.
A restart is a coordinated re-entry.
Restart Is Not Rewind
The concert resumes after a power failure.
Should the band restart the song?
Continue from the middle?
Skip it?
Different event forms permit different restart semantics.
The crucial distinction is:
resumption decides which prior state remains valid;
rewind pretends some already-received event state did not happen.
How Events Work | The Live Moment explains why the past of a live event cannot literally be edited away.
The Audience Needs a State Label
Technical problem.
Everyone waits.
Five minutes pass.
Ten.
Twenty.
People begin asking:
Is it still happening?
The audience does not need every backstage detail.
It needs enough truth to understand the current state.
Useful communication can distinguish:
- temporarily paused;
- waiting for a safety check;
- expected restart time known;
- restart time unknown;
- session relocated;
- event abandoned.
How Events Work | The Host owns the audience-facing human interface.
Interruption owns the state being communicated.
Do Not Promise a Restart Time You Do Not Know
“We’ll be back in five minutes.”
Thirty minutes later, trust is lower than if the event had said:
We are assessing a technical issue. We do not yet have a confirmed restart time. We will update you at 8.30 pm.
An update time can sometimes be more honest than a guessed restart time.
State communication should separate what is known, what is unknown and when the next information will arrive.
The Interruption Creates a Second Clock
Official event clock:
paused.
Real-world clock:
still moving.
This creates consequences.
Venue hire window shrinks.
Last train approaches.
Staff shifts extend.
Catering degrades.
Children become tired.
A long interruption can make technical resumption possible but operational completion unreasonable.
Interruption Consumes Slack
An event has thirty minutes of buffer.
A fifteen-minute stop consumes half.
A forty-minute stop pushes the event beyond its planned envelope.
Now recovery choices become harder:
- shorten later segments;
- move a break;
- drop optional content;
- extend venue time;
- finish late;
- abandon part of the programme.
General Scheduling owns buffers and programme allocation.
Interruption owns the state shock that consumes the event’s recovery capacity.
Stage Management Turns Interruption Into Controlled Hold
A live production stops.
Backstage cannot simply dissolve.
How Events Work | The Stage Manager owns show-calling and backstage live execution.
During interruption, stage management may need to preserve:
- which cue was last completed;
- which cue was interrupted;
- where performers are;
- what technical systems remain safe;
- what must be reset before restart;
- which sequence will resume.
The interruption becomes a controlled hold instead of unstructured waiting.
Technical Failure Has More Than One Recovery State
Primary microphone fails.
Backup works.
The event may not need to stop at all.
Entire sound system fails.
Now interruption may be necessary.
Critical power infrastructure becomes unsafe.
Now the correct state may be evacuation or abandonment, depending on professional assessment.
Events should classify failure consequence before selecting recovery.
Safety Is a Harder Gate Than Programme Value
The audience really wants the show to continue.
The sponsor really wants the show to continue.
The performer really wants the show to continue.
If the authorised safety condition says continuation is unacceptable, desire is not a valid substitute.
This article does not own risk assessment or emergency management.
Its narrow event-state principle is:
restart only after the blocking condition has been cleared by the authority responsible for clearing it.
Weather Can Interrupt Without Owning the Event
Rain.
Lightning.
Heat.
Wind.
Weather owns the atmospheric mechanism.
Interruption owns the event’s state response after the weather crosses a relevant threshold.
This preserves the estate boundary cleanly.
Medical Incidents Can Create Local or Global Interruption
One attendee needs assistance at the rear of the venue.
The whole event may not need to stop.
A performer collapses onstage.
The event may need immediate interruption.
The correct medical response belongs to trained professionals.
The event-state lesson is about scope:
not every local problem requires global stoppage, but some local events change the whole event state.
An Interruption Can Fragment the Audience
Some people wait.
Some leave.
Some go to the toilet.
Some seek food.
The audience that resumes is not necessarily the audience that stopped.
Interruption can therefore change crowd distribution, attention and energy before the programme changes at all.
How Events Work | The Crowd owns those collective behaviours.
Interruption owns the stop state that caused the redistribution.
Restart Requires Re-Gathering Attention
“We are ready.”
Technically ready?
The audience may still be outside.
A restart needs both system readiness and receiver readiness.
The host can help restore a common now:
Thank you for your patience. We are resuming from the beginning of Question 3.
The sentence performs two jobs:
- signals that the event has re-entered running state;
- tells participants which preserved state is authoritative.
The Livestream Can Be Interrupted Differently From the Room
The physical room stops for ten minutes.
The stream shows a holding slide.
Or the stream itself fails while the room continues.
Now the event has diverging receiver states:
physical audience = RUNNING
remote audience = INTERRUPTED.
Hybrid events therefore need to model interruption separately by channel.
A room-level restart does not automatically restore remote access.
Remote Participants Need State Communication Too
Blank video.
Silence.
Is the event over?
Did their internet fail?
Did the platform crash?
A holding state can reduce uncertainty:
The session is temporarily paused. The stream is still connected. Next update at 3:20 pm.
That is digital event-state signage.
Tickets and Re-Entry Can Become Interruption Problems
The venue evacuates temporarily.
Participants may need to re-enter.
Do scanned tickets still work?
Are wristbands used?
Does the ticketing system treat the first scan as final?
How Events Work | The Ticket owns participant access entitlement.
Interruption owns the temporary state change that may require that entitlement to be exercised twice.
Re-entry logic should be designed before the venue suddenly needs it.
Accreditation State May Need to Persist Through the Stop
Crew leaves the controlled area during interruption.
On return, role-based access still matters.
How Events Work | The Accreditation owns working-role access.
The interruption should not accidentally dissolve security boundaries merely because the normal programme paused.
A Long Stop Can Change the Economics Without Changing the Event Identity
Overtime.
Extra venue hours.
Transport changes.
Food waste.
Supplier standby.
The event can remain “the same event” while the interruption creates new cost states.
Those economic effects belong to Finance, Contracts or Vendor analysis where relevant.
Interruption owns the event-state cause.
At Some Point, Resumption Stops Being the Best Model
Five-minute pause.
Same event, obviously.
Five-hour pause.
Probably still possible in some formats.
Three-week pause.
Now the event may need rules for postponement, continuation or replacement.
There is no universal duration threshold.
Continuity depends on the event’s governing system, preserved state and practical context.
Abandonment Is a Terminal Interruption State
Suspension says:
we are stopped, but continuation remains open.
Abandonment says:
this occurrence will not continue to ordinary completion under the current live state.
What happens next can vary.
IFAB’s 2026/27 Law changes state that an abandoned football match is replayed unless competition rules or organisers determine otherwise, with additional provisions for certain situations.
The transferable lesson is that abandonment does not itself answer every downstream question.
It changes the event into a new resolution problem.
An Abandoned Event May Have No Ordinary Result
Competition stops before sufficient completion.
Does the partial score count?
Is the event replayed?
Is a result declared under special rules?
How Events Work | The Result owns how an event converts completed or specially governed performance state into an official outcome.
Interruption owns the path that led the event into an incomplete terminal state.
Partial Experience Cannot Be Un-Delivered
The concert is abandoned after forty minutes.
The audience did not receive zero concert.
They received forty minutes and then non-completion.
This complicates:
- refund policy;
- participant satisfaction;
- sponsor delivery;
- recordings;
- public communication;
- event memory.
Those downstream domains keep their own owners.
The interruption article records the essential fact:
the event exists as a partially delivered occurrence.
Interruption Creates Strong Traces
“The year the lights went out.”
“The match that stopped for the storm.”
“The ceremony everyone had to evacuate.”
An interruption can become more memorable than the planned programme.
How Events Work | The Trace owns what remains afterward.
Interruption often generates unusually strong stories because it exposes the machinery that normal flow hides.
The Next Edition Can Learn From the Stop
Why did restart take twenty minutes?
Why did nobody know who could authorise resumption?
Why did ticket scanners reject re-entry?
Why did remote viewers see a black screen?
These are valuable handover questions.
How Events Work | The Handover owns cross-edition learning.
A good interruption review records state failures, not only the original trigger.
The Trigger and the Interruption Are Different Objects
Lightning causes the stop.
The interruption is the event’s response state.
Power failure causes the stop.
The interruption is the event’s response state.
Medical emergency causes the stop.
The interruption is the event’s response state.
This distinction prevents the Events branch from cannibalising Weather, Engineering, Medicine, Security or Risk.
Decision Gate: Can the Same Event Resume?
Before resumption, ask:
- Has the blocking condition actually cleared?
- Who has authority to confirm that?
- Is preserved event state known and valid?
- Are critical systems ready?
- Are participants and staff ready?
- Can the audience be reassembled or reconnected?
- Does enough operational time remain?
- Can access and safety conditions still be satisfied?
- Has the restart state been communicated clearly?
If a critical answer remains no, “we really want to continue” is not a restart plan.
Failure Mode 1: Nobody Knows Whether the Event Is Paused or Over
The audience receives silence instead of state.
Repair: communicate the current status, what is known, what is unknown and when the next update will arrive.
Failure Mode 2: Restart Authority Is Ambiguous
Several people believe they can say go.
Repair: define stop, clear, restart and abandon authority before the live event.
Failure Mode 3: The Event Forgets Its Own State
Score, cue or programme position becomes disputed.
Repair: preserve authoritative checkpoint data at interruption.
Failure Mode 4: Safety Clear and Operational Ready Are Confused
The hazard is gone, but technical systems or participant positions are not ready.
Repair: treat safety clearance as necessary but not automatically sufficient for restart.
Failure Mode 5: A Guessed Restart Time Becomes a Broken Promise
The event repeatedly moves the time.
Repair: use update deadlines when restart timing is genuinely unknown.
Failure Mode 6: The Room Resumes but the Stream Does Not
Hybrid receiver states diverge.
Repair: include physical and remote channel readiness in the restart gate.
Failure Mode 7: Re-Entry Was Never Designed
Participants leave during the stop and cannot get back in.
Repair: define ticket, wristband and access-state behaviour for temporary evacuation or interruption.
Failure Mode 8: The Event Resumes After Its Practical Envelope Has Collapsed
Venue, transport, staffing or participant constraints make completion unreasonable.
Repair: include external time and capacity constraints in the continuation decision.
Failure Mode 9: Abandonment Is Announced Without Downstream Instructions
People know the event is over but not what happens to tickets, transport, results or future communication.
Repair: pair terminal state with the next information path, while keeping specialist refund, result and legal decisions with their proper owners.
Why This Matters for Mathematics and Computing Students
Interruption is a state-machine problem.
RUNNING is not the only state.
A robust system needs intermediate and terminal states.
For example:
RUNNING
→ STOP REQUESTED
→ STOPPED
→ CONDITION CHECK
→ READY TO RESUME
→ RUNNINGor
STOPPED
→ CONDITION NOT CLEARED
→ ABANDONED.
Students can then ask which state variables must be persisted across the stop.
That is the same question software systems ask during pause, crash recovery and checkpoint restoration.
Why This Matters for English Students
These words are not interchangeable:
delayed
paused
stopped
suspended
resumed
postponed
abandoned
cancelled.
Different domains use them differently, so good reading tracks the definition used by the governing event.
The larger language lesson is powerful:
state words change what people believe can happen next.
For Parents: A Pause Is Not Failure
Children often interpret stopping as losing.
But good systems stop on purpose.
Check.
Reset.
Clarify.
Continue when ready.
A school performance pausing because a child is unwell is not a badly designed event if the pause protects the person and the restart is handled calmly.
Sometimes stopping is evidence that the system still knows what matters.
A Compact Interruption Model
RUNNING
The event is live.
↓
TRIGGER
technical / environmental / medical / security / rule / other event-specific cause
↓
STOP AUTHORITY
Who can interrupt the live sequence?
↓
CHECKPOINT
time / score / programme / people / systems / access
↓
STOPPED / SUSPENDED
Live progression is contained while continuation remains open.
↓
ASSESS
Has the blocking condition cleared?
↓
RESTART GATE
safety + systems + people + access + authority + communication
↓
RESUME
Restore the same event from the accepted preserved state.
or
ABANDON
Close the live occurrence and hand downstream consequences to result, ticket, contract, communication and other proper owners.
What This Article Does Not Own
It does not own Risk generally.
It does not own emergency response or medical care.
It does not own Weather.
It does not own Scheduling or Resilience generally.
It does not own Cancellation.
It does not own football officiating.
Its canonical event job is:
explain how an already-started event stops while preserving enough state and authority to decide whether the same event can resume or must enter a terminal incomplete state.
Frequently Asked Questions
What is the difference between interruption and cancellation?
Interruption happens after an event has started and stops its live progression. Cancellation generally means the planned event or edition does not occur as intended. Exact terminology varies by domain.
What state has to be saved when an event stops?
It depends on the event, but examples include time, score, programme position, cue state, participant positions, access state and unresolved decisions. The saved information should be enough to resume consistently if continuation is authorised.
Who decides whether an event can restart?
The governing rules, venue procedures and event authority structure determine this. The person communicating the restart is not necessarily the person authorised to decide it.
What does “abandoned” mean?
In this article, it means the interrupted occurrence will not continue to ordinary completion under its current live state. Specific sports, competitions and events may define abandonment more precisely and specify different downstream consequences.
Can an event resume after a long interruption?
Sometimes. Whether it remains the same event depends on governing rules, preserved state, elapsed time, practical conditions and the event form. There is no universal duration threshold.
Why should remote and physical audiences be tracked separately?
Because one channel can be running while another is interrupted. Hybrid events may therefore need separate receiver-state checks before declaring the whole event resumed.
Research and Current Rules Example
- IFAB Laws of the Game 2026/27 — Law 5: The Referee — current football rules defining referee authority to stop, suspend or abandon a match and to supervise restarts under the Laws.
- IFAB Laws of the Game 2026/27 — Law 7: The Duration of the Match — current rules on match periods, allowance for time lost and related timing structure.
- IFAB — Law changes 2026/27 — current changes including the treatment of abandoned matches and downstream replay/competition-rule consequences.
The IFAB rules are a current real-world example of interruption state and authority, not a universal rulebook for concerts, conferences or ceremonies. Every event should follow its own governing rules, professional safety procedures, venue requirements and legal obligations.
Teaching Guide
Core idea: stopping and ending are different system states.
Primary question: What information must survive a stop so the same event can resume consistently?
Secondary question: Why can a hazard be cleared while the event still remains unready to restart?
Classroom activity: Give students four events—a football match, school concert, science fair and livestream lesson. Interrupt each with one problem. Students must define the stop state, what is preserved, the restart gate and what would force abandonment.
Computing connection: design a finite-state machine with RUNNING, STOPPED, READY_TO_RESUME, RESUMED and ABANDONED states. Identify illegal transitions.
English connection: compare delayed, suspended, postponed, abandoned and cancelled. Ask why event rules must define them rather than relying on everyday intuition.
Misconception to correct: “If the problem is fixed, restart immediately.” Better: the original blocking condition may be cleared while people, systems, access and communication are still not ready.
Exit check: A concert pauses because the power fails. Power returns, but the audio system has not been tested and half the audience is outside. Is the event ready to resume? What other state must be checked?
Final Thought: A Pause Preserves Possibility
The event stops.
For a moment, nobody knows whether the next state is continuation or ending.
That uncertainty can feel like failure.
Sometimes it is the opposite.
A good system can stop before it causes greater damage.
Remember where it was.
Wait for the world to become acceptable again.
Then ask the right question:
Are we actually ready to continue?
If yes, the event returns to motion.
If no, it ends honestly.
The intelligence is not in refusing to stop.
It is in knowing what must be true before starting again.