Weekly status report template — three versions you can copy
Pick by audience, not by taste: a team channel wants five lines, a manager wants a short email with the ask in it, and an at-risk week wants an escalation that reads like a decision request rather than an apology.
1. The five-line update (Slack, standup, team channel)
Status: On track / At risk / Blocked — one clause on why
Done: the outcome, not the activity ("checkout latency down to 380ms")
Next: one thing, with a day
Blocker: what is stuck, who has to decide, by when
Ask: one sentence, or write "none"
Five lines survive being read on a phone between meetings, which is the only time anyone reads it. Anything longer needs a headline, and the headline is line one.
2. The manager email (weekly, 150 words)
Subject: Weekly — [project] — week of [Mon DD] 1. Status: [on track / at risk / blocked]. [One sentence why.] 2. Shipped: [outcome] ([number]); [outcome] ([number]). 3. In flight: [item] — [owner], due [date] ([% done]). 4. Risk: [what could happen] — impact [scope/schedule/budget] — decision needed by [date]. 5. Next week: 1) [thing] 2) [thing] 3) [thing]. 6. Ask: [one sentence] — or "nothing needed from you this week".
3. The at-risk version (escalation, not confession)
Situation: [what changed, stated as fact, no blame] Impact if nothing changes: [date slips / cost / customer visible] What we tried: [two lines, with the result of each] Decision needed from you by [date]: [one choice, two options max] If no decision: [the default we will take, and what it costs]
The last line is what makes an escalation work. A manager who knows that silence produces a specific outcome tends to answer, and you are no longer waiting.
What managers read first
Three things, in this order: the status line (can I stop worrying), the ask (do I have to do something), the dates (is anything late). Everything else is context. If the ask sits in paragraph four as "we might need to discuss resourcing", it will be read as noise and answered next month.
Five mistakes that make a report unreadable
1. Activity instead of outcome — "worked on the migration" tells nobody whether it is done. 2. Status in the middle. 3. A risk with no decision attached, so it just recurs every week. 4. Percentages with no base. 5. Three asks, which is zero asks.
FAQ
How long should a weekly status report be?
Five lines for a team channel, about 150 words for a manager email. If it takes more than two minutes to read, the status is buried.
What if I have nothing to report?
Say it in line one and say why — waiting on review, blocked on access, a week of maintenance. Silence reads as a problem.
Should it include numbers?
One or two, tied to an outcome: tickets closed, plan burned, days ahead or behind. A number with no baseline is decoration.
Want the draft written for you? Paste your rough notes into the weekly report generator, or turn a meeting transcript into the raw material first. Related: summarising long source material.