Free Run of Show Template (CSV, PDF & AFFiNE)

Free run of show template with a filled 90-minute hybrid workshop example, producer and chat cues, a cut list, and blank and filled CSV and PDF sheets.

AFFiNE Workshop & Event Run-of-Show template showing a logistics header, preparation checklist, and minute-by-minute agenda table with time, duration, segment, speaker, and tech notes columns

A run of show is the minute-by-minute script that the host, speakers and crew follow during an event. Each row gives a start time, a duration, a segment, an owner and a cue. This page gives you the AFFiNE run of show template, a filled 90-minute hybrid workshop example, and blank and filled sheets as CSV and A4 PDF.

What is a run of show?

A run of show (often shortened to ROS) is an internal production document. An agenda tells attendees what will happen. The run of show tells the team exactly when each segment starts, who owns it, what has to happen technically, and what to do if it slips. Everyone working the event reads from the same version.

What the AFFiNE template includes. The Use this template button copies a one-page AFFiNE document with:

  • A logistics header with quote blocks for Location, Resources Folder and Emergency Contact.
  • A Preparation Checklist (-30 Mins) with to-dos for checking audio and video inputs, verifying screen-sharing permissions, opening slide decks with notifications paused, and starting the recording.
  • A Minute-by-Minute Agenda table with five columns: Time (Start-End), Duration, Activity / Segment, Speaker and Tech / Notes. The sample rows run from 09:00 to 10:00: Welcome & Housekeeping (5 min), Keynote Presentation (15 min), Interactive Workshop (30 min), Q&A / Buffer Time (10 min) and Event Close at 10:00.
  • Scripting & Facilitation Notes with an Internal Instruction and a Spoken Script for the welcome and for the hand-off to the collaborative whiteboard.
  • A Post-Event Debrief with prompts for what went well, what had technical issues, and follow-up action items.

The 90-minute example, the CSV sheets and the PDFs below were made for this page. They are separate downloads, not part of the AFFiNE template.

Run of show vs agenda vs cue sheet

AgendaRun of showCue sheet
Who reads itAttendeesHost, speakers, producer and crewTechnical operators (sound, video, stream)
Level of detailTopics and rough timesExact start times, durations, owners, cues and fallbacksOne numbered line per technical action
Typical contentSession titles, speakers, breaksEverything in the agenda plus cues, locations and contingenciesCue number, trigger, action, operator
When it is usedShared before the eventRehearsal and the live eventLive, by the people running the equipment

For a small workshop, the run of show usually carries the cues itself, so a separate cue sheet is not needed. Larger productions often give each operator their own cue sheet. If you only need to tell people what a recurring meeting covers, the weekly team meeting agenda template is lighter. If you are attending a conference rather than running a session, plan your day with the conference itinerary template instead.

What each column means

The downloadable sheet uses seven columns (the CSV splits Time into Start and End). Five map to the AFFiNE table: Time, Duration and Segment keep their meaning, Speaker becomes Owner, and Tech / Notes becomes Cue. Location and Contingency are added for hybrid events. You can add the same two columns to the table in your AFFiNE copy.

  • Time: start and end in the venue's local time, such as 13:20–13:50. Each start must equal the previous row's end.
  • Duration: minutes for the segment. Write durations first and work out the times from them.
  • Segment: a short name everyone recognizes, such as "Group readouts".
  • Owner: the one person responsible for the segment starting and ending on time. If two people share a row, name the one who makes the call.
  • Cue: the exact actions at the start of the row and who triggers them, such as "Producer spotlights Kwame" or "Post the whiteboard link in chat".
  • Location: where the segment happens. For hybrid events, write both the room and the online space, such as "Room B tables + Zoom breakouts".
  • Contingency: what to do if the segment fails or overruns, decided in advance so nobody has to improvise live.

Filled example: a 90-minute hybrid workshop (13:00–14:30)

Illustrative example: Fernhill Software, its people, rooms and links are fictional. The Q3 Product Strategy Workshop runs in Room B with remote attendees on Zoom, from 13:00 to 14:30 local time on Thursday, November 12, 2026. Roles: Nadia Haddad (host, keeps time and makes cut calls), Marcus Lindqvist (producer), Ines Carvalho (facilitator), Kwame Mensah (speaker) and Ana Ruiz (room lead and emergency contact).

Illustrative run of show for a fictional 90-minute hybrid workshop from 13:00 to 14:30, listing seven segments with durations, owners and producer cues, with the 10-minute Q&A buffer highlighted.
The filled run of show. Every start time equals the previous row's end time.
TimeMinSegmentOwnerCueLocationContingency
13:00–13:055Welcome and housekeepingNadia (host)Title slide. Producer starts recording and posts the welcome message in chat.Room B stage + ZoomIf under half the room has joined, start at 13:03 and keep housekeeping to 2 minutes.
13:05–13:2015Context talk: what changes in Q3Kwame (speaker)Slides 2-9. Producer spotlights Kwame.Room B stage + ZoomOver by 3 min: skip slides 7-9 (appendix).
13:20–13:5030Breakout exercise: map customer pain pointsInes (facilitator)Producer opens 4 Zoom breakout rooms and posts the whiteboard link. Room lead hands out prompts to 2 tables.Room B tables + Zoom breakoutsIf breakouts fail, run one shared whiteboard in the main room.
13:50–14:0515Group readoutsInes (facilitator)Producer sends a 60-second warning, then closes breakouts. Room lead passes the handheld mic.Room B + Zoom main roomHear 3 of 6 groups live; the rest post a summary in chat.
14:05–14:1510Decisions and next stepsNadia (host)Slide 10. Scribe types actions into the shared notes page.Room B stage + ZoomDo not cut. Park open questions for the follow-up email.
14:15–14:2510Q&A / bufferNadia (host)Producer reads the top chat questions; room lead brings the mic.Room B + ZoomThis row absorbs delay. Shorten or drop it first.
14:25–14:305Close and surveyNadia (host)Producer posts the survey link, then stops recording at 14:30.Room B stage + ZoomDo not cut. The survey link also goes in the follow-up email.

Check: the seven durations add up to 90 minutes (5 + 15 + 30 + 15 + 10 + 10 + 5), exactly the booked slot. The 10-minute Q&A / buffer row is 11% of the slot.

Preparation checklist, 30 minutes before:

  • 12:30: Room lead checks the room mic, camera and display.
  • 12:35: Host opens Zoom and makes the producer a co-host.
  • 12:40: Producer sets up 4 breakout rooms and tests screen share.
  • 12:45: Facilitator opens the whiteboard and prints table prompts.
  • 12:50: Speaker runs slides 2-9 with notifications paused.
  • 12:55: Holding slide on screen; producer admits early arrivals.

How to plan a run of show backward from the end time

Start from the time you must finish, not the time you start. The end is usually fixed by the room booking, the next meeting or people's calendars, while the start is the part that slips.

  1. Fix the hard end. In the example, the room and the remote attendees' calendars end at 14:30.
  2. Reserve the close. Put the close and survey at 14:25–14:30 so it happens even on a bad day.
  3. Place the buffer just before the close. The example holds 10 minutes at 14:15–14:25 as Q&A that can shrink. A planning rule of thumb is to hold back 10 to 15% of the slot, which is 9 to 14 minutes in a 90-minute session. This is a working habit, not a researched figure, so add more for live demos, several speakers or a platform the team has not used before.
  4. Place the segments you cannot drop. Decisions and next steps sit at 14:05–14:15, so they come before anything that might be cut.
  5. Fit the flexible segments into what is left. That leaves 65 minutes for the welcome (5), the context talk (15), the exercise (30) and the readouts (15).
  6. Write start times last and check them. Each start must equal the previous end, and the durations must add up to the booked slot.
  7. Mark what can shrink. For each flexible row, note in Contingency how many minutes it can give back. Those notes become your cut list.

Virtual and hybrid version: producer and chat cues

Online and hybrid sessions need a second pair of hands. The producer runs the platform so the host can watch the room and the clock: recording, spotlighting speakers, opening and closing breakout rooms, and posting links in chat. In the AFFiNE template, put these actions in the Tech / Notes column and add a producer line to the Preparation Checklist.

If you run the session on Zoom, give the producer co-host rights. By default only the host or a co-host can assign participants to breakout rooms and spotlight a video. The host has to promote a co-host during the meeting; Zoom's role guide notes that co-hosts cannot be assigned ahead of time. That is why the example's checklist has the host making the producer a co-host at 12:35.

Write chat messages in advance so the producer can paste them without typing under pressure:

TimeProducer actionChat message
12:55Share the holding slide; admit early arrivalsNone
13:00Start recording; post the welcome message"Welcome! Mics are muted. Questions go in chat and we will take them at 14:15."
13:05Spotlight the speakerNone
13:20Open 4 breakout rooms; post the whiteboard link"Breakouts are open. Board: [whiteboard link]. Add notes in your group's frame."
13:49Send the 60-second warning to all roomsNone
13:50Close breakouts; spotlight the facilitatorNone
14:15Read the top chat questions to the host"Q&A is open. Upvote a question by replying +1."
14:25Post the survey link"Two-minute survey: [survey link]. Thank you for joining."
14:30Stop recordingNone

For a hybrid room, also repeat questions from the room into the mic so remote attendees can hear them, and give the room tables the same time warnings as the breakout rooms.

What to cut when you run late

Decide the cut order before the event and give one person, usually the host, the authority to call it. Cut from the most flexible row first and protect the rows that produce the outcome.

OrderCutSavesRunning total
1Shorten or drop Q&A / buffer (14:15–14:25)10 min10 min
2End the breakout exercise at 13:45 instead of 13:505 min15 min
3Hear 3 of 6 groups live; the rest post in chat7 min22 min
4Skip context slides 7-9 (appendix)3 min25 min

Never cut: decisions and next steps, the close and survey, and stopping the recording.

Illustrative cut list for the fictional 90-minute workshop, showing four cuts in order that recover 10, 5, 7 and 3 minutes, plus three items never to cut.
The cut list recovers up to 25 minutes without touching the decisions or the close.

If the workshop starts 10 minutes late, step 1 alone recovers the time. If a technical problem costs 20 minutes, steps 1 to 3 recover 22. A cut list cannot rescue a plan that is too long by design: if a realistic delay is more than the list can absorb, shorten the plan before the event.

Download the run of show template

  • Blank run of show CSV: a header row (Start, End, Duration (min), Segment, Owner, Cue, Location, Contingency) and 10 empty rows. It opens in Excel, Google Sheets or Numbers.
  • Filled run of show CSV: the seven rows of the 90-minute example.
  • Blank run of show PDF: two A4 landscape pages. Page 1 is the timed table with 10 rows; page 2 has roles, the 30-minute preparation checklist, a producer cue lane, a cut list and a debrief.
  • Filled run of show PDF: the same two pages completed with the example.

The PDFs are for printing and are not fillable forms. Use this template and Preview open the AFFiNE template described above, with its five-column table and 09:00–10:00 sample. The downloads do not update or sync with that AFFiNE page.

For more agenda formats, read the guide to agenda templates or browse all agenda templates.

FAQ

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

An agenda tells attendees what is covered and roughly when. A run of show is the internal version for the team: exact start times, durations, one owner per segment, technical cues and fallbacks. Attendees rarely see it.

What should a run of show include?

At minimum: start and end time, duration, segment, owner and cue for each row. For hybrid or multi-room events, add location and contingency. The AFFiNE template also includes a logistics header, a 30-minute preparation checklist, host scripts and a debrief.

How much buffer should a run of show have?

There is no standard figure. A common planning rule of thumb is 10 to 15% of the slot, placed just before the close; the example uses 10 minutes in 90. Add more for live demos, several speakers or a platform the team has not used before.

Who owns the run of show on the day?

One person, usually the host or an event lead, keeps the master copy, watches the clock and makes cut calls. Everyone else works from that version, so changes go through that person. In the example, Nadia Haddad has this role.

Can I use the run of show template for a virtual or hybrid event?

Yes. The AFFiNE template's checklist already covers screen-sharing permissions and recording, and the Location field accepts a meeting link. For hybrid events, add a producer, pre-written chat messages and a Location column, as in the example above.

Get more things done, your creativity isn't monotone