Plan an In-Person Event Run-of-Show with Timings, Owners and Backups
Get a minute-by-minute run-of-show table with start times, durations, owners, cues, backup plans and flagged buffer slots, plus an overrun plan and owner checklist.
You getOne-line summary, table and overrun plan
Prompt
Act as an experienced event producer who writes run-of-show documents for in-person marketing events.
Your job: build a minute-by-minute run-of-show for my event. Before writing anything, ask me these questions in one numbered message and wait for my answers:
1. What is the event (type, goal, headcount) and venue?
2. What are the load-in, doors-open, program-end and venue-out times?
3. Which segments must happen, and who is on the team?
4. What worries you most about the day?
Rules:
- Every segment has a start time, duration in minutes, a named owner and a one-line backup plan.
- Add at least one buffer slot of 5-15 minutes for every 90 minutes of schedule, and label each one BUFFER.
- Times add up exactly with no gaps or overlaps, and the last segment ends at the venue-out time.
- Flag any moment where one person owns two things at once.
- Give each segment a cue: who signals the next step and how (mic, slide, music, radio).
Output format:
1. One-line summary: event, headcount, total runtime.
2. Table: Start | End | Min | Segment | Owner | Cue | Backup plan.
3. Overrun plan: segments to cut or shorten first, in order.
4. Conflicts flagged.
5. Owner checklist: each owner and their segments.
End with one line listing your assumptions and anything still missing.Example output
Tips and common edits
Why this works
- Requiring an owner and backup plan for every segment turns a schedule into a usable working document.
- Labeled buffer slots per 90 minutes give the day built-in room to absorb overruns.
- The conflict check catches one person being booked for two jobs at the same moment.
Use this a week or two before a launch party, meetup or conference session. Have your timings, segment list and team names ready. Works well in ChatGPT, Claude or Gemini.
Common edits
- Add a column for location or room if your event runs across several spaces.
- Ask for a short printable version with only times, segments and owners for staff badges.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a Product Launch Timeline Backward from Launch Day with Owners and Checkpoints
Get a dated launch calendar from teaser phase through launch week, with one owner per task, channel assignments, dependencies and go/no-go checkpoints.
Write an AP-Style Press Release for a Launch or Event with a Journalist Pitch
You get an inverted-pyramid press release built only from your facts, clearly marked spots for real quotes, a three-sentence pitch email and a list of missing facts.
Write a Product Launch Announcement for Email, Social, and Blog
You get one core launch message and a single call to action, adapted into a matched email, social post, and short blog post, each written to a set length.
Positioning Statement and Messaging Hierarchy for a Product Launch
Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.
Plan a Flash Sale with Real Deadlines, Stock Caps and Honest Countdown Copy
You get an offer plan with discount depth, margins, exact start and end times and unit caps, plus email, SMS, social and banner copy that matches it.
Plan a Trade Show Booth with Opener Script, Lead Scoring and 48-Hour Follow-Up
You get a complete booth plan: headline, a 10-second opener, scored qualification questions, capture fields, a 48-hour follow-up email, a timeline and metrics.