Event Run Sheet Template

This is a run sheet template — the live operational timeline for show day. Use it to map timings, cues, crew owners, supplier notes, and handovers from load-in through doors, programme, close, and strike before you issue the live version to production teams.

A production schedule usually covers the wider timeline across planning, load-in, setup, rehearsals, live delivery, strike, and debrief. A show flow focuses on the sequence of programme moments the audience or stage team experiences. A cue sheet captures technical or operational cues such as audio, lighting, video, staging, comms, doors, or announcements. A run sheet connects these into one live operating view for the people delivering the event.

Static run sheets are easy to share early, but live events rarely follow a frozen document. A supplier is late, doors move, a credential decision changes, a crew member swaps shifts, a cue is delayed, or a venue issue needs escalation. If the run sheet is copied into separate spreadsheets, PDFs, chats, and printed notes, the team can lose confidence in which version is current.

Version control warning: If your team says "which run sheet are you looking at?" during event day, the document has stopped acting as operational control.

A useful event run sheet should include a clear header, version details, timings, milestones, show flow, cues, task owners, crew responsibilities, supplier and venue notes, accreditation or access notes, issue and change tracking, handover notes, and post-event follow-up prompts.

• Event name, venue/site, date, timezone, version, owner, publish time and approval status • Milestones for load-in, setup, rehearsals, doors, registration, show moments, breaks, close, strike and handover • Show flow, cues, buffers, changeovers, room moves, supplier moments and audience-facing schedule dependencies • Named owners for production, crew, suppliers, venue/site, accreditation, workforce, admissions and reporting • Live issue, change, escalation, decision and post-event follow-up fields

Use this copy-ready structure before a downloadable asset exists. Add one row per live delivery moment and keep the owner, dependency, and status columns current as the event moves closer to doors.

• Record exact times for load-in, rehearsals, briefings, doors, programme blocks, breaks, close and strike • Add buffer time between high-risk moments such as supplier arrivals, changeovers, queues, room turns or stage movement • Mark decision points where the team must confirm whether the plan is still valid • Separate public schedule times from backstage production timings when needed • Assign an owner to approve timing changes and communicate impact

• List each show moment, speaker/artist movement, transition, announcement, technical cue or audience instruction • Connect cues to owners such as showcaller, stage manager, audio, lighting, video, venue operations or admissions • Include cue dependencies so a delayed arrival, access issue or room change does not surprise the show team • Record what changes if a cue moves, is skipped or needs escalation • Keep the cue view aligned with the wider event run sheet

• Add crew call times, shift ownership, role notes, briefing times, reporting points and communication channels • Confirm task owners for production office, stage, gates, registration, venue/site, suppliers, VIP areas and issue response • Document who can approve task changes, reassignments and emergency coverage • Connect volunteer or casual staff instructions to the same run sheet context • Capture gaps so workforce planning can improve next time

• Include supplier arrival windows, setup notes, loading instructions, onsite contacts and dependencies • Add venue or site notes for access routes, rooms, stages, back-of-house, power, parking, signage and services • Confirm which supplier or venue changes must appear in the run sheet before live delivery • Connect RFQ or supplier scope to what the production team expects onsite • Record supplier and venue issues for post-event reconciliation

• Note credential requirements for crew, suppliers, speakers, artists, VIPs, media, contractors and venue teams • Map access notes to zones, rooms, backstage areas, gates, loading bays, vehicles and restricted spaces • Confirm who approves exceptions and where those decisions are logged • Align access notes with admissions, ticketing, staffing and supplier arrival plans • Capture access issues that affect future accreditation setup

• Log live issues with owner, severity, timestamp, status and resolution note • Record run sheet changes with what changed, who approved it, who was notified and what is affected next • Keep handover notes beside the relevant timing or cue so context is not lost between teams • Flag unresolved items that need post-event follow-up • Use the issue record to improve future run sheet templates

• Compare planned timings against actual delivery and note where buffers were too short • Review show flow changes, supplier delays, crew gaps, venue issues and accreditation exceptions • Capture decisions that should become default run sheet rows for future events • Share reporting notes with production, commercial, finance and leadership stakeholders • Link follow-up actions to the event record instead of rebuilding the story from chat messages

The run sheet template gives teams a clear starting point. Event Suite Production Ops helps when the run sheet needs to become live operational control: show flows, task owners, supplier notes, access context, issue logs, handovers, and reporting connected to the same event record rather than copied across static documents.