Event Run Sheet

What is a Event Run Sheet?

An Event Run Sheet is a master timeline document that outlines every aspect of an event, minute by minute. It acts as the operational blueprint for event planners, venue staff, suppliers, and clients. Unlike a creative brief or a high-level agenda, a run sheet is a functional tool designed to ensure that everyone involved in the execution of an event knows exactly what they should be doing, where they should be, and when they should be doing it.

At its core, the run sheet transforms abstract event concepts into concrete actions. It bridges the gap between the planning phase and the live execution. For a business, this document is often the difference between a seamless professional experience and a chaotic disaster. It is particularly critical for events with multiple moving parts, such as conferences, product launches, gala dinners, or complex corporate meetings.

The document typically serves two primary audiences: the internal team (production managers, stage managers, technicians) and the external stakeholders (clients, venue managers, speakers). While the level of detail may vary for each version, the master run sheet serves as the "single source of truth." If a dispute arises regarding timing or logistics, the run sheet is the final arbiter.

A well-constructed run sheet does not merely list times; it integrates technical cues (lighting and sound changes), logistical movements (catering service, registration opening), and human elements (speaker introductions, breaks). It is a living document that evolves from the initial draft through rehearsals to the final "show call."

In the context of business documentation, the Event Run Sheet often accompanies the initial Business Proposal and the contractual Statement of Work. While the proposal sells the vision and the SOW defines the commercial terms, the run sheet defines the reality of how that vision will be executed on the ground.

When to Use an Event Run Sheet

The common misconception is that run sheets are only necessary for massive-scale productions like award shows or music festivals. In reality, any event that benefits from structure—and involves more than one person—requires a run sheet.

Corporate Conferences and Seminars These are the most standard use cases. With multiple speakers, breakout sessions, AV requirements, and catering breaks, the complexity is high. A run sheet ensures that Session A ends on time so that the room can be reset for Session B. It coordinates the arrival of guest speakers and ensures their presentation slides are loaded and tested.

Product Launches Timing is everything for a product launch. The reveal moment must be synchronized with lighting, music, and video cues. A run sheet is essential here to map out the precise sequence of the "reveal," ensuring that the CEO's speech aligns perfectly with the technical elements.

Gala Dinners and Award Ceremonies These events involve a rigid sequence of service (entrées, main course, dessert) intersected with entertainment and speeches. The kitchen staff relies on the run sheet to pace food service, while the audio-visual team relies on it to cue microphones for winners.

Internal Meetings and Board Retreats Even for internal business meetings, a run sheet can be valuable. For a high-stakes board meeting, a run sheet can allocate time for specific presentations, Q&A sessions, and voting procedures. It prevents the meeting from running over schedule and ensures all agenda items are covered.

Virtual and Hybrid Events In the era of remote work, run sheets have adapted to include "virtual call times," streaming status checks, and moderator cues. For hybrid events (in-person and digital audiences simultaneously), the run sheet is even more critical, as it must synchronize the live show with the broadcast feed.

When is a Run Sheet Overkill? For a casual team stand-up or an impromptu brainstorm, a simple agenda suffices. The rule of thumb is: if the failure of a specific timing cue would result in a noticeable problem (e.g., the video plays before the speaker starts, or lunch arrives during a serious presentation), you need a run sheet.

Key Components and Sections

A generic agenda lists "Time" and "Activity." A professional Event Run Sheet breaks the event down into granular columns to manage the complexity. While specific formats vary, the following components are standard in a comprehensive run sheet.

1. Time Columns

• Start Time: The scheduled time the specific item begins.
• End Time: The scheduled time the item ends.
• Duration: The length of the segment. This helps in pacing—if a speech is running long, the duration column highlights exactly how much time is being lost elsewhere.

2. Activity/Description

This is a brief but clear description of what is happening. Avoid vague terms like "Lunch." Instead, use "Lunch Service Served - Plated Chicken." Be specific about what is occurring.

3. Responsibility/Owner

Who is responsible for this segment? This column lists the role or specific person. Examples: "MC," "Keynote Speaker," "AV Tech," "Venue F&B Manager." This ensures accountability. If the microphone isn't working, we know immediately whose column to look at.

4. Technical/AV Cues

This is the bridge between the schedule and the production crew. It details what needs to happen technically.

• Audio: Mic on/off, specific music tracks (intro vs. background), sound levels.
• Visual: PowerPoint slide change, video playback, lighting state (dim for speech, spotlights for awards).
• Stream: Camera cuts, lower-thirds graphics, commercial breaks.

5. Logistics/Operations

This column covers the physical movement within the venue.

• F&B: Coffee refill, water station check, clearing plates.
• Security: Guest of Honor arrival, VIP escort.
• Registration: Desk opening, badge printing check.

6. Notes/Contact Info

A section for special instructions that don't fit elsewhere. This is also the place for emergency contacts. If a key decision-maker is running late, their phone number should be accessible here.

7. Milestones

These are hard points in the show that cannot move. Doors opening, the keynote starting, the venue curfew. These are often color-coded to indicate they are "fixed points."

How to Write an Event Run Sheet (Step by Step)

Creating a run sheet is an iterative process. You cannot simply sit down and write a final draft; it evolves as the event details are confirmed. Follow these steps to build a robust document.

Step 1: Establish the "Hard" Parameters

Before filling in the activities, identify the immovable boundaries. These are your anchors.

• Venue Access: When can you start setting up?
• Doors Open: When do guests arrive?
• Start/End Times: When does the content actually begin and when must the event finish (curfew)?
• Turnaround Times: If the room needs to be flipped from a theater style to a banquet style, how long does the venue say it takes? Always add a 15% buffer to their estimate.

Step 2: Draft the High-Level Agenda

Work backward from the end time and forward from the start time to create a skeleton. Define the major blocks:

• Registration & Networking
• Opening Remarks
• Keynote Session
• Break
• Panel Discussion
• Closing & Networking

At this stage, don't worry about the minute-by-minute cues. Just get the flow right. Ensure you have allocated time for transitions. A common error is scheduling a panel from 10:00 to 10:45 and the next session at 10:45. You must schedule "Changeover" from 10:45 to 10:50.

Step 3: Flesh Out the Details (The "Drill Down")

Now, expand each block into specific actions.

• Instead of: "Keynote Speech."
• Write:
  • 10:00 - 10:05: Intro by MC (Walk to stage, Mic 1 on)
  • 10:05 - 10:45: Keynote by John Doe (Slide deck 'Keynote_A_final.pptx')
  • 10:45 - 10:50: Q&A (Runner brings handheld mic to audience)

Step 4: Integrate Technical Requirements

Collaborate with your AV lead or production manager. Ask them what they need to make the above happen. Add their cues to the technical column.

• "Lighting Cue LX-04: Wash Stage."
• "Audio: Play upbeat entrance track."
• "Video: Confidence monitors on for speaker."

Step 5: Incorporate Logistics and F&B

Consult with the venue or catering manager. Map out when food and beverage service occurs. Ensure it doesn't clash with important announcements (e.g., don't start clattering plates during the CEO's emotional closing speech).

Step 6: The "Emergency" Review

Read through the run sheet imagining something goes wrong.

• Scenario: The keynote speaker is stuck in traffic.
• Check: Does the run sheet have a 10-minute buffer or an optional "icebreaker" activity that can absorb the delay? If not, adjust the schedule.
• Scenario: The fire alarm goes off.
• Check: Is the emergency assembly point noted in the document?

Step 7: Distribute and Version Control

Save the document with a clear naming convention: EventName_RunSheet_v2_Draft.xlsx.

• Send the "Internal Master" to the AV team, venue staff, and your internal event team. This contains all the technical notes.
• Send the "Client/Stakeholder Version" to speakers and VIPs. This should only show their relevant times and high-level info to avoid confusing them with lighting cues.
• Crucial: Stop editing at a certain "lock" point (usually 24-48 hours before the event). Constant changes cause confusion.

Common Mistakes to Avoid

Even experienced event planners can fall into traps when constructing run sheets. Being aware of these pitfalls is the first step to avoiding them.

1. Overpacking the Schedule The optimism bias is strong in event planning. Planners often underestimate how long it takes to move 500 people from a keynote hall to a breakout room. If the venue says the walk is 5 minutes, schedule 10. If you schedule back-to-back sessions with zero transition time, the first delay of the day will domino through the entire event, forcing the end of the event to be cut short.

2. Being Too Vague "Speaker talks" is not a row item. "Speaker A: Topic X (15 mins)" is better. "Speaker A: Intro (2 mins) + Topic X (12 mins) + Q&A (1 min)" is best. The more specific you are, the easier it is for the team to execute.

3. Ignoring the "Bump In" and "Bump Out" A run sheet should ideally cover the setup and breakdown, not just the show time. If your event starts at 9:00 AM, your run sheet should start at 6:00 AM with "Venue Open," "Power Check," "Crew Call," and "Rehearsal."

4. Lack of Buffers Events are organic. Q&A sessions run over; microphones fail. You must build "flex time" into the schedule. A good rule of thumb is a 5-10 minute buffer every 90 minutes. If you don't use it, you get a break. If you need it, you saved the show.

5. Version Chaos Nothing ruins an event faster than a team member running an old version of the schedule. "I thought we cut that video?" someone asks, holding a printout from three days ago. Use a cloud-based platform or distinct color coding for changes so everyone is literally on the same page.

6. Forgetting the Audience Experience The run sheet often focuses entirely on the stage. Don't forget the audience. Include rows for "House Lights Up," "Background Music Volume," "Restroom Check," and "Temperature Check." If the audience is uncomfortable, the content doesn't matter.

Tips for Success

Creating the document is only half the battle; using it effectively is what ensures success.

Use Color Coding Visual cues help process information quickly.

• Red: Fixed points (Doors open, Start, End).
• Yellow: Warnings (Deadlines for AV cues, catering cut-offs).
• Green: Completed items (during the live event).
• Blue: Technical cues.

Assign a "Runner" On the day of the event, the Event Manager should not be glued to the run sheet; they need to be looking at the big picture. Assign a dedicated "Stage Manager" or "Runner" whose sole job is to manage the run sheet, check off items, and cue the next person.

Conduct a "Table Read" Before the event, gather the key speakers and the MC. Sit down and read through the run sheet. Walk through the transitions. "Okay, John, when you finish your speech, you will hand the mic to Sarah, who will come from stage left." This reveals timing issues and awkward transitions that look fine on paper but don't work in reality.

Sync with Other Documents The run sheet does not stand alone. Ensure it aligns with your Budget Plan (so you aren't scheduling overtime you can't afford) and your Risk Assessment (ensuring safety drills are scheduled). If you are using external vendors, ensure their call times match the obligations in their contracts.

Print It Out Technology is great, but Wi-Fi fails and batteries die. Always have physical, laminated color copies of the run sheet for the Stage Manager, Sound Engineer, and Lighting Director. In a dark control room, a piece of paper is often more reliable than an iPad.

The "10-Minute" Rule Ensure that every critical speaker or stakeholder is briefed on their timing 10 minutes before they go on stage. The run sheet should dictate this briefing. "09:50 - Runner briefs Speaker on timing."

Example Event Run Sheet

Event: Annual TechSummit 2024 Opening Day Date: October 15, 2024 Location: Grand Ballroom, Convention Center

Time	Activity	Responsibility	Technical / AV Cues	Logistics / Notes
07:00	Venue Access & Crew Call	Ops Mgr	Power ON, Check Headsets	Security unlock doors. Coffee service for crew.
07:30	Tech Rehearsal - Opening Sequence	AV Director	Test all mics, video playback, lighting states
08:30	Registration Desk Setup	Registration Team		Print badge stock, setup iPads.
09:00	Speaker Check-in	Event Coordinator		Green Room open. Water & snacks available.
09:30	House Open	Venue Staff	BGM: Upbeat playlist (Med Vol). House lights 100%.	Ushers at doors.
09:55	Take Your Seats Announcement	MC	Mic 1 On. House lights dim to 80%.
10:00	Opening Video	Producer	Play Intro_Video.mp4. Audio: Vol 100%. House lights dark.
10:02	Welcome Address - CEO Jane Doe	CEO	Mic 1 On. Lighting: Spot stage center. Slides: Welcome.pptx.	Runner on standby for applause.
10:15	Keynote: Future of AI - Dr. Smith	Dr. Smith	Mic 2 On. Slides: AI_Keynote.pptx. Lectern light on.
10:45	Q&A Session	CEO + Dr. Smith	Mic 3 (Handheld) to audience.	Runner brings mic to aisle 3.
10:55	Transition to Break	AV Tech	House lights 100%. BGM: Network_track.mp3.
11:00	Morning Coffee Break	F&B Manager		Coffee stations replenished. Staff clear front row.
11:30	Break Ends - First Bell	MC	Audio: Ding sound. BGM fades.
11:35	Panel Discussion: Startup Growth	Moderator	4x Lavalier mics ON. Slides: Panel_1.pdf.	Panelists seated on stage.
12:30	Event Wrap Up	MC	Thank you speech.
12:35	House Close / Lunch Service	Venue	BGM High. House lights 100%.	Direct traffic to dining hall.

Frequently Asked Questions

What is the difference between a Run Sheet and an Agenda? An agenda is a high-level overview intended for attendees. It tells them what is happening. A run sheet is a detailed operational plan intended for the event team. It tells them how it happens, when technical cues occur, and who is responsible for each segment.

What format should an Event Run Sheet be in? Excel or Google Sheets is the industry standard. The grid format allows for easy sorting and filtering. For very complex events with multiple rooms, specialized event management software like Asana, Monday.com, or dedicated tools like Cvent can be used, but the output is usually a spreadsheet-style view.

How detailed is too detailed? If the document becomes difficult to read on a printed A4 page, it is likely too detailed or cluttered. The key is grouping. Instead of listing every light change as a separate row, group them under a "Technical Notes" column for that segment. However, for "Show Call" (the actual event time), you cannot be too detailed.

Who needs to receive the Run Sheet? The "Master Run Sheet" goes to the Event Producer, Stage Manager, Technical Director, and Venue Manager. "Stripped Down" versions (containing only their specific segments) should go to speakers, caterers, and security. Don't overwhelm a VIP speaker with technical lighting cues; send them a schedule that only shows their call time and stage time.

What do I do if the event falls behind schedule? Never try to "make up time" by speeding up the current activity (e.g., asking a speaker to talk faster). This creates stress and lowers quality. Instead, use the pre-planned "flex time" or cut a later, lower-priority segment (such as a short break or a lengthy intro video). The Run Sheet should highlight which segments are "droppable" in case of delay.