Weekly updates fail in two opposite ways: a one-word “on track” that hides real risks, or a page of activity that nobody reads to the end. A fixed five-line structure avoids both, and makes week-on-week change easy to see.
The five lines
- Status — on track, at risk or off track, with one sentence of why.
- What changed since last week — outcomes, not activities.
- Risks and blockers — each with what is being done about it.
- Decisions needed — from whom, by when.
- Next milestone — what will be true by when.
Work is progressing well. Team is working on integrations and testing. Some delays but should be fine.
Status: at risk — payment integration is 4 days behind. Changed: login and profile screens are complete and tested. Risk: vendor sandbox access still pending; escalated to their account manager on Tuesday. Decision needed: approve moving the beta by one week (Priya, by Friday). Next milestone: beta build to client testers — currently 21 Nov.
Outcomes, not activity
“Worked on testing” describes effort. “Checkout tested on Android and iOS; two defects open” describes a result the reader can use. If a line only describes effort, ask what is now true that was not true last week.
Be honest early about “at risk”
An update that says “on track” for six weeks and then “off track” is not a status report; it is a surprise. Marking a project “at risk” with a clear plan is usually received far better than a late, unexplained slip.
Examples in this guide are fictional and written for teaching — not client material or measured results.
