Every event produces two run sheets. There is the one the organiser writes — a tidy spreadsheet of start times — and there is the one the MC and the AV crew actually wanted, which explains what happens when the start times fail. They will fail. A run sheet's job is not to predict the day; it is to keep the day recoverable when the prediction goes wrong, which it does roughly from the second item onward.

Build it backwards, then buffer it

Our method is to start from guest arrival and build backwards, locking the immovable anchors first — venue access, the curfew, and any formalities that cannot shift. Everything else flexes around those fixed points. Working backwards also exposes the fantasy maths early: if bump-in starts at two and doors open at six, the afternoon does not have room for everything currently scheduled in it, and it is far better to discover that on paper than on the loading dock.

Then buffer every transition, and be most generous exactly where organisers are most optimistic — before speeches, before food service, and before entertainment. The classic collision is the speech scheduled against mains: the speaker competes with cutlery, the kitchen competes with the speaker, and both lose. Speeches overlapping meal service sit among the most common run-sheet failures we see, and the failure is purely one of scheduling, not performance. Five minutes of nothing between segments is not dead air. It is the shock absorber.

Cues, not clock-times

Here is the production insight most corporate run sheets miss: clock-based cueing fails on contact with real speakers. Speakers overrun. They also underrun, which is somehow harder to plan for. Once the 7.42pm item starts at 7.51, every timestamp below it is fiction — even a ten-second deviation breaks a clock-based chain. So write cues instead: the lights change on the MC's final thank-you line, not at 8.15; the video rolls when the speaker walks to the lectern, not at 8.32. Times still appear on the sheet, but as targets. The cues are the triggers.

This is also why the MC's version needs more than times. Brief your MC about two weeks out with the full run sheet plus everything that never makes the master copy: bios with phonetic spellings, the sponsors who must be thanked, housekeeping, tone guidance, and any sensitivities in the room — with all subsequent changes routed through one channel. An MC forced to guess the pronunciation of a board member's surname, live, has been failed by a document, not by their own preparation.

One event, several versions

Resist the single monster document. Large productions issue tailored run-sheet versions per department, and the practice scales down to any event with more than one supplier. The kitchen does not need the AV cue list; the AV desk does not need the canapé timings; the MC needs the narrative, not the bump-out schedule. Every version carries a version number and a last-updated stamp, because the most dangerous document at any event is the superseded run sheet still circulating confidently on somebody's phone.

Whichever version you are holding, the same items go missing, event after event. The omissions we see most often:

  • Supplier arrival and access times
  • Mobile numbers for every key person — on the sheet, not in someone's contacts
  • The soundcheck window, protected as a real booking
  • Bump-out — the event does not end when the guests leave
  • Phonetic spellings for every name the MC must say aloud

The hour the run sheet must protect

One block deserves its own defence: the speaker's arrival and soundcheck. Our event-day protocol is short, and we hold to every line of it. Meet the speaker at the entrance — not the lobby — 60 to 90 minutes before their slot, and walk them to the green room without info-dumping en route; whatever needs saying can wait until they have put their bag down. Then a proper soundcheck: 20 to 30 minutes, physically walking the stage, testing the lavalier across the speaker's full range of movement, playing any videos at full volume, and agreeing a subtle end-of-slot signal with the AV desk so nobody has to mime a wristwatch from the wings.

The stakes are simple: poor AV destroys a speaker's credibility, which makes AV quality part of the speaker investment rather than a separate line item. You did not pay a five-figure fee to have the keynote delivered through a crackling lapel mic. The run sheet is where that hour gets defended — written in, buffered on both sides, and never traded away when the afternoon runs late.

A good run sheet is like good insurance: mostly unread, until the moment it is the only thing that matters. Build it backwards, cue it on actions, split it by department, stamp every version — and accept that the highest praise it can earn is that nobody mentioned it at all.