Operations guide
Wedding Planner Vendor Communication: What Every Message Should Clarify
A practical checklist for wedding planner vendor communication: identifiers, requested actions, deadlines, authority, and follow-up in every message.
The short answer
Every vendor message should make five things instantly clear: which wedding it concerns, what action you need, by when, what's attached, and who can approve the answer. Messages missing any of these force a reply-and-clarify cycle that slows down the vendor relationship. A consistent format for subject lines, identifiers, and closing lines cuts clarification rounds and gives vendors a message they can act on without guessing.
What should a purpose-first subject line include?
A subject line should tell the vendor what you need before they open the message, not just name the couple. Lead with the action type, then the wedding identifier, then the date if it's relevant. Vendors managing many weddings scan subject lines to triage, so a vague one gets opened late or skipped entirely.
Most planners default to subject lines that only list a couple's names, which forces the vendor to open every message to learn if it's urgent. A purpose-first format front-loads the request type, such as confirmation needed, final count, change request, or invoice question. This lets a vendor's inbox rules or manual triage sort messages by urgency without opening each one, which matters most during peak season when a single florist or caterer is juggling many weddings at once.
- Lead with the request type: confirm, revise, approve, or send
- Include the wedding identifier immediately after the request type
- Add the event date when the message concerns a specific week
- Avoid subject lines that only state a couple's names
- Keep subject lines short enough for quick scanning on a phone
What wedding identifiers must appear in every vendor message?
Every message needs the wedding date, the couple's name or file identifier, and the venue name if the vendor serves multiple properties. These details let a vendor locate the correct file within seconds, especially when they work with your studio on more than one wedding at a time.
Vendors who work with multiple planners, or with your studio on several weddings in one season, cannot rely on memory to match a message to a file. A missing date or an inconsistent spelling of a couple's name sends them searching their own records before they can even read the request. Standardizing identifiers in a fixed order at the top of every message removes that search step entirely.
Common questions
How long should a vendor message be?
Long enough to state the identifier, the action, and the deadline clearly, and no longer. Most well-formed vendor requests fit in three to five sentences; if a message needs more context, use a short call followed by a written confirmation.
Should every vendor message go through one team member?
Not necessarily, but every wedding should have one named point of contact per vendor so messages don't arrive from multiple team members with conflicting instructions. Note that contact in your vendor record and route requests through them.
What should happen when a vendor doesn't respond at all?
Follow your standard follow-up cadence, then escalate to a phone call, and document the gap in your vendor record. Repeated non-response on time-sensitive items may warrant a direct conversation about how the vendor prefers to communicate going forward.
Do these standards apply to text messages too?
Yes, in a shortened form. Texts should still include the wedding identifier and a clear action, even if the format is more casual than email, since vendors juggling multiple weddings need the same context regardless of channel.
Who should own the vendor communication standard for a studio?
One person, usually the studio owner or operations lead, should own the written standard and update it as the team grows. Individual planners still write the messages, but one owner keeps the format consistent.
Continue the system
Related planner resources
Turn this guidance into a repeatable process for your planning team.