A weekly status update earns its place when it answers the questions a leader would otherwise call a meeting to ask. Six signals do that: overall health, completed milestones, current-week priorities, risks and blockers, resources needed, and next-week projected activities. Together they form a short decision loop — where the work stands, what moved, what matters now, what could derail it, what it needs, and what happens next.
Paste this into your update, replace [project name], and fill each section in a few tight lines. Keep it short enough to read in under two minutes.
Weekly Status — [project name]
Week of: __________
1. Overall health
Status: On track / At risk / Off track
One line on why.
2. Completed milestones
- What shipped or closed this week.
3. Current-week priorities
- The few outcomes this week is built around (with owners).
4. Risks & blockers
- Risk / blocker — owner — impact — what is being done.
5. Resources needed
- Specific asks: people, budget, decisions, access.
6. Next-week projected activities
- What comes next and what “done” looks like.Each signal answers one question. Keep every section to a few lines — the value is in the edit, not the volume.
If a section is not answering its question, it is taking up space. This mapping keeps the update honest.
| Signal | Management question it answers |
|---|
Read top to bottom, the six signals move a reader from orientation to action. Overall health sets the frame. Completed milestones prove momentum. Current-week priorities focus attention. Risks and blockers surface what could break the plan. Resources needed convert concern into a decision someone can make. Next-week projected activities set the expectation the following update will be measured against.
The discipline is brevity. Each section is a few lines, written so a leader can scan the whole update and know whether to keep moving, unblock something, or step in — without a meeting.