It is a sequence of operational buffers — and one of them has to be empty on purpose.
You have a schedule. Most likely you built it the way everyone does: you listed what you want to happen, put times next to each item, and checked that the hours add up. They do. The arithmetic is correct.
The problem is that the schedule was borrowed. A wedding timeline sequences a venue, a caterer, and a room full of people who are already on site. An elopement timeline sequences a drive, a light window, and two or three people who are arriving from different directions. Those are different problems, and the second one has no published benchmark to check against.
A schedule where every block touches the next one is not a tight schedule. It is a schedule with no margin, which means the first delay is also the last.
Nothing unusual has to happen for an unbuffered timeline to fail. The road is slower than the map said. The officiant arrives at the pullout instead of the trailhead. Someone needs ten minutes that nobody allocated. Each of those is ordinary. A buffered sequence absorbs them; an unbuffered one passes them forward, and by the time the delay reaches the ceremony it has collected everything in front of it.
Not getting ready — being ready to leave. This window closes when everyone and everything is in the vehicle, not when the last person is dressed. It is the window most often measured from the wrong end.
The drive, the park, and the walk in. Transit is an estimate, which means it is a range, not a time. The common error is treating the estimate as if it were the margin. It is not. The margin is what sits after it, as a separate block.
A labeled, deliberately empty block before the ceremony. Nothing is scheduled in it and nothing is supposed to be. It is not contingency for a disaster — it is how a sequence absorbs ordinary variance without moving the one time of day that cannot move.
Everything else is built backward from that fixed point: the light. The ceremony time is calculated, not chosen, and once it is set, each window above is positioned relative to it rather than stacked forward from morning.
You are not behind. Your timeline is unbuffered.
The Elopement Feasibility Audit is a free Notion template — fifteen questions, six of which are Gates that can end the wedding day. One of them asks the question this page is about: what is your day-of timeline being checked against? Every question names who can answer it and what happens if the timing is wrong.
You answer all fifteen from memory, then count what is still unresolved. The number you start with is the point.
Keep going: see why a wedding timeline doesn't work for an elopement or review the checklist nobody gives you.
🔒 No spam, no drip of wedding tips you didn’t ask for.