Most status meetings exist because no one figured out a better way to communicate. They are called not because an hour of synchronized discussion is the most efficient way to share information — but because no one has a system for the alternative.
The alternative is a written status update. It takes five minutes to write, five minutes to read, and it gives recipients the information at a time that works for them.
Here is how to write one that actually works.
Why Written Status Updates Beat Meetings
A status meeting forces everyone into a synchronous time block. A written update does not.
A status meeting surfaces information once, in real time, at a pace determined by whoever talks loudest. A written update can be scanned in30 seconds, searched later, and referenced without a calendar invite.
A status meeting creates the appearance of communication without guaranteeing it. A written update, done well, communicates more clearly than most live conversations.
The only reason to default to a meeting is if the information requires live discussion, debate, or real-time decision-making. For most status updates, it does not.
The Structure That Works
1. One-Line Summary
Lead with the headline. What is the overall status in one sentence?
“This is the weekly status for Project X — on track for the March 31 launch, with one open dependency on the design team.”
This gives the reader the context before they read the detail.
2. What Is Working
Two to three bullets. What has progressed this week? What milestones were hit?
- Delivered the data model to engineering ahead of schedule
- Design review completed, approved with one revision noted
- Client feedback incorporated into the revised scope document
Be specific. “Things are going well” is not a status update.
3. What Is at Risk
One to two bullets. What could slip, what has slipped, what needs attention?
- API integration testing delayed3 days due to a third-party issue — team is monitoring
- Design revision from last week still pending — may affect final review timeline
Do not bury risk. Naming it clearly and early is what makes it manageable.
4. What You Need
One bullet, maximum. What decision, action, or input is needed from the recipient?
- Need sign-off from [stakeholder] on the revised scope by Thursday to stay on schedule
If you need nothing, say that: “No blockers or outstanding items this week.”
The Format Rules
Keep it short. One page maximum — aim for 250 words. If you cannot write a useful status update in that length, you are either not being selective enough or the project has genuinely become too complex for this format. In the latter case, a meeting might actually be warranted.
Use plain language. No jargon, no acronyms unless your audience uses them daily. Write for someone who was not in the room.
Send it on a schedule. Weekly is standard. Bi-weekly if the pace is slower. Predictable cadence is what makes written status updates reliable — not volume.
When to Use a Meeting Instead
Call a meeting when:
- A decision needs to be made in real time
- There is conflict or disagreement that requires live negotiation
- The update is sensitive and requires the ability to read the room
- The audience is larger than 8–10 people and Q&A is likely to be valuable
For everything else, write it.
The Real Rule
Status meetings are a default, not a necessity. Written status updates are not a replacement for all meetings — they are a replacement for the status meetings that exist only because no one thought of the alternative.
Related JSW resource: For recurring office status tracking, see the Office Control Logs & Trackers workbook with six editable Excel logs and a dashboard. View details →