How Event Planners Build a Run of Show

If you have ever attended a well-executed event — one where the speakers transitioned smoothly, the music cues landed perfectly, the lighting shifted at just the right moment, and every segment felt intentional — you were experiencing the result of a well-built run of show.

A run of show (sometimes called a show flow, production schedule, or cue sheet) is the minute-by-minute operational document that guides an event from start to finish. It is not a marketing timeline. It is not an agenda. It is the coordination blueprint that tells every team member what is happening, when it is happening, who is responsible, and what comes next.

Building a strong run of show is one of the most critical skills in event operations, and it is one of the most commonly done poorly.

What a Run of Show Document Actually Contains

At its most basic, a run of show is a time-indexed document that maps every moment of an event. But a truly useful run of show goes far beyond listing start and end times for each segment.

A comprehensive run of show includes: the exact time each segment begins and ends, the person or team responsible for each segment, the technical cues required (lighting changes, audio cues, video playback), the physical setup required (stage configuration, furniture placement, prop positioning), transition notes between segments, contingency instructions for common failure scenarios, and communication protocols for who needs to be notified when changes occur.

The document serves as a shared language between production, catering, entertainment, AV, stage management, and front-of-house teams. When built well, it eliminates the need for most day-of-event questions because the answers are already documented.

Timeline Structure and Pacing

One of the most common mistakes planners make is building timelines that are too tight. Every segment is scheduled back-to-back with no buffer. On paper, it looks efficient. In reality, it creates cascading delays.

Experienced planners build buffer time into every transition. A five-minute gap between a panel discussion and a keynote allows for microphone changes, stage resets, and audience movement. A ten-minute buffer before dinner service accounts for the time it takes guests to move from one space to another.

Pacing also matters emotionally. A run of show should have rhythm — high-energy moments followed by breathing room. Intense programming blocks followed by networking breaks. The pacing of an event affects how guests feel, and that pacing is designed in the run of show.

The best planners also think about what happens before and after the guest-facing program. Load-in schedules, sound checks, rehearsals, and strike plans are all part of the full run of show. An event does not begin when guests arrive — it begins when the first truck pulls up to the loading dock.

Communication with Production Teams

A run of show is only as good as its distribution. A beautifully detailed document that lives in one person's inbox is operationally useless.

Production teams need the run of show in advance — ideally at least 48 hours before the event — with clear instructions about which version is final. They also need to know who has authority to approve changes, because changes will happen. A speaker might request a different introduction. A sponsor might want their logo displayed during a different segment. The client might want to add a surprise moment.

Each change to the run of show must be communicated to every affected team simultaneously. When changes are communicated to the AV team but not the stage manager, or to the caterer but not the lighting designer, the result is confusion. This is why the week before a major event is so operationally intense — it is when the run of show transitions from draft to living document.

Common Mistakes Planners Make

Beyond overly tight timelines, several other mistakes undermine run-of-show effectiveness.

The first is building the document in isolation. When one person writes the run of show without input from production, AV, catering, and other teams, critical operational details get missed. The planner might schedule a champagne toast at 8:15 PM without realizing the bar team needs twenty minutes to pour and distribute glasses for three hundred guests.

The second is confusing the run of show with the guest-facing agenda. The agenda tells guests what they will experience. The run of show tells the team how to deliver that experience. These are different documents with different audiences.

The third is failing to include contingency notes. What happens if the keynote speaker runs ten minutes long? What happens if the AV system fails during a video presentation? What happens if dinner service is delayed? Experienced planners include if-then instructions for the most likely disruption scenarios.

The fourth is not assigning a single owner. Someone must have final authority over the run of show — typically the stage manager or lead producer. When multiple people can edit the document without coordination, version control becomes a problem, and conflicting instructions create operational risk.

A run of show is not paperwork. It is the operational backbone of the event. Treat it with the same seriousness you would give to a construction blueprint. Because on event day, that is exactly what it becomes.