Free Wedding
Run Sheet Generator

The anchor moments

Start with the spine of the day - the moments everything else hangs off. Guests arriving, the ceremony, the confetti line, family and wedding party photos, the entrance, each course, speeches, cake cutting, first dance, the send off. Give each one a start time and a rough duration. The generator above lays these out for you the moment you set a ceremony time, because every anchor is a fixed distance from that one decision.

What each vendor needs from it

This is the part most templates skip, and the part vendors actually read. Each vendor plans their work backwards or forwards from a different anchor:

• Hair and makeup works backwards from when the bride needs to be finished - not from when the ceremony starts. The finish time has to leave room for dressing, photos at the house, and travel, which is why the chair schedule starts so much earlier than most couples expect.
• Your photographer plans around light. The one time in the sheet they cannot move is the sunset window - golden hour portraits have to slip out between reception moments, and the spot gets scouted while it is still daylight.
• The caterer needs the service windows and the microphone times, because plates and speeches cannot share the room - food that lands during a toast goes cold on the pass.
• The DJ or band needs load-in and sound check scheduled before guests are anywhere near the room, plus the exact cue tracks - processional, entrance, cake, first dance, last song.
• The celebrant, florist and transport each carry quiet deadlines of their own - legal paperwork on the signing table, installs finished before chairs go out, cars that leave early enough to do a lap if the bride runs ahead of schedule.

The buffers

Every travel leg gets the real drive time plus margin, and the three things that always run long - speeches, family photos, the gap between "guests seated" and food actually landing - get a hard edge and a named person holding the clock. A run sheet without buffers is a wish list. The Detailed level of the generator writes these rows in for you, including the warnings that only make sense once a day has gone wrong: who holds the touch-up kit, when the one bag going to the venue gets packed, who gives each speaker their one-minute warning.

About three months out. By then the big decisions are made - venue, celebrant, photographer, caterer - and the planning changes character: it stops being about choosing vendors and becomes about who needs to be where, when. That is exactly the question a run sheet answers, and it is much easier to build one calmly at three months than frantically in the final week.

Build the skeleton first - ceremony time, the anchor moments, rough durations. Tighten it as details land: the florist confirms an install window, the venue confirms when the room can be set, the photographer names the sunset time. The final version should reach every vendor a week or two before the day. The common failure mode is the opposite: a schedule assembled at midnight two days out, sent to some vendors and not others. The generator on this page is designed to get you a complete first draft in about three minutes, so the skeleton exists long before the panic would have started.

Here is the uncomfortable truth about wedding-day horror stories: almost none of them are about a timeline that did not exist. They are about a timeline that existed and did not reach the right person. The couple had a schedule - the caterer was working from an older copy. The photographer asked for the timeline three times and got silence. The schedule changed on the morning and the groomsmen were the last to hear. Creation is the easy half; distribution is where wedding days break.

That has a practical consequence for how you share yours. An emailed PDF is frozen at the moment you hit send - so every change after that moment creates two versions of your wedding day, and you now have to remember who has which. The more vendors you have, the worse the arithmetic gets.

This is the actual reason to save the sheet you generated above into PlannedBy rather than emailing yourself the PDF and stopping there: the run sheet becomes one live link. You edit in one place, everyone sees the current version, and each vendor gets their own view - your florist reads the florist's cues, not your makeup schedule. Print copies still have their place on the day itself; the live link is what keeps them all telling the truth until then.

They are two doors into the same document. If you want to read a complete example first - a full sample day, every row visible, with the reasoning explained - start with the wedding run sheet template page and come back. If you want your day on screen now, use the generator above: it asks four questions and hands you a draft to edit, which is faster than adapting someone else's example line by line.

Either way, the run sheet is one piece of the day - PlannedBy also handles the guest list, seating and the rest of the coordination, and the pricing page has the full picture if you get to that point. The generator stays free either way.