For Planners
Wedding Planner Vendor Communication: A 90/60/30/7-Day Checklist
A practical vendor communication timeline for wedding planners, including what to confirm 90, 60, 30, and 7 days before the event and what to share on the wedding day.
Colara ยท July 31, 2026

A wedding planner vendor communication checklist keeps final details from turning into a week of scattered emails. The goal is not to contact every vendor constantly. It is to ask for the right information when it can still be changed, then move the team toward one approved plan.
Use this 90/60/30/7-day framework as a baseline. Move the dates earlier for destination events, complex builds, tenting, permitting, extensive rentals, or multiple locations.
Free printable
Track every vendor confirmation
The PDF includes the countdown checklist plus a final confirmation tracker for the vendor team.
Before the countdown: build one vendor record
- Company, role, primary contact, wedding-day contact, phone, and email
- Contracted service and coverage hours
- Arrival, setup, strike, and pickup requirements
- Outstanding balance and due date
- Insurance, permit, power, meal, parking, and access needs
- Dependencies on other vendors
- What the couple or planner still owes them
Attach the contract or a concise summary to the record. The timeline should reflect the agreement, but it should not be the only place the agreement can be checked.
90 days before: surface long-lead decisions
- Confirm the guest-count range, venue access, and major locations.
- Request rental, floral, lighting, staging, and transportation requirements.
- Identify permits, insurance, power, rigging, fire-marshal, and delivery restrictions.
- Confirm design direction and selections awaiting approval.
- Review transportation routes, capacity, accessibility, and travel buffers.
- Verify beauty-team service counts and timing.
- Ask photo and video teams about coverage, first look, sunset, and locations.
The output is not a final timeline. It is a complete list of decisions that could make the timeline impossible if discovered later.
60 days before: build the operational draft
- Send the first working timeline to major operational vendors.
- Confirm ceremony length, reception flow, service style, speeches, dances, and traditions.
- Draft load-in, setup, room-flip, and strike windows.
- Compare rental orders to the layout and guest count.
- Confirm menu, dietary process, vendor meals, and service assumptions.
- Verify entertainment inputs, sound, power, stage, and microphone needs.
- Confirm transportation pickup points, contacts, and contingency process.
Ask vendors to comment on conflicts and dependencies, not rewrite the schedule. One planner should maintain the master.
30 days before: collect final details
- Collect the latest guest count, floor plan, seating, and meal information.
- Request the name and mobile number of the person physically working the event.
- Confirm arrival, setup, coverage, service, strike, and pickup times.
- Verify delivery locations, parking, loading entrances, elevators, and access contacts.
- Resolve balances, insurance documents, permits, and certificates.
- Confirm photo groups, ceremony order, music, and pronunciation of names.
- Document the weather plan, decision-maker, and deadline.
Build the master schedule using the wedding day timeline template for planners. Every item should include time, place, owner, and execution notes.
7 days before: release one final version
Wedding week communication should be short and specific. Send each vendor:
- The final timeline or role-specific live view
- Venue address, access route, parking, and arrival instructions
- Planner lead and wedding-day contact numbers
- Their confirmed arrival, service, meal, strike, and pickup details
- Weather status and when a change will be announced
- A request to confirm receipt and flag unresolved conflicts
Track confirmation by vendor. "Sent" is not "confirmed." Follow up directly with anyone who has not responded.
Wedding day: communicate by impact
- What changed: dinner moves from 6:30 to 6:40.
- Why, if useful: ceremony started ten minutes late.
- What to do: catering holds salads; DJ moves introductions.
- Who owns the next update: planner confirms room entry.
Text or call for urgent action. Use the shared live timeline as the current source. Keep general chat separate from operational instructions.
After the wedding: close the loop
- Confirm rental pickup, personal-item handoff, balances, and damage records.
- Thank the vendor team personally.
- Request credits, gallery access, or publication information when appropriate.
- Record performance notes privately while details are fresh.
- Update preferred-vendor and referral notes.
A vendor confirmation message
Hi [Name], we are one week out from [Couple]'s wedding on [Date]. Your current schedule is [arrival/setup/service/strike]. Please review the linked timeline and confirm these times, your wedding-day contact number, and any unresolved access or power needs by [Deadline]. The planner contact is [Name and Phone]. Thank you for helping us keep the full team aligned.
Vendor communication FAQ
When should a planner contact all vendors?
Introduce yourself when coordination transfers to you. For many weddings, 60 days for operational review, 30 days for final details, and 7 days for confirmation creates a dependable rhythm.
Who should receive the full timeline?
Core operational vendors should have the shared schedule. Each vendor can receive a filtered view relevant to their role. Private family, financial, and team notes should stay in the master.
How do planners prevent old timeline versions?
Maintain one live source, label exports with a release date, stop sending editable attachments, and make updates in the shared version. Alert affected vendors directly after a material change.
Give every vendor one current plan
Colara combines vendor records, role-specific access, a shared live timeline, confirmations, and wedding-day communication in one planner workspace.
Built for planners
Vendor updates that send themselves
Share a live timeline link with every vendor in Colara and the 90/60/30/7-day updates in this checklist stop being emails you have to remember, because everyone is already looking at the current version. Try it free.