Wedding-Week Timeline vs. Wedding-Day Timeline

A wedding-week timeline exists to coordinate people, not vendors. It maps every personal and family event from the week before the wedding through the couple's departure, so nobody misses a rehearsal dinner or shows up at the wrong hotel for brunch.

This timeline is built for the wedding party, family, and close friends, not for vendors running the reception. It answers questions like when the welcome party starts, when out-of-town guests arrive, and when the couple needs to leave for their honeymoon flight.

A wedding-day timeline exists to run one day with precision. It breaks the wedding day into specific time blocks for setup, hair and makeup, photos, ceremony, cocktail hour, reception, and breakdown, and it goes to every vendor working that day.

This is the document a planner or coordinator uses to keep vendors on schedule and catch problems before guests notice them. It is far more granular than the week timeline, often tracking events in fifteen-minute increments during key moments like the ceremony and grand entrance.

The couple or a family point person usually owns the wedding-week timeline, since it covers personal events across multiple days and locations. The planner or day-of coordinator should own the wedding-day timeline, since they are the one physically present and directing vendors during the event.

If you do not have a planner, one person needs to be named the owner of the day-of timeline in writing, even if that person is a friend or family member. Ownership means one person decides on the final version and communicates changes.

The week timeline stays at the level of events and general times, since its audience is family and friends who need the big picture, not a minute-by-minute schedule. The day timeline needs granular detail, because vendors are coordinating with each other in real time and small delays compound quickly.

A useful test: if a time slip would only affect personal plans, it belongs in the week timeline's level of detail. If a time slip would affect a vendor's setup or another vendor's timing, it needs the day timeline's precision.

Vendors should never receive the full wedding-week timeline, since most of it is irrelevant to their work and includes personal details that do not need wide distribution. Vendors need the wedding-day timeline, and often only the portions relevant to their specific role.

Some planners create vendor-specific excerpts, sending the caterer a timeline focused on meal service and the photographer a timeline focused on portrait and ceremony timing. This keeps each vendor focused on their own responsibilities without extra noise.

Personal events like the rehearsal dinner or morning-of hair and makeup belong in both timelines, but at different detail levels. The week timeline notes that hair and makeup happens Saturday morning; the day timeline lists exact start times for each person in the chair.

Setup and delivery windows belong almost entirely in the day timeline, since they are vendor logistics. Note when florals arrive, when rentals get dropped off, and when the venue opens for vendor access, and confirm these windows match what vendors listed in their contracts.

Both timelines need a named backup plan for weather, delays, and no-shows, but the day timeline needs it in more operational detail since it affects real-time decisions. Build contingency notes directly into the day timeline, such as an indoor backup start time or a delay threshold before the coordinator calls the couple.

Version control matters most for the day timeline, since it changes more often as vendor details firm up. Label every version with a date, distribute only the current version, and retire old copies so nobody follows an outdated schedule.