Run of show

It looks like a table: time, what happens, who is on stage, which music plays, what is on screen, who gives the cue. Rows sit one minute apart at the opening and the close, five minutes apart during talks. The run of show appears about two weeks out and changes five more times before the day. The producer owns it, but the crew and the client both mark it up, each reading their own column.

A conference for two hundred people, four blocks, three breaks. Without the schedule this happens: a speaker finishes seven minutes early, the host improvises, the sound engineer has no second microphone ready, the camera is on a wide shot and the start of the next talk is missing from the recording. Seven minutes on paper costs nothing. The same seven minutes on the day quietly delete one of your planned deliverables.

It comes together like this. The client sends times, names and job titles in the exact form they should appear in captions. We add the technical rows: when the set changes, when the sting plays, when we cut to a close up. Then the run of show is read out loud at the site visit, line by line, with the host and the crew. On the day it hangs printed in the control position and backstage.

Where it gets overdone: thirty second precision for a company breakfast with forty guests. Nobody holds that, and the producer spends the morning chasing numbers instead of watching the room. The more common failure is different. The schedule exists, but nothing in it says what happens if a speaker does not arrive or a deck will not load. An empty stage is the most expensive thing at any event.

Every run of show we write carries an extra column: time to end. Each row shows how many minutes remain until the programme is meant to finish, so the host sees an overrun instantly instead of doing arithmetic. The other habit: we leave the last fifteen minutes empty as a buffer and tell the client not to fill them. Most events use it, and the ones that do not finish on time.