Most weekly status updates fail in the same way: they are written to be produced, not to be read. This is the template we recommend to CEOs who want the update to replace the meeting — with per-project lines that carry real information and red-flag callouts that make bad news impossible to bury.
The format rules
Before the template itself, three rules that make it work. First, the update answers three questions and only three: what changed, what’s at risk, and what needs a decision. Anything else is narrative. Second, every line has one owner — a name, not a team. Third, every claim that can carry a source carries one: the client email, the ticket, the signed quote. An update without sources is an opinion, and opinions are what the meeting was for.
The template
Subject: Weekly update — [date]
From: [CEO or chief of staff] · To: leadership · Read time: 2 min
1. What changed this week
Three to five bullets, each with a source. “Acme confirmed the October 3 delivery date in writing (email, Tue).” “Renewal quote sent at €12k, up from €10k (quote #118).” If a bullet has no source, it doesn’t go in.
2. Per-project lines
One block per active project, three lines each:
- Status: on track / at risk / blocked — never anything else
- Delta: what moved this week, one sentence. “No change” is a valid answer.
- Next step: one owner, one date — “Léa ships the integration to staging (Sep 19)”
3. Red flags
Anything that changed for the worse, stated flat: “Beta launch moved from Sep 15 to Sep 29 — vendor slipped, new date confirmed in writing.” A red flag without a recovery date is not a red flag, it is a confession. If this section is empty three weeks running, be suspicious — not relieved.
4. Decisions needed
Items that require the CEO, each with a recommendation and a deadline: “Approve the €12k renewal discount — recommended, protects Q4 expansion. Needed by Sep 18.” This section is the only survivor of the old meeting.
The copy-paste version of this template — formatted and ready to drop into your docs or email — lives at /templates/weekly-status-update.
The red flags to watch for
A template is only as good as its failure modes, so here are the five phrases that mean your update is drifting back into theater — and what to do about each.
“On track” with no source
“On track” is the update equivalent of “fine.” It carries no information and cannot be verified. Require that any “on track” line at risk of slipping names the verifiable milestone it refers to.
Scope creep in the deltas
When “what changed” quietly becomes “what we did,” the update has become a diary. Diary entries describe activity; deltas describe movement. The reader needs the second.
The vanishing red flag
A red flag that appears one week and disappears the next without a resolution line has been reclassified, not fixed. Keep a running line until there is a written resolution to link to.
Decisions without recommendations
If every decision lands on the CEO’s desk open-ended, your team has learned to outsource judgment upward. Require a recommendation with every ask — the CEO can always overrule it.
Where BrainFlow fits
The template’s hardest rule is sourcing. BrainFlow does that part for you: CC one address on your threads and the “what changed” section assembles itself from what was actually written — dates confirmed, prices quoted, terms agreed — each with a link to the source email. The red-flag section stops depending on whether someone volunteered the bad news, because BrainFlow flags contradictions privately the day they appear in a thread.
Your next update could write its own sourced section.
CC BrainFlow on your threads and every claim in your weekly update comes with the email to prove it. Free for 7 days — no card required.
Start free for 7 daysFrequently asked questions
How long should a weekly status update be?
Two minutes to read. For a startup with four to six active projects, that means three to five lines per project, each with one owner and one next step with a date. If your update is longer, people skim it, and a skimming reader is functionally the same as a cancelled meeting.
Who writes the weekly status update?
One owner per project writes their own lines — never a manager aggregating on their behalf. Aggregation is where bad news gets softened. The CEO or chief of staff assembles the sections, but the words about a project come from the person who owns it.
Should the weekly update replace the weekly meeting entirely?
Replace the reporting part entirely. Keep a short slot for decisions and blockers the update surfaced, with the facts already in writing. Most teams find thirty minutes of reporting collapses into ten minutes of actual decision-making once the update carries the information.