Build a Run of Show
Builds a minute-by-minute run of show with owners, cues, AV notes, a cut list and contingencies for keynotes, field events, dinners and booth sessions, and checks the timing math.
- Trade shows & field
- intermediate
- CSV
- Google Sheets
- Slack
Example prompts
Once the skill is added, start a chat with one of these and attach your file if you have one.
Build a run of show for our 90-minute keynote: 3 speakers, a customer panel and a product demo.
Turn this agenda into a minute-by-minute run of show for the field event with owners.
Add contingencies: speaker late, demo fails, Wi-Fi drops.
What this skill does
This skill turns a rough agenda into a run of show your producer, AV crew, speakers and event lead can all work from. It breaks the agenda into segments, adds the transitions people forget (walk-ups, mic swaps, panel sets, video rolls) and gives every row an owner, a cue, audio, video and lighting notes.
It then checks the timing: every start time follows from the one before, the show ends before the hard stop, and there's a buffer. You also get a cut list for when things run long, a contingency plan with who decides what, a crew contact sheet and an asset list of decks, videos and music.
When to use it
- You're producing a keynote, general session or user conference opening
- You need a day-of schedule for a field event, dinner or booth theater
- Your agenda lives in an old spreadsheet and the times no longer add up
- You want a contingency plan for late speakers, failed demos and Wi-Fi drops
- The AV crew asked for a cue sheet
How it works
- 1IntakeAsks once for the event format, room, time zone, hard end, agenda, AV setup and who's on the crew.
- 2Segments and transitionsBreaks the agenda into rows, adding the hand-offs and resets that eat time on show day.
- 3Cues and ownersGives every row a named owner, a spoken cue, and audio, video, slides and lighting notes.
- 4Timing checkRecomputes start and end times, flags gaps and overlaps, and reports buffer or overrun against the hard end.
- 5Contingencies and crewAdds a cut list, a contingency plan with decision owners, a crew contact sheet and an asset list.
What you'll need
- Agenda with segments, speakers and rough lengths
- Venue, room, time zone, doors time and hard end
- AV setup: mics, screens, playback, streaming
- Crew roles and how they communicate
What you get
A run-of-show table with start, end, duration, segment, who's on stage, owner, cue, audio, video and slides, lighting and notes, under a header with call times, doors, start, hard end and buffer. It comes with an ordered cut list, a contingency table (risk, trigger, who decides, action, host line), a crew contact sheet and an asset list, as Markdown and CSV.
Tips
- Work backward from the hard end, like a venue curfew or the next session, not forward from the start.
- Give every transition its own row; walk-ups and panel sets add up fast.
- Name one person who decides when things go wrong, so the crew isn't waiting on a group.
- Agree time cards with speakers before the show and pick two or three checkpoints to use the cut list.
- Keep a recorded backup of any live demo ready on a second machine.
What's in the download
event-run-of-show/SKILL.md6.1 KBevent-run-of-show/assets/sample-agenda.csv893 Bevent-run-of-show/references/contingencies.md2.4 KBevent-run-of-show/references/examples.md2.9 KBevent-run-of-show/scripts/check_timing.py4.0 KB
Read the SKILL.md
---
name: event-run-of-show
description: Builds run-of-show and cue sheets for live B2B events such as conference general sessions, user conference keynotes, field events, executive dinners, booth theater sessions and product launches. Produces a timed segment list with owners, speaker cues, AV and stage notes, walk-in and walk-out music, contingencies and a crew contact sheet, and checks the timing math. Use for run of show, event timeline, cue sheet, day-of schedule or production schedule.
license: MIT
metadata:
author: eventmarketingsoftware.com
version: "1.0"
category: trade-shows-and-field
source: https://eventmarketingsoftware.com/skills/event-run-of-show
---
# Event run of show
Turn an agenda into a minute-by-minute run of show that a stage manager, AV crew, speakers and the event lead can all
run from, with timing that adds up, a named owner for every segment, cues, contingencies and a crew contact sheet.
## Intake
If the user has an `event-context.md` file, read it first. Then ask for anything missing in ONE message:
1. Event type and format: keynote, general session, field event, dinner, booth theater, launch, or a full day.
2. Date, venue and room, local time zone, doors time and hard end time (venue curfew, next session, buses).
3. The agenda: segments, speakers and rough lengths (paste, upload, or a slide list).
4. AV setup: stage, screens, mics (handheld, lav, podium), confidence monitor, playback, streaming or recording.
5. Team: who's the producer or stage manager, AV lead, speaker wrangler, event lead, and how they communicate
(radio channel, headset, chat).
6. Anything fixed: sponsor mentions, legal disclaimers, live demos, awards, catering service times.
If the user only gives a rough agenda, build the run of show and list every assumption at the top.
## Connectors (optional)
- **Google Sheets connector:** read the agenda or write the run of show to a new tab after approval.
- **Slack connector:** post the final run of show link or the crew call times after a preview and a yes.
- **No connector:** work from pasted text or CSV/XLSX; return a Markdown table plus a downloadable CSV.
## Method
```
- [ ] 1. Fix the anchors (doors, start, hard end)
- [ ] 2. Break the agenda into segments with transitions
- [ ] 3. Assign owner, cue, AV and notes per segment
- [ ] 4. Check the timing math
- [ ] 5. Add buffer and cut list
- [ ] 6. Write contingencies
- [ ] 7. Build the crew contact sheet and call times
- [ ] 8. Validate
```
### 1. Anchors
Work backward from the hard end. Note crew call, speaker call, doors, show start and hard end in the header.
### 2. Segments and transitions
Every hand-off is its own row: walk-ups, mic swaps, video rolls, stage resets, panel chairs going on. Typical
transition lengths to use when the user doesn't say (label as assumptions): speaker walk-up with walk-on music 0:30,
panel set or strike 1:00 to 2:00, demo machine switch 0:30 to 1:00, video roll as long as the video.
### 3. Owner, cue, AV, notes
- **Owner:** one named person or role who makes the segment happen (not "team").
- **Cue:** the trigger in words ("On 'please welcome Jane', play walk-on, lights up, slide 1"). Standby cues go in
the row before.
- **AV:** mics by number, slide deck file name, video file, playback source, lighting state, audio levels.
- **Notes:** speaker intros, sponsor or legal lines, giveaways, translation, captions, accessibility needs.
### 4. Timing math
Start time of each row = start of the previous row + its duration. Total = sum of durations and must end at or
before the hard end. Use `scripts/check_timing.py` when code execution is on, or do it in-chat with the same rules.
Report gaps, overlaps, and the end time.
### 5. Buffer and cut list
Keep at least a few minutes of buffer before the hard end for a keynote, and say how much you kept. Add a cut list:
which segments shrink or drop, in order, if the show runs long (for example "cut Q&A to 5 min", "drop video 2").
### 6. Contingencies
Write a short plan for each likely failure: speaker late or missing, demo fails, slides won't load, mic fails,
Wi-Fi or stream drops, fire alarm or evacuation, medical issue, running long or short. Each: trigger, who decides,
what happens, what the host says. Patterns: [references/contingencies.md](references/contingencies.md).
### 7. Crew contact sheet
Role, name, phone (if provided), radio channel, location during the show, call time. Don't invent phone numbers;
leave placeholders.
### 8. Validate
- Times add up and end before the hard end; no overlaps unless intentional (pre-set during a video).
- Every row has an owner and a cue; every speaker has a mic and a call time.
- Every video or deck named in the rows appears in an asset list.
- Time zone stated once in the header.
## Output
1. **Header block:** event, date, room, time zone, crew call, speaker call, doors, start, hard end, buffer kept.
2. **Run of show table** with these columns in this order:
`#, start, end, duration, segment, on_stage, owner, cue, av_audio, av_video_slides, lighting, notes`
Times as HH:MM (24-hour unless the user prefers 12-hour), durations as M:SS or H:MM:SS.
3. **Cut list** (ordered).
4. **Contingency plan** table: `risk, trigger, decides, action, host line`.
5. **Crew contact sheet** table: `role, name, phone, channel, position, call_time`.
6. **Asset list:** decks, videos, music, with file names and owner.
A filled example: [references/examples.md](references/examples.md). Sample input: `assets/sample-agenda.csv`.
## Approval gates
- Show the final table before writing to a shared sheet or posting to Slack; act only after a yes.
- Don't send speaker call times to speakers directly; give the user drafts.
## Script (optional)
```
python scripts/check_timing.py run_of_show.csv --start 09:00 --hard-end 10:30
```
Reads a CSV with `segment` and `duration` (M:SS, MM or H:MM:SS), and optional `start`. It recomputes starts and
ends, flags rows whose given start doesn't match, and reports total time, buffer or overrun. Standard library only.
## Related skills
booth-staffing-schedule (shift grids), exec-dinner-planner (dinner run of show), booth-staff-briefing (booth theater
logistics for staff).
FAQ
What is a run of show for an event?
How do I make a run of show for a keynote?
What's the difference between a run of show and an agenda?
Can this skill check the timing of an existing run of show?
More trade shows & field skills
intermediate
Book Meetings Before the Show
Plans and writes the outreach that books meetings at a conference: a dated timeline, tiered email and LinkedIn sequences, rep and exec notes, SDR talk tracks and confirmations.
easy
Build a Booth Staffing Schedule
Turns show hours, staff availability, roles and booked meetings into a fair booth shift schedule with role coverage, breaks, per-person schedules and a list of gaps.
intermediate
Find Target Accounts in an Event List
Matches a show's exhibitor, sponsor, speaker or attendee list against your ICP and CRM, then gives you a tiered target list with owners and a play for each tier.
intermediate
Plan an Executive Dinner
Plans an executive or VIP dinner end to end: ranked guest list, invite volume, personal invites, RSVP tracker with a waitlist, confirmations, seating and a host brief.
easy
Turn an Exhibitor Manual Into a Checklist
Reads a show's exhibitor manual or service kit and gives you a dated checklist with owners, every early-order and shipping deadline, and the booth rules your builder needs.
easy
Write a Booth Staff Briefing
Creates the booth briefing your team will actually read: goals per person, roles, openers, qualifying questions mapped to scanner fields, demo flow, lead rules and logistics.