Key Takeaways
- A run of show is a production document, not a programme schedule — it contains every technical cue, not just timings
- The production company builds it, but the brand must confirm: speaker names and order, product reveal sequence, VIP treatment, media protocol
- The run of show is live from week 4 of production and never final until 48 hours before doors open
- Every transition between programme elements is a cue in the run of show — transitions are where shows lose energy
- The show-caller's version of the run of show is different from the client version — it includes technical annotations not in the client document
What a run of show actually contains
A run of show for a product launch is not a programme booklet. It is a cue document — a minute-by-minute, sometimes second-by-second specification of every action that occurs in the production, in sequence. For a 3-hour product launch with a 150-guest invite-only press event, the run of show will typically be 8–12 pages long. It contains: guest arrival and doors procedure; pre-event entertainment cues; programme start cue; each speaker's walk-on music cue, introduction, presentation duration, walk-off cue and transition to next element; the reveal sequence broken into individual cues (lighting state 1, music out, hold, lighting state 2, cover release, product close-up lighting state, photography hold); press Q&A opening and close cues; networking transition; service cues; close of event.
What the brand must provide to build it
The production company can draft the run of show's technical structure — the cues it knows from the production design. What it cannot draft without the brand: the confirmed speaker order and names; the specific product reveal sequence (what is revealed, in what order, using what mechanism); VIP treatment protocol (who receives special greeting, early access, specific seating); media protocol (which journalists have one-on-one time, when it occurs, how it is managed); any embargo protocol (if product information is under embargo until a specific time, every team member in the production needs to know the embargo terms); and the close sequence (how guests exit, what the post-event experience is).
The live document
A run of show that is finalised at week 4 and delivered as a static document will be wrong by show day. Speaker order changes, content delivery formats shift, VIP additions require programme adjustments, and technical discoveries during the site visit change cue sequences. The run of show is a live document — it is maintained, version-controlled and distributed as a current version to all department heads at every update. The show-caller holds the master version. All changes go through the show-caller. "I just changed the presenter order" spoken to a production assistant on show morning is not a change until the show-caller has confirmed it in the document and notified all departments.
The transitions problem
Transitions between programme elements are where product launch energy dies. The speaker finishes, the MC takes the stage, the production scrambles to change the presentation content on the LED wall, the lighting operator waits for a cue that hasn't come, the audio team plays holding music that doesn't match the event's tone. Thirty seconds of visible scramble between programme elements tells the room that no one is running the show. Every transition in the run of show must have: a defined length (typically 30–90 seconds depending on the context), a defined action for every department (lighting state, audio content, LED content, stage position), and a cue that ends it. Transitions are not pauses. They are programme elements with their own cues.