What Should Be in a Community Event Run of Show?
A run of show is an internal production timeline listing each event moment, its scheduled time, accountable owner, location, cue, readiness check, and backup plan. It tells the event team how to deliver the public agenda.
A run of show is the behind-the-scenes schedule your event team follows to make the program happen. Unlike a public agenda, it identifies the precise time, cue, responsible person, location, preparation required, and backup action for each transition. For a festival, community concert, fundraising gala, or downtown celebration, a workable run of show keeps volunteers, performers, technicians, and organizers using the same plan.
You do not need a television production crew to benefit from one. A spreadsheet, shared document, or event tool can work if the people executing the event can find the current version and understand it quickly.
What is the difference between an event agenda and a run of show?
A public agenda tells attendees what happens. A run of show tells staff how and when to make it happen.
| Public agenda | Internal run of show |
|---|---|
| 5:00 PM: Gates open | 4:30 PM: Gate lead confirms scanners, cash float, wristbands and radio channel |
| 6:00 PM: Music begins | 5:53 PM: Stage manager confirms performer ready; 5:58 PM: AV cues walk-on music |
| 7:00 PM: Awards | 6:50 PM: Awards are staged and presenter meets emcee at backstage point |
| 8:00 PM: Event ends | 7:55 PM: Announce last call; 8:00 PM: Begin controlled guest exit |
The event production guides from Events Authority and Prime AV similarly describe a run of show as a timed working document with segment ownership, technical cues and contingencies. Their sample formats are helpful references, but a smaller community event can use fewer columns.
The eight fields worth putting in every run of show
The best columns are the ones the crew will actually read while working.
- Scheduled time: Use a real clock time. Add the planned duration if it helps.
- Activity or cue: Name the specific action, not merely the program segment.
- Lead or owner: Identify one accountable role for the action.
- Location: Stage, parking entrance, vendor row, information booth or a named room.
- Ready check: What must be done before this step begins?
- Communication cue: Who calls the next action, and which radio channel or phone group carries it?
- Backup action: State what the team should do if the step cannot happen on time.
- Status or actual time: Capture a meaningful shift, cancellation or completion on event day.
A performer might need a microphone and a stage entrance. A vendor opening might need electricity, a fire marshal's required check, and a clear access lane. The same format can accommodate both.
Copy-ready run of show: fictional community festival
The times below are illustrative and should be replaced with your actual permits, venue agreement and site operations. They are not safety rules.
| Time | Action | Owner | Location | Ready check | Backup / notes |
|---|---|---|---|---|---|
| 2:00 PM | Production and safety walk-through | Event lead | Entire site | Map, permits, access points | Document outstanding issues |
| 2:45 PM | Confirm vendor setup complete | Vendor coordinator | Vendor area | Power, water, entrances | Escalate blocked access |
| 3:15 PM | Radio and communication test | Operations lead | Team stations | Contact sheet | Use designated backup phone group |
| 3:30 PM | Stage sound and mic check | Stage manager | Main stage | Performers and AV ready | Adjust line-check order |
| 4:30 PM | Gate team briefing | Front-gate lead | Entry | Wristbands, ticket tools | Open a secondary check-in station if approved |
| 4:50 PM | Final site readiness call | Event director | Operations point | Leads report ready | Hold opening if needed |
| 5:00 PM | Open gates | Gate lead | Entry | Safety and operations clearance | Communicate delayed opening |
| 5:55 PM | Standby for first act | Stage manager | Backstage | Talent, sound, announcer | Move to approved alternate segment |
| 6:00 PM | First act begins | Show caller | Stage | Performer ready | Update live timing |
| 7:00 PM | Community recognition | Emcee / stage lead | Stage | Honorees, names, microphone | Shortened script if running late |
| 7:50 PM | Closing announcement | Emcee | Stage | Departure routes confirmed | Repeat exit directions |
| 8:00 PM | Program ends, controlled exit | Operations lead | Entire site | Gate and parking teams ready | Follow approved crowd plan |
| 8:30 PM | Vendor and crew load-out begins | Site lead | Loading area | Public exit and access clearance | Stagger vehicle movements |
The most important column is the owner. When a row says "everyone," it often means nobody knows who has final responsibility. Assign one person to make the call, even when five others help execute it.
Build the timeline backward from a few fixed moments
Start with the nonnegotiable times: event opening, paid performance start, venue curfew, last permitted alcohol service, required site closure, or an accessibility accommodation that must be ready at a specific hour. Confirm those requirements in the actual contracts and permits.
Then work backward. If gates open at 5:00 PM, when must the gate lead receive supplies? When must vehicles stop driving through public areas? When must vendors finish setup? Who needs to inspect the walkways? Working backward exposes conflicts that a visitor-facing agenda hides.
For stage programming, allow time for microphone handoffs, introductions, awards, accessibility announcements and transitions. A run of show that only lists performance start times can look precise while still being impossible to execute.
Give the event one person who calls the show
Large productions often have a stage manager or show caller. Community events can use a designated event lead or operations coordinator. What matters is that one role owns the live master timeline and can issue a clear cue: "Stage team, standby for awards" followed by "Awards, go" when ready.
That person should know who has authority to delay, evacuate, or cancel the event. A show caller cannot override an emergency response or safety decision. Ready.gov's emergency planning guidance emphasizes planning communications and response responsibilities before a disruption.
Keep your command structure short enough to remember:
- Event director: Overall operations and designated decisions within approved authority.
- Safety lead: Monitors hazards and initiates required safety actions under the plan.
- Show caller: Coordinates the program and communicates schedule changes.
- Area leads: Confirm readiness for stage, gates, volunteers, vendors and site services.
- Communications lead: Sends attendee, sponsor and vendor updates when approved.
One person may fill more than one role at a tiny event, but do not overload the person responsible for monitoring weather or safety with unrelated tasks.
Add a 'what if' column without turning the run of show into the emergency plan
The run of show should reference established contingency procedures, not attempt to replace them. For example, a row can say "If weather suspension is called, stop stage cues and follow Weather Plan B." The actual plan should specify safe locations, evacuation or shelter procedures, who has authority, and how guests are notified.
Create a separate, appropriately reviewed safety and weather plan for your site. The National Weather Service's lightning guidance recommends a designated weather monitor, identified shelter locations and a clear resumption rule after thunder. An event timeline should never encourage people to remain outdoors in dangerous weather to preserve the schedule.
For non-safety disruptions, small backups can be practical: a missing presenter gets a shorter introduction; a delayed meal service shifts a thank-you segment; an absent volunteer is replaced from an identified backup roster.
A simple pre-event briefing script
Use a short version of this before opening:
Today we are following Run of Show version [number], updated at [time]. [Person] is calling program cues. [Person] has responsibility for safety decisions under the approved plan. Radio channel [number] is for operations. Each lead, please confirm your first assignment and any blockers now. Schedule changes go through [show caller]. Do not make independent changes that affect entrances, public movement or safety.
Make the briefing accessible for volunteers who were not involved in months of planning. A useful run of show can be operated by somebody who just arrived with the latest version.
How to update the run of show on event day
Avoid multiple copies named "final FINAL newest." Put a version number, date and owner at the top. Make one live document the source of truth and tell every team lead how updates will be communicated. If cell service could fail, keep printed essential instructions and approved backup communication methods.
When something changes, update the future cue and owner, not just the time. For example, shortening the awards segment may change the microphone location, the number of presenters and the music cue. If the event is already running, your caller should announce the adjustment to affected leads before a new version quietly appears in a folder.
After the event, preserve the final run of show and any material incident or operational records under the organization's retention rules. A short debrief can compare planned and actual times and improve the next event.
Common mistakes that make run sheets unusable
Writing it only for the public. A schedule that says "Concert at 6" does not tell the audio crew when to check microphones.
Leaving roles blank. The person who makes a cue happen must be identifiable.
No time for transitions. Moving guests, presenters, equipment and vehicles takes real time.
Mixing safety decisions into ordinary timing adjustments. Nobody should be pressured to continue a program during an unsafe condition.
No common version. If vendors and volunteers have different schedules, the run of show stops being a shared instruction.
No backup communication. Assume at least one radio battery, phone or signal will fail.
Keep the details together without burying the team
Docket Den is built to help community organizations organize event responsibilities, supporting documents and follow-ups. Whether you use a platform or a shared document, the goal is the same: give every person executing an event a clear cue, a clear owner and the correct information when it matters.
This guide is general event planning information. Follow local permits, venue rules, emergency procedures and qualified safety guidance for your particular site and event.
Frequently asked questions
Is a run of show the same as an event itinerary?
No. An itinerary normally describes where participants go and when. A run of show adds operational cues, owners, readiness requirements and alternatives for the people producing the event.
Does a small nonprofit event really need one?
If several volunteers, vendors, performers or service providers must coordinate timed activities, even a one-page run of show can help. Keep the format proportional to the event.
Who writes a community festival run of show?
Usually an event coordinator or production lead, with input from area leads, partners and the people responsible for safety. One person should own the final consolidated version.
Should every vendor be able to see the full run of show?
Not necessarily. Share the instructions, deadlines, loading times and emergency information relevant to them. A separate vendor briefing may be more useful than a stage-by-stage cue sheet.
How early should the run of show be finished?
Create a working draft as soon as fixed program times are known. Review it with leads before event day, then publish a controlled version after the final coordination meeting. There is no universal deadline.
What if the main act runs late?
The show caller should identify which downstream activities can legally and safely move, then coordinate the change with affected leads. Curfews and safety requirements take precedence over keeping a performance on schedule.
Sources
Related reading
Event Sponsorship Tracking: How to Deliver Every Promised Benefit
A practical guide to event sponsorship tracking for nonprofit organizers: agreements, logos, recognition, due dates, proof of delivery and sponsor follow-up.
ReadHow to Manage Event Volunteers Without Losing Track of Shifts or Assignments
Learn how to schedule event volunteers, confirm shifts, fill coverage gaps, plan check-ins, and organize a simple volunteer roster for community events.
Read
