Operations guide

How to Write a Useful Weekly Client Update as a Wedding Planner

A repeatable weekly client update format for wedding planners that reduces status questions and keeps decisions moving.

7 min readReviewed August 12, 2026Juno product & planning team

The short answer

A useful weekly client update is short, structured, and answers three questions: what moved, what needs a decision, and what happens next. It lists completed work, open decisions with a deadline, upcoming milestones, any blocker, and who owns the next step. Sent on a fixed day, it replaces most ad hoc status questions.

What should a weekly client update actually accomplish?

A weekly update should give the couple enough information to trust that planning is on track without needing to ask. It should surface anything that requires their input and remove the need for a status-check email or call. If it does neither of those things, the format needs to change.

Many planners treat the weekly update as a courtesy or a way to look busy. That framing leads to long, vague recaps that couples skim and forget. The update exists to do two jobs: confirm progress and force decisions forward. Anything that does not serve one of those jobs is filler and should be cut, even if it feels informative to include.

Confirm what was completed since the last update
Force any pending decision into the couple's view
Remove the need for a separate status-check message
Give the couple a clear sense of what happens next

What structure keeps a weekly update short and useful?

Use a fixed five-part structure every time: completed work, open decisions, upcoming deadlines, blockers, and ownership of next steps. Keeping the order identical week to week lets couples scan quickly instead of reading closely. Skip sections that have nothing to report rather than padding them.

The value of a template comes from repetition, not creativity. Once a couple learns the format, they stop reading every word and start scanning for the parts that matter to them that week. A consistent structure also makes it faster for you or a team member to write, because you are filling in a known shape rather than composing from scratch.

Completed work: what was finished since the last update
Open decisions: what the couple needs to choose and by when
Upcoming deadlines: what is due in the next one to two weeks
Blockers: what is stuck and what is being done about it
Ownership: who is handling each next step, planner or couple

Who owns writing and sending the update each week?

One person should own the update for each client, usually the lead planner assigned to that wedding. If a second team member handles a task during the week, they report it to the owner rather than sending a separate note. This keeps the couple receiving one voice instead of a scattered stream of messages.

Splitting update ownership across multiple team members is a common source of confusion. Couples end up with conflicting or duplicate information, and no one is accountable for whether the update actually went out. Assign one owner per client at kickoff, write it into your internal process, and treat a missed update as a process failure worth reviewing, not an isolated slip.

Assign one update owner per client at project kickoff
Route team updates through the owner instead of the couple
Log the send date so missed weeks are easy to spot
Reassign ownership formally if a lead planner changes

How do you handle open decisions and blockers without alarming the client?

State the decision or blocker plainly, give the deadline, and name the next step you are taking. Avoid vague language that sounds like a warning without a plan attached. A blocker described with a clear next action reads as normal project management, not a crisis.

Couples do not need every detail of why a vendor has not responded or why a decision is delayed. They need to know it exists, whether it affects their timeline, and what is being done. Pair every blocker with an action you or the vendor are taking, and pair every open decision with a specific date it needs to be resolved by. This turns anxiety-inducing information into a manageable line item.

State the decision or blocker in one plain sentence
Attach a specific deadline to every open decision
Name the next action being taken on any blocker
Avoid open-ended language that implies a problem with no plan

When should you skip sending a weekly update?

Skip the update only when there is genuinely nothing new to report and no pending decision, and say so briefly rather than going silent. During slow planning phases, consider moving to a biweekly cadence rather than sending empty weekly notes. Never skip an update when a decision or deadline is outstanding.

A weekly update sent purely out of habit, with no new information, trains couples to stop reading it closely. If a wedding is in an early or quiet stage, it is reasonable to agree on a lighter cadence with the couple in advance rather than manufacturing content. The exception is any week with an open decision or approaching deadline. Those always warrant an update regardless of cadence.

Skip only when there is no progress and no pending decision
Send a short note confirming there is nothing new this week
Shift quiet planning phases to a biweekly cadence by agreement
Never skip a week that includes an open decision or deadline

How do you keep updates consistent across a full client roster?

Use the same template and send day for every active client so the habit becomes routine rather than a per-client judgment call. Track send dates in one place so gaps are visible across the roster, not just within one file. Consistency at the studio level matters more than any single update being perfectly written.

As a roster grows, the risk is not that one update is poorly written, it is that some clients quietly stop receiving them. Build a simple check, whether a shared calendar, a task list, or a tracker column, that shows the last update date for every active client at a glance. Review that list on a fixed day each week rather than relying on memory or individual planners flagging their own gaps.

Use one template across every active client, not one per planner
Assign a fixed weekly send day for the whole studio
Track the last update date for every client in one place
Review the full roster for gaps on the same day each week

How often should you review and refine the update format?

Review the template roughly once per quarter, or immediately after a client complains about missing information. Ask whether couples are still asking status questions the update should be answering, since that is the clearest sign the format needs adjustment. Keep changes small so the format stays predictable.

A weekly update format is a working document, not a fixed script. If several clients ask the same question the update was supposed to cover, that section needs to be clearer or moved higher. If a section consistently has nothing to report, it may not belong in every send. Make changes deliberately, document the current version, and apply it studio-wide rather than letting individual planners drift into their own formats.

Review the template on a fixed quarterly schedule
Revise sooner if a client asks a question the update should cover
Remove any section that consistently has nothing to report
Document the current template so the whole team uses one version

Common questions

Should weekly updates go through email or a shared document?

Either works as long as it is consistent and searchable later. Pick one channel per client, tell them where to expect it, and avoid mixing email and other channels for the same update on the same wedding.

How long should a weekly client update be?

Short enough to read in under a minute, typically a handful of lines per section. If an update regularly runs long, the content likely belongs in a separate document rather than the weekly note.

What if there is genuinely nothing to report that week?

Send a brief note confirming there is no new progress or open decision rather than skipping silently. For clients consistently at this stage, consider shifting them to a biweekly cadence instead.

Should couples be expected to reply to every update?

Only when a decision is pending. Say explicitly whether a reply is needed, and if not, tell them the update is informational so they are not left wondering if action is required.

Continue the system

Related planner resources