How to write a run-of-show that survives the actual night

What a run-of-show is for

A run-of-show (sometimes called a running order or show flow) has one job: to make sure that everyone working on an event knows what happens next, when, and what they have to do about it. The host, the sound technician, the lighting operator, the caterer and the person standing at the door all read the same document, from different angles.

It is not the same as the programme guests see. The guest programme says “19:30 Dinner”. The run-of-show says that at 19:25 the bar closes, at 19:28 the host is at the microphone, at 19:30 lights dim to the dinner state and background music drops, and at 19:32 the kitchen is told to send the starter. That level of detail is what lets a busy night feel effortless from the outside.

The columns every run-of-show needs

The format matters less than consistency, but most professional documents settle on the same set of columns. A spreadsheet works well because it can be sorted, filtered and printed.

Some events add a column for the stage manager’s standby calls, and larger productions split sound, light and video into separate columns. For a typical corporate party or launch, the eight above are enough.

Above the timed lines, put a short header block. It should hold the event name, date, venue address, version number, and the key contacts with phone numbers: producer, venue manager, technical lead, caterer and the client’s decision maker. Below it, list crew call times: when each supplier arrives, when the technical check starts, when the rehearsal happens and when doors open. Many problems on the day come from someone arriving an hour after they were needed, and a single list of call times prevents that.

Writing each line so it cannot be misread

The most common failure is not a missing item but an ambiguous one. A few habits help:

• One owner per line. “Marketing team” is not an owner. A name is.
• Times in one format. Use 24-hour times throughout. In Denmark that is standard anyway, but international speakers and suppliers may still read “8:15” as morning.
• Verbs for actions. “Doors open”, “Lights to dinner state”, “Host introduces award 2” leave less room for interpretation than labels like “Awards”.
• Cues tied to something observable. “Music fades when CEO reaches the lectern” is easier to execute than “music fades at 20:15”, because the CEO may be two minutes late.
• Exact file names for every video, slide deck and audio track, matching the files on the playback computer.

Agree the cue language with the technical crew before the day. If the sound and lighting team numbers their lighting states and audio tracks, use the same numbers in the document, so “LX 4” and “track 3” mean exactly one thing to everybody.

Write transitions as their own lines. The moment between a speech and a video, or between dinner and the first dance, is where most awkward silences happen, and it is usually the moment nobody wrote down.

Buffers, overruns and the reality of timings

Some parts of an evening run long almost every time: arrival drinks, speeches, award ceremonies with many winners, and anything involving moving a crowd from one room to another. Other parts can be cut if needed: a second music set, a closing video, a late snack.

Build the schedule with that in mind. Leave a few minutes of buffer after each speech block, and mark which items are flexible. When the night runs fifteen minutes behind, whoever holds the schedule then knows exactly where to recover the time without asking anyone. It also helps to agree a hard stop with each speaker, in writing, and to tell them who will signal when time is nearly up.

A concept and scheduling phase that tests the timings early, by reading speeches aloud and walking the route between rooms, catches most overruns before they are printed.

Versions, sharing and the freeze

A run-of-show changes constantly in the last two weeks, and that is fine as long as everyone works from the same version. Put a version number and a date in the header of every page. Send each new version to the full list of suppliers, with a short note on what changed, rather than sending only the changes to the people involved.

Then freeze it. A sensible freeze point is the day before the event, or after the rehearsal on the day. After that, changes are made by hand on the printed copies by the person holding the schedule, and called out on the radio or in person. Last-minute emails with new attachments are rarely read by the technician who is already up a ladder.

Print copies for the desk, the stage manager, the host and the kitchen. Phones run out of battery, and a crew member at a lighting desk cannot scroll a PDF while running cues.

The contingency section most documents lack

At the end of the document, add a short page of “if this, then that”. It does not need to cover every possibility, only the likely ones:

• a speaker is late or ill: who replaces them, or which item moves up;
• a video will not play: what the host says, and whether it is skipped or retried later;
• the weather turns on an outdoor element: where guests go, and who decides;
• a medical incident: who calls for help, where the first aid kit and the nearest defibrillator are;
• a power cut or fire alarm: the venue’s procedure and the assembly point.

Most of these will not happen. Writing them down means the team does not have to improvise when one does, which is what good on-site management relies on.

Rehearse it, then trust it

A run-of-show is only proven once it has been walked through. Even a short technical rehearsal, running every cue in order without the full speeches, shows which transitions are too tight and which files are missing. Where possible, get the host and the main speakers on stage beforehand so they know where to stand, which microphone to use and where the exit is.

On the night, one person holds the document and calls the show. Everyone else follows that person, not their own copy. That single point of authority is what makes the document work under pressure, and it is the difference between a schedule on paper and a schedule that survives contact with the actual night.

Afterwards, keep the marked-up printed copy. The handwritten changes show where the plan met reality: which speech ran six minutes long, which transition needed an extra cue, which supplier arrived late. Fold those notes into the template for the next event, and each run-of-show starts from a better draft than the last one.