The day-of timeline is the one document every vendor will ask for and no one teaches you to write. It has to coordinate a photographer, a caterer, a DJ, an officiant, two families, and a wedding party — most of whom have never met — down to the quarter hour. Written well, the day runs itself and you get to be present at your own wedding. Written badly (or living in six slightly different versions), the day runs on group texts.
The five phases
Every wedding day, whatever its style, decomposes into the same five phases. Build the timeline phase by phase, then fill in events:
- Getting ready (3–4 hours). Hair, makeup, photos of the details, the quiet hour nobody regrets scheduling.
- Ceremony (20–40 minutes, plus the 30-minute pre-seat window).
- Cocktail hour (60–90 minutes — it's covering photos, room flip, or both).
- Reception (4–5 hours: entrance, dinner, toasts, dances, party).
- Send-off (15 minutes that require more coordination than they look like).
A real timeline, with the math showing
Here's a 5:00 pm ceremony wedding, worked backward and forward. The specific times matter less than the durations and buffers — steal those.
| Time | Event | Note |
|---|---|---|
| 12:00 pm | Hair & makeup final round | Started 9:00 for a party of six |
| 1:30 pm | Photographer arrives | Details first: rings, invites, dress |
| 2:00 pm | First look + couple portraits | 45 min, private |
| 3:00 pm | Wedding party photos | 45 min |
| 3:45 pm | Family formals | 30 min — use a shot list, assign a wrangler |
| 4:15 pm | Couple hides; buffer | The load-bearing 15 minutes |
| 4:30 pm | Guests seated; prelude music | Officiant confirms license location |
| 5:00 pm | Ceremony | 25 min per the script |
| 5:30 pm | Cocktail hour; room flip if needed | Couple joins last 20 min or skips |
| 6:30 pm | Grand entrance | DJ has phonetic name list |
| 6:40 pm | First dance | While everyone's already watching |
| 6:50 pm | Dinner service | Vendor meals served now too |
| 7:30 pm | Toasts | Three speakers, 4 min each. Enforce this |
| 7:50 pm | Parent dances | |
| 8:00 pm | Dance floor opens | |
| 9:45 pm | Last call; cake or late snack out | |
| 10:15 pm | Last dance (guests) | |
| 10:30 pm | Send-off | Coordinator staged exit items at 10:00 |
The rules that make it survive contact
Buffer is a scheduled event, not leftover time. The 4:15 "couple hides" block above isn't slack — it's what absorbs the 20 minutes that family formals will run over. Put 15 minutes of named buffer before the ceremony and before the entrance. If nothing goes wrong, you get water and a moment alone with your almost-spouse. Nothing about that is wasted.
Work backward from fixed points. The ceremony time and the venue's hard end are immovable; everything else derives. Sunset is a semi-fixed point too — ask the photographer what month-and-latitude golden hour you're working with before setting the ceremony time, not after.
Every event gets an owner. Not "toasts at 7:30" but "toasts at 7:30 — DJ cues, best man first." On the day, the timeline's owner is not you. A coordinator, a ruthlessly organized friend, an aunt with lanyard energy — someone whose job is to look at the clock so you never do.
One master, many views. The photographer cares about light, the caterer about service times, the DJ about announcements. They can each get their slice — but derived from one master document, so a change propagates instead of forking. Six vendors with six PDFs is how dinner lands during the toasts.
Feed the vendors when you eat. It's in most contracts anyway, and a photographer who eats at 6:50 is back shooting by toasts. Schedule it or lose your photographer to a sandwich at exactly the wrong moment.
Distribution: the last mile
The timeline fails most often not in the writing but in the handoff — version four goes out Tuesday, version five exists only in your head. One week out, every vendor gets the same thing: the current schedule, their arrival time, the venue's loading rules, and the day-of contact (again: not you). If anything changes after that, it changes in the master and everyone gets told once.
How this works in ringbearer
ringbearer's day-of module is the master copy: phases, events, durations, per-event notes, and a total that recalculates as you drag things around. Vendors get a read-only share link to the live schedule — no accounts, no attachments, no stale versions — and there's a print view for the coordinator's clipboard because paper doesn't run out of battery. On the day itself, the app highlights what's happening now and what's next; we ran our own wedding on it, phone in hand. The day-of tour is here. The ceremony block deserves its own script — that guide is here.
The point of all this
A timeline this detailed can read as control-freak energy. It's the opposite. Every minute you schedule in advance is a decision nobody has to make at 7:30 pm on the day — least of all you. The couples who look effortless at their own wedding are the ones whose Tuesday selves did the worrying. Let the document carry it.
See how this works in the app: the product tour.