A vague update such as ‘still working on it’ leaves teammates guessing whether a decision, review or new deadline is needed. A good progress message is short because it answers the most important questions in a predictable order. It should make it easier for the recipient to act, not just prove that you were busy.

Lead with the outcome

Write the result the reader cares about first. ‘The draft budget is ready for review’ is clearer than a paragraph describing each spreadsheet tab you touched. When a deliverable is not complete, say what is ready and what still prevents completion. Avoid hiding a delay in positive language.

Separate facts, obstacles and requests

Use three distinct ideas: what changed, what is blocked, and what you need from someone else. If a data source is missing, identify its owner and how it affects the decision. A risk is not the same as a confirmed failure, and an estimate should not be presented as a fact.

Give a next action with an owner

‘We should review this’ makes everyone responsible and nobody accountable. State who will check which part and when a response is useful. Do not assign work to a colleague without their agreement or authority. If the reader has no action, say ‘No action needed’.

Choose the detail level for the audience

A manager may need the decision and risk. A teammate continuing your work may need file paths and method notes. Link to a detailed document rather than pasting every revision into a chat. Protect confidential information and check access permissions before sharing.

Example in practice

An operations assistant could write: ‘Inventory summary: 12 of 14 supplier entries reconciled. Two require confirmation from purchasing, which I requested this morning. The report will be ready after those values arrive; I will update you on Thursday. No action needed unless a deadline has changed.’ This identifies progress and dependency without pretending the result is complete.

Important limits

If a safety incident, service outage or sensitive data breach is involved, follow the organisation’s formal escalation policy rather than treating a routine status update as sufficient.

Try it on one decision

Rewrite one long update into four lines: outcome, unfinished work, requested decision, next checkpoint. Ask whether the reader could identify their own next action.

Use the Respectful Conversation Planner when your update requires a difficult request.