An event-day run sheet is a detailed schedule that breaks down every task, supplier, and responsible person against a specific time — unlike the guest programme, which only shows what the audience will see. Without one, coordination on the day happens verbally and on the fly, which with more than a couple of suppliers involved almost always produces confusion at exactly the moments with the least room for error.
Why a run sheet is a different document from the guest programme
The guest programme shows an event as a sequence of moments the audience sees — registration, opening remarks, a break, lunch. A run sheet goes a level deeper: it covers everything that happens before, during, and after each of those moments, and who's responsible for it. Where a guest programme might run ten lines, a run sheet for the same day can easily run to a hundred — technician arrival, sound check, catering delivery, speaker arrivals, photographer setup, venue teardown.
Confusing the two documents is a common mistake — sending suppliers the guest programme instead of a run sheet leaves out exactly the information they need to know when to be on site and what to do once they're there.
What a run sheet needs to include
A good run sheet gives every item a precise time (not "morning" or "afternoon"), a responsible person with a phone contact, an exact location within the venue (not just the building name), and a note on dependencies — what has to be finished before this item can happen.
| Part of the day | What the run sheet should cover | |---|---| | Setup (before guests arrive) | Supplier arrivals, equipment build, sound check, catering setup | | Guest arrival | Who runs registration, where hosts/hostesses stand, how late arrivals are handled | | Main programme | Exact timing of each segment, transitions between them, who cues the speaker | | Breaks | Who restocks catering, how long it actually runs (not just the programme's stated length) | | Wrap-up and teardown | Who's responsible for equipment removal, when the venue needs to be cleared |
Building in time buffers
A schedule planned to the exact minute with no buffer almost always slips on the very first item — a speaker arrives two minutes late, a break runs long, a technician needs extra time to swap a microphone. A realistic run sheet builds in a short buffer at critical transitions (between the last guests arriving and the official programme starting, for example) rather than just summing up the estimated length of each item.
Buffers shouldn't be spread evenly across the day — they belong where the risk of slippage is highest: moving between an outdoor and indoor part of the programme, key guest arrivals, technically demanding transitions like a scene change or swapping speaker equipment.
Who owns the run sheet on the day
A single run sheet needs a single owner during the event — someone tracking actual time against plan and making the call on adjustments when something slips. Without that role, every supplier ends up watching only their own piece of the schedule, and nobody sees the whole picture as one delay starts cascading into the items that follow.
That person (often an event manager or production coordinator) needs the run sheet physically on hand or on their phone, not buried in an email sent a week earlier — and should have a direct line to every key supplier, not just one contact person for the whole team.
Communicating the run sheet to suppliers
A run sheet buried in a long email is easy to lose track of. It works better sent as a standalone, clearly formatted document, and for larger events, backed up with a short briefing the day before where the critical points get walked through in person or by phone — especially anywhere multiple suppliers depend on each other.
Why it's worth walking the run sheet before the event
Reading a run sheet is different from actually picturing it in motion. A short step-by-step walkthrough of the whole day — who's standing where, what's happening in parallel, where bottlenecks could form (all guests arriving in the same room at the same time catering is being carried through, for instance) — surfaces collisions that don't show up on paper. This doesn't require a physical site visit; mentally walking the schedule against a floor plan is often enough.
For recurring event formats (an annual conference at the same venue, say), it's useful to compare the new run sheet against notes from the previous year — spots that caused problems last time are highly likely to be risky again unless the programme has changed significantly.
Handling changes on the day
Even the best-prepared run sheet shifts once the event is underway — a speaker runs late, a break gets cut short, a technical problem eats extra time. The goal isn't avoiding changes entirely, it's having a clear process for getting them in front of everyone affected. A short, ongoing line of communication between the run sheet owner and key suppliers — a shared messaging group, for instance — works better than assuming everyone will notice a change on their own.
For larger events with several parallel rooms or zones, it's worth having a dedicated person tracking timing locally in each one and flagging bigger deviations to whoever owns the overall schedule. Without that structure, one person can't watch everything at once, and small delays start stacking up unnoticed.
Next step
If you're planning an event with several suppliers and need help building a run sheet that actually holds up on the day, reach out through our contact form or take a look at our services — we build the run sheet as part of full event production.