example of run sheet for event

Event Execution Run Sheet Standard Operating Procedure

Document Control

• Document ID: SOP-OPS-001
• Version: 1.0
• Effective Date: [__________]
• Review Cycle: Annual

1. Purpose & Scope

This document establishes the standardized protocol for creating and executing a minute-by-minute production schedule for [Event Name]. The scope covers all logistical transitions, technical cues, and stakeholder handoffs from load-in to load-out.

2. Prerequisites

• Software: Access to [Collaborative Project Management Tool] or [Spreadsheet Software].
• Documentation: Finalized event floor plan, technical rider, and site contact list.
• Communication: Dedicated radio channels or [Messaging Platform] group for the production team.
• Hardware: Printed copies of the run sheet for all [Department Leads].

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Pre-Event Logistics (T-Minus 48 Hours)

• Finalize the master timing document with all [Vendor] and [Talent] arrival times.
• Confirm all "hard stops" and "soft cues" with the technical production team.
• Distribute the digital draft to all [Department Leads] for final sign-off.

Phase II: Load-In and Sound Check

• Verify venue access and loading dock availability at [Time].
• Execute sound/light check against the technical rider; document all [Equipment] adjustments.
• Conduct a full walk-through with [Key Stakeholders] to verify stage positioning.

Phase III: Live Execution

• Initiate "Green Room" call for [Speaker/Performer] at [Time].
• Execute stage transitions based on the minute-by-minute cue sheet.
• Monitor real-time adjustments; log any deviations from the plan in the [Incident Log].

Phase IV: Load-Out and Debrief

• Oversee strike of all [Audio/Visual] equipment.
• Perform venue walkthrough with [Venue Representative] to confirm no damage.
• Schedule post-mortem meeting for [Date] to review [Performance Metrics].

5. Quality Assurance, Pro-Tips, and Pitfalls

• Quality Assurance: All cues must be cross-referenced against the [Technical Rider] 24 hours prior to the event.
• Pro-Tip: Always build in a 10% "buffer time" for every transition to account for technical delays.
• Common Pitfall: Failing to account for "housekeeping" time (microphone swaps, furniture moves). Ensure these are explicitly listed as separate line items.

6. FAQs

Q: What should I do if the event falls behind schedule? A: Identify the "non-negotiable" segments. If running late, truncate filler content or transition segments rather than cutting essential [Keynote/Presentation] time.

Q: Who is authorized to make changes to the run sheet during the event? A: Only the [Event Producer] or [Stage Manager] may authorize deviations to the master schedule to ensure communication remains centralized.