Write a Work Update That Gets a Decision, Not Just a Reply

Know what the update needs to do

A work update is not a diary of everything you did. It is a tool that helps someone understand the current state of work and decide what happens next. Before writing, ask who will read it and what they need from it. A manager may need to know whether a deadline is at risk. A client may need to approve a choice. A teammate may need a clear handover. The same project can require different updates for different readers.

Start with the outcome, not the activity. Instead of leading with meetings attended or hours spent, state what is complete, what is moving, what is blocked, and what you need. This does not mean hiding effort. It means placing the information where a busy reader can use it. Clear written communication has a purpose, an audience, and enough accurate detail for the reader to act.

Use a stable structure readers can scan

A reliable update can follow five parts: current status, completed work, next work, risk or blocker, and decision or support needed. Use short headings or bullets when the channel allows. The reader should be able to find the issue without searching through a long introduction. If there is no decision needed, say that clearly so people know the update is informational.

Keep the level of detail proportionate. A daily team update may be three lines. A client report may need context, dates, and links to evidence. Do not use a template as an excuse to repeat words that do not help. If nothing changed, say what is being monitored and when you expect a clearer answer. Predictable structure helps colleagues compare updates across time and notice what requires attention.

Name the date and time zone whenever a deadline affects people in different locations. If an update is based on an estimate, mark it as an estimate. If a status reflects one part of a larger project, say which part. These small details prevent a reader from making a decision based on a different interpretation of words such as tomorrow, complete, or on track. When an update includes a link, say what the reader will find there and whether it needs review. This reduces the chance that important evidence sits unopened in a message thread.

Make progress concrete without overselling

Describe finished work in terms that can be verified. Say that you completed a draft, tested a process with three users, reconciled a record, or prepared options for review. Link to the relevant document or task when appropriate. Avoid claiming that work is done when a necessary approval, quality check, or dependency remains. An accurate partial update is more useful than a confident sounding statement that surprises people later.

If you report a result, give enough context to prevent misunderstanding. A faster response time may have come from a smaller workload. A completed task may still require a colleague to review it. You do not need to make the update defensive, but you should make it legible. Credibility grows when people learn that your status words mean the same thing each time.

Raise blockers while there is still room to act

A blocker is not only a crisis. It can be missing information, an unavailable approver, unclear scope, a technical dependency, or a conflict between two priorities. State the blocker early, explain its likely effect, and name what would unblock it. This gives the reader a chance to help before the deadline passes. Waiting until the work is late can make a manageable risk look like a surprise.

Be specific without blaming people. Write that approval is needed on an option, that access has not yet been granted, or that a decision is needed between two requirements. Avoid vague phrases such as waiting on someone when the reader cannot tell what action is required. In distributed work, people may see the message hours later. A clear blocker lets them respond when they arrive rather than asking several rounds of questions.

Ask for one decision at a time

If you need a decision, make it unmistakable. State the choice, the options if there are options, your recommendation if you have one, and the date by which you need a response. A manager should not have to infer that a paragraph describing a problem is actually a request for approval. Clear requests protect both the project and the relationship.

Where possible, make the answer easy. Instead of asking what someone thinks about a broad plan, ask whether they approve option A, prefer option B, or need a short call to decide. Include the trade-off in plain language. This is not about pushing responsibility upward. It is about giving the person with the authority or context enough information to make a timely choice.

Build a habit that works across time zones

For remote or international teams, written updates often carry information that would otherwise be exchanged in a hallway or meeting. Send them early enough for others to respond in their working hours, define any time zone attached to a deadline, and avoid local shorthand that a new colleague may not understand. If the work is urgent, use the agreed escalation channel rather than hoping an update alone will be seen in time.

After a few weeks, review whether your updates lead to fewer follow-up questions and faster decisions. Ask a colleague which section is most useful and what they still have to ask you for. Refine the format around the work, not around a perfect template. This skill is small but visible: it helps people trust that you understand both your task and the information others need to move it forward.