Glossary: Event production
Run of show
The shared sequence of an event, showing what happens, when it happens and who coordinates each transition.
Definition
A run of show is the operational sequence of a live event, connecting programme segments with timings, participants and production responsibilities. It gives the event team a shared view of the audience experience and the transitions required to deliver it.
What a run of show coordinates
An event programme tells guests what they can expect. A run of show tells the delivery team how that experience unfolds. It includes moments that guests may never notice, such as preparing the next presenter, clearing furniture during applause or confirming that an introductory video has finished before someone speaks. These connections often determine whether an otherwise strong programme feels composed or improvised.
The document should follow the event's actual operating needs. A conference may require speaker names, presentation references and panel transitions. A performance may need entrances, set changes and interval arrangements. It is not a transcript of every conversation or a substitute for specialist technical documents. Its value lies in making the overall sequence understandable across departments without burying important decisions in unnecessary detail.
Fields that make the document usable
Each row should represent a meaningful programme segment or operational transition. Use consistent names for people, locations and media assets. Distinguish the intended clock time from duration, because a segment can start late while still requiring its full agreed length. Identify who owns the transition rather than assuming that everyone understands an instruction such as stage ready.
| Field | Operational purpose |
|---|---|
| Start and duration | Show the planned timing and how much programme time the segment occupies. |
| Segment and participants | Identify the activity and the people expected to deliver it. |
| Transition | Describe how the previous segment hands over to the next. |
| Owner | Name the role responsible for coordinating that handover. |
| Notes and dependencies | Record necessary readiness checks, approved alternatives or linked documents. |
Keep detailed operator instructions in the cue sheet when they would make the shared sequence difficult to scan.
Plan timing without pretending it is fixed
Some moments are anchored to a clock, while others depend on the completion of an action. Doors opening may have a scheduled time, but a presenter entrance might depend on applause ending and the stage manager confirming readiness. Label these differences explicitly. Otherwise, an operator may mistake a planning estimate for permission to act regardless of what is happening on stage.
Agree where time can move
Identify flexible material before the event: optional remarks, a shortened introduction or a discussion that can finish earlier with approval. Protect essential access arrangements, safety checks and contractual commitments from casual compression. A realistic recovery plan says who may approve a change and how participants will hear about it. It does not simply instruct the crew to catch up.
Ownership, revisions and briefing
Appoint one document owner to consolidate approved changes. Content teams, technical departments and guest coordinators can contribute information, but competing master copies create conflicting instructions. Every issued version needs a clear date or revision label. Establish where the current copy lives and how printed copies will be replaced or visibly corrected when a meaningful update is approved.
- Check participant names, pronunciation notes and arrival arrangements with the responsible coordinator.
- Confirm that segment durations include entrances, applause and furniture movement where relevant.
- Review transitions with audio, lighting, video and backstage representatives.
- Brief affected people directly when an approved revision changes their next action.
The show caller normally uses the agreed sequence to coordinate live execution, while the document owner preserves the underlying programme record.
Scenario: a Dubai conference running late
Imagine a Dubai conference where the opening interview finishes later than planned. The next segment combines a short film, a presenter introduction and a panel discussion. The team does not start the film merely because its printed clock time has arrived. Backstage readiness, audience attention and the presenter's position still determine whether the transition can proceed cleanly.
The producer approves removing an optional spoken recap rather than rushing the panel's access arrangements. The caller communicates the revised sequence to operators, while the stage manager briefs the presenter before entry. The run of show records the approved omission and revised expected times. This hypothetical adjustment preserves the essential programme while giving every department the same explanation of what changed and why.
After the event, the owner records actual timings separately, preserving a useful comparison without rewriting the original plan.
Keep programme control separate from safety authority
A run of show is not permission to proceed through an unresolved technical or safety concern. A scheduled entrance cannot override an unavailable accessible route, and a planned scene change cannot authorize unapproved structural work. Responsible specialists and venue procedures retain their authority. The document should identify the communication route for a hold, including who updates presenters and audience-facing teams.
Common weaknesses include copying optimistic durations from an invitation, omitting transitions and circulating changes without checking who received them. Another is treating the run of show as the entire production schedule. Installation, rehearsals and crew arrangements need their own coordinated planning. A concise live sequence works best when those supporting plans are complete and their relevant dependencies are clearly referenced.
Frequently asked questions
Is a run of show the same as an agenda?
No. An agenda primarily describes programme content for participants or guests. A run of show adds operational timing, transitions, responsibilities and production notes so the delivery team can coordinate what happens around that content.
Who should approve the run of show?
The appointed producer or event lead usually approves the programme, with technical and operational contributors confirming their areas. The approval structure should be agreed early, especially where speakers, performers or venue restrictions create dependencies.
Should every action have an exact clock time?
Not necessarily. Clock times support planning, but some actions should follow observable triggers or readiness confirmation. Clearly distinguish estimates, fixed commitments and action-dependent transitions so a printed time is not mistaken for an automatic instruction.
Can the run of show change during the event?
Yes, through the agreed decision and communication process. Changes need an authorized owner, a clear description and direct communication to affected people. Silent edits to a shared document are unreliable when operators are concentrating on live delivery.
How detailed should the document be?
Detailed enough to coordinate the whole programme without becoming unreadable. Include essential transitions and responsibilities, then reference specialist documents for operator-level instructions. Rehearsal usually reveals whether missing information or excessive detail is slowing practical use.

Producing an event?
Planning, technical production, stage, sound, light and streaming for concerts and corporate events.
Music event management