The standard weekly status report is a monument to the sender's discomfort with silence. It's usually a list of what you did last week, what you're doing this week, and occasionally a "blocker" section that nobody fills in honestly. It takes two hours to write. It takes thirty seconds to skim. It changes nothing.
The weekly report that works is structurally different. It's built for the reader's decisions, not the sender's anxiety.
The Structure of a Useful Weekly Update
A useful weekly update answers exactly three questions:
1. What's off track?
Start here. One to three items that are at risk, behind, or blocked. Include: what the issue is, who's affected, and what you're doing about it. No sugarcoating.
2. What's on track?
One paragraph. Not a list — a paragraph. The reader doesn't need granular status on everything that's fine. They need confidence that you're on top of it. One short summary does that job.
3. What do you need from me?
This is the most skipped and most valuable section. Decisions you need, resources you need, conflicts you need resolved. Be specific. "I need alignment on priority" is not specific. "I need a decision by Thursday on whether we ship Feature X or Feature Y — here's the trade-off" is specific.
A simple template:
`text
Weekly update: [area] — [date]
- Exceptions / risks
- [Metric or initiative] is [red/amber] because [reason].
Owner: [name]. Next action: [action] by [date].
- Decision needed
- Decision: [specific call].
Options: A / B. Recommendation: [choice]. Deadline: [date].
- On-track summary
- [One short paragraph. No victory lap.]
- Changes since last week
- [What materially changed, not everything that happened.]
`
The Distribution Problem
A weekly report sent to 15 people is a weekly report read by 2. If you're writing for a broad audience, you're writing for no one. The most effective weekly update cadence: a short, structured update to your manager (one page, weekly), and a separate operational update to your team (daily or every other day).
Don't try to serve both audiences with one document.
