How to Make a Wedding Day Timeline From One Time

Twelve rows. To make a wedding day timeline, type one ceremony time into the run sheet generator: it writes twelve rows across three sections, from getting ready at 11:00 AM to a send-off at 11:00 PM. Ten of those rows carry a label, two exist only because the florist needs them, and five land with a blank in them. The five blanks are the job. The twelve rows are arithmetic.

One typed ceremony time produces twelve rows across three sections.

The problem is the second version, not the first

The first version is easy. Nine lines in a phone note - hair done, photos, ceremony, drinks, dinner, speeches, cake, dancing, finish. Four minutes of work, and it is not wrong.

It dies on the second version. The celebrant shifts the ceremony twenty minutes and a list of clock times has no way of knowing that dinner moved too. Every row gets retyped, then re-sent to a group larger than it feels: The Knot Worldwide's 2026 Real Weddings Study, drawn from 10,474 couples married in 2025, puts the average wedding at 13 hired professionals.² Thirteen people, each holding whichever copy they downloaded first.

A schedule written as clock times has to be rewritten. A schedule written as offsets from a few typed anchors recalculates itself. That is the whole difference between the two documents, and it is invisible until the first thing moves.

How to make a wedding day timeline in five moves

1. Type only the times somebody else has already locked

The builder asks for four: PREPARATION, CEREMONY, RECEPTION and DAY ENDS, with a fifth, CANAPE HOUR, appearing when that section is on the grid. You do not need four. You need the ones that are real - the celebrant's slot, the venue contract, the curfew. Leave the rest blank on purpose.

Blank is not missing. A blank field is an instruction to derive, and a derived time follows the anchor it came from forever. A guessed time typed into the same field looks identical on screen and behaves like a fact.

If the ceremony time itself is still open, stop here and settle it. It is the hinge, it is the hardest thing to renegotiate, and what time the ceremony should start decides the light, the meal and the travel behind everything below.

2. Let the offsets do the placing

Type a 3:00 PM ceremony with the day ending at 11:00 PM, and this is the day that comes back.

Two of those rows have no label at all. The 12:30 PM and 5:00 PM lines exist because the florist has to be somewhere, and a row with one supplier's name on it is still a row that has to be on the sheet. Set a canape hour and a thirteenth appears: couple portraits at canapes plus 45 minutes, capped at 20.

Put your own ceremony time in Type it into the run sheet generator and read the day it writes back. If it is not your day, you now know exactly which anchor is wrong.

3. Fill the five blanks

The engine will not invent a fact it does not hold, so it leaves a prompt where the fact belongs. On a 3:00 PM day there are exactly five.

Four of the five are one line each. The fifth is the whole afternoon: the groupings list is the only item on this page that a late start cannot compress, because forty people do not assemble faster because the cars ran late. Print it, hand it to somebody who is not in the photographs, and the 20-minute cap holds.

The five rows that arrive with a prompt in place of a fact.

4. Pad the transitions, not the end of the night

Defaults place rows. They cannot see your driveway. Jordan, founder and lead wedding coordinator at Managing Matrimony, publishes a 25-moment Australian run sheet built on a 4:00 PM Sydney ceremony and names under-padded transitions as the biggest mistake couples make: add 30 minutes after the ceremony for photographs and travel, 15 minutes before the reception entry, and 10 minutes between each speaker.¹

Note where that padding goes. It sits at the transitions, ahead of an anchor that matters - never at the end of the night, where a buffer protects nothing but the pack-down. The generator already holds 45 minutes between leaving the getting-ready address and the ceremony starting. If the drive is 30 minutes you have 15 minutes of slack. If it is 40, you do not have a schedule, you have a hope.

Three padding blocks, each sitting ahead of a time that has to hold.

5. Send a column, not a document

The run sheet ships with two supplier columns, photographer and florist, and each row carries different text in each. Your florist does not need the speech order. Your photographer does not need the delivery window for the arrangements.

So do not send thirteen people a forty-row file. Send each of them the rows with their name on. One source, filtered per column, no second version in circulation - which is also why it goes out as a link rather than a PDF. A file is out of date the moment anything changes, and the copy people are holding is whichever one they downloaded first.

One sheet. Six rows for the photographer, three for the florist.

What happens when the ceremony moves twenty minutes

Something moves. The celebrant runs late, the light is better at 3:20, the venue changes the access time.

Push the ceremony to 3:20 PM and eleven of the twelve rows follow it: getting ready to 11:20 AM, leave for the venue to 2:35 PM, dinner to 7:05 PM, first dance to 8:50 PM. The send-off does not move. It stays at 11:00 PM, because somebody typed it and a typed time is placed exactly where it was typed.

That is the rule underneath the whole method, and it is worth saying flatly: the times you decide are law, and the times you leave alone are arithmetic. A live schedule re-runs the arithmetic. A spreadsheet asks you to.

The same day with the ceremony at 3:00 PM and at 3:20 PM, row for row.

Common questions

When should I write it? Once the ceremony time and the photographer's booked hours are both confirmed. Those two set the shape of the day. Anything written before them is guesswork you will redo.

How detailed should a wedding day timeline be? Twelve rows is a working day. Managing Matrimony's Australian sample runs 25 moments across four phases for a 100-guest Sydney wedding.¹ Somewhere between the two is right for most days, and the rows you add should be the ones a supplier acts on.

Is a run sheet the same thing as a timeline? Yes. Run sheet is the Australian term and timeline is the American one for the same document.¹ If your celebrant asks for a run sheet, send them this.

How much time do I leave between the ceremony and the reception? Three hours by default, of which about 90 minutes is guests holding a drink. We pulled that one apart separately in how long between the ceremony and the reception.

Do I need a separate timeline for each supplier? A separate view, not a separate document. The moment there are two documents there are two truths.

What if the venue changes the ceremony time after I have sent everything out? Change the anchor. Everything derived from it follows and every shared view updates on the link people already have.

Who this is not for

Three days should not use this method.

A day with no confirmed ceremony time. Deriving a schedule from a number nobody has agreed to just spreads the guess across twelve rows. Settle the ceremony first, then come back.

A multi-day or cultural celebration. The engine writes the standard Australian day. Give the builder section names it does not know - SANGEET, MEHNDI, a second reception - and it hands you an hourly grid to fill in yourself instead of a written day. Useful, but it is scaffolding, not a draft.

A wedding already run by a coordinator with their own format. They will rebuild it their way, and they should. Turning up with the anchors typed, the groupings list printed and the supplier columns decided still saves the first two meetings.

For everyone else, the whole method is one field and five blanks. Start with the free tools, and note that the paid side is a single payment for the wedding rather than a monthly charge - see pricing.