The run of show is the document that changes most, and every timing shift means re-cutting the schedule and then re-cutting the call sheets that depend on it. The details it needs already live in your agenda and your vendor list; the manual work is assembling them into a minute-by-minute plan and keeping every copy current. This guide covers what a run of show template includes, how to structure one you can reuse, and where AI can build and maintain it.

It's one workflow from our guide to AI for corporate event planning.

What a run of show is and what it includes

A run of show is the minute-by-minute schedule of an event: what happens, when, and who is responsible for making it happen. It's the document the whole team runs on during the event itself, from the stage manager to the AV lead to the caterer.

A complete one usually tracks, for each moment:

• Time and duration — start, end, and how long the segment runs.
• What happens — the segment, the speaker, the transition.
• Cues — lighting, sound, video, stage changes.
• Who owns it — the person responsible, on-site.
• Notes — the detail that isn't obvious from the line above.

The difference between a run of show and a public agenda is the cue and ownership columns. The agenda tells attendees what to expect. The run of show tells your team exactly what to do and when — which is why it changes far more often, and why a shift in one segment ripples through every downstream time.

Building a run of show template you can reuse

A good template is the same structure applied to every event, so your team reads it the same way each time. Building it once and reusing it removes the "where's the AV cue column this time" friction that comes from rebuilding the document per event.

The reusable version fixes the columns and the section breaks — pre-show, doors, program, transitions, close, load-out — and leaves the content blank. For each event you fill it from the agenda. A run of show template does this well until something moves; then the limitation shows, because a static table doesn't recalculate the times below the change, and it certainly doesn't update the separate call sheets you cut from it.

Using AI to build and sync your run of show

This is where AI earns its place, because the run of show is mostly derived from documents you already have. Give it the agenda, the speaker list and the vendor contacts, and it can draft the full run of show into your template — segments placed on the timeline, owners assigned, obvious cues filled in. You refine the judgment calls; you don't build the grid from scratch.

The ongoing value is in the syncing:

• Recut the timeline when something moves. The keynote runs ten minutes long, or a sponsor slot is added. AI redraws every downstream time and flags any hard constraint it now breaks — the hard stop on the venue, the catering service window.
• Generate the call sheets. From one run of show, each role needs its own view: the AV lead's cue sheet, the stage manager's cues, the caterer's service times. AI can cut those per-role sheets and re-cut them when the master changes, so the versions don't drift.
• Distribute the current version. When the run of show updates the day before, the drafted note to the team goes out with what changed highlighted, for you to send.

What stays human is every real-time decision on the day. A run of show is a plan, and events don't follow plans exactly; the call to hold the doors or cut a segment is the stage manager's, live. AI keeps the document accurate up to the moment the event starts. For coordination that continues live and across systems, our guide to AI for corporate event planning covers more.

If you re-cut the same schedule and call sheets by hand every time a time moves, talk to us. The document this feeds off is your event planning checklist, which AI can build the same way.