Get the weekly status report template
Free to use and adapt. Save this page to get an email when the template is updated.
Get the program newsletter template
Free to use and adapt. Save this page to get an email when the template is updated.
Which update for which audience
Most status problems are audience problems: one document trying to serve engineers, partner teams and executives at once. Pick the format by who reads it.
| Update | Who reads it | Typical cadence | What it answers |
|---|---|---|---|
| Weekly status report | Workstream leads, partner teams, your manager | Weekly | Are we on track, what changed, what do you need from me? |
| Program newsletter | The wider org and anyone affected by the launch | Every few weeks, or at milestones | What is this program, what shipped, what is coming? |
| Exec review | Sponsors and leadership | Monthly or at decision points | Is this still worth it, and what decision do you need from us? |
When to use it
Start the weekly report the week the program kicks off, even if there is little to say: the habit matters more than the content in week one. Add a newsletter once people outside the core team start asking what the program is. Hold an exec review when you need a decision, not on a calendar alone.
| Send it when | Skip it when |
|---|---|
| Several teams depend on each other’s dates | One team owns the work and sits together |
| Leadership is asking about the program in hallways | The program is a week long |
| You need a decision or a trade-off approved | Nothing has changed and nobody needs to act (send a one-line “no change”) |
A filled example
The Lantern weekly status, in the RAG format: each workstream gets a rating in words, never color alone, and a one-line reason.
| Workstream | Status | Why | Ask |
|---|---|---|---|
| Migration plan | Green | Plan signed off by all five teams | None |
| Index rebuild | Amber | Rebuild running at about half the planned speed; cutover date holds if the Nov 12 batch-size change fixes it this week | Data lead to confirm the fix by Thursday |
| Cutover | Amber | Shadow run 1 done; shadow run 2 blocked while the staging GPU cluster is down | Eng lead to give a restore date this week |
| Security & privacy review | Red | No reviewer assigned yet; it gates customer traffic | Security to name a reviewer this week |
Lead with the overall status and the one thing you need, then the table. A reader who stops after two lines should still know whether to worry.
Good vs bad
| Flag | What it looks like | Fix |
|---|---|---|
| Watermelon | Green on the outside, red on the inside: every row green until the week it slips | Rate against the date, not the effort; go amber early |
| No ask | A red row with no named person and no date to fix it | Every amber or red row ends in an ask with an owner |
| Activity, not outcomes | A list of meetings held and tickets closed | Report progress against milestones and what changed |
| Wall of text | Paragraphs that bury the status below the fold | Summary first, table second, detail linked |
How to run it with a team
- Agree the workstreams and the RAG definitions at kickoff, so “amber” means the same thing to everyone.
- Ask each workstream lead for a status and a one-line reason by a fixed time each week.
- Write the summary yourself. Challenge any rating that doesn’t match what you’ve heard.
- Send it at the same time every week, and keep past reports in one place so trends are visible.
- Roll the weekly reports up into the newsletter and the exec review instead of writing those from scratch.
Inside the template
| Field | What to put there |
|---|---|
| Overall status | One RAG rating and one sentence on why |
| Asks | Decisions or help you need, each with an owner and a date |
| Workstream table | Status, reason and ask for each workstream |
| Milestones | Next few milestones with dates and whether they are on track |
| Risks | Top risks from the risk register that changed this week |
The program newsletter template has a short “what is this program” paragraph, what shipped, what’s next, and who to contact.
Get the weekly status report template
Free to use and adapt. Save this page to get an email when the template is updated.
Get the program newsletter template
Free to use and adapt. Save this page to get an email when the template is updated.