Run of Show Template for Conferences

TL;DR

• A run of show template is a minute-by-minute grid that maps every moment of your event: what happens, when, who does it, and what the crew need to cue.
• The six columns that earn their place are time, item, who, cue, tech and notes. Anything else is clutter.
• An example run of show table for a full conference day sits further down, ready to copy and adapt.
• The document is only half the job. A host uses it live to protect the clock, warn the crew early and absorb the overruns nobody planned for.
• Build it once, share it with everyone on headset, and the day stops feeling like a series of near misses.

A run of show template is the one document that keeps a conference on time when a hundred small things try to pull it apart. I have hosted more than 800 events, and the ones that run smoothly are never the lucky ones. They are the ones where the show template was clear, everyone on headset was reading the same grid, and the host knew the running order cold. This guide covers what a run of show is, the columns it actually needs, a worked example for a conference day, and how a host uses it in the room.

If you organise events, you already know the feeling of a schedule that lives in three different heads and one out-of-date email. This replaces that.

What is a run of show template?

A run of show template is a structured, minute-by-minute plan of an event, laid out as a table so the whole team can follow it live. It is the operational script for the day: not the content of the talks, but the choreography around them.

Think of it as the difference between a guest list and a floor plan. The agenda tells delegates what sessions exist. The run of show tells the host, the AV crew, the stage manager and the client exactly what happens at 09:02, who is speaking, what needs to be on screen, and who moves next. It is sometimes called a show flow or a cue sheet, and the principle is the same.

One shared version is the whole point. When the host, the sound desk and the organiser are all reading the same show template, a missed cue becomes a glance at a shared line rather than a whispered argument at the side of stage.

What columns does a run of show template need?

A run of show template needs six columns and no more: time, item, who, cue, tech, and notes. Each one answers a different question the room will ask under pressure.

• Time. The clock time each item starts, not the duration. Durations hide slippage; clock times expose it instantly.
• Item. A short label for what is happening. “Welcome and housekeeping”, “Keynote”, “Panel”, “Break”, “Awards”.
• Who. The named person on stage or on mic. Full name and, for introductions, the exact title and organisation.
• Cue. The trigger that starts the item and who calls it. “Host cues VT”, “Stage manager sends walk-on music”.
• Tech. What the AV crew need ready: slide deck loaded, lower-third name graphic, lectern mic live, house lights down.
• Notes. The catch-all for anything odd: a sponsor mention, a presentation clicker handover, a speaker who must leave early for a train.

Resist adding more columns. A grid that spills off the page is a grid nobody reads at 08:55. If a detail does not change what someone does in the next few minutes, it belongs in a separate brief, not the run of show.

Example run of show table for a conference day

Here is a worked example run of show table for a single-stage conference morning. Adapt the times and items to your agenda, but keep the six columns.

Notice how the cue and tech columns do the quiet work. By the time the panel starts at 10:45, the crew already know four lapel mics are needed, and the host has flagged in the notes to confirm the mic order during the break. Nothing is a surprise.

Name the Q&A tool in the tech column so the crew know what goes on screen. When I am hosting, that line reads RoomReader, my own live question software: it comes with the booking, runs in the delegates’ phone browsers, and there is nothing to download.

How does a host use the run of show live?

A host uses the run of show as a live control panel, not a document to admire beforehand. On the day, one copy sits on the lectern and a second sits with the stage manager, and both work from the same lines.

The clock column is where the real judgement happens. The energy in a room is a curve, and so is the schedule: things slip, speakers overrun, a demo takes longer than promised. A good host reads the current time against the run of show constantly and starts clawing back minutes early, trimming their own links and tightening a Q&A, long before the afternoon is in trouble.

The cue column tells the host what to trigger and when, so a handover to a video or a walk-on never lands on dead air. The tech column lets the host warn the crew ahead of a change rather than after it. And the notes column is where the day’s landmines live: the speaker leaving early, the sponsor mention that must not be dropped, the hard out on a segment.

Used this way, the run of show turns a host from a nervous presenter into the calm person the whole room relies on. It is also the backbone of a strong start, which is worth planning as carefully as you open the conference.

Who owns the run of show on the day?

The host and the stage manager jointly own the run of show once the doors open, with the organiser as the single source of changes. Before the day, the organiser builds and circulates it. On the day, control passes to the people running the room.

That handover matters. If three people can edit the schedule mid-morning, you get three versions and a confused crew. Agree in advance that any change goes through one person, is spoken over headset, and is marked on the master copy. Everyone else adjusts to that single line.

This is also why a run of show is worth building even for a small internal event. It forces the awkward questions early: who introduces the CEO, how long is the demo really, what happens if the keynote runs late. Answer those on paper and the room feels effortless.

Common run of show mistakes to avoid

The most common run of show mistakes are writing durations instead of clock times, burying the cues, and never sharing the final version. Each one quietly breaks the day.

Durations force everyone to do mental arithmetic while a session overruns, which is exactly when nobody has spare attention. Clock times show slippage at a glance. Vague cues (“start panel”) leave the crew guessing who triggers what. And a run of show that only the organiser has seen is worthless the moment they step out to deal with a catering problem.

Build it clearly, keep it to six columns, and get it into the hands of everyone on headset. When you want the whole day run by someone who works from a grid like this, you can check availability and send the agenda across.