How to Build an Event Run Sheet and Schedule

Step 01

Separate activity time from transition time.

Speakers changing, rooms clearing, equipment resetting and attendees moving all take time. Entering a five-minute changeover between sessions is different from making every session five minutes longer because the schedule then shows where the transition belongs.

Use the optional note for an operational cue such as ‘slides checked’, ‘doors open’ or ‘host introduces speaker’. Keep private contact details and sensitive operational information in the appropriate internal system.

Step 02

Worked example: a community workshop.

A programme contains registration for 20 minutes, opening remarks for 10, a 45-minute main session, a 15-minute break, a 60-minute workshop and a 10-minute closing. Activity time totals 160 minutes.

Five changeovers at five minutes add another 25 minutes. Starting at 09:00 produces a scheduled finish of 12:05 before any extra contingency is added.

• Scheduled span = total activity minutes + changeover minutes between activities.
• Each activity starts after the previous activity and its following changeover.
• The displayed time uses the timezone of the device building the schedule.

Step 03

Add contingency deliberately.

Do not hide every buffer inside session durations. Add visible setup, overrun or recovery blocks where the team can use them. Events with live speakers, public access, travel or technical demonstrations generally need more contingency than a small internal meeting.

For events crossing time zones or daylight-saving changes, confirm the authoritative timezone in the shared version rather than relying on an unlabeled local time.

Step 04

Checks before sharing the final schedule.

• Confirm access, setup and venue opening times.
• Check speaker, supplier and accessibility requirements.
• Assign an owner for cues and timekeeping.
• Include breaks and realistic audience movement.
• Create a simplified attendee agenda separately if the operational run sheet contains internal notes.

Step 05

Choose the export that matches the reader.

Keep the text version for a quick operational message, use the CSV when the delivery team needs to sort or extend the run sheet in Excel or Google Sheets, and use the iCalendar file when the timed activities belong in Google Calendar, Outlook, Apple Calendar or another compatible calendar.

The calendar file converts the device-local schedule into UTC instants so calendar software can display the corresponding time. Confirm the intended venue timezone after import, especially if the person building the schedule is in another location or the event crosses a daylight-saving change.

• The CSV contains start, finish, activity, duration, following changeover, note and builder timezone.
• Each activity is a separate event in the calendar export; changeovers remain visible in the following start time and event description.
• Keep internal contacts, access details and sensitive production information in an appropriately controlled system.