For planners · Client workflow
How Should Wedding Planners Communicate With Clients?
Set a clear client channel, response expectation, escalation route and decision process before wedding-season messages become reactive work.
On this page
Define the route before the urgent message arrives
A communication charter tells clients where to send a question, what counts as urgent, when they can expect an acknowledgement, and where a final decision will be recorded. It is a service boundary, not a promise to be available at all hours.
Choose a small number of channels. A client portal can be the front door for current tasks and decisions, while an agreed urgent route handles time-sensitive event-day issues. The client portal matrix helps define what belongs where.
| Situation | Client route | Planner response | Record after reply |
|---|---|---|---|
| Routine question | portal or agreed project channel | acknowledge within your stated working window | answer or task if work is needed |
| Choice requiring approval | decision record | present options and a decision date | approved option and rationale |
| Document update | portal/current file location | point to the current version | update date and owner |
| Event-week change | agreed urgent route | acknowledge, assess impact, name next step | timeline/vendor/client record |
| Out-of-scope request | agreed project channel | explain scope and available next step | scope note if accepted |
Write the charter in plain language
This fictional wording is a starting structure, not a universal service promise:
Use the project portal for questions, information and approvals. We review it on working days and will acknowledge messages within the response window in your agreement. For a change that affects the event within 48 hours, use the urgent contact route. A conversation is not a final decision until we record the approved option in the project.
Replace “response window” and “urgent contact route” with the terms you actually provide. Do not borrow a speed you cannot consistently deliver.
Worked example
At 18:00 on a fictional Thursday, a client sends a message asking to add ten dinner guests for a wedding in three weeks. The charter directs the message to the project channel. The planner acknowledges it the next working morning, checks venue capacity and catering timing, then records a decision with the cost and schedule impact. The client approves the option in the decision record. The final count is not changed merely because the first message existed.
Review the system after one month
Ask: did clients know where to ask, were urgent issues distinguishable from normal questions, did approved choices reach the right record, and did the team have one visible current version? Adjust the charter where the real workflow produced friction.
Cakd Business and Agency provide a client portal and decisions. The charter remains an intentional operating practice; it does not claim automatic triage or response management. For a portfolio-level view of what needs attention, run the weekly multi-wedding review.