---
name: webinar-run-sheet
description: Builds webinar and virtual event run sheets and producer cue sheets. Produces timed segments, host, speaker and producer roles, slide, poll and video cues, chat prompts, CTA moments, Q&A ownership, clip flags for repurposing, a tech rehearsal plan, a pre-flight checklist and backup plans for when a speaker drops or the stream fails. Use for a webinar run of show, virtual or hybrid session production, a webinar checklist, rehearsal planning or a producer script.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: webinars-and-virtual
  source: https://eventmarketingsoftware.com/skills/webinar-run-sheet
---

# Webinar Run Sheet

Builds the producer's document for one live or simulive session: a minute-by-minute run sheet everyone can follow, who owns each cue, when polls and CTAs fire, who handles Q&A, which moments to flag for clips, and what happens when something breaks. Works for webinars, virtual event sessions, and hybrid sessions streamed from a stage.

## Intake

If the user has an `event-context.md` file, read it first and don't ask for anything it already answers.

Ask for whatever is missing in ONE message:

1. Session title, date, start time and time zone, total length, live or simulive (pre-recorded played as live), webinar or hybrid.
2. Outline: segments in order with rough minutes, or just the topic and speakers so you can propose one.
3. People: host or moderator, speakers (internal, customer, guest), producer, Q&A or chat moderator. Note if one person plays several roles.
4. Interactive pieces: number of polls (and draft questions if any), chat prompts, demo, video, handouts, and which ones your platform supports. Say "unsure" if unknown; you'll mark them as "confirm in platform".
5. The CTA and when it should appear (demo request, meeting, content offer, next event).
6. Q&A format: live at the end, threaded through, or upvoted; and whether questions are pre-collected from registration.
7. Repurposing plans: will the recording be clipped? (default yes, so clip flags are added)

## Data sources (connectors optional)

- If a Google Sheets connector is available, offer to write the run sheet to a new tab so the team can edit it live.
- If a Slack connector is available, you may draft the rehearsal reminder or the "go live" checklist message for the team channel. Post only after a clear yes.
- Otherwise, return Markdown plus a downloadable CSV of the run sheet.
- Don't fetch URLs or platform docs. Mark platform-specific steps "confirm in platform". Never require a paid service.

## Method

1. **Set the clock.** Build the run sheet in real clock time in the host's time zone with a running "elapsed" column. Add a pre-show block starting at least 30 minutes before go-live (green room, sound and screen-share check) and a post-show block (debrief, recording check).
2. **Shape the segments.** Default 45 minute shape, adjust to the user's length:
   - 0:00 to 0:03 welcome, housekeeping (chat, Q&A box, recording, captions), first chat prompt
   - 0:03 to 0:30 content, broken into blocks of no more than about 10 minutes, each ending with an interaction (poll, chat prompt, question)
   - mid-session poll and soft CTA
   - 0:30 to 0:42 Q&A
   - 0:42 to 0:45 recap, main CTA, next steps, thank you
   Put the main CTA before people start leaving, not only in the last minute.
3. **Assign every cue.** Each row has one owner. Producer owns slides advancing (unless speakers drive), polls, video, CTA pop-ups, recording; moderator owns chat and Q&A triage; host owns transitions and time. Name a backup for each critical cue.
4. **Plan Q&A.** Seed 3 questions in advance (from registration answers if available) so Q&A never starts in silence. Moderator groups similar questions and passes them to the host in order. Define the cutoff and what happens to unanswered ones (answered in the follow-up email or FAQ).
5. **Write the polls and prompts.** 2 to 4 options, one question each, results used in the talk. Chat prompts should be easy to answer in a few words.
6. **Flag clips.** Add a `Clip` marker to rows where a strong moment is likely (a story, a number, a demo payoff, the best Q&A answer). The producer notes the real time during the show for the editor.
7. **Rehearsal and pre-flight.** Use [references/preflight-checklist.md](references/preflight-checklist.md): a tech rehearsal 2 to 5 days before with everyone on their real setup, then a pre-flight checklist 30 minutes before and a 5 minute "go" check.
8. **Backup plans.** For each risk: speaker no-show or drop, presenter audio fails, screen share fails, demo breaks, platform or stream fails, host loses connection, very low or very high attendance, hostile or off-topic chat. Each gets a trigger, an owner and an action. Have slides and a pre-recorded demo with the producer.
9. **Hybrid sessions:** add a room column (stage manager, room mic for audience questions, confidence monitor, remote speaker return feed) and make sure online Q&A gets equal time.

Domain rules that matter:
- Every minute of the run sheet has an owner; nobody improvises transitions.
- Interaction at least every 10 minutes keeps people from drifting.
- Announce recording and captions at the start.
- The CTA appears at least twice: mid-session (soft) and at the close (main).
- Simulive: someone is still live in chat and Q&A, and the run sheet marks which parts are recorded vs live.

## Output templates

**1. Run sheet** (also as CSV):

| # | Clock time (TZ) | Elapsed | Length (min) | Segment | On screen | Speaker | Producer cue | Moderator cue | Interaction | CTA | Clip | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|

**2. Roles and contacts** (role, name, backup, how to reach them during the show, never in public chat).

**3. Polls and chat prompts** (when, wording, options, what the speaker does with results).

**4. Q&A plan** (seed questions, triage rules, cutoff, follow-up for unanswered).

**5. Rehearsal agenda**, **6. Pre-flight checklist**, **7. Backup plan table**:

| Risk | Trigger | Owner | Action | Audience message |
|---|---|---|---|---|

**8. Post-show** (recording check, clip timestamps to editor, unanswered questions list, attendee and no-show lists to follow-up owner).

Worked example: [references/example-run-sheet.md](references/example-run-sheet.md).

## Validation checklist

- [ ] Clock times add up: each row's start plus length equals the next row's start, and the session ends on time.
- [ ] Every row has an owner; every critical cue has a backup.
- [ ] No content block runs longer than about 10 minutes without an interaction.
- [ ] CTA appears at least twice, the first before the last 10 minutes.
- [ ] Q&A has seed questions and a plan for unanswered ones.
- [ ] Backup plan covers speaker drop, audio, screen share, demo and platform failure.
- [ ] Platform-specific features are marked "confirm in platform" unless the user confirmed them.
- [ ] House style: contractions, plain words, no dashes as punctuation.

## Approval gates

- Return the run sheet as a draft. Don't post to Slack, send calendar invites or write to a sheet without showing the content and getting a clear yes.

## Privacy

- Keep speakers' phone numbers in the roles table only, never in on-screen notes or public chat prompts.
- Don't name attendees on screen when reading questions unless they agreed. "Someone from a healthcare company asks" is fine.

## Related skills

event-run-of-show (in-person events), webinar-repurposing (turn the recording into content), event-invite-sequence (the emails before the session), no-show-recovery (after it).
