Most event-day problems are not caused by disasters. They come from small misunderstandings: the caterer arrives before the venue opens, the photographer thinks the ceremony is at four while the band thinks five. A single, shared timeline prevents nearly all of them.

What a timeline is for

A timeline, also called a run sheet or schedule, lists what happens at what time, who is responsible and where. It is not a script. It is a shared reference so every vendor can plan their own work around everyone else’s.

Start with the fixed points

Begin by writing down the moments that cannot move:

  • Ceremony start time.
  • Meal service time.
  • Key rituals, speeches or performances.
  • Venue access and curfew times.
  • Sunset, if outdoor photography matters.

Everything else is arranged around these anchors.

Work backwards for setup

For each fixed point, ask what has to be finished before it and how long that takes. Then add a buffer.

A simple method:

  1. Write the time the guests expect something to happen.
  2. Subtract the time needed for the last task before it.
  3. Subtract the time for the task before that, and continue.
  4. Add 15 to 30 minutes of buffer at each major stage.

Delays compound, so a buffer in the morning protects the whole day.

Sample event timeline

Here is a simplified example for a wedding with a ceremony and an evening reception. Adjust all times to your event.

Time Activity Responsible
08:00 Venue opens, decor team arrives Decorator
10:00 Sound and lighting setup AV team
12:00 Caterer arrives, kitchen setup Caterer
14:00 Couple preparation begins Makeup artist
15:30 Photographer arrives for details Photographer
16:30 Final venue check, seating confirmed Coordinator
17:00 Guests arrive Coordinator
17:30 Ceremony Officiant
18:15 Group and couple photographs Photographer
19:00 Reception begins, welcome drinks Caterer
19:45 Speeches MC
20:15 Dinner service Caterer
21:30 Cake and first dance MC, DJ
23:00 Closing, teardown begins All vendors

Information to include

A useful timeline is more than times. For each vendor include:

  • Name and mobile number of a person who will answer on the day.
  • Arrival time and loading access instructions.
  • Power, water and parking arrangements.
  • Setup and teardown windows.
  • Any special instructions, such as dietary needs or sound checks.

Add the venue address, a map pin, and the on-site contact on the first page.

Share it early and keep one version

Send the timeline to all vendors at least a week before the event, and again the day before with any changes. Label each version with a date so everyone can see which is current. Use one shared document or link, not several copies in different chats.

Ask each vendor to confirm they have read it. A short reply such as “Confirmed, arriving at 12:00” is enough.

Plan for the things that go wrong

Build contingencies into your plan:

  • Weather: have a wet-weather location or tent decision time, for example “decide by 10:00”.
  • Late guests or delayed ceremony: know which items can shift and which cannot, such as meal service.
  • Vendor delay: keep backup contact numbers and a person who can stand in for simple tasks.
  • Equipment failure: spare cables, batteries and extension cords cost little and save the day.

Run a final walkthrough

Before guests arrive, walk the venue with the key people. Check the layout against the plan, test sound and lights, confirm the ceremony path, and make sure every vendor knows where to park and unload.

This ten-minute walk finds issues while there is still time to fix them.

Debrief afterwards

Within a few days, note what worked and what did not. Which tasks took longer than expected? Where did vendors wait? Use the answers to improve the next timeline.

Connect the plan to your contract

A timeline works best alongside written terms. If you provide a service with fixed hours, say so in your agreement. Our event vendor contract checklist covers how to document hours, overtime and access.

Clear timing is a quiet kind of professionalism. Customers may never see your run sheet, but they will notice that everything simply worked.