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

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

Example for: a SaaS product launch evening, 80 guests, rooftop venue, load-in 3:00 pm, venue out 10:00 pm.

Summary: Product launch evening for 80 guests, 7 hours from load-in to venue out.

StartEndMinSegmentOwnerCueBackup plan
15:0016:0060Load-in, AV and stage setupMarcusPriya radios startSpare mics and HDMI kit in van
16:0016:3030Tech rehearsalMarcusDana on micSkip walk-through, test demo only
16:3016:4515BUFFERPriya—Absorbs late setup
16:4517:0015Staff briefingPriyaRadio callPrinted brief left at check-in
17:0017:4545Doors, registration, drinksSofiaMusic onPaper guest list if tablet fails
17:4517:505Seat callDanaMusic fadesStaff walk floor to move guests
17:5018:0010WelcomeDanaTitle slideDana cuts to 5 min if late
18:0018:2020CEO keynoteLeoWalk-on musicDana delivers short version from notes
18:2018:3515Live product demoNinaDemo slidePre-recorded video on backup laptop
18:3518:4510BUFFERPriya—Absorbs keynote overrun
18:4519:0520Customer panelDanaPanel chairs setDrop to two panelists
19:0519:1510Audience Q&ADanaRunner micsUse 3 pre-collected questions
19:1519:205Close and demo stations openLeoFinal slideDana closes
19:2020:2060Networking, food, demo stationsPriyaMusic upCatering lead covers food timing
20:2020:3010BUFFERPriya—Extends networking if needed
20:3020:4515Last call, gift bagsSofiaLights up 50%Bags placed at exit table
20:4521:0015Guests outPriyaMusic offStaff guide to elevator
21:0021:5050TeardownMarcusRadio callVenue crew helps with stage
21:5022:0010BUFFERPriya—Final venue walk-through

Overrun plan

  1. Cut Q&A to 5 minutes.
  2. Drop panel to two speakers (15 min).
  3. Shorten networking to 45 minutes.
  4. Shorten welcome to 5 minutes.

Conflicts flagged

  • 18:20: Marcus runs AV and is the only one who can switch to the backup demo laptop. Brief Sofia as second operator.
  • Dana hosts 17:45 to 19:15 straight; set water and a cue card at the lectern.

Owner checklist

  • Priya: buffers, briefing, networking, guests out
  • Marcus: load-in, rehearsal, teardown, AV all night
  • Dana: seat call, welcome, panel, Q&A
  • Leo: keynote, close
  • Nina: demo
  • Sofia: registration, gift bags

Assumptions: catering runs its own timeline; venue access confirmed for 3:00 pm. Missing: wet-weather plan for the rooftop.

Written by AI from this prompt. Your results will vary.

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 in Marketing