What Is a Runsheet? Your Complete Guide to Every Occasion
A runsheet is the operational backbone of any well-run event - a time-based document that tells everyone involved what happens, when it happens, and who's responsible for making it happen. Whether you're planning a wedding reception, coordinating a corporate conference, or managing a band performing at a music festival, a runsheet is what keeps the day from unravelling when things inevitably don't go to plan.
This guide covers what a runsheet actually is, what goes into one for different types of events, and - for musicians and bands - the specific details that make a performance runsheet genuinely useful on the day.
In this article:
What Is a Runsheet?
What's in a Wedding Runsheet?
What's in a Corporate Event Runsheet?
What's in a Birthday or Milestone Event Runsheet?
What's in a Public or Community Event Runsheet?
Run Sheets for Musicians
What Should a Band's Performance Runsheet Include?
What's in a Wedding Band Runsheet?
What's in a Festival Set Runsheet?
What Does a Musician Need From the Event Runsheet?
How to Write a Runsheet That Actually Works
What Is a Runsheet?
A runsheet - sometimes called a run of show, order of events, or event order - is a sequential, time-stamped document that maps out every moment of an event. It's more detailed than a general event agenda, which typically gives guests a broad overview of what to expect. A runsheet is an operational guide for your team, vendors, and any performers involved.
At its core, a good runsheet answers five questions for every item on it: what's happening, when does it start, how long does it run, who's involved, and what setup or preparation needs to happen beforehand. The format varies depending on the event type, but most runsheets share a few common columns - time, activity or item, duration, and the name of the responsible person or vendor.
Runsheets are used across virtually every event category: weddings, corporate conferences, community festivals, live music events, birthday celebrations, product launches, and more. The complexity scales with the event, but the purpose stays the same - keeping everyone on the same page so the day runs as intended.
What's in a Wedding Runsheet?
A wedding runsheet is typically the most detailed kind you'll encounter, because weddings involve multiple vendors, often two separate venues, and a timeline that needs to account for everything from the bridal party getting ready in the morning to the last song of the night. A single miscommunication between the photographer, caterer, and band can send the evening's timing sideways, which is why a thorough runsheet matters more here than almost anywhere else.
Most weddings use two related documents: a wedding day runsheet covering logistics from the morning onwards (shared with the bridal party, suppliers, and coordinator), and a reception order of events (shared with the venue, MC, and entertainment). These can be combined into one document or kept separate depending on complexity.
A wedding runsheet typically covers:
Getting ready schedule - hair, makeup, dress, departure times
Ceremony timing - arrival, processional, readings, vows, signing, recessional
Photography schedule - family group shots, bridal party portraits, couple portraits
Cocktail hour timing and catering cues
Reception arrival and room reveal
Entrée, main, and dessert service times
Speeches - names, order, and estimated duration
First dance, parent dances, and any other choreographed moments
Live music or DJ set times and scheduled breaks
Cake cutting and any traditional formalities
Bump-out and venue vacate time
For bands and entertainment specifically, the wedding runsheet will include load-in time, soundcheck window, set start and finish times, and break positions. Many coordinators pull this into a separate section and hand it to the band as their own brief, rather than sharing the full 10-page document covering catering and florist arrival.
What's in a Corporate Event Runsheet?
Corporate events range from a boardroom presentation for 20 people to a multi-day conference for hundreds of attendees, so the runsheet scales in complexity accordingly. What stays consistent is the need for clear sequencing and a named owner against every item - particularly for AV and technical moments, which can derail a program quickly if they're not precisely managed.
A corporate event runsheet typically covers:
Venue access and setup start time
AV and technical setup and testing window
Registration and guest arrival
Welcome address - speaker name and duration
Keynote presentations - speaker, topic, duration, and slide deck handover deadline
Panel sessions and Q&A windows
Morning tea, afternoon tea, and lunch breaks with catering cues
Breakout sessions - room allocation, facilitator, and duration
Award ceremonies or staff recognition moments
Networking time
Closing remarks
Bump-out and venue vacate time
Corporate runsheets often include a dedicated AV notes column - recording when to play a video, when microphones need to be swapped between speakers, when slides need to advance automatically, and when countdown clocks or holding screens should be displayed. This level of detail is what separates a professionally run event from one that spends 10 minutes fumbling with a laptop while 200 people wait.
What's in a Birthday or Milestone Event Runsheet?
Milestone celebrations - 21sts, 30ths, 50ths, engagements, baby showers, retirement parties - are often run without a professional event coordinator, which makes having a runsheet even more valuable. Without one, the MC is guessing when to call speeches, the caterer is out of sync with entertainment, and guests spend long stretches waiting for something to happen.
A birthday or milestone event runsheet typically covers:
Guest arrival window
MC welcome and introductions
Entrée service
Speeches - who's speaking, in what order, and the MC's cue
Main course service
Entertainment - live music set times, DJ program, or other activations
Cake presentation and birthday song
Dessert or late-night food
Special moments - slideshow, video message, surprise guest appearance
Music transitions across phases of the evening
Venue bump-out time
Even a one-page version with times written in the margin helps everyone stay aligned. The goal isn't a perfect document - it's making sure the MC, the venue, and the entertainment are all working from the same timeline.
What's in a Public or Community Event Runsheet?
Public events - outdoor markets, music festivals, community fairs, charity galas, sporting presentations - involve the largest number of stakeholders and the highest risk of things running off-schedule. A runsheet here functions as a coordination document that multiple teams reference simultaneously: stage managers, site managers, volunteer coordinators, and vendor teams all draw from it.
A public event runsheet typically covers:
Site access and bump-in schedule for vendors, stalls, and stage teams
Volunteer and staff briefing time
Gates open and public arrival time
Stage program - act names, set times, set durations, and changeover windows
Public address announcements - timing, content, and who delivers them
Food and beverage service windows
Special activations, demonstrations, or community acknowledgements
VIP or guest of honour arrival and formal welcome
Regulatory requirements - noise curfew, capacity checks, safety announcements
Emergency procedures note and contact list
Gates close and public exit
Bump-out schedule by zone
For multi-stage events, each stage typically has its own runsheet that feeds into a master document. Stage managers work from the individual stage sheet; the event director works from the master. Both need to be kept in sync throughout the day.
Run Sheets for Musicians
Whether you're performing solo, as a duo, or with a full band, having your own runsheet - separate from the event's master document - is what keeps your logistics tight on the day. The event coordinator's runsheet tells you when you're playing. Your own musician's runsheet tells you everything else: when to arrive, when to eat, how the sets are structured, and who to call if something goes wrong.
What Should a Band's Performance Runsheet Include?
A band performance runsheet is an internal document covering the operational side of a gig. It runs in parallel to the event runsheet but goes deeper on what the band specifically needs to manage. This document is typically prepared by the band leader or booking manager and shared with all members before the event.
A band performance runsheet typically includes:
Venue name and full address
Load-in time and parking notes
Soundcheck time and expected duration
Break between soundcheck and performance start
Vendor meal time, if provided by the venue
Set structure - set 1 start time, duration, break window, set 2 start time, etc.
Set lists per set, if confirmed in advance
Any key event moments requiring a specific music cue (first dance, grand entrance, finale)
Bump-out time and any venue access restrictions
This document is separate from the set list - it's the operational wrapper around the music. A band that arrives without it is relying on memory and text messages, which tends to cause problems on the day.
What's in a Wedding Band Runsheet?
A wedding band runsheet is more detailed than a standard gig sheet because the band is woven into the event's narrative. Specific songs align with specific moments - the first dance, the walk-in, the final song of the night - and the timing between those moments matters to the couple, the venue, and the MC.
A wedding band runsheet typically includes:
Load-in and bump-in window, noting any venue access restrictions
Soundcheck schedule, including whether guests will be present and what areas are accessible
Ceremony music requirements, if the band is performing at the ceremony - prelude, processional, signing music, recessional
Cocktail hour set - start and finish time, style of music, band configuration (solo, duo, or full band)
Reception dinner or background music phase
First dance song - confirmed title and key if transposing
Parent dances
Full band performance sets - start times, durations, and break positions
Any venue-imposed curfew or volume restrictions
MC and band communication cues - how does the MC signal the band to begin?
Venue contact on the day
Bump-out time
Having this as a standalone brief - separate from the wider wedding runsheet - means band members can reference it independently without wading through florist timelines and catering schedules. The band leader can prepare it from the master runsheet, then distribute only the relevant sections to each performer.
What's in a Festival Set Runsheet?
A festival set runsheet is leaner than a wedding runsheet, but precision matters more because stage changeovers at festivals are timed to the minute. Arriving late to stage or running over your set time affects every act after you on the program.
A festival set runsheet typically includes:
Festival name, stage name, and stage location on site
Stage manager contact name and number
Bump-in time - often 15 to 20 minutes before set time, sometimes less
Soundcheck window, if one is allocated (not always guaranteed at festivals)
Set start time - hard, non-negotiable
Set duration - hard, with a note on how the stage manager will signal time
Set list in performance order
Click tracks, backing tracks, or specific technical requirements
Load-out timing and who handles gear removal from stage
Backline sharing notes, if sharing equipment with another act
Festival runsheets rarely accommodate flexibility, so the key information is knowing exactly what time you're on, how long your setup window is, and who to report to on arrival. Anything else is secondary.
What Does a Musician Need From the Event Runsheet?
Bands and musicians don't need the full event runsheet - they need the sections that directly affect their performance. When receiving an event runsheet from a client or coordinator, these are the key details to pull out and keep accessible on the day:
Load-in and venue access time
Whether there's a designated loading zone or time slot
Soundcheck window and whether guests will be present
When vendor meals are served
Performance start times and set durations
Any key event moments that require a live music cue
Venue contact on the day
Bump-out time and any venue restrictions on pack-down
If the event runsheet doesn't clearly include these details, contact the coordinator to confirm them before the day. A band briefing document that extracts just the musician-relevant items - separate from the full event runsheet - is the cleanest way to brief everyone in the group and make sure no one is working from outdated information.
How to Write a Runsheet That Actually Works
The best runsheets are specific enough to be useful without being so dense that nobody reads them past page one. A few principles hold true across every event type.
Use real clock times, not countdowns. "7:30 PM - First dance" is more useful than "T+90 minutes - First dance." On event days, people think in clock time - they're not mentally tracking minutes from an anchor point set three hours earlier.
Assign a person to every item. If the runsheet doesn't say who's responsible for a cue, nobody is responsible for it. The most common point of failure on event days isn't that nobody planned something - it's that two people assumed the other was handling it.
Build in buffer time. Events run late. If speeches are allocated 20 minutes but realistically take 35, the runsheet needs to absorb that without breaking the second half of the evening. Padding between key moments, even by five minutes, gives you room to recover without a cascade of delays.
Circulate it early and update it consistently. The runsheet issued three weeks out will change. Use a clear version number or "last updated" date on every document, and make sure every vendor is working from the same current version on the day.
Keep a master and a simplified version. The full master is for you, your coordinator, and key vendors. A simplified version - covering only the key moments - is what you share with the MC, band members, or anyone who only needs to know their part.
A one-page runsheet that everyone reads and understands will always outperform a comprehensive document that nobody finishes. Start with what matters most, and add detail where it's genuinely needed.
