The person asking for a status update almost never wants the status. They want the answer to a question underneath it: is this on track, and do I need to worry? Most updates fail because they deliver activity — a chronological account of what happened — when what the reader needs is an assessment. Motion is not progress, and a list of things you did is not an answer.
Lead with the verdict, then the evidence
Open with the one thing the reader is anxious about: on track, at risk, or off track. Say it in the first sentence, plainly. Then give the two or three facts that justify the verdict. Burying "we'll miss the date" under three paragraphs of activity doesn't soften it — it just delays the reader's understanding and makes you look like you were hiding it. The bravest and most useful update opens with the bad news, because the bad news is the entire reason status updates exist.
Green, yellow, red — and mean it
A simple health signal does most of the work if you're honest with it. The failure is the perpetual optimism where everything is green until the week it's suddenly, inexplicably red. Yellow is the most valuable status you can report — it means "trouble is forming and there's still time to act." A project that goes green-green-green-RED was never actually green; someone was managing the reporting instead of the risk. Calling yellow early is a sign of control, not weakness.
Report against the plan, not against yesterday
"We made progress" is meaningless without a yardstick. Progress relative to what? Status only has meaning against the plan — where you expected to be by now versus where you are. When the work and the plan live on a shared board like Axtio, a lot of the update becomes a shared glance: here's what was due, here's what's done, here's the gap. That grounds "on track" in something verifiable instead of a feeling, and it lets the reader see the same reality you're describing.
Name blockers with a request attached
A blocker reported without an ask is just a complaint. "We're stuck on legal review" tells the reader there's a problem but hands them nothing to do about it. "We're stuck on legal review — can you nudge Sam to prioritize it this week?" turns the update into a lever. The most useful thing a status update does is surface the specific help you need from the specific person reading it, early enough for them to actually provide it.
Keep it short enough to be read
A status update that runs long doesn't get read carefully; it gets skimmed, and the one line that mattered gets skimmed past. Ruthless brevity is a feature — the verdict, the evidence, the blockers, the ask, and stop. If your updates habitually balloon, running a draft through an editing tool like Wrivio to cut the hedging and filler is a quick way to get them back to a scannable length without losing the substance. For updates that go to stakeholders or clients, sending a clean one-page PDF keeps the formatting intact across every inbox and gives them a durable record they can forward without it turning into a garbled reply-chain. The goal isn't to prove you were busy; it's to let a busy person understand the situation in thirty seconds and know exactly what, if anything, they need to do.
