How to Write a Status Update That's Actually Useful

Most status updates fail in a way nobody feels bad about. Someone who knows the work well, and has been at it all week, writes down everything they did — the emails, the context, the chain of events — and hands the reader a faithful, chronological account that leaves them with more questions than they started with. The update is accurate, sincere, and not yet useful.

The fix is a different goal. A useful update reduces uncertainty; a weak one describes activity. Get that distinction right and the structure looks after itself.

What makes an update "useful" rather than just "clear"

A useful status update is one that changes what the reader is uncertain about; a merely clear one is just easy to read. The two are not the same, and the difference is where most updates quietly fail.

Most advice about updates is really advice about style — be concise, use bullets, do not bury the lead. None of it is wrong, but style is downstream of purpose, and most updates do not fail at being clear. They fail at being useful: they do not change what is uncertain for the person reading.

A useful message does at least one of four things for the reader. It reduces uncertainty about the state of the work, about the decision required, about the risk, or about what you are going to do next without being chased. When none of those happens, you have sent information, not usefulness. This is the same conclusion reached by people who study busy readers from very different angles: Barbara Minto's Pyramid Principle puts the answer first and hangs the support beneath it; the military convention BLUF — "bottom line up front" demands the conclusion in the first sentence; and Harvard's Todd Rogers, in Writing for Busy Readers, shows that decision-makers skim and triage under time pressure, so the purpose and the ask have to be obvious almost at a glance.

The six-question shape

The six-question shape is a sequence that turns any update into something the reader can act on: what is happening, so what, what is in hand, what is not, what you recommend, and what you need. Once the job is to reduce uncertainty, the structure is remarkably stable — whether it is a written note, the first ninety seconds of a meeting, a one-line Slack message, or a client escalation. A useful update answers six questions, in roughly this order:

1. What is happening? The current state, in a sentence. Not the history.
2. So what? Why it matters — for the outcome, the client, the date, the margin.
3. What is in hand? What you have already put in place, and who owns it.
4. What is not in hand? What is still unresolved, and what you are deliberately not trying to solve right now.
5. What do you recommend? Your proposal, with the trade-off named — not a menu of equal options.
6. What do you need from me, if anything? A decision, a nod, air cover, an introduction, or simply to be kept informed.

You do not show the reader the scaffolding. You bake it into the sentences so they feel clarity, not structure. Here is the whole shape in three lines a junior developer could send:

The staging server has been flaky since Tuesday. It has slowed testing by about a day and will start to hit the build date if it is not fixed by Thursday. I have logged a ticket with the host and chased twice, with no response yet. If nothing moves by end of play Wednesday, I will ask our account manager to escalate. No action needed from you — just flagging.

Nothing in that requires being a manager, and nothing in it wastes one's time.

The "so what?" rule does most of the work

The "so what?" rule is the habit of stating the consequence of a fact rather than leaving the reader to infer it. Of the six questions, the second does more than all the others combined, and it is the one most updates skip. So what? is the hinge between the sender, who has been inside the work and knows why it matters, and the reader, who has not. Weak updates stop on the near side of that hinge and leave the reader to work out the implication themselves.

Run this test before you send anything important: read it back and try to finish the sentence "…and the consequence of that is…". If you cannot finish it without adding new facts, the consequence is missing. Watch what the move does to a flat update:

• Before: "Nothing new on recruitment. Still waiting on the agency."
• After: "No movement on recruitment this week — the agency has not sent the next shortlist. The practical consequence is that the early-March start date is now at risk by about two weeks. I have chased twice. If I do not see the shortlist by Friday, I would like to add a second agency in parallel rather than wait them out. Say if you would rather I held off."

Same facts. The first hands the reader a problem; the second hands them a decision.

"A recommendation you are half-sure about is more useful than a description you are fully sure about." — The Control Standard

The "so what?" can be overplayed — a contributor who turns every wobble into a crisis becomes noise rather than signal. Executive usefulness is not manufactured urgency. It is making the implications that matter explicit and leaving the ones that do not alone.

In live rooms, convert discussion into control

A spoken update follows the same six-question shape as a written one, with one extra job: turning open discussion into an owned decision before the meeting moves on. Updates mostly live on the page, but the same shape carries into meetings, where the failure modes are sharper. The most common is discussion without conversion: the room talks about an issue for eight minutes, everyone nods, and it leaves in the same state it arrived — no owner, no date, no decision. The useful contributor is the one who says, "Shall I own this through to next Friday and bring back a recommendation?" That single sentence turns talk into a control point, and it is how a room ends up better steered than it was found.

A clean update is not a soft skill. It is an operational asset: each one is a small deposit in the trust a manager can invest at range, which is exactly what lets you stop being the bottleneck without work drifting. The Control Standard develops this into a full practice for communicating in a way the rest of the business can act on. If you want to see where your work is currently going unseen, the free Drift Report below scores it in about five minutes.