Wedding day timeline: how to build the minute-by-minute schedule
A wedding timeline is the document that says what happens, at what time, where and who’s in charge, from the moment the first vendor arrives until the last one leaves. Built well, every vendor knows their part and you only deal with what slips.
This article is for wedding planners and wedding organizers who want to stop improvising it every time. How to sell day-of coordination as a service I covered in selling day-of wedding coordination; here we focus on the document itself.
There’s no typical schedule: there are constraints
First: there’s no standard timeline that works for every wedding. Each one is built from that day’s constraints, and your job is to gather them before writing a single time:
- The venue: from what time you can get in to set up, until what time you can stay, whether there’s a curfew on music and when everything has to be torn down.
- The ceremony: whether it’s civil, religious or symbolic, where it’s held and how long it lasts. If it depends on a third party (a registry office, a church, an officiant), their schedule rules and isn’t negotiable.
- Travel: how long it takes from the ceremony to the venue at that time of day, and whether guests travel on their own or in hired transport.
- Each vendor: how long they take to set up and tear down, what they need (power, space, a table, water) and how many hours they’re booked for.
- What the couple wants no matter what: an entrance, a dance, a speech, a surprise. Ask at the first meeting, not the week before.
With that in hand, the timeline almost builds itself. Without it, you’re making up times.
How to build it, step by step
An order that works:
- Start from what doesn’t move. Ceremony, venue closing time and the DJ’s or band’s booked hours. Those are your posts.
- Place the big blocks between the posts. Reception, entrance into the venue, meal, dancing, close. No minutes yet.
- Break each block into moments. For example, the entrance into the venue splits into: guests seated, cue to the DJ, couple’s entrance, first toast.
- For each moment, write down who does what. “Toast” isn’t enough: who tells catering, who lowers the music, who hands the microphone to the speaker.
- Backwards, the setup. What time each vendor arrives to be ready in time, and in what order, so they don’t collide at the loading door.
- Forwards, the teardown. Who leaves first and who checks nothing is left behind.
An example, purely as an example
This fragment is an example built to show the format, not the times. Yours come from each wedding’s constraints:
| Time | What happens | Where | Who | Notify |
|---|---|---|---|---|
| 8:30 pm | Guests seated | Hall | Venue team | Coordination |
| 8:40 pm | Music down, entrance cue | DJ booth | DJ | Couple, photo and video |
| 8:45 pm | Couple’s entrance | Main door | Coordination | Catering |
| 8:55 pm | Toast and words from a relative | Dance floor | Relative with microphone | DJ |
| 9:05 pm | First course goes out | Kitchen | Catering | Coordination |
What matters in the example isn’t the times but the columns: each row has someone responsible and someone to notify. If a row has nobody responsible, that moment will fail.
Buffers: where to put them and how big
Buffers aren’t spread evenly: they go where the schedule slips most. The usual places:
- Before and after the ceremony, especially if there’s travel or it depends on a third party.
- The couple’s arrival at the venue, which is almost never at the agreed time.
- The first food service, which depends on guests being seated.
- Setup, if one vendor arrives after another and needs the first to finish.
How much buffer to leave depends on each wedding and on what you’ve seen at previous ones. What does help: noting after every event how much each moment slipped. With a few dates logged, your buffers stop being guesswork. It’s the same logic of calculating by real pace rather than the peak that I explain in how many staff an event needs.
Who gets it (and which version)
Not everyone needs the same document. What works is one full version and several short ones:
- Full version: for you and your team. Everything, with setup, teardown, phone numbers and plan B.
- Vendor version: each one gets their arrival time, their setup, the moments when they’re involved and a day-of phone number. Catering doesn’t need to know when the florist arrives, but does need to know when the couple enters.
- Couple’s version: the important moments, without the logistics.
- Version for the family member the couple picks: someone who knows where they need to be and who to call.
Send it with time to spare, ask each vendor to confirm they’ve read it and send the final version a few days before, with the version date in the title. That way nobody works from an old schedule.
If you work with assistants, the full timeline is also your roadmap for delegating. I cover that in delegating an event to a coordinator.
The plan B, in writing
Plan B isn’t “we’ll see on the day”. It’s a short written list of what fails most and what you do in each case:
- Rain, if anything is outdoors: where it moves to, who moves what and how fast. Decide in advance at what time the call is made and who makes it.
- A vendor arriving late or not at all: who gets called, which moment shifts and what can be skipped.
- The ceremony runs late: which blocks get shortened afterwards, based on what the couple said matters to them.
- Someone feels unwell: where the first aid kit is, who has the venue’s emergency number.
Two lines per case are enough: what happens and who decides. The couple shouldn’t find out about almost any of them.
Frequently asked questions
How far ahead should I start the timeline?
Far enough ahead to talk to every vendor and get their confirmation. An early first draft, a round with vendors afterwards and the final version a few days before. Set your own deadlines in your proposal and stick to them.
Should I use a spreadsheet or a document?
Whatever is easiest for you to keep up to date. A spreadsheet with fixed columns (time, what, where, who, notify) lets you filter by vendor and build the short versions without rewriting. What matters is that there’s only one current version.
What if the couple changes something the week before?
You change it, let the affected vendors know and send the new version with a date. If the change adds hours or work that wasn’t in your proposal, say so at that moment, not afterwards.
Organizing your wedding business, with me
Having a standard timeline, a proposal that says what each service includes and fees that cover all the real hours is part of what we can work on, so the business doesn’t depend on you doing everything yourself. The first 30-minute call is free. Message me on WhatsApp and I’ll tell you whether it’s a fit.
