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

An event run sheet is the single document your entire team reads on event day. It lists every activity in chronological order with exact times, locations, responsible people, and notes. Unlike a planning checklist that covers weeks of preparation, a run sheet focuses on one day: what happens, when, where, and who owns it. It is the execution layer of your broader event planning workflow, turning strategy into a document your crew can follow in real time.

The difference between a smooth event and a chaotic one often comes down to whether the run sheet was built with enough detail and shared early enough. This guide walks through how to create an event run sheet from scratch, with practical structure, real timing logic, and a system for handling changes when the day does not go as planned.

Define the Run Sheet Structure

Every run sheet needs five columns. Skip any of them and your team will spend the day asking questions instead of executing.

Time. Use a 24-hour clock format (14:00, not 2 PM). This eliminates confusion for vendors who work across time zones or handle multiple events in a day. Include both start and end times for each block.

Activity. Describe the task in five words or fewer. "Florist setup, main hall" is better than "The florist arrives and begins setting up arrangements in the main hall." Your team needs to scan the sheet in seconds, not read paragraphs.

Location. Specify the exact area within the venue. "Loading dock B" is useful. "Venue" is not. For multi-room events, this column prevents half your team from standing in the wrong place.

Lead. Name the person responsible for confirming this task is complete. Not the company name. The actual human your team will call if something goes wrong. Include their phone number in a separate contact appendix so the main sheet stays clean.

Notes. Reserve this for exceptions, dependencies, and warnings. "Cannot start until AV check is complete" or "Venue charges overtime after 23:00" belong here. General reminders do not.

If you have already built an event communication plan, use it to identify who needs to receive the run sheet and in what format. Some team leads prefer a printed copy. Vendors often want a digital version they can reference on their phones.

Map the Full Timeline with Buffers

Start by listing every activity from the first vendor arrival to the final pack-down. Most planners underestimate this step because they think of the event as the program itself. In reality, a 4-hour wedding reception requires 10 to 12 hours of run sheet coverage: load-in, setup, rehearsal, guest arrival, ceremony, reception, teardown, and venue handback.

Work backward from the first public moment. If guests arrive at 16:00, the venue needs to be fully set and the team briefed by 15:30. That means setup completion by 15:00, vendor load-in starting by 12:00, and your advance team on-site by 11:00. Each milestone creates a deadline for the previous block.

Build 15-minute buffers between every transition. Transitions are where run sheets break. The caterer finishes plating, and the emcee needs to announce dinner. If your sheet shows the kitchen wrapping at 19:00 and the dinner call at 19:00, you have zero margin. Set the dinner call at 19:15 and use those 15 minutes to confirm the food is staged, the service team is positioned, and the AV team has the right music queued.

Double buffer high-risk blocks. Anything involving guest movement (ceremony to cocktail hour, cocktail hour to reception room) takes longer than you expect. Add 20 to 30 minutes for these transitions. A corporate gala with 300 guests cannot move between rooms in 10 minutes, regardless of what the venue sales manager promised during the site visit.

For a deeper breakdown of the logistics behind these transitions, our event logistics planning guide covers load-in sequencing, vendor arrival windows, and access point mapping.

Assign Ownership and Contact Chains

A run sheet without names is a wish list. Every line item needs a lead who is accountable for execution and empowered to make decisions if something goes sideways.

Assign one lead per block, never two. Dual ownership means nobody owns it. If the DJ and the lighting tech both "own" the dance floor transition, neither will take charge when the fog machine triggers the fire alarm. Pick one. The other is support.

Create a contact appendix. List every vendor, team member, and venue contact with their name, role, phone number, and the specific run sheet blocks they are involved in. Keep this as a separate sheet or a second page. Printing it on the same page as the timeline makes both harder to read.

Identify your decision chain. When the caterer calls at 17:45 to say they will be 30 minutes late, who decides whether to shift the dinner timeline or extend the cocktail hour? Build this into the run sheet header: "Timeline changes during event: contact [Lead Planner name] at [phone]. If unreachable, [Backup name] has authority."

If you manage a team of coordinators, our guide on how to brief event staff covers the pre-event walkthrough process that turns a run sheet from a document into shared understanding.

Build Contingency Notes into the Sheet

Most run sheet templates treat contingency as a separate document. That is a mistake. When something goes wrong at 18:30, nobody pulls out a second binder to look up Plan B. They look at the run sheet. Put the backup instructions right where the team will see them.

Add an "If delayed" note to every high-risk block. Next to "18:00, Ceremony begins," add a note: "If delayed past 18:20, cut processional music to two songs. Notify caterer to hold plated starters." This gives your team a decision framework without waiting for a phone call.

Flag weather-dependent blocks. Outdoor events need a clear trigger point for the indoor backup. "If rain at 15:00, move ceremony to Ballroom B. Florist redirects arrangements (30 min). Chairs stay outdoor under tent for cocktails." Write this on the run sheet, not in an email from three weeks ago.

Mark vendor dependencies. Some tasks cannot start until another finishes. If the lighting rig cannot go up until the staging company finishes the platform, note the dependency explicitly: "Lighting setup. Depends: stage build complete. Delay impact: 1:1 (every hour of stage delay = one hour lighting delay)."

Your event risk management plan should inform these notes. Review it during run sheet creation and pull the most likely scenarios directly into the timeline.

Distribute, Brief, and Update Live

A run sheet that lives on your laptop helps nobody. Distribution and live management are what separate a useful document from a pretty spreadsheet.

Send the run sheet 72 hours before the event. This gives vendors and team members time to flag conflicts, ask questions, and adjust their own schedules. Send it as a PDF (not an editable doc) with a clear version number in the filename: "RunSheet_v3_Johnson-Wedding_2026-06-28.pdf."

Hold a 15-minute team briefing the morning of. Walk through the run sheet with your on-site team. Do not read every line. Focus on the three blocks most likely to go off-script and confirm who owns each one. This is also when you distribute printed copies. For a full briefing framework, see our event staff briefing guide.

Manage live updates through a single channel. When the timeline shifts during the event (and it will), announce changes through one communication method. If your team uses radios, call out the change on the main channel. If you use a group chat, post the update there. Never split updates across channels. The person who missed the radio call and did not check the chat is the person who will run the old timeline.

Log actual times next to planned times. After the event, compare planned versus actual for every block. This data is gold for future run sheets. If cocktail-to-dinner transitions consistently take 25 minutes instead of your planned 15, update your default buffer for the next event.

Tracking vendors, timelines, and contacts across multiple events is where dedicated tools save hours. Abastio centralizes your contractor database, event timelines, and budget tracking in one dashboard, so the information feeding your run sheet is always current instead of scattered across spreadsheets and email threads. You can explore the full feature set on the pricing page.

Frequently Asked Questions

What is the difference between a run sheet and a run of show?

They cover the same concept. "Run sheet" is more common in the UK, Australia, and corporate event circles. "Run of show" is the preferred term in the US entertainment and production industry. Both refer to a chronological timeline of every activity during an event day, including setup and teardown. Use whichever term your team and vendors recognize.

How far in advance should I create the event run sheet?

Start the first draft two weeks before the event, once vendor contracts are signed and the program is confirmed. Refine it during the final week as you confirm load-in times, headcounts, and vendor contacts. Lock the final version 72 hours before the event and distribute it as a PDF. Last-minute changes after distribution should go through a single update channel, not a new version of the document.

How detailed should each entry on the run sheet be?

Each entry should take five seconds or fewer to read. Use short descriptions (five words maximum for the activity column), exact times in 24-hour format, specific locations within the venue, and one named lead per task. Save longer explanations for the notes column, and only when they affect execution. If your team needs to read a paragraph to understand a task, the entry is too long.

Should vendors receive the full run sheet or only their sections?

Send vendors the full run sheet. They need context beyond their own tasks to coordinate with other teams on-site. A caterer who knows the ceremony ends at 18:30 can time their plating accordingly, even if their first listed task is at 19:00. Redact pricing or client-sensitive notes if needed, but do not strip the timeline down to isolated blocks.

How do I handle run sheet changes during the live event?

Designate one person as the timeline controller. All changes go through them, and they announce updates through a single channel (radio, group chat, or in-person runners). Never split updates across multiple channels. When a block runs late, the controller references the "if delayed" notes on the run sheet and makes the call. After the event, log the actual times next to planned times to improve future run sheets.