run of show template for events

Event Execution Master Schedule Standard Operating Procedure

Document Control

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

1. Purpose & Scope

This document establishes the standardized framework for orchestrating live event logistics. It is designed to ensure seamless synchronization between production, talent, and venue operations. This procedure applies to all [Company Name] events requiring a minute-by-minute technical and operational sequence.

2. Prerequisites

• Software: Access to [Collaborative Spreadsheet Tool/Project Management Platform].
• Hardware: Hard copies of the final schedule printed on [Paper Size] for all key stakeholders.
• Communications: Dedicated [Radio Channel/Messaging Group] for stage management.
• Documentation: Finalized event floor plan and technical rider.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Drafting and Integration

• Input all confirmed agenda items into the master template.
• Sync technical cues (lighting, audio, video) with the event timeline.
• Assign specific "Go" times for each transition.
• Review timing buffers with [Department Head Name] to account for potential delays.

Phase II: Validation and Distribution

• Conduct a tabletop walkthrough with the production team.
• Identify and label "Hard Stops" (e.g., live broadcast windows or transit departures).
• Distribute the approved version to all stakeholders via [Communication Channel].
• Confirm receipt and understanding of the schedule from all department leads.

Phase III: Execution and Real-time Adjustment

• Stage Manager initiates the "Call" sequence 5 minutes prior to start.
• Log all actual start/end times versus the planned schedule in the [Column Name] column.
• Document all deviations or "on-the-fly" adjustments in the [Notes Column].
• Communicate schedule shifts to the [Role/Department] via [Communication Method].

Phase IV: Post-Event Debrief

• Compare actual timeline against the planned schedule to identify bottlenecks.
• Archive the marked-up schedule in [Digital Repository Name].
• Update the master template based on lessons learned during the execution.

5. Quality Assurance, Pro-Tips, & Pitfalls

• QA: Ensure every transition has a "Ready," "Standby," and "Go" call.
• Pro-Tip: Always build in a 10% "buffer time" for every major segment to mitigate cascading delays.
• Common Pitfall: Failing to account for movement time (e.g., moving talent from green room to stage). Always include "Transit Time" as a line item.

6. FAQs

Q: How should I handle a segment that is running behind schedule? A: Identify the "Non-Essential" segments marked in the schedule as [Optional/Compressible] and truncate those to regain time without impacting the primary program.

Q: Who is authorized to make changes to the schedule once the event has started? A: Only the [Job Title, e.g., Stage Manager or Event Lead] has the authority to issue "Go" calls for schedule deviations to ensure consistency across all departments.