Operations guide
Why Every Wedding Planner Needs a Client Decision Log
Learn why wedding planners need a client decision log, what fields to track, who owns it, and how it differs from meeting notes.
The short answer
A wedding planner decision log is a running record of every client-facing choice that affects budget, vendors, design, or logistics. Each entry captures what was decided, who decided it, why, what it changed, and what it triggers next. Unlike meeting notes, it tracks only confirmed outcomes, so planners never re-litigate settled choices or lose track of what a change actually touched.
What is a wedding planner decision log?
A decision log is a single, chronological record of confirmed client choices, kept separate from general meeting notes. Each entry states the decision, the reason behind it, who approved it, and what it affects downstream. It exists so anyone on the team can answer 'what did we agree on and why' without re-reading old emails or notes.
Think of it as the source of truth for choices that carry consequences: a color palette that constrains florist and rental orders, a headcount that sets catering minimums, a venue swap that resets the whole timeline. Meeting notes capture the conversation that led there; the decision log captures only the result. When a client, vendor, or new team member asks 'why is it set up this way,' the log answers in one line instead of a search through months of messages.
- Log only confirmed decisions, not options still under discussion
- Separate the log from meeting notes even if both live in the same tool
- Write each entry so it stands alone without needing the original conversation
What fields belong in every decision log entry?
Every entry needs seven minimum fields: the decision itself, the date, who made it, who approved it, the reason, what it affects, and any downstream tasks it creates. Skipping any of these turns the log into a list of facts with no way to trace impact or accountability. Keep the format identical across every client so your team can scan entries without relearning structure each time.
- Decision: a one-sentence statement of what was chosen
- Date: when the decision was finalized, not when it was discussed
- Decided by: the client, planner, or joint call that made it
Common questions
Do we need a decision log if we already take detailed meeting notes?
Yes. Meeting notes capture discussion; a decision log captures only the outcome and its effects. Notes get long and hard to search, while a log stays short and lets you find any decision in seconds.
How far back should we keep decision log entries?
Keep the full log through the wedding date and for a defined retention period afterward that matches your studio's records policy. Do not delete entries even after a decision is reversed; mark them superseded instead.
Should assistants and associate planners have edit access to the log?
Give them access to add entries within their assigned events, but route reversals or budget-impacting edits through the lead planner. This keeps ownership clear without blocking day-to-day logging.
What happens when a client changes their mind after we've already booked something?
Log the reversal as a new entry that references the original decision, note who requested it and any cost or timeline impact, and route it through your standard change request process before confirming with vendors.
Can the decision log replace our contract or scope documents?
No. The log tracks decisions made during planning, not the legal terms of service. Keep contracts and scope documents as separate, authoritative records the log can reference but never override.
Continue the system
Related planner resources
Turn this guidance into a repeatable process for your planning team.