run of show event template word

Event Production Execution Scripting Standard

Document Control

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

1. Purpose & Scope

This document provides the standardized framework for developing, maintaining, and executing a synchronized production script for [Event Name]. This procedure covers the lifecycle of the technical cue sheet, from initial drafting to post-event archival, ensuring all stakeholders maintain operational alignment during live production.

2. Prerequisites

• Software: Microsoft Word or compatible word processing suite.
• Access: Permissions to the event management repository at [Repository URL/Path].
• Materials: Finalized event agenda, technical rider, and AV cue list.
• Communication: Access to the production intercom system or designated [Communication Tool] channel.

3. Roles & Responsibilities

4. Step-by-Step Procedure

Phase 1: Structural Setup

• Open the standardized production document template located at [Template Path].
• Save document as: [Event_Name]_Production_Script_YYYYMMDD.
• Define the [Time Zone] for all timestamp entries.
• Populate the "Header Information" section with [Event Name], [Venue Location], and [Date].

Phase 2: Content Population

• Import the master agenda into the "Schedule" table.
• Insert rows for "Pre-Show," "Live," and "Post-Show" segments.
• Assign a unique "Cue ID" to every transition (e.g., C-001, C-002).
• For each segment, define:
  • Time: Start and end duration.
  • Cue: Specific trigger (e.g., "Speaker exits stage").
  • Action: Technical command (e.g., "Fade music," "Switch to Camera 2").
  • Owner: Assigned [Staff Member/Role].

Phase 3: Validation and Review

• Conduct a "Table Read" with the production team to verify timing logic.
• Review all transition notes for clarity and brevity.
• Verify that all [Emergency Contact] numbers are listed in the footer.
• Export the final version to [PDF/Print Format] for physical distribution.

5. Quality Assurance, Pro-Tips, and Pitfalls

• QA: Every cue must have a clearly defined "Trigger" and "Action." If a cue is ambiguous, it is considered a failure point.
• Pro-Tip: Use a high-contrast font (e.g., Arial or Helvetica, 12pt) to ensure readability in low-light production environments.
• Pro-Tip: Include a "Buffer" column to track time slippage relative to the master clock.
• Common Pitfall: Over-scripting. Only include essential technical cues; avoid cluttering the document with narrative dialogue that does not require a technical change.

6. FAQs

Q: How should I handle unplanned schedule delays during the event? A: Use the "Buffer" column to adjust the start time of subsequent segments. The Stage Manager must announce the "Adjusted Time" over the intercom once the shift exceeds [Number] minutes.

Q: What is the standard for naming cues? A: Use a prefix-number system (e.g., A = Audio, V = Visual, L = Lighting) followed by a sequential number to allow for quick verbal communication during the event.