The run of show template that keeps a hard stop from slipping

A schedule for the weeks before an event is not the same document as the script for the day itself. One tracks tasks. The other tracks minutes. Mix the two, and the day-of document ends up too vague to call cues from, or too detailed to have kept up to date for six weeks.

Skift Meetings puts it simply: a run of show is a minute-by-minute guide that outlines the timing, cues, and other important details for the team. In the UK, the same document usually goes by another name — a running order — same script, same cues, different side of the Atlantic. In practice, that means naming who is on stage, what triggers the next cue, and who owns the call.

Which document is which

Three documents can cover show day, and mixing them up is where a team loses time. The Events Industry Council's own accepted-practices guide defines a Function Schedule as the timetable outlining all functions that compose the overall event — every session, every room, across the whole meeting. A day-of-event schedule works close to that: hour by hour, for the whole team, arrival to departure. A call sheet narrows it down further, to one person or one crew: where to be, and who to call if something changes. A run of show narrows it further still — one show, cue by cue, owned by whoever calls it from the desk.

Build it backwards from the hard stop

Most people build a run of show forward: doors, welcome, first speaker, and so on, adding minutes as they go. That works until the last segment runs long, and nobody notices until the room was meant to be empty.

Start from the other end instead. Write down the moment the show has to stop, then place every segment backwards from it. A segment gets the minutes it can afford, not the minutes it would like.

That hard stop is not always yours to move. In England and Wales, a one-off event run under a Temporary Event Notice must have fewer than 500 people at all times, including its own staff. Go past that, and you are breaching the notice's terms — GOV.UK's own guidance warns that breaching a Temporary Event Notice can mean prosecution, not just a fine. On an established site, you'll need a premises licence if you want to sell alcohol or offer entertainment from a particular venue. Its hours were fixed long before your event was booked. Either way, the curfew field in your template is not a target to negotiate on the night.

The columns that make it a script, not a list

A list of segments with times next to them is not yet a run of show. A few more columns turn it into something a team can call from.

Duration matters more than the clock time next to it. A segment written as 10:42–10:49 looks precise and is usually wrong by the time doors open. A segment written as seven minutes survives a late start, because every segment after it shifts by the same seven minutes.

The show-stop nobody writes down

A run of show should carry one segment nobody hopes to use. The UK's Health and Safety Executive defines a show stop as a rapid and controlled halt to a performance to prevent further risk to the audience or to initiate an evacuation. It only works if it is planned, not improvised.

HSE's own guidance says the plan should name who can call a stop. It should say how they reach the stage and the audience, with wording agreed in advance for the announcement. Decide it ahead of time, not during the incident. That row belongs in the same document as the segment it might interrupt, not in a separate safety file nobody opens live.

The Purple Guide, the UK's guide to running events safely, is written by the industry for the industry. Treat its safety segment the way you treat any other cue: written out in full, checked before doors, and known by name to whoever is standing at the desk.

Version control, and who gets a copy

A run of show changes until minutes before doors, sometimes after. A version number and a last-updated time, together on one line, are not paperwork: they tell a stage manager the sheet in hand is not the one from Tuesday's rehearsal.

Give a full copy to whoever calls the show, and to production. Give the relevant slice, their own segments only, to talent and to any outside crew — so a change to one act doesn't have to travel through people it doesn't concern. Mark a change as "Changed" rather than silently editing the time: the team reads the status column before it reads the clock.

One limit is worth writing down before you rely on it: a show that crosses midnight is not something the formulas here follow. The calculations assume one calendar day start to finish. Split a schedule that runs past midnight into two sheets, or track it by minutes elapsed since the start instead of by the clock.

Where it lives once the show starts

Squena keeps a filled-in run of show as a document under the event, next to the team assigned to it. A show caller and the crew who load out after are not one shared assignment: each can hold their own slot, with its own start and end.

What it will not do: run the cue-by-cue math for you. Those formulas live in the spreadsheet. Squena holds the file, the team and their slots — not the running order's own calculations.