Get Myself MarriedPlanning a wedding without losing the plot

Planning & Timeline

The Buffer Hour and Why Wedding Days Run Late Without One

Wedding schedules fail because every element is timed at its best case. Delays accumulate forwards and nothing recovers time, so lateness compounds across the day.

Open notebook with blank pages, surrounded by white flowers and rings, creating an elegant setup.
Photograph by Ylanite Koppens via Pexels
Editorial note. Independent reporting and analysis. Nothing here is sponsored or paid for. How we work.

Wedding days run late with striking regularity, and the cause is structural rather than a failure of discipline. A timeline built from optimistic estimates cannot absorb anything.

Delays travel forward and nothing pushes back

A wedding schedule is a chain. Each element starts when the previous one finishes, so a delay early in the day is inherited by everything after it.

There is no mechanism that recovers time. Elements can overrun but they very rarely underrun, because the shortest realistic duration is roughly what was already assumed.

The result is a one-way ratchet. Twenty minutes lost in the morning is still twenty minutes lost at the point where the caterers need people seated.

Estimates are made at best case

When a supplier says an hour, they usually mean the working time under good conditions, not the elapsed time including the couple being found and moved.

Transitions are where the missing time lives. Gathering a group for photographs, moving guests between rooms, and getting people to sit all take longer than anyone allocates.

A useful correction is to time the movements rather than the activities. Every change of location or configuration deserves its own line on the schedule.

The buffer has to be somewhere specific

Spreading slack thinly across the day does not work, because it gets absorbed silently and nobody notices it has gone until it is needed.

A single named block of thirty to sixty minutes is more robust. It sits somewhere flexible, typically the drinks reception, and its length is the schedule's tolerance.

The drinks reception works because guests are occupied and self-directed. Stretching it is invisible; stretching a seated meal is not.

Some points cannot move at all

Certain moments are fixed by outside forces. Ceremony slots booked with a registrar, sunset for photographs, and a licence or curfew ending the evening do not negotiate.

Everything between two fixed points has to fit, which means the buffer has to sit before the constraint rather than after it.

Catering has its own physics. Food prepared for a stated service time degrades if it waits, so a late meal is a quality problem as well as a scheduling one.

Somebody has to be watching the clock

A schedule with no owner drifts. The couple cannot do it, because they are inside the event and cannot see the whole room.

A coordinator, venue manager or a briefed friend holds the timeline and makes small corrections early, while they are still small.

The decisions that keep a day on time are unglamorous: starting photographs with whoever is present, cutting a group shot, moving guests through while a queue is short.

Questions readers ask

Do we need a run sheet for a small wedding?

A short one, yes. Small weddings have fewer lines but the same joins, and with fewer helpers a missing owner is more obvious rather than less.

Who should hold the run sheet if we have no coordinator?

Someone who is not in the wedding party and not making a speech. The role needs to be free to walk away and chase something without being missed.

Planning & Timelinerun sheettimelinewedding day
More in Planning & Timeline
Aparna Kulkarni
Contributing writer, Get Myself Married

Aparna writes about timelines and the decisions that unblock everything else.

Also by Aparna Kulkarni