Slack belongs in the middle, not at the end
Every run-sheet has an end, and almost every first draft puts the buffer there — a vague thirty minutes before the venue clears, a placeholder called "wind down" that is really just hope written in a box. It does not work, because time pressure compounds forward. A delay at the ceremony does not pause at the drinks reception and wait politely. It arrives at dinner still late, makes service later, and consumes the evening in increments until the final bracket — the one you left loose — is gone before anything in it has happened.
The mechanism is simple: slack placed at the end of a sequence absorbs nothing, because the events that run over already happened upstream. The end of the day is not where the problems land; it is where the unpaid bills come due.
Put buffer where the risk is. That means three places.
After the ceremony, before the drinks. The legal part runs long — a reading goes over, a register takes longer to sign than anyone expects, a wheelchair needs a clear path that requires the crowd to move. Build fifteen minutes here, and it arrives at the reception as a comfortable start rather than a scramble. Guests rarely notice early; they always notice flustered.
Between drinks and the call to dinner. This bracket is when photographs of the wedding party happen and when group shots consume real time. A tight gap here is where afternoons start dying. The walk from outdoor terrace to dining room alone, for a hundred people who have been drinking and talking, can run twelve minutes against the five on the sheet.
Before the first dance or the room change. Clearing and resetting a room has a fixed minimum; it does not speed up because the timeline is optimistic. Hold a buffer before the evening segment begins and the floor will be ready, the speeches finished, the caterers level. Remove it and the first dance happens over the sound of chairs.
One practical rule: a buffer that shares a name with an activity will be stolen by that activity. "Extended drinks" expands to fill the time. Call it nothing on the public-facing order of events, and keep it named only on the working sheet. It is not a secret agenda item; it is structural tolerance, the same role a seam allowance plays in a garment — invisible until you need it, catastrophic to be without.
The instinct to stack events tightly reads as polish in a draft and chaos on the day. A run-sheet with honest slack in the right places is not a loose plan. It is an accurate one.