FRAME-09ExecuteSave

Status reports, newsletters and exec reviews

Three ways to tell people how a program is going: a weekly status report for the people doing the work, a newsletter for the people around it, and an exec review for the people who fund it.

Get the weekly status report template

TPL-01 · v1 · updated Nov 17, 2026
BlankOverall status, asks, workstreams, milestones and risks, with prompts in every section.Word .docx · 12 KB
Filled exampleFilled in for the running example: five teams moving a support assistant onto in-house inference.Word .docx · 12 KB

Free to use and adapt. Save this page to get an email when the template is updated.

Get the program newsletter template

TPL-10 · v1 · updated Nov 17, 2026
BlankWhat the program is, what shipped, what's next and what it means for readers.Word .docx · 11 KB
Filled exampleFilled in for the running example: five teams moving a support assistant onto in-house inference.Word .docx · 11 KB

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.

Which program update to send to which audience
UpdateWho reads itTypical cadenceWhat it answers
Weekly status reportWorkstream leads, partner teams, your managerWeeklyAre we on track, what changed, what do you need from me?
Program newsletterThe wider org and anyone affected by the launchEvery few weeks, or at milestonesWhat is this program, what shipped, what is coming?
Exec reviewSponsors and leadershipMonthly or at decision pointsIs 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.

When to send each update and when not to
Send it whenSkip it when
Several teams depend on each other’s datesOne team owns the work and sits together
Leadership is asking about the program in hallwaysThe program is a week long
You need a decision or a trade-off approvedNothing 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.

Example weekly status for Lantern
WorkstreamStatusWhyAsk
Migration planGreenPlan signed off by all five teamsNone
Index rebuildAmberRebuild running at about half the planned speed; cutover date holds if the Nov 12 batch-size change fixes it this weekData lead to confirm the fix by Thursday
CutoverAmberShadow run 1 done; shadow run 2 blocked while the staging GPU cluster is downEng lead to give a restore date this week
Security & privacy reviewRedNo reviewer assigned yet; it gates customer trafficSecurity 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

Common status report problems and how to fix them
FlagWhat it looks likeFix
WatermelonGreen on the outside, red on the inside: every row green until the week it slipsRate against the date, not the effort; go amber early
No askA red row with no named person and no date to fix itEvery amber or red row ends in an ask with an owner
Activity, not outcomesA list of meetings held and tickets closedReport progress against milestones and what changed
Wall of textParagraphs that bury the status below the foldSummary first, table second, detail linked

How to run it with a team

  1. Agree the workstreams and the RAG definitions at kickoff, so “amber” means the same thing to everyone.
  2. Ask each workstream lead for a status and a one-line reason by a fixed time each week.
  3. Write the summary yourself. Challenge any rating that doesn’t match what you’ve heard.
  4. Send it at the same time every week, and keep past reports in one place so trends are visible.
  5. Roll the weekly reports up into the newsletter and the exec review instead of writing those from scratch.

Inside the template

Weekly status report template fields and what to put in them
FieldWhat to put there
Overall statusOne RAG rating and one sentence on why
AsksDecisions or help you need, each with an owner and a date
Workstream tableStatus, reason and ask for each workstream
MilestonesNext few milestones with dates and whether they are on track
RisksTop 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

TPL-01 · v1 · updated Nov 17, 2026
BlankOverall status, asks, workstreams, milestones and risks, with prompts in every section.Word .docx · 12 KB
Filled exampleFilled in for the running example: five teams moving a support assistant onto in-house inference.Word .docx · 12 KB

Free to use and adapt. Save this page to get an email when the template is updated.

Get the program newsletter template

TPL-10 · v1 · updated Nov 17, 2026
BlankWhat the program is, what shipped, what's next and what it means for readers.Word .docx · 11 KB
Filled exampleFilled in for the running example: five teams moving a support assistant onto in-house inference.Word .docx · 11 KB

Free to use and adapt. Save this page to get an email when the template is updated.