How to plan an event timeline
An event has two timelines. One is counted in weeks and gets you to the day. The other is counted in minutes and gets you through it. Most trouble comes from the place where they meet.
The short answer
Work backwards from the event date. Set the decisions that have the longest lead times first: venue, date, headline talent and the main vendors. Then set deadlines for everything that feeds the day itself, such as the final guest count, content and vendor arrival times. In the last two weeks, turn those decisions into a minute-by-minute schedule for the day and send each vendor the part that is theirs.
Two timelines, two jobs
- The planning timeline is a list of deadlines over weeks or months. It answers "what has to be decided by when".
- The event-day timeline is a list of times over one or more days. It answers "what happens at 6:15 PM, and who makes it happen". Producers call this a run of show.
They are different documents. A planning timeline lives well in a project tool or a spreadsheet. The event-day timeline needs start times that follow from one another, because one change moves everything after it.
A planning timeline, working backwards
These ranges suit a mid-size event such as a gala, a company meeting or a one-day conference. A larger event starts earlier.
| When | Decide or do | Why then |
|---|---|---|
| 4 to 6 months out | Date, venue, budget, the purpose of the event | Everything else depends on these. |
| 3 to 4 months out | Headline talent or speakers, caterer, production company | Good vendors book up, and their needs shape the room. |
| 2 to 3 months out | Rough program: the main blocks of the day and their order | Vendors need it to quote and plan crew. |
| 6 to 8 weeks out | Invitations out, floor plan, rentals, transport | Guests need notice. Rentals need counts. |
| 4 weeks out | First full event-day timeline, shared with vendors | Early enough to catch clashes such as a sound check during lunch service. |
| 2 weeks out | Final guest count, menus, speaker content due | Caterers and venues set their own cut-offs around here. |
| 1 week out | Event-day timeline agreed with the client and the venue | Leaves time to fix what the walk-through finds. |
| 2 to 3 days out | Final version to every vendor and crew member | Late enough to be right, early enough to be read. |
Turning the plan into the day
This is the step that gets skipped. A plan says "band booked, dinner at 6:30". The day needs more.
- Write down the fixed points. Venue access, doors, the time on the invitation, the venue's hard out, anything a contract ties to a time.
- List everything that happens, in order. Include what guests never see: load-in, sound check, room flips, meals for crew, load-out.
- Give every item a length. Start times then follow from the item before.
- Name an owner for each item. One person, not a company.
- Add the gaps. Moving a room of people takes longer than anyone expects.
The full method is in how to build a run of show, step by step.
Who gets what
The client wants the program. The caterer wants service times and their load-in. The band wants load-in, sound check and set times. Sending everyone the whole document means most of each page is not for them, and people stop reading. Send each person their part. See what to send each vendor before an event.
Common mistakes
- Only the guest-facing program is written down. The crew's day starts hours before doors.
- Deadlines with no owner. "Content due" needs a name next to it.
- The first full timeline arrives the week of the event. There is no time left to fix a clash.
- Several copies in circulation. Put a date and a version on every one you send.
myROS is built for the second timeline: the event-day schedule and the packets that go to each vendor. It is not a registration or ticketing tool, and it does not replace a project tool for the months before.
Common questions
How far in advance should I start planning an event?
For a mid-size event such as a gala or a one-day conference, four to six months is common. The date, the venue and the budget come first because everything else depends on them. A large conference or a destination event usually starts a year out.
What is the difference between an event timeline and a run of show?
An event timeline can mean either the planning schedule in weeks or the schedule for the day. A run of show is the second one: the minute-by-minute plan for the event day, with a start time, a length and an owner for each item.
When should vendors get the event-day timeline?
Send a first full version about four weeks out, even with gaps, so clashes show up early. Send the final version two or three days before the event and say what changed.
What goes on an event-day timeline that guests never see?
Load-in, sound checks, rehearsals, room flips, crew meals and load-out. These take most of the day and decide whether the guest-facing program starts on time.
Can I plan an event timeline in a spreadsheet?
Yes, and many teams do. A spreadsheet works well for the planning deadlines. For the event day, check that start times recalculate when you change a length or reorder rows, because that is where spreadsheets tend to break.