---
title: "Event Run of Show Template: Structure, Fields and Examples"
description: "A run of show template for B2B events — the columns that matter, worked examples for a conference, webinar and dinner, and the handoffs it has to cover."
canonical: "https://attendir.com/blog/event-run-of-show-template"
updated: "Sep 24, 2026"
---

# Event Run of Show Template: Structure, Fields and Examples

A run of show is the minute-by-minute schedule telling everyone working an event what happens, when, and who is responsible. A usable one has six columns — time, duration, segment, who is on, cue or action, and owner — and covers the day from doors open to load-out.

Most teams build one the night before in a panic, in whatever tool is open, and then discover during the event that the marketing moments are missing entirely. The agenda is in there. The AV cues are in there. The moment where you actually ask 300 people to share the event is not.

This guide covers the column structure that works, three worked examples you can copy for a conference session block, a webinar and an executive dinner, the handoffs a run of show has to make explicit, and the promotion beats most run of shows leave out.

## The Column Structure

Six columns cover nearly every event. More than that and people stop reading it on a phone backstage.

| Time | Duration | Segment | Who's On | Cue / Action | Owner |
|---|---|---|---|---|---|
| 08:30 | 30 min | Doors open, registration | Reg desk (3) | Walk-in music up, badge printers live | Ops |
| 09:00 | 10 min | Welcome + housekeeping | Host | Opening slide, wifi code on screen | Marketing |
| 09:10 | 35 min | Opening keynote | Speaker 1 | Lower thirds, record start | AV |
| 09:45 | 5 min | Transition | Host | Session 2 holding slide | AV |

**Time** is absolute clock time, not offsets. Offsets require arithmetic under pressure and people get it wrong.

**Duration** is there so the whole thing can be re-timed when something overruns, which it will.

**Segment** is what is happening, in plain language.

**Who's On** names people, not roles, wherever possible. "Host" is fine if there is one host all day; "Speaker" is not.

**Cue / Action** is what has to physically happen — a slide, a mic swap, a recording start, a door close, a push notification.

**Owner** is one named person per row. Not a team. One person.

## Worked Example: Conference Session Block

| Time | Duration | Segment | Who's On | Cue / Action | Owner |
|---|---|---|---|---|---|
| 13:00 | 15 min | Room reset from lunch | AV + venue | Chairs re-set, mics tested | Ops |
| 13:15 | 5 min | Audience settle | Host | Holding slide + countdown timer | AV |
| 13:20 | 3 min | Session intro | Host | Speaker bio slide, record start | AV |
| 13:23 | 30 min | Panel | 3 panellists + moderator | Handheld mics x4, lower thirds | AV |
| 13:53 | 10 min | Audience Q&A | Moderator | Roving mic, question queue on screen | Ops |
| 14:03 | 2 min | Close + share prompt | Host | Share QR slide up, shown for full 2 min | Marketing |
| 14:05 | 15 min | Break | — | Break music, recording stop | AV |

The row at 14:03 is the one most run of shows are missing, and it is covered in more detail below.

## Worked Example: Webinar

Virtual events need a tighter run of show, not a looser one, because there is no room to read.

| Time | Duration | Segment | Who's On | Cue / Action | Owner |
|---|---|---|---|---|---|
| T-30 | 15 min | Tech check, all presenters | All | Audio, video, screen share tested | Producer |
| T-15 | 15 min | Green room | All | Presenters muted, waiting room on | Producer |
| T-0 | 2 min | Open, housekeeping | Host | Recording start, chat opened | Producer |
| T+2 | 25 min | Main presentation | Speaker | Slides advanced by presenter | Speaker |
| T+27 | 15 min | Q&A | Host + Speaker | Q&A panel surfaced, chat moderated | Producer |
| T+42 | 3 min | CTA + next event | Host | CTA slide, link dropped in chat | Marketing |
| T+45 | — | Close | Host | Recording stop, follow-up email triggered | Marketing |

Use relative time (T-30, T+2) for webinars, because the same script gets reused across time zones.

## Worked Example: Executive Dinner

Small high-intent events need a run of show most of all, because the failure mode is social rather than technical.

| Time | Duration | Segment | Who's On | Cue / Action | Owner |
|---|---|---|---|---|---|
| 18:30 | 30 min | Arrival drinks | Host + 2 reps | Name badges, seating plan on display | Field Marketing |
| 19:00 | 10 min | Seated, welcome | Host | Phones-down request, round-the-table intros begin | Host |
| 19:10 | 20 min | Intros round table | All guests | 60 seconds each, host times it | Host |
| 19:30 | 45 min | Main course + guided discussion | Host | Question 1 of 3 introduced | Host |
| 20:15 | 30 min | Open discussion | All | Questions 2 and 3 as needed | Host |
| 20:45 | 5 min | Close + next step | Host | Follow-up offer stated once, clearly | Field Marketing |

The [executive roundtable and VIP dinner playbook](/blog/executive-roundtable-vip-dinner-playbook) covers the guest-list and discussion design that sits underneath this.

## The Handoffs a Run of Show Has to Make Explicit

A large share of event-day problems come from handoffs rather than from the schedule itself. Build these in as their own rows:

- **Mic handoffs** between speakers, especially panel-to-keynote.
- **Recording start and stop**, named as actions rather than assumed.
- **Slide deck ownership** — who is advancing, the presenter or the AV desk. Decide this once, in writing.
- **The moment a session becomes a break** and who announces it.
- **Who is watching the clock** and who has authority to cut a segment short.

That last one matters more than it sounds. If nobody has explicit authority to end an overrunning session, nobody will.

## The Promotion Beats Most Run of Shows Forget

A run of show is an operations document that also happens to be the only time your entire audience is in one place and paying attention. Marketing moments belong in it as timed rows with owners, not as good intentions.

The beats worth scheduling:

- **The share prompt at session close.** A QR code or short link on screen for a full two minutes, with the host saying one sentence about it. Not a logo in the corner of a slide.
- **The photo moment.** A backdrop or stage shot that attendees actually want to post, at a time when they are holding their phones anyway.
- **The next-event mention.** One line, once, from the stage.
- **The follow-up trigger.** The row that fires the post-event email sequence, so it goes out while the event is still live in memory.

The share prompt is worth being specific about because the economics are unusually good. Advocacy-driven registrations run in the $4–18 cost-per-registration range against $30–90+ for paid acquisition, and each share delivers roughly 50–150 impressions into a network that overlaps your audience closely. Programs that build the ask into the moment rather than hoping for it land in the 20–40% share-rate band. Snoball's published share-referred click-to-registration figure is 31.9%, which is why a scheduled thirty seconds on stage outperforms a great deal of paid promotion.

For the full post-event sequence that the last row triggers, see [post-event marketing](/blog/post-event-marketing).

## Building and Sharing the Document

Keep it in one place everyone can reach on a phone — a shared sheet is almost always better than a document, because the table structure survives small screens and the sort order stays intact. Print two copies for the front-of-house desk anyway; wifi fails.

Version it by date in the filename, lock editing to two people on event day, and put the on-site phone numbers of every owner at the top. The run of show is the only document anyone will open when something goes wrong, so the numbers belong there rather than in a separate contact sheet.

## Frequently Asked Questions

### What is a run of show?

A run of show is the minute-by-minute schedule for an event day, listing every segment with its start time, duration, who is on, the cue or action required, and a single named owner. It covers the full day from doors open to load-out and is the document the entire event team works from live, including AV, ops, hosts and marketing.

### What should a run of show template include?

Six columns cover nearly every event: absolute time, duration, segment name, who is on, the cue or action required, and one named owner per row. Beyond the agenda itself, include handoff rows for mic changes, recording start and stop, slide ownership, and the marketing moments such as the on-stage share prompt and the follow-up email trigger.

### What is the difference between a run of show and an agenda?

An agenda is the attendee-facing schedule of sessions and breaks. A run of show is the internal operational script, which includes everything the agenda hides: room resets, tech checks, mic handoffs, recording cues, holding slides and who has authority to cut a session short. The agenda is usually a subset of the run of show.

### Who owns the run of show?

One person should own the document itself, usually whoever is running event operations, with editing locked to two people on the day. Each individual row then has its own named owner. Shared ownership of the whole document is the most common cause of two conflicting versions circulating on event morning.

### Should a webinar have a run of show?

Yes, and a tighter one than an in-person event, because there is no room to improvise and no visual cues between team members. Use relative times such as T-30 and T+2 rather than clock times so the same script can be reused across time zones, and include the pre-event tech check and green room as numbered rows.

A run of show is where an event program's discipline becomes visible, and it is the cheapest place to add the promotion beats most events leave on the table. To see what the sharing half of that is worth, start with the [event sharing benchmark](/event-sharing-benchmark).