Back to journal
Operations3 min read

Day-of-Event Run Sheet: The Format That Keeps Everyone Aligned

Adapt the sample run sheet with times, actions, owners and dependencies. Keep one version and an accessible contact panel for the event team.

Written byBookaBooking guides

Last reviewedBooka

An event producer reviewing the run sheet backstage before guests arrive
Booka Journal / South Africa

The short answer

What to know before you start

Use one run sheet with time, action, owner and dependency columns, plus a version date and urgent contacts. Share the final version with every supplier. The sample below is a template to adapt, not a schedule required by Booka.

At a glance

Day-of-Event Run Sheet: The Format That Keeps Everyone Aligned quick facts
Version ownerOne organiser maintains the schedule and distributes changes.
Each rowTime, action, responsible person and prerequisite.
RecoveryAgree buffers and who may change the order.

Publish one version everyone trusts

Give the run sheet an event name, date, version time and owner. Send the same version to the venue, providers and decision makers.

When a timing changes, name the affected rows and ask the relevant people to acknowledge the update. Do not assume that sending a new attachment means everyone has read it.

Show dependency logic, not just schedule rows

Include the condition that makes each activity possible. A soundcheck depends on equipment access and power; a speech depends on the speaker and microphone being ready.

Illustrative evening-event run sheet — replace names and times

Scroll across to read every column.

Illustrative evening-event run sheet — replace names and times
TimeActionOwnerDependency
15:00Venue opens for setupVenue leadAccess and power available
16:00SoundcheckSound leadEquipment installed
17:00Guests arriveHostGuest areas and welcome music ready
18:00Welcome speechMCSpeaker and microphone confirmed
18:15Meal serviceCatering leadHost releases service
19:30Entertainment startsPerformerMC gives agreed cue
22:00Guest programme endsEvent leadTransport and exit plan ready
22:15Pack-downSupplier leadsGuests clear; venue permits access

Build realistic recovery buffers

Ask each provider how much setup and transition time their work needs. Put buffers where one delayed activity would block several others.

If a delay uses up a buffer, the decision maker should confirm what can move or shorten. Do not automatically extend paid supplier hours or move safety-critical work to recover time.

Add a rapid response panel

Keep urgent contacts and fallback actions on the same document, shared only with the people who need them. Identify who can approve extra cost and who directs guests.

Run-sheet contact panel

Version/owner: [date, time and name]
Venue lead: [contact]
Event decision maker: [contact]
Technical lead: [contact]
Provider contacts: [contacts]
Weather/fallback location: [agreed plan]
Extra-cost approval: [person and limit]
If a key person is delayed: [who informs whom]

Next step

Need smoother day-of coordination?

Manage booking details, supplier updates, and critical messages from one place.