Event Planner AI ProAll free guides

Free event operations template

Event Run of Show Template and Example

Turn the event timeline into a handoff the whole team can actually run.

Open the run-of-show generatorBuild my event brief
Updated August 2, 2026 · Free to use and print · No signup

Decide before you task

The four decisions that shape this plan.

01

One accountable owner

Every row needs one person who knows it is theirs. A department name or group chat is not ownership.

02

A real start condition

Record what must be ready before the moment begins, not only the ideal clock time.

03

A visible dependency

Show the arrival, setup, approval, cue, guest movement, or vendor handoff that can block the next row.

04

A usable fallback

Write what changes when the moment runs late, equipment fails, attendance shifts, or the location becomes unavailable.

Planning timeline

Work in the order that protects your options.

Start with the brief

Protect the event outcome

  • Name the guest experience and the few moments the schedule must protect.
  • Record attendance, access, dietary, venue, weather, vendor, and travel constraints.
  • Separate fixed times from flexible blocks.
  • Choose the final decision owner for conflicts.
Build backward

Expose hidden setup

  • Begin with doors-open or guest-ready time and work backward through access, delivery, setup, tests, and briefing.
  • Add travel, load-in, security, registration, food-safety, and room-reset time where relevant.
  • Include what each owner needs before their row can start.
  • Keep setup tasks out of the guest-facing schedule only when another operational view preserves them.
Add the live sequence

Make cues and handoffs explicit

  • Give every important moment a start, expected duration, owner, location, and cue.
  • Add guest movement and transition time instead of treating it as zero.
  • Mark hard stops, vendor departure, venue curfew, and transport commitments.
  • Place short recovery buffers where delay is most likely to accumulate.
Stress test it

Ask what breaks next

  • Walk through late speakers, missing supplies, low attendance, long food service, weather changes, and technical failure.
  • Choose which moments shorten, move, combine, or disappear first.
  • Verify that each fallback is possible with the actual venue, people, and equipment.
  • Share the revised version and retire old copies.
Run and close

Keep one source of truth

  • Name the person calling time and the channel used for updates.
  • Record material changes without turning the document into a chat transcript.
  • Protect guest safety, access, and the core outcome before decorative timing.
  • Finish with cleanup, rentals, payments, item recovery, transport, and post-event ownership.

Working example

A run of show needs owners and fallbacks.

Adapt this structure to the actual venue, people, contracts, access needs, and risks. Times are examples, not universal recommendations.

TimeMomentOwnerFallback
2:00 PMVenue access and delivery checkOperations leadStage critical items first; defer optional decor
3:00 PMRoom, registration, and technical setupSetup leadsOpen a reduced guest-ready footprint
4:15 PMTeam briefing and final checksEvent leadBrief by role; publish one written update
5:00 PMDoors open and guest arrivalGuest experience leadMove check-in to the clearest accessible entrance
5:45 PMPrimary program momentProgram leadProtect the opening and close; shorten internal transitions
7:30 PMClosing, departure, and load-outOperations leadPrioritize guests, rentals, food safety, and venue handback

Brief starter

Bring these facts into the planning pass.

  1. 01Event outcome and must-protect moments
  2. 02Guest-ready time, hard stops, curfew, and transport commitments
  3. 03Venue access, rooms, routes, capacity, and accessibility
  4. 04Vendor arrival, setup, service, strike, and contact details
  5. 05Owners, cues, dependencies, supplies, and communication channel
  6. 06Likely failure points and the first acceptable simplification
Build the free event brief

Verify the world before you execute.

This guide organizes planning questions; it does not verify venues, vendors, routes, accessibility, capacity, weather, safety, contracts, or local requirements. Confirm those details with the responsible providers and qualified professionals.

Clear answers

Questions people ask while planning.

What columns belong in an event run of show?+

A useful minimum is time, duration, moment or action, owner, location, dependency or cue, required resources, and fallback. Add contacts or technical details only when the team needs them during execution.

How is a run of show different from a guest itinerary?+

A guest itinerary communicates what attendees need to know. A run of show contains the operational setup, owners, cues, dependencies, transitions, and fallbacks required to make those moments happen.

Who should update the run of show during an event?+

Use one source of truth and one person authorized to publish changes. Other owners should report changes through the agreed channel rather than circulating competing versions.

Continue from brief to plan

Build the run of show, contingencies, and next actions in one place.

Apple shows Event Planner AI Pro's current regional price, live version, and availability before installation.

View on the App Store