What Do You Do When a Live Programme Runs Long?

Almost every cohort asks the same thing within the first week of the timing module: what happens when a segment runs over and the clock does not care? Learners usually expect a trick. The honest answer is that recovery is mostly decided before the programme starts, in how the running order was built and who was told what.

A programme that overruns by four minutes is rarely in trouble if the plan already named where four minutes can come from. A programme with no named flexibility turns every delay into an argument at the side of the stage. The first habit we teach is to write the flexibility down, next to the segment it belongs to, in plain words the whole team can read.

In this note I answer the question the way I answer it in class, step by step, using the kind of sample rundown learners work with: a ninety-minute streamed discussion with an opening, three panel blocks, a short audience segment and a close.

A buffer is a deliberate gap in the running order, not a hope. Learners often spread spare minutes thinly across every segment, which looks tidy but gives nobody anything useful to spend. We teach placing buffers at natural joints, usually after a block with several speakers, where overruns tend to collect.

On the sample rundown, a three-minute buffer sits after the second panel block and a two-minute one before the close. Each carries a label: this time is not content. If the presenter reads the sheet and sees a labelled buffer, the decision to use it becomes routine instead of a negotiation.

Buffers also protect the end. A programme that must finish at a fixed time, because a venue is booked or a stream window closes, needs its end-time guarded more firmly than its middle. We practise working backward from the finish, so the last segment keeps its length even when the middle stretches.

• Place buffers after segments with the most speakers
• Label every buffer so nobody mistakes it for content
• Protect the closing segment before anything else

When the buffers are spent and the programme is still behind, someone has to cut. The skill is having the order of cuts agreed in advance. In the course we ask learners to mark each segment as fixed, flexible or optional, and to rank the flexible and optional ones from first to trim to last.

A fixed segment is one tied to something outside the show: a guest who leaves at a set time, a sponsor message with an agreed slot, a handover to another team. Flexible segments can shorten without losing their point. Optional ones can be dropped whole, such as a second audience round or a recap.

Writing this ranking on the cue sheet changes how people behave under pressure. The producer is not inventing cuts at speed; they are reading a decision made calmly days earlier. Presenters also appreciate knowing which part of their time is safe, which lets them relax into the parts that are not.

• Mark every segment fixed, flexible or optional
• Rank what to trim first, second and third
• Agree the ranking with the presenter before rehearsal

Running short sounds easier and is not. A discussion that finishes eight minutes early leaves an awkward hole, especially on a stream where viewers expect the advertised length. We teach learners to prepare a small stock of extension material: a follow-up question set, a longer audience round, or a summary the moderator can expand.

These items sit on the page like optional segments in reverse, each with an estimated duration and a position where it can slot in cleanly. They are not filler to be improvised from nothing. The moderator should know which two or three extensions exist and which one suits the mood of the room.

Learners sometimes worry that planning for a short show signals low confidence. It does the opposite. A plan that handles both directions lets everyone stop watching the clock with anxiety and start listening to the conversation, which is where a good live programme actually comes from.

A timing change needs one voice. In a small team that is usually the producer or stage manager; on a streamed event it may be the person running the clock in the control room. We ask learners to name that person on the handover notes and to write down how the message reaches the presenter, whether by earpiece, a card held up, or a note on the monitor.

The wording matters too. Short, agreed phrases such as wrap in two minutes or move to the close are easier to act on than explanations. In rehearsal we practise giving and receiving these calls until they feel ordinary, because a first-time cue delivered mid-sentence rarely lands well.

One more point from experience: tell the presenter what has changed and what has not. Saying you are three minutes over, the buffer is gone, and the close is untouched gives them a complete picture in a single breath and keeps the tone steady.

• Name one person who calls timing changes
• Agree short phrases and the channel they travel on
• Say what changed and what stays fixed

Timing recovery improves with repetition, so the module includes an exercise where learners receive a sample rundown and a list of simulated problems: a guest arrives late, a video clip runs long, an opening speech doubles in length. For each, they rewrite the plan on the spot using their buffers and trim ranking.

Most learners find their first attempt too aggressive, cutting far more than needed. By the third problem they tend to settle into small, reversible moves, such as shortening a transition or merging two questions, and keep the larger cuts in reserve.

Instructors review these rewrites and comment on clarity as much as arithmetic. A correct adjustment that nobody on the team could follow is still a weak plan. We look for pages that a presenter could read in a few seconds and act on without asking anyone to explain.