Run-of-Show Playbook for Multi-Stage Events

A run-of-show is the operating script for event day. For multi-stage events, it should coordinate stages, sessions, speakers or artists, crew, vendors, access control, communications, contingency plans, and live changes. This playbook is for festival producers, conference showcallers, venue ops leads, agencies, and promoters who have outgrown “everyone has their own PDF” — and need one spine the radios can trust.

A run-of-show (ROS) is a time-ordered execution document: who does what, where, with which resources, and what happens if the plan moves. It is not marketing copy and not a public agenda poster — it is the internal contract between programming, production, security, vendors, and comms. For multi-stage programmes, the ROS ties parallel lanes to one reference clock so Stage B does not discover a headline change when Stage A’s crowd surges.

Multi-stage festivals, conference campuses, and multi-room venues multiply dependencies: shared backline, crew buses, power, noise curfews, accreditation lanes, and sponsor commitments. Without a shared ROS, you get three truths — programming’s grid, production’s WhatsApp, and security’s spreadsheet — and attendees hear a fourth on social media.

• Reference clock and time zone — one source, no ambiguous “doors” vs “show” • Stage or room lanes with session/performance blocks, holds, and curfews • Named owners per block (showcaller, stage manager, room captain, comms lead) • Crew call times, meal breaks, and shared-resource bookings • Vendor servicing windows, load-in/out, and noise or access restrictions • Access control: credential types, gate open, artist coaches, VIP corridors • Attendee comms triggers (app, screens, SMS) tied to approved changes • Contingency rows: weather, medical, power, artist no-show, security hold • Post-event handoff: strike, debrief owner, incident log, sponsor proof

Build the ROS from the same time base as your schedule template — usually five- or ten-minute resolution on show day. Mark setup, performance, and strike explicitly; steal buffer from catering before you steal it from safety. Conference sessions need room turnover and AV reset rows; festivals need changeover physics and shared crew conflicts visible on one grid.

Every ROS block needs a single accountable owner — not a group chat. Showcaller holds the master clock; stage managers own lane execution; comms owns outward messaging after production signs off. Agencies running multiple clients should namespace ROS versions so a change on Client A never forks Client B’s master file.

RACI on the ROS row: Add a lightweight RACI or “R/A” column on critical rows: who must be consulted before the clock moves versus who can execute once approved.

Vendors do not run on artist ego — they run on servicing windows, vehicle bands, and power sharing. Tie food, merch, activations, and sponsor builds to the same ROS clock as stages. When a slot moves, trigger a vendor delta review, not a surprise at the gate.

Publish credential and gate logic against ROS truth: when lanes open, when artist coaches must arrive, when re-entry rules change. Check-in and crowd flow should reference the same entitlements as ticketing and registration — not a list exported at lunch. Conference programmes should align badge reprints with session room captains when rooms move.

Define the comms tree: who may announce delays, who speaks to sponsors, who updates attendee channels. Escalation paths should be on page one — medical, security, utilities, artist management — with radio channels or roles, not names that go on holiday without a backup.

Live changes need version discipline: what moved, who approved, which lanes were notified, and what attendees were told. Maintain a change log row in the ROS (or linked schedule) so post-event review is evidence-based. Marketing should not publish set times or room moves that production has not signed off.

Spreadsheet risk: If three producers can edit different “master” files, you do not have a run-of-show — you have a lottery. Compare how governed platforms reduce forked truth versus static files.

Within 72 hours, capture overruns, bottlenecks, vendor friction, access incidents, and comms gaps against the final ROS version — not memory. Feed lessons into next year’s schedule template and ops checklist. Sponsors and finance often need proof tied to the same timeline production used on the day.

EventSuite connects schedules, tasks, vendor records, access, attendee comms, and reporting so run-of-show changes reference one programme model — fewer midnight merges and fewer doors that disagree with the grid. Use the event operations checklist and multi-stage schedule template to operationalise this playbook, then book a demo to map your stages and ownership model.