One project. 3 different conversations.

01 / The client needs confidence and a decision path.

A client update should make the project understandable. Explain what is ready, what changed, and where their input is needed. Include the relevant work and ask a specific review question. The reader should not need to understand the team’s internal production structure to make a useful decision.

02 / The contributor needs actionable context.

The person making the work needs the exact task, the latest reference, and the agreed constraints. A vague reassurance that the client likes the direction is less useful than a clear record of what was approved and which changes remain. Separate required revisions from exploratory suggestions.

03 / The project lead needs dependencies.

The person coordinating delivery needs to see risks across the work: a delayed input, conflicting feedback, or two tasks depending on the same contributor. That view supports prioritization. It should connect what is happening within a task to its effect on the wider project.

Keep one reality behind the different messages.

Tailoring an update does not mean changing the facts. Use the same current status, decision record, and deliverable links. Adjust the detail and the request for the audience. If your versions contradict one another, the communication system will create the confusion it was meant to remove.

Before you send.

Ask what the recipient needs to understand or do. Then remove details that do not support that purpose. Keep deeper context linked and available. A short update can still be rigorous when it gives the right person a reliable route to the information they need.