Operations guide
Wedding Planner Event-Week Checklist and Final Verification Process
A structured event-week verification process for wedding planners covering confirmations, counts, contacts, contingencies, and issue ownership.
The short answer
An event-week checklist for wedding planners is a controlled verification process that confirms every vendor, count, document, and contact is locked before the wedding, with a named owner for each item and a clear escalation path if something falls through. It runs on a fixed schedule (typically seven days, three days, and one day out) rather than a single generic list, so nothing gets checked only once and forgotten.
What should the seven-day confirmation pass cover?
The seven-day pass is the first formal checkpoint where every vendor, count, and document gets verified in writing, not assumed. It exists to catch problems while there is still time to fix them, not just to record that a wedding is happening soon.
This pass should be done by the lead planner directly, not delegated, because it is the last point where a missing confirmation is still a minor fix instead of a wedding-day scramble. Send a single confirmation message to each vendor rather than assuming last month's contract is still accurate, and require a reply, not just a read receipt.
- Confirm arrival time, load-in window, and point of contact for every vendor
- Reconfirm final guest count with the venue and any headcount-dependent vendors
- Verify final payment amounts and due dates against the payment schedule
- Request updated certificates of insurance if the venue requires them
- Check that all signed contracts and riders are in one accessible folder
- Confirm weather contingency triggers for outdoor elements with the venue
How should final headcounts and seating be locked down?
Final counts should be locked in writing with the venue, caterer, and rental company on the same day, using one number that every vendor agrees to. A mismatch between vendors on guest count is one of the most common and most expensive event-week failures.
Treat the guest count as a single source of truth that gets distributed, not something each vendor tracks independently. If the caterer's number and the rental company's number differ even by a few seats, resolve it before event week starts, since same-week corrections often carry rush fees or simply cannot be made.
- Pull the final count from the couple's confirmed RSVP list, not an estimate
- Send the same number to caterer, venue, rentals, and any per-head vendors
- Confirm seating chart matches the final count and any last-minute changes
- Note dietary restrictions and confirm the caterer has the current list
- Flag any discrepancy between vendors within 24 hours of noticing it
What documents and contacts need to travel with the planner on the day?
Every planner should carry a single physical or digital packet with contracts, timelines, contacts, and emergency information, accessible without needing a signal or a login. Relying on scattered email threads or a phone that could die is not a plan.
Build this packet at the seven-day mark and update it once at the three-day mark, not continuously, so there is a clear final version everyone is working from. Assign one team member to hold a backup copy in case the lead planner's copy is unavailable for any reason.
- Printed or offline copy of the full day-of timeline for every team member
- Emergency contact list including couple, family point person, and all vendors
- Copies of signed contracts and any addendums for on-site disputes
- Venue contact and after-hours emergency number for the property
- Local vendor for common fixes: tailor, florist backup, or transportation
- Copy of insurance certificates if the venue requests proof on-site
How should the team be briefed before the wedding day?
A team briefing should happen in person or by call within 48 hours of the wedding, covering roles, timeline, and who owns which decisions if something changes. A briefing sent only by email the week before does not count as a briefing.
The goal of the briefing is to remove ambiguity about ownership, not to repeat the timeline word for word. Every team member should leave knowing exactly what they are responsible for and who to contact if their part of the day is at risk.
- Walk through the full timeline with every team member present, not just leads
- Assign a single decision-maker for each phase: ceremony, reception, vendor issues
- Clarify who talks to the couple's family versus who talks to vendors
- Review the contingency plan for weather, delays, or vendor no-shows
- Confirm each person knows their arrival time and what to bring
- Set a check-in time and method for the morning of the wedding
What should the rehearsal actually verify?
The rehearsal should confirm physical logistics, not just walk through the ceremony order. It is the last chance to catch access issues, timing problems, or missing people before the wedding itself.
Treat discrepancies found at rehearsal as urgent, not minor, since there is limited time left to fix them. If a vendor or key family member cannot attend rehearsal, schedule a short separate call to walk them through their specific cues rather than assuming they will figure it out on the day.
- Confirm the actual walking route, timing, and cues for the wedding party
- Test access points, load-in doors, and any locked areas vendors will use
- Verify sound, lighting, or officiant logistics that were only discussed before
- Identify who is missing from rehearsal and confirm they know their role separately
- Note any last-minute changes and update the timeline packet immediately after
How should contingencies and issue ownership be handled during the event?
Every known risk should have a named contingency and a named owner before the wedding day starts, not a general sense that the team will handle it. Ownership without a written plan tends to collapse under pressure.
The point of assigning ownership in advance is to avoid a moment where three people are solving the same problem while another goes unnoticed. A short written log during the event, even a few lines per issue, also makes the post-wedding debrief far more useful.
- Assign one person to own weather decisions and the deadline for making them
- Name a backup vendor or plan for each high-risk service, like catering or music
- Designate who communicates delays to the couple versus who fixes the problem
- Set a clear threshold for when an issue gets escalated to the lead planner
- Keep a simple written log of issues and resolutions during the event
Common questions
How far in advance should the event-week checklist start?
Most planners start formal verification seven days out, add a second pass at three days, and do a final walkthrough the day before. Anything vendor-facing should be confirmed at least twice before the wedding.
Who should own the checklist if a planner has an associate on-site?
One person, usually the lead planner, owns the master checklist even if an associate executes parts of it. Shared ownership without a single accountable name is how items get missed.
What happens if a vendor does not confirm during the final week?
Escalate immediately with a phone call and a hard deadline for response, and have a backup vendor or contingency plan ready if the deadline passes without answer.
Should couples see the full event-week checklist?
No. Share a simplified version covering what they need to know, like arrival times and personal item drop-off, and keep vendor logistics and contingency plans internal.
Continue the system
Related planner resources
Turn this guidance into a repeatable process for your planning team.