Run Of Show Template

Why most production timelines fall apart

I built my first proper Run Of Show Template about eight years ago on a live music broadcast that had three network feeds, two backup cameras, and a weather delay protocol nobody had ever tested. The document I was handed by the previous producer was a single page that said "8:00 PM - show starts" and hoped for the best. We missed our first commercial block by eleven minutes and the host had to ad-lib through a segment that was supposed to air during a pre-taped intro. A run of show is just a timeline document that maps every second of a production against what should be happening on each channel, each department, and each piece of hardware. It is not a schedule. A schedule tells you when to show up. A run of show tells you what happens at 2:14 PM on camera three when the guest says something unexpected and the director needs to know whether to cut to a buffer or hold the live shot. Most people I see online are looking for a downloadable file they can open and fill in. That works until something goes wrong. The real value is in how you structure it before the first call time, not what you do at execution.

Run Of Show Template

Here is what a functional one actually looks like in practice. I keep mine in a shared spreadsheet format because version control matters more than anything else at 6 AM on call day. You have your master columns: timecode, segment title, video source, audio source, graphics overlay, talent position, and a notes column for anything that could go sideways. Timecode is always in 24-hour format and always includes a running clock from show start, not just wall clock time. If your show is two hours long and starts at 7 PM, the first entry is 0:00 and the last is 120:00. This eliminates the mental math that causes missed cues. Video source means exactly which camera or feed is active. Audio source means mic assignment or music bed status. Graphics overlay is anything from lower thirds to full-screen packages. Talent position is not just who is on screen, but where they are seated or standing and whether they need a stand-in during transitions. The notes column is where you put contingency information like "if red light stays on past 3:45, switch to camera 2 and page the floor manager." That column is the most important one on the sheet. I build my templates around a master row at the top that lists every hard stop in the production. These are non-negotiable moments: the national anthem, the sponsor read, the federal disclaimer, the closing theme. Everything else slots around those points. When I started doing this, I used to let producers fill in the gaps freely and then spend two hours trying to reconcile conflicting documents. Hard stops first, flexible segments second. It cuts the reconciliation time down to maybe ten minutes if everyone is decent about updating their section.

The part nobody talks about

There is a hidden column that most templates skip. I call it the trigger column. It is a single cell per row that states the exact condition that activates the next line item. Without it, people make assumptions about when segments should move forward. Assumptions are how you end up with a host reading a cue card while the engineer is still building the set for the next segment. For example, a trigger might read "after sponsor read completes AND floor manager confirms camera 1 is clear." That is a specific, observable condition. An engineer can verify it. A floor manager can report it. An assumption like "when the segment ends" is useless because different departments define segment end differently. I learned this the hard way during a political debate broadcast in 2019. The moderator was supposed to transition to the Q&A segment at 1:15:30 based on a soft agreement with the stage manager. The stage manager thought the soft agreement meant 1:17:00 because she was waiting on a network feed delay check. The moderator started the Q&A at 1:15:30 and the network feed had not yet cleared its buffer, so we got six seconds of pre-roll audio bleeding into the live shot. The trigger column would have made that impossible because the network feed clearance was an explicit prerequisite, not an implicit one.

Adding a trigger column adds about five minutes to template creation time but saves roughly forty-five minutes during rehearsal because there is no ambiguity about what needs to happen and when. That is not a metaphor. I tracked it over three months of live broadcasts and the average time saved per episode was 43 minutes of rehearsal discussion.

Common mistakes I see constantly

People put too much detail in the wrong columns and too little in the right ones. A typical mistake is writing a paragraph of context in the segment title column instead of keeping that context in the notes column. The segment title should be short enough to read at a glance from twenty feet away. If someone is reading your run of show from a booth across the room and has to stop to parse a sentence, the title is too long. Another mistake is using wall clock time for everything. Wall clock time changes when people arrive late, when equipment takes longer to set up, or when the day starts earlier than planned. Running clock time is relative to show start and never changes. If the show starts at 7 PM or 7:12 PM, the segment that is supposed to begin at 0:45:00 is still at 0:45:00. Everyone in the room uses the same reference point regardless of when they walked in. Someone will also build a template that is far too granular for the actual production scale. A local church broadcast does not need individual camera cues for every segment. A corporate webinar does not need a trigger column for every graphics overlay. I once saw a high school drama department use a run of show template designed for a network news broadcast and spend the entire performance arguing about whether the lighting board operator needed a separate line item or if it could go in the notes column. The template was fighting them instead of serving them.

What a Run Of Show Template cannot do

It cannot replace communication between departments. A beautifully formatted template that sits in a folder nobody checks is worse than a poorly formatted one that everyone references. I have seen producers spend three days building perfect templates and then never share them with the stage management team until call time. The template is worthless in that scenario because the people who need it most never saw it. It also cannot handle truly unscripted events well. If your production involves improvisation, live audience interaction, or breaking news, the run of show becomes a living document that needs a designated updater. Without that role, the document diverges from reality within the first fifteen minutes and nobody trusts it anymore. For those situations, I recommend keeping a skeleton run of show with only the hard stops and a separate whiteboard or shared doc for real-time updates. The template provides the structure. The whiteboard provides the flexibility. One more thing worth mentioning bluntly: a run of show template does not fix a bad rehearsal process. If your team has not run through the segments at least once in dress rehearsal, the most detailed template in the world will not prevent the same mistakes from happening live. I have produced events where the template was flawless and the rehearsal was terrible. The template was still useful for recovering from mistakes, but it did not prevent them. Rehearsal is where prevention happens. The template is where recovery happens.

Where to get a starting point

There is no universal template that works for every production type. A theater production needs different columns than a corporate event needs different columns than a sports broadcast. The structure I described above is a framework you adapt, not a file you download and hand off. If you need a starting file, Google Sheets and Microsoft Excel both have free run of show template options you can pull up and strip down to what you actually need. The key is removing everything you do not use rather than adding to a pre-made file. Pre-made templates tend to include columns for things you do not have, and those extra columns create noise that slows down decision making during a live event. I keep a master template in my Google Drive that I copy and modify for each project. It has the columns I described plus the trigger column, a department owner column for each row, and a status column that marks each segment as pending, in progress, complete, or skipped. The status column is what turns the document from a static plan into an active production tool. When a segment is complete, you mark it and the next trigger becomes visible as the active path forward. It sounds minor but it reduces confusion during multi-department productions significantly.