An event run sheet is the shared working schedule that turns an event plan into coordinated action. It records what happens, when it happens, where it happens, who owns it, which supplier or team member is involved, and what must happen first.
You may also hear it called an event schedule, running order, or run of show. The labels vary, but the purpose is similar: give the working team one clear operational document for moving from venue access and setup through guest departure and pack-down.
Quick summary
- Build the schedule from setup to pack-down, not only around the headline programme.
- Give every important action a time, location, accountable owner, supplier, cue, dependency, and contingency.
- Use buffers before high-consequence transitions such as ceremonies, performances, speeches, room changes, and transport movements.
- Use an operational version for the event team and a simpler guest-facing order of the day where needed.
- Issue one approved version with clear version control after a final walkthrough or rehearsal.
What Is an Event Run Sheet?
An event run sheet is a detailed coordination document for the people delivering an event. It links the programme to practical operations, including venue access, supplier arrivals, room preparation, technical checks, catering, guest movement, announcements, performances, photography windows, and closing tasks.
A broad event schedule may show only major milestones. A guest-facing running order may show when guests should arrive, eat, watch a performance, or leave. A production run of show is usually more detailed, with cues for the MC, technical team, lighting, sound, stage management, and backstage handoffs. One event can need all three versions.
The run sheet does not replace supplier contracts, venue requirements, risk assessments, permits, insurance documents, or legal records. In England and Wales, GOV.UK refers to a marriage schedule or marriage document as the legal ceremony record. That is separate from the operational schedule used to coordinate a wedding day.
For a multi-stage celebration, treat the run sheet as a live control document. It should help the team answer five questions quickly: what is happening now, what happens next, who is responsible, what could block it, and what is the fallback plan?
Event Run Sheet Template: The Essential Columns
Set up your document as a spreadsheet or shared table. Use one row for each meaningful action, cue, handoff, or checkpoint rather than placing an entire programme section in one vague row.
| Column | What to record | Why it matters |
|---|---|---|
| Date | Event date or setup day | Prevents confusion when access, rehearsal, and event dates differ. |
| Start and finish | Planned start, end, and duration | Shows the true time available and exposes clashes. |
| Activity | Specific task, programme item, or cue | Makes the action clear enough to brief and complete. |
| Location | Room, entrance, stage, loading area, or holding room | Helps people and suppliers move to the right place. |
| Accountable owner | One person responsible for making it happen | Prevents shared responsibility becoming no responsibility. |
| Supplier or support team | Caterer, venue, DJ, AV team, photographer, transport contact, or family representative | Clarifies who contributes. |
| Status | Guest-facing, backstage, setup, live, or complete | Separates visible programme moments from operational work. |
| Cue | Announcement, music start, lighting change, slide, or signal | Connects the action to its trigger. |
| Dependency | What must be ready first | Shows why one delay may affect another task. |
| Equipment or materials | Microphones, signage, menus, props, place cards, instruments, or documents | Reduces last-minute omissions. |
| Contact | Relevant phone number or communication channel | Allows quick issue resolution. |
| Contingency | Fallback action if the plan cannot proceed | Turns disruption into a prepared decision. |
| Completion | Not started, in progress, complete, or issue raised | Supports live tracking. |
For complex corporate programmes, a run sheet and supplier plan keeps responsibilities, timings, and handoffs visible from setup through on-site delivery. Keep the main sheet readable, then add separate tabs for contacts, equipment, guest lists, seating, or technical specifications.
How to Build the Run Sheet From Setup to Pack-Down
1. Start with objectives and constraints
Record the event purpose, guest arrival window, venue access times, fixed closing time, key programme moments, and non-negotiable rituals or presentations. Note restrictions such as noise limits, catering windows, room capacities, loading access, parking, or a required departure time.
2. Add venue access and supplier arrivals
Begin with the earliest operational activity. Include venue opening, decorator and production access, deliveries, unloading, room preparation, furniture placement, floral installation, signage, catering setup, and supplier briefings.
Do not assume every supplier can arrive whenever convenient. Add a dependency for each major arrival, such as the venue being unlocked, a loading route being available, or a room being cleared before décor installation begins.
3. Schedule technical and programme checks
Add sound, microphone, presentation, lighting, music, stage, catering, and rehearsal checks before guests arrive. A performance should not simply appear as “7:30 p.m. entertainment.” Record the performer call time, sound check, holding point, introduction, performance slot, finish cue, and equipment removal.
4. Map the guest journey
Continue with arrival, registration or greeting, cloakroom, drinks reception, seating, ceremony, meal service, speeches, performances, networking, and departure. Include transitions between rooms and allow time for people to move, not just the formal activity itself.
5. Close the event properly
Finish with guest departure, final announcements, music finish, collection of personal items, supplier strike, equipment removal, waste checks, venue sign-off, and any next-day collection. A schedule that ends at the last speech leaves practical work undocumented.
A minute-by-minute run of show helps coordinate guest arrival, production cues, service standards, and contingencies when an event has many moving parts.
Assign Responsibilities and Make Handoffs Visible
Every critical row should have one accountable owner, even when several people support the task. Typical roles include the client or event owner, planning lead, venue contact, production or technical lead, MC, caterer, entertainment lead, photographer or videographer, transport contact, and emergency contact.
Handoffs deserve their own rows. Instead of writing “speeches,” record who confirms speakers are ready, who tells the MC, who checks microphones, who cues the presentation, and who releases the caterer to serve afterward.
- Owner: Who confirms completion?
- Support: Which supplier, colleague, or family member helps?
- Input: What person, item, approval, or information is required?
- Handoff: What is passed to whom, and by when?
- Escalation: Who decides if the plan cannot proceed?
Add Buffers, Dependencies, and Contingencies
Small delays cascade when there is no recovery time between activities. Build buffers before high-consequence transitions, such as a ceremony, product reveal, meal service, first dance, performance block, room turnover, or scheduled transport movement.
For weddings and other multi-stage celebrations, transport-friendly timelines can prevent travel delays from cascading through the schedule. Include realistic movement time between venues, rooms, parking areas, preparation spaces, and guest seating.
Use this contingency format:
- Risk: What might go wrong?
- Trigger: How will the team know action is needed?
- Decision owner: Who chooses the response?
- Fallback action: What happens instead?
- Communication method: How will suppliers and guests be informed?
Examples include moving a ceremony indoors if weather changes, shortening networking if registration runs late, using a backup microphone, delaying a performance during a technical issue, or changing a photography window. The contingency should be practical and authorised, not an open-ended instruction to “be flexible.”
Adapt the Template for Different Events
A generic event run sheet is a starting point, not a finished plan. The right emphasis changes according to the audience, programme, cultural requirements, supplier count, and production complexity.
Corporate events, launches, conferences, and galas
Prioritise registration, brand presentation, speaker arrivals, presentation files, AV checks, product reveal cues, networking, catering, media capture, and closing announcements. Add a clear approval route for programme changes involving executives, clients, presenters, and technical teams.
Illustrative example: a product launch row might include presenter ready, reveal asset loaded, lights set, MC introduction, reveal cue, photography position, applause window, and transition to demonstrations. Each item needs an owner and dependency.
Weddings, sangeets, and multi-stage celebrations
Map each ceremony and celebration separately, including preparation, processions, family roles, officiant requirements, outfit changes, performances, speeches, meals, photography windows, guest movement, and venue transitions. Confirm the order and duration of cultural rituals with the couple, families, and relevant officiants rather than assuming a standard sequence.
Use an operational version for suppliers and a simpler order of the day for guests where appropriate. The supplier version may include staging, sound checks, family call times, and contingency actions.
Private celebrations and destination events
For birthdays, anniversaries, milestone dinners, and thematic parties, focus on guest arrival, décor installation, food service, entertainment, speeches, photographs, and the host’s key moments. Destination events require additional attention to accommodation or transport coordination, remote approvals, local supplier access, weather, venue rules, and communication across locations.
Pre-Event Review Checklist
- Are the event date, time zone, venue, and document version correct?
- Do setup, arrival, programme, departure, and pack-down connect without unexplained gaps?
- Does every critical row have one accountable owner?
- Are supplier, venue, emergency, and escalation contacts current?
- Are venue access, loading, room turnover, technical checks, and catering dependencies included?
- Have travel, guest movement, rituals, speeches, performances, and outfit changes been timed realistically?
- Are weather, equipment, supplier delay, speaker absence, and late-running contingencies documented?
- Have legal, venue, safety, insurance, and permit documents been checked separately?
- Has the team completed a walkthrough, rehearsal, or cue-to-cue review where appropriate?
- Has one person approved the final version and recorded later changes?
Use a controlled master copy and a short change log. If a timing changes on event day, record what changed, who approved it, and which suppliers need to know.
When a Run Sheet Needs Professional Coordination
Professional coordination becomes particularly useful when an event includes multiple rituals, several venues, complex production cues, a large supplier team, destination logistics, or a client team without enough time to manage live operations.
Patel Events describes its planning work as covering strategy, design, logistics, supplier coordination, rehearsals, showcalling, on-site delivery, and contingency planning. Its stated experience spans weddings, sangeets, corporate events, private celebrations, and destination events, supported by 27+ years, more than 500 events executed, and a network of 50+ trusted vendors.
Frequently Asked Questions
What is the difference between an event run sheet and a running order?
A running order normally lists the sequence and timing of visible programme items. An event run sheet is broader and more operational, including setup, suppliers, owners, technical cues, dependencies, guest movement, and contingencies.
How far in advance should an event run sheet be created?
Start a working version as soon as the venue, date, format, and major programme elements are known. Build detail as suppliers and timings are confirmed, then complete a final review after the walkthrough or rehearsal.
Who should receive the final event run sheet?
Share the relevant operational version with the event owner, planning lead, venue contact, key suppliers, MC, production or technical team, caterer, entertainment team, and anyone responsible for a critical handoff.
Should guests receive the same run sheet as suppliers?
Usually not. Guests need a simple order of the day. Suppliers need access times, call times, cues, contacts, dependencies, and contingency instructions.
How do you add cultural ceremonies and performances to a wedding run sheet?
Give each ceremony or performance its own rows for preparation, participants, location, start cue, duration, supporting suppliers, photography requirements, and transition afterward. Confirm the sequence with the couple, families, and officiants.
Does an event run sheet replace a venue risk assessment or legal ceremony document?
No. It is an operational coordination tool. Venue requirements, risk assessments, permits, insurance documents, contracts, and legal ceremony records remain separate documents.
Conclusion: Turn the Plan Into a Shared Operating Document
The best event run sheet is more than a list of times. It connects people, places, suppliers, cues, dependencies, handoffs, guest movement, and fallback actions so the team can make informed decisions while the event is live.
Build the first version early, start with setup and finish with pack-down, test it through a walkthrough or rehearsal, and issue one approved copy with clear version control. Adapt the detail to the event rather than forcing every celebration into the same format.
For support with event strategy, design, logistics, supplier coordination, rehearsals, and on-site delivery, contact Patel Events, a London-based event planning and management company serving events across the UK and beyond.