---
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).
