How to write weekly status updates
A practical guide to writing weekly status updates: the best structure, common mistakes, and how to keep stakeholders aligned.
How to write weekly status updates
A good status update is short, honest, and decision-oriented. This guide gives you a structure you can reuse every week.
A simple structure that works
Use this every week so people know what to expect.
- Summary (1–2 sentences)
- Progress/Wins
- Timeline/Milestones (what changed)
- Risks & blockers
- Decisions needed (yes/no questions)
- Next week plan
- Links (plan, docs, demos)
Common mistakes (and how to avoid them)
Too much detail, no decisions
Stakeholders don’t need every task. They need a summary, risks, and decisions needed. Keep the detail for the team.
Vague risks
“Blocked” is not enough. State what is blocked, why, and what you need (person/date/decision).
Dates change without explanation
If the timeline changes, say why and what you’re doing about it. Trust comes from transparency.
No single source of truth
If updates live in 10 different places, people will ignore them. Share one link and keep it current.
Make it easy to trust your updates
Keep one living plan (timeline + board). Share the same link every week, and update it before meetings. This reduces repeated questions and prevents conflicting slide decks.