What to Do When Your Event Runs Late

When an event starts running late, the fix is rarely one big cut. Decide early, take the time back from the things you control (buffer, Q&A, breaks, changeovers) before you take it from speakers, protect the times that cannot move, and tell each affected person once, clearly, before they go on.

A common failure is that nobody decides anything for an hour, and the last speaker before lunch is told to do 20 minutes in 7.

Decide at a checkpoint, not in a panic

Pick checkpoints in your run of show, usually the end of each block before a break. At each one, compare the clock with the plan and do one sum:

Minutes late, minus buffer still ahead, equals minutes to recover.

If the answer is zero or less, spend buffer and carry on. If it is positive, decide where the minutes come from now, while there are still several places to take them from. A sensible rule: once you are more than five minutes behind at a checkpoint, act, even if there is buffer left. Buffer spent at 10:30 is not there for the overrun at 12:15.

Only one person should make this call. Usually it's the producer or show caller; everyone else feeds them the numbers.

Where to take time back

Option	What it usually gives	Who pays	Tell
Spend buffer	Whatever is left	Nobody, today	Nobody
Shorten Q&A	2–5 min per talk	Audience	Host or moderator, speaker
Shorten a break	5 min	Audience, catering	Host, catering lead
Tighten changeovers	1–2 min each	Crew	Stage manager, host
Ask an upcoming speaker to trim	2–5 min	That speaker	The speaker, in person, early
Merge or drop a segment	A whole slot	That segment's people	Everyone affected, producer decides
Run past the planned end	As much as the venue allows	Venue, catering, stream, travel	Venue first, then everyone

Work down the table in that order. The top rows cost almost nothing; the bottom rows cost goodwill or money. The minutes in the table are rules of thumb from our own experience of scheduling, not measurements. A few notes:

• Q&A is the cleanest cut because nobody prepared it. Say "time for one question" rather than skipping it entirely. Running live audience Q&A covers how to close one gracefully.
• Breaks can usually lose 5 minutes, but not much more. People still need the toilet and coffee, and a break cut too short just means people walk in late to the next session.
• Changeovers tighten if the next speaker waits at the side of the stage with their mic already on, and the host introduces them while they walk.
• Asking a speaker to trim works only with notice. A speaker told 20 minutes before their slot can cut a section. A speaker told as they walk up will rush everything, which usually costs more time than it saves.
• Running past the end almost always costs something. Check the room booking, catering, a livestream slot and anything else fixed before you assume you can.

Worked example: 12 minutes behind at 10:28

Take the half-day conference morning worked through in the run of show guide: talks of 20 minutes with 5 minutes of Q&A, a 20-minute break at 10:44, a 40-minute panel ending 11:44, 11 minutes of buffer before a hard out at 12:30.

The keynote runs 8 minutes over, and Talk 1 loses 4 minutes to a slide problem. Talk 1's Q&A ends at 10:28 instead of 10:16: 12 minutes late, with 11 minutes of buffer left. You could spend the whole buffer and still be 1 minute short, with two hours to go.

Instead:

• Talk 2 Q&A: 5 minutes down to 2. Saves 3.
• Coffee break: 20 minutes down to 15. Saves 5.
• Panel: 40 minutes down to 36, by taking one fewer audience question. Saves 4.

That is 12 minutes. After its 3-minute changeover, Talk 2 now runs 10:31 to 10:51, its Q&A ends 10:53, the break ends 11:08, and the panel finishes at 11:44, back on the original schedule with all 11 minutes of buffer still in hand. No talk was shortened.

What to tell speakers, and how

Tell them once, before they go on, with the new number. Don't make them work out the arithmetic.

To an upcoming speaker, at least 15 minutes ahead if you can:

"We're running about 6 minutes behind. Could you land your talk in 17 minutes instead of 20? Your clock will start at 17, and you'll get the usual signals at 5 and 1. If you need to drop something, the case study is the natural cut."

To a moderator:

"We need the panel to finish at 11:44 exactly. That means one audience question instead of two. I'll give you the 5-minute signal at 11:39."

Then make sure the clock matches what you said. If you promised 17 minutes, the speaker's countdown should start at 17:00, not 20:00 with a hope that they finish early. The guide to keeping speakers to time has wording for the moment a speaker on stage goes over.

What to tell the audience

Give a time, not an apology. "We'll start again at 11:08, so grab a coffee and be back for the panel" is useful. "We're running a bit late, sorry everyone" invites people to wander. Never announce the delay more than once.

What not to do

• Don't take it all from the last speaker before a break. It is unfair, and that speaker will overrun anyway.
• Don't silently start a shorter clock. A speaker who planned for 20 minutes and sees 17:00 without warning loses a minute just working out what happened.
• Don't let Q&A run because the room is enjoying it while you are behind. Promise to take questions at the break instead.
• Don't run sessions early in a multi-room event. People plan to move between rooms at the published times. Running multiple rooms and tracks covers the rules for parallel sessions.

When the problem is technical

Have a plan per failure, written in the run of show, before you need it:

Failure	First move	Clock
Mic dies	Hand over the spare handheld; fix the lapel later	Keep running
Slides won't load	Speaker starts without them, or host fills while the laptop is swapped	Pause if the speaker hasn't started
Video won't play	Skip it, host says one line about what it would have shown	Keep running
Stream or remote speaker drops	Host moves to the next item while the crew reconnects	Next segment
Power or venue problem	Follow the venue's procedure	Pause

The rule behind the "Clock" column: if the speaker lost time through no fault of their own, give it back, and take it from Q&A or the buffer later. If they hadn't started yet, pause until they can.

Anything involving safety is different. A fire alarm, a medical emergency or a crowd problem is not a scheduling decision. The UK Health and Safety Executive's event guidance describes a show stop as a rapid and controlled halt to a performance and advises identifying the key people who can start one, who communicates with performers and who communicates with the audience, and agreeing the wording of announcements. Know your venue's procedure and who holds that authority before doors open.

Adjusting the clock live

In StageClock the Control Panel has time-adjust buttons (−1m, −30s, −10s, +10s, +30s, +1m), so you can shorten the running countdown to the length you agreed with the speaker, or give back time lost to a technical fault. The next button (or the right arrow key) moves to the following segment, and the "Wrap Up" message type or the "Wrap Up Now" quick send prompts a speaker who is past time.

Frequently asked questions

What if a speaker refuses to shorten their talk?

Then recover the time elsewhere and let them run their full slot, but hold the end of it firmly. A visible clock and an agreed signal do more than a negotiation backstage. If they are the keynote, consider giving them their full time and cutting their Q&A instead.

Key takeaways

• Check the schedule at fixed checkpoints and do one sum: minutes late minus buffer ahead.
• Take time from buffer, Q&A, breaks and changeovers before taking it from any speaker.
• Tell each affected person once, before they go on, with the new number, and make the clock match it.
• Give back time lost to technical faults, and recover it later from Q&A or buffer.
• Safety stops follow the venue's procedure, not the run of show.

Sources

• Planning for incidents and emergencies (UK Health and Safety Executive, updated January 2026)