For planners · Venues & vendors
How Should Wedding Planners Confirm Vendors Before a Wedding?
Confirm the current plan with every wedding vendor through one ledger, named owners and an escalation path for missing or changed details.
On this page
Confirm one current plan, not a collection of old emails
Run vendor confirmation from a single ledger that names the current version, what each supplier must confirm, who owns the follow-up and what happens if a detail changes. The objective is not to send one generic reminder. It is to resolve the dependencies that could affect the wedding-day plan.
Timing depends on the agreement, venue and supplier. Use the dates in the actual records rather than a universal number of weeks.
| Vendor | Confirm | Current source | Owner | Due | Status | Escalate if |
|---|---|---|---|---|---|---|
| Venue | access, rooms, loading, contact, contingency | venue plan | planner | access conflicts with timeline | ||
| Catering | final count, dietary details, service timing | final guest record | planner | count or timing is unresolved | ||
| Transport | route, pickup, capacity, contact | transport brief | named owner | route changes or capacity is short | ||
| Music | arrival, setup, cues, power and contact | current timeline | planner | setup conflicts with another supplier | ||
| Florals/rentals | delivery, setup, collection, quantities | approved decision | named owner | order differs from approved plan |
Use a three-step confirmation cycle
- Prepare: reconcile the timeline, guest count, decisions and venue instructions before asking anyone to confirm them.
- Confirm: send each supplier only the details relevant to their work and ask for a clear acknowledgement or correction.
- Close: record the response, update the current plan and notify every affected owner of a material change.
An acknowledgement is not a resolution if the supplier flags a conflict. Put the conflict in the ledger with an owner and next action until it is closed.
Worked example
For a fictional Saturday event, the caterer confirms a meal-service time that overlaps the photographer’s requested portrait window. The planner records the clash rather than accepting both messages. After the couple chooses a revised portrait slot, the planner updates the timeline, sends the relevant change to both suppliers and marks the ledger item complete only after each confirms the new version.
Make escalation ordinary
Define who may approve a timing, budget or scope change; who contacts the client; and when the venue needs to be involved. This protects the team from treating a late reply as an informal approval. Keep contract interpretation and commercial changes in the appropriate agreement process; a confirmation ledger is not legal advice.
Cakd can keep vendor records, timeline tasks and decisions together. It does not automatically send confirmations or determine whether a supplier response resolves a dependency. During a busy season, surface unsettled records in your multi-wedding review.