The status update is the most-written, least-read document in most companies. Weekly updates that nobody reads aren't a reporting problem — they're a writing problem. Updates get skipped when they make the reader work too hard to find the one thing they care about: is this on track, and do you need anything from me?
Answer the two questions first
Every stakeholder reading your update wants the same two things:
- Is it on track? (Green/yellow/red, ahead/on/behind — any honest one-word scheme.)
- Is anything needed from me?
Put both in the first two lines. Everything else is supporting detail for whoever wants it.
- Weak: three paragraphs of activity narrative, with the schedule slip mentioned in paragraph four.
- Strong: "Status: yellow — API integration slipped 3 days (vendor auth issue). Need: a decision on the fallback provider by Thursday. Details below."
Report outcomes, not effort
"Worked on the migration" tells the reader nothing. "Migrated 60% of user records; on pace to finish Friday" tells them everything. The test: could a reader repeat your update to their own boss and sound informed? Activity lists fail that test; outcome statements pass it.
- What moved since last update
- What's blocked, and on whom or what
- What happens next, by when
Three bullets in that shape beat a page of narrative.
Never bury the bad news
The instinct to cushion a slip under three paragraphs of wins is universal and always backfires. Readers develop radar for it, and worse, they stop trusting your greens because your yellows arrive late. State the problem, the impact, and your plan in that order: "The vendor API change broke export; customer-facing impact starts Monday; fix is in review, shipping tomorrow." Delivering that without spin is a skill — writing it in a tone that's honest without being alarmist is exactly the kind of message worth a rewrite pass with a tool like Wrivio before it goes out, so the words land as "in control of a problem" rather than either panic or gloss.
Keep a stable format
Readers skim faster when the update looks the same every week: same sections, same order, same place for the status flag. A boring, predictable format is a feature. It also makes gaps visible — an empty "risks" section week after week either means smooth sailing or means nobody's looking, and both are worth knowing.
Let the board tell the routine story
Half of what goes into status updates — task-by-task progress — is better answered by a live, visible board that stakeholders can check anytime. Action-board tools like Axtio keep per-task status self-service, which frees your written update to cover what a board can't: risks, decisions, and what you need from the reader. Update prose is for judgment; boards are for state.
Right-size the frequency
A daily update nobody asked for trains people to skip your name in their inbox. Match cadence to the decision speed of the audience: leadership usually needs weekly, a delivery team may want daily, a steering committee monthly. When in doubt, ask readers what they'd miss if the update stopped — the answer is your real table of contents.
