Write a Status Update That Makes the Next Decision Easy
A status update is useful when the reader can quickly understand where the work stands and whether they need to act. A list of activities may not answer either question. Before writing, identify the recipient and what they need to know to keep the work moving.
Lead with the current position
State whether the work is on track, waiting for an input, under review or affected by a change. Use a specific description rather than a vague positive label. “Draft complete, awaiting product details for the final section” is more useful than “Going well.” Include the relevant deadline so the reader can interpret the timing.
Separate progress from the request
Briefly explain what has been completed since the previous update. Then identify the blocker or decision needed, who should respond and when the answer is required. If there are several options, describe the practical consequence of each. Do not hide an important request at the end of a long paragraph about routine activity.
- Current position: what is complete and what remains.
- Change: what has happened since the last update.
- Request: the exact information or approval needed.
- Next step: what you will do once the decision arrives.
Be precise about uncertainty
If the completion date depends on an external response, state the dependency instead of presenting the date as certain. For example, explain that a draft can be finished after the missing images are approved, and give the planned turnaround after that approval. Avoid blaming language when describing a delay; focus on the missing input and the action that would resolve it. Keep the update in the agreed project channel so later readers can follow the sequence without searching across several private conversations.
Take it into your working day
A clear update tells the reader where the work stands, what changed and what decision would move it forward.