Write Client Updates That Get Decisions

Many client updates are accurate and still ineffective. They list activity, attach documents, and describe the week. Then they end without telling the client what to do.

The best update is not a report on your effort. It is a tool for moving the work forward. It gives the client enough context to make the next decision quickly.

Lead with the outcome, not the chronology

Clients do not need a replay of every call and task. Start with the current project position: what is complete, what is at risk, and what decision matters now.

Compare these openings:

“This week we held three stakeholder interviews and reviewed the process map.”

“The team agrees the handoff process is the main source of delay. We need a decision on the proposed owner before we can finalize the pilot plan.”

The second version gives the client a reason to read and a clear path to respond.

Use a four-part update

Keep the format consistent so clients can scan it quickly:

1. Progress: the completed output or validated finding

2. Risk or change: what could affect the plan

3. Next step: what you will do next if the plan holds

4. Decision needed: one action, owner, and deadline

This structure works in an email, a project workspace, or a short slide. It separates facts from the recommendation and prevents the client from having to infer the ask.

Make the decision request specific

“Please review” is not a decision request. It asks the client to discover the work you need from them.

Instead, name the choice and the consequence:

“Please confirm whether the pilot will include all regional teams or only the Midwest group by Wednesday. An all-region pilot requires two additional training sessions and moves the launch by one week.”

This request is easier to answer because it tells the reader:

• what choice is available
• who should make it
• when you need it
• what changes if they choose either path

If several decisions are needed, rank them. Do not send a list of ten asks and call it an update. Lead with the decision that blocks the most important next step.

Put the evidence where the decision happens

Link or attach the minimum evidence the client needs: a one-page recommendation, a short comparison table, or the relevant section of the draft. Do not bury the decision in a long deck or a chain of messages.

For a meaningful tradeoff, a small table can help:

State your recommendation. Clients hire consultants for judgment, not just information. Be direct about the path you believe best serves the agreed outcome.

Close the loop when the client responds

When a decision arrives, record it in the project plan and tell the client what will happen next. If no response arrives by the stated deadline, follow up with the consequence rather than a generic reminder.

For example: “We have not received the pilot-scope confirmation, so we are holding the training schedule. A response by Friday keeps the September launch feasible.”

Clear updates do more than reduce email traffic. They create shared ownership. The client sees where their action matters, and you avoid carrying an unmade decision silently into the next week.

Related: Reduce Admin Friction in Client Updates | How to Prioritize Client Requests Without Constant Reprioritization