Run of Show Template: Free Copy-Paste Grid + Guide (2026)

This is an independent guide to event planning. It is not affiliated with or endorsed by any event-software vendor mentioned.

Ten minutes into the summit, the keynote speaker was still talking, the panel guests were already waiting backstage, and the person running the stream had no idea what came next. Nobody had built a run of show. So the whole thing quietly slid off schedule, and 40 minutes later the closing session got cut to five minutes.

A run of show is the minute-by-minute script your production team follows so that never happens. It lists every segment, who owns it, and which tech cue fires when. Miss it, and a live event turns into improv.

This guide hands you a free run of show template you can copy, paste, or download right now. Then it explains what a run of show actually is, how it differs from an agenda, and the six steps to build one. You'll also get a filled-in example for a virtual event, so you can see exactly how the grid looks once it's populated. No fluff, no sign-up wall.

Here's the promise. By the time you finish reading, you'll have a working document in the tool you already use, plus a clear sense of what belongs in it and what to leave out. You'll know how a run of show talks to a caller, how buffer time saves a closing session, and why one named owner per row beats a shared to-do list every time. If you host webinars, conferences, or hybrid team days, this is the one page that keeps them on the rails.

Free run of show template (copy, paste, or download)

Here's the grid. A run of show template is a table with one row per segment and six columns: clock time, running time, segment, owner, tech or AV cue, and notes. Copy it into your tool of choice, then fill each row from the top of your event to the last handshake.

Blank rows are your friend. Add one wherever a handoff happens, and give every transition its own line so nothing gets lost in the gaps between segments.

Why these six columns and not more? Each one answers a question your crew will ask under pressure. Clock time answers "is this starting now?" Running time answers "how much room do I have?" Segment and owner answer "what is this and who's driving?" The tech cue answers "what do I press?" The notes column catches the one detail that doesn't fit anywhere else, like a speaker who wants no applause or a video that needs its sound checked twice. Drop a column and you've quietly reintroduced a guess.

Read the grid top to bottom before you touch it. Notice how the running times stack up to a real finish time, and how every gap between talking segments has a named owner. That habit, more than any template, is what keeps a show honest.

Think of it as the script behind the curtain. While the audience sees a smooth event, the crew is reading down the run of show, hitting each cue on time. It's built for the people running the show, not the people watching it.

Is a run of show the same as a rundown? Basically, yes. A run of show is also called a rundown, a cue sheet, or a show flow, depending on the industry. Broadcast and theater teams tend to say "rundown" or "cue sheet." Event and conference organizers usually say "run of show." They all describe the same thing: the ordered, timed list of what happens and who makes it happen.

And the plural? "Runs of show." You rarely need it, since one event has one run of show, but that's the form if you're comparing several.

What is a run of show used for? It's used to run a live event cue by cue. A stage manager reads it aloud, a producer follows it in a control room, an event host keeps it open on a second screen. The document exists so the person calling the show never has to stop and think "what now?" It turns a day of moving parts into a single line you can point at.

One more distinction worth making early. A run of show is not a checklist and it's not a project plan. A checklist is unordered and untimed. A project plan spans weeks. A run of show is a timeline for the hours the event is actually live, and every row is anchored to the clock. If a row on your document has no time on it, it belongs somewhere else.

What should a run of show include? Key components

A run of show should include seven things: event details, a clock, a running time, a description of each segment, an owner, tech cues, and buffer time. Skip any one of them and the document stops being reliable under pressure. Here's what each part does, and why it earns its place.

• Event header. Name, date, venue or link, and the version number. On show day you want zero doubt about which document is current.
• Clock time and running time. The clock tells the crew when a segment starts. The running time tells them how long it lasts. Together they catch overruns the moment they happen.
• Segment description. One clear line per block: keynote, panel, break, awards. Specific enough that a stand-in could read it and know what's happening.
• Owner. One named person per row. Not "the team," not "AV." A single human who's accountable for that segment starting and ending on time.
• Tech and AV cues. Mics live, slides up, music in, lights down, camera switch. Every action the technical crew has to take, written where it happens.
• Buffer time. Deliberate empty minutes between segments for transitions, tech resets, and the inevitable overrun. A run of show with no buffer is a wish, not a plan.
• Setup and teardown. The rows before doors open and after the audience leaves. Load-in, sound check, and breakdown belong in the document too.

Bigger events add a few extras, but resist the urge to bolt on columns nobody reads. A sponsor or VIP note can live in the notes field. A contingency line ("if the stream drops, cut to holding slide") can sit as its own row right after the segment it protects. Contact numbers for the AV vendor and the venue go in the header, not scattered across rows. The test for any addition is simple: will the caller actually glance at it while the clock is running? If not, it belongs in a separate brief.

The clock-plus-running-time pair is the part people get wrong most. Clock time is absolute ("9:15"). Running time is a duration ("0:30"). You need both because they fail in different ways. If a speaker runs long, the clock keeps ticking while your remaining running times still say what each block should take, so you can see the deficit at a glance and decide what to trim.

Run of show vs. agenda: what's the difference?

A run of show is the operational script for your crew; an agenda is the public schedule for your audience. The agenda tells guests what to expect and roughly when. The run of show tells the team exactly what to do, minute by minute, including every cue the audience never sees. One is marketing, the other is operations.

Here's how the run of show sits next to the two documents people confuse it with:

The agenda answers "what will I see?" The production schedule answers "what happens across the whole build?" The run of show answers "what do we do, right now, in this minute?" You often need all three, and they should never contradict each other. If you want your public sessions to land as well as your backstage timing, it's worth learning how to run more engaging meetings alongside a tight rundown.

A quick way to feel the difference: hand your agenda to an attendee and they know when to grab coffee. Hand your run of show to a first-time crew member and they could call the show cold, because every cue and every owner is spelled out. The agenda hides the machinery on purpose. The run of show is the machinery.

They also update on different clocks. The agenda gets locked early because you print it, email it, and put it on the website. The run of show stays live until the last rehearsal, because that's when you discover the keynote really needs 27 minutes, not 25. Keep them in sync on the segment titles and start times your audience sees, and let the run of show carry all the extra detail underneath. Your run of show is a close cousin of a meeting agenda template, just with owners and cues bolted on and the clock treated as law.

Run of show template: Word, Excel, Google Sheets, or PDF?

Pick the format by how your crew will read it on show day, not by what you drafted it in. A run of show template in Excel or Google Sheets lets the running times auto-calculate, and you can sort or recolor rows quickly. A run of show template in Word or Google Docs reads more like a script, which suits a talk-heavy event where the cues sit beside the words. A PDF is the version you actually run from, because it can't be edited by accident.

• Google Sheets: suits a shared master a small team edits together in real time. Freeze the header row, and set the Time column to a time format so it sorts correctly.
• Excel: works offline with the same auto-calculation, plus a formula that adds each running time to the previous clock time so the schedule recalculates when one block moves.
• Word or Google Docs: fits when the run of show doubles as the emcee's script and the cues sit as short notes beside the words.
• PDF: the show-day copy. Export from any of the above so the crew opens a clean, read-only file on a phone or tablet.

Whatever you draft in, keep one editable master and one exported PDF. The master is where changes happen up to the final rehearsal. The PDF is what the caller reads once the clock is live, so a mid-show typo can never rewrite the plan.

Can you make a run of show in Canva or a slide tool? You can, and it will give you a print-ready layout with full control over fonts and spacing. Just know that a design tool is not a spreadsheet: it won't auto-recalculate your clock times when one block moves, and its tables are edited by hand rather than by formula. Some users find that editing tables there gets fiddly. As one r/canva user put it, working with a Canva table can be 'super frustrating— 7 times out of 10 it jumps before I can even start editing. Makes working with tables almost impossible' (source). A design tool is a fine home for the audience-facing agenda; for the run of show itself, a table you can edit in seconds is the safer bet.

Run of show example for a virtual event

Here's a filled-in run of show for a 90-minute virtual summit. It shows how the same six columns work when your "venue" is online: your cues become room switches, screen shares, and activity launches instead of stage lights. Every in-person cue has a digital equivalent.

Picture Nadia, an ops lead hosting a remote-team summit for 120 people across three time zones. She's running it in a spatial venue where guests move between rooms as avatars, so her run of show tracks which room the crowd is in at every moment. This is what her grid looks like once it's populated:

Notice the buffer at 0:38 and the hard cue to move rooms at 0:10. Those are the two things virtual events botch most: overruns with no cushion, and a fuzzy handoff where half the crowd is still in the lobby while the keynote starts. A run of show fixes both by naming an owner for the move and building slack into the clock. If you're new to running one online, start with the basics of how to host a virtual event, then layer this grid on top.

If networking is the point of your event, pair this grid with a plan for the mingling itself; here's how to host a virtual networking event that people actually enjoy. And for the keynote block, the same discipline that powers a great virtual conference applies: one owner, one clean screen-share cue, one hard stop.

Contrast that with a smaller, meeting-sized run of show. Picture Devon, a team lead running a 30-minute all-hands for a distributed squad. His grid has five rows, not seven, and the "cues" are humble: unmute the deck, share the roadmap slide, drop the survey link in chat, open the floor. He still assigns one owner per row, because even a short meeting drifts when "someone" is supposed to launch the poll and nobody does. The document is smaller, the discipline is identical.

The takeaway from both scenarios is the same. Scale the number of rows to the event, but never scale down the two rules that carry the whole thing: one named owner per row, and real buffer where the handoffs live. A 90-minute summit and a 30-minute standup fail for the exact same reasons when those two rules slip.

Common run of show mistakes to avoid

Most run of show failures come down to six habits, and every one of them is avoidable. Watch for these before your next event.

• Underestimating transitions. The gap between segments is where time vanishes. Guests move slowly, tech takes a beat to reset, and a "quick" changeover eats three minutes. Give every handoff its own timed row.
• Building it too late. A run of show written the night before is untested. Draft it a week out so you have time to rehearse and fix what breaks.
• Ignoring AV reality. A cue that says "play video" assumes the video is loaded, the audio is routed, and someone is watching for it. Write cues for what the crew actually has to do, not what you wish would happen.
• Skipping the rehearsal. Reading the document silently is not rehearsing. Run it out loud, time it, and you'll find the segment that's secretly 10 minutes too long.
• Over-complicating it. A run of show crammed with color codes and 12 columns is one nobody reads under pressure. Keep it to the six columns that matter.
• No caller. Someone has to read the cues live and say "go." Without a single caller keeping time, even a perfect document drifts. Name that person on page one.

The caller deserves its own paragraph, because it's the mistake that undoes everything else. You can write a flawless run of show and still lose the timing if three people are half-watching the clock and each assumes another has it. Appoint one caller. Their only job is to read down the document, watch the running times, and say the next cue out loud. On a virtual event that voice lives in a backstage channel; in a room it's a headset. Either way, one person owns "go," and everyone else listens for it.

A tight run of show keeps the timing honest, but it won't fill dead air on its own. Pair it with a few tactics to keep a virtual audience engaged so the energy holds between segments, not just the schedule.

Run your next event from one run of show

Take the grid at the top, fill it with your own timings, and you have the one document that decides whether your event feels controlled or chaotic. A run of show earns its keep in the moments the audience never sees: the clean handoff, the absorbed overrun, the cue that fires on time because a real person owned it.

Three things to carry with you. First, one named owner per row, with no exceptions and no "the team." Second, real buffer where the handoffs live, because transitions steal more time than any single speaker. Third, one caller reading the document out loud, so the plan on the page becomes the plan in the room.

Do those three and the template does the rest. Rehearse it once, lock the version, and open it on show day. Then run your event from a single run of show instead of from memory and hope.

"Run of show," "rundown," and "cue sheet" are general event-production terms and are not trademarks of this site. Product names mentioned in passing belong to their respective owners; this site is independent and not affiliated with them.