# Live Stream Run-of-Show Architect

Build a minute-by-minute live stream plan with segment ownership, audience interaction, technical cues, moderation, and failure contingencies.

## Prompt

You are a live broadcast producer who specializes in run-of-show design, technical coordination, and audience safety.

Inputs:
1. Event purpose, audience, platform, and duration: {{event_context}}
2. Hosts, guests, topics, demos, and audience activities: {{program_elements}}
3. Streaming setup, locations, communications, and crew roles: {{technical_setup}}
4. Registration, moderation, promotion, and follow-up plan: {{audience_operations}}
5. Safety, privacy, accessibility, legal, and contingency constraints: {{constraints}}

Do the following:
1. Define the broadcast objective, audience promise, success criteria, and segment mix, removing elements that cannot be executed reliably within the duration.
2. Build a minute-by-minute run of show with program content, speaker, visual source, audio source, technical cue, producer cue, audience action, and hard timing.
3. Specify rehearsals, speaker briefing, green-room flow, handoffs, lower thirds, media playback, captions, interpretation, moderation, delay, and backstage communication.
4. Create contingency paths for guest absence, connection failure, demo failure, audio loss, harmful chat, privacy exposure, overrun, underrun, and platform outage, including who decides and what replaces the segment.
5. Produce the run-of-show table, cue sheet, role matrix, rehearsal plan, moderator guide, emergency scripts, asset checklist, recording and backup plan, and post-event handoff. Include explicit go, hold, skip, and end authority.

## Best for

Event, community, and marketing teams producing live video that needs disciplined timing, moderation, accessibility, and technical recovery.

## Compatible tools

- Claude
- ChatGPT

## How to use

- List every speaker, asset, and technical source.
- Assign one owner to each live decision.
- Rehearse transitions and failure substitutions.
- Prepare emergency language for the host.

## Customization tips

- Use hard outs for fixed event durations.
- Make backup assets start from a known cue.
- Test captions and interpretation end to end.
- Define who can hold, skip, or end the stream.

## Example input

Event: 60-minute live launch of an open-source climate-data portal on YouTube and LinkedIn. Program: host welcome, director interview, eight-minute live demo, researcher panel, audience Q&A, and closing. Setup: remote guests, studio host, OBS, remote contribution platform, captions, and two-person production crew. Constraints: public chat, embargoed dataset names must not appear before launch, demo sandbox may be unstable, and one panelist needs live German-to-English interpretation.

## Example output

The run of show assigns hard time, visual source, technical cue, and owner to every segment. The demo has a prerecorded backup beginning from the same host line, while embargoed browser tabs are excluded from screen-share profiles. Interpretation gets a sound check and dedicated return audio. Moderation rules cover personal data, harassment, and unsupported claims. The producer has skip authority, the host has controlled filler prompts, and the director owns early termination.