Why Every Wedding Planner Needs a Client Decision Log

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
• Approved by: the lead planner or account owner who confirmed it counts
• Reason: the short rationale, especially if it overrides an earlier choice
• Affects: which vendors, budget lines, or timeline items are touched
• Downstream tasks: what must happen next and who owns it

Where should decisions come from and how do you capture the source?

Every logged decision needs a source reference so anyone can verify it later: an email thread, a signed proposal, a meeting note, or a text confirmation. Verbal-only decisions without any written trail are the highest-risk entries and should be confirmed in writing before they go in the log. This single habit prevents the most common dispute a planner faces: a client saying 'I never agreed to that.'

Sourcing does not need to be elaborate. A link to the email, a screenshot of the text, or a reference to 'confirmed on the 4/12 call, recap sent same day' is enough. What matters is that the source exists somewhere your team can pull up on demand. If a decision came from a quick hallway conversation at a venue walkthrough, send a one-line recap to the client afterward and log that recap as the source, not the conversation itself.

• Link or reference the email, contract, or message where the decision was confirmed
• Send a written recap after any verbal decision before logging it
• Treat undocumented verbal decisions as pending until confirmed in writing
• Store the source reference in the log entry, not just in your inbox

Who owns the decision log and who can change it?

One person, usually the lead planner on the account, owns the log and is responsible for its accuracy. Associates and assistants can add entries within their assigned tasks, but reversals, budget-impacting edits, and anything affecting the client contract route through the lead planner. This prevents the log from becoming inconsistent when multiple people touch the same client file.

Ownership does not mean the lead planner writes every entry personally. It means they are the final check before an entry is treated as settled, especially on high-stakes items like vendor selections or budget reallocations. On larger teams, name a backup owner for coverage during time off, and make sure that backup knows where the log lives and how entries are structured.

• Assign one lead planner as the accountable owner per client file
• Let associates log entries within their own assigned tasks
• Require lead planner sign-off on reversals and budget-impacting changes
• Name a backup owner for coverage during absences

How do you handle a reversed or changed decision?

Never delete or overwrite a decision entry. Add a new entry that references the original, states what changed, who requested it, and what it now affects, then mark the original as superseded. This preserves the full history so you can explain to a client, vendor, or team member exactly how a choice evolved and why.

Reversals are where decision logs earn their keep. A client who changes the guest count in month three needs a record that shows the original number, the new number, who approved the change, and which vendor contracts or seating plans now need updates. Route any reversal with cost or timeline impact through your standard change request process so it gets the same review as a new decision, not a quiet edit.

• Mark the original entry as superseded instead of deleting it
• Create a new entry linked to the original decision it replaces
• Note who requested the reversal and any cost or timeline impact
• Send the reversal through your change request process before confirming with vendors

What should be visible to the client versus kept internal?

Share a client-facing summary of major decisions and their status, but keep internal notes on rationale, vendor negotiations, or team disagreements out of that view. Clients need to see what was decided and confirm it matches their understanding; they do not need visibility into every internal debate that led there. This distinction protects both trust and your team's ability to think out loud.

A practical split: the client sees a short list of confirmed decisions tied to their wedding, phrased plainly, without internal shorthand or vendor pricing discussion. Your internal log carries the full detail, including who approved what and why, plus any sensitive notes about budget tradeoffs or vendor performance. If you use a shared view for clients, review it before sending to strip anything that was only meant for your team.

• Give clients a plain-language summary of confirmed decisions only
• Keep vendor pricing discussion and internal disagreements out of client view
• Review any shared decision view before sending to catch internal notes
• Use consistent, neutral language in client-facing entries to avoid confusion

How does a decision log differ from meeting notes, and how often should you review it?

Meeting notes record what was discussed in a specific conversation; the decision log records only the outcomes that resulted, stripped of discussion and organized by impact rather than by date of meeting. Review the log at each major milestone and before any vendor deadline to confirm nothing was missed or left unconfirmed. A log that nobody reviews drifts out of sync with reality just as fast as notes that nobody reread.

Meeting notes are chronological and conversational; a decision log is topical and consequence-focused. You might reference the same decision from three different meetings in your notes, but it should appear once in the log, updated if it changes. Set a review cadence tied to your planning timeline rather than a fixed weekly habit, since decision density varies by phase: heavier near contract deadlines, lighter in early planning.

• Review the log before every vendor payment or contract deadline
• Check for decisions discussed in notes but never logged
• Reconcile the log against the timeline at each major planning milestone
• Flag any decision older than a set threshold with no downstream tasks completed