Weekly Status Report Template for Small Teams (One Screen, Async)

Most status meetings are five people describing work that's already visible somewhere else. The weekly status report replaces them with one screen, written in 30 minutes, read async. The format below is deliberately short: if it takes longer than a screen, people stop reading it by week three — and then you're back in the meeting.

The 5 sections (in this order)

1. Shipped: what went live last week, one line each, past tense. If a "shipped" item needs a paragraph of context, it didn't really ship.
2. In flight: what's moving and when it lands. One line each with a date — a status without a date is a wish.
3. Blocked: what's stuck, what it's waiting on, and who unblocks it. This is the only section where it pays to name names.
4. Risks & watchlist: things that aren't problems yet. Two lines max; this section is why the report gets skimmed by whoever cares about the next two weeks.
5. Numbers: the two or three metrics the team actually steers by, with last week's values next to them. Trend beats snapshot.

What to cut (the report-killers)

• Per-person updates. The moment the report reads like five separate narratives, it's five reports. Group by outcome, not by person.
• Activity descriptions. "Worked on the migration" says nothing; "migrated 60% of users, remaining 40% scheduled Thursday" says everything.
• The color-coded RAG matrix. Five statuses is five chances to argue about what amber means. Shipped/in-flight/blocked covers it.

Why async beats the Monday meeting

A written report is skimmable in 90 seconds, searchable in three months, and readable by whoever was out Friday. A meeting is none of those. Keep a 15-minute Monday slot anyway — but make it optional and agenda-free: it exists for the two conversations the report started, not for reading the report aloud.

The 30-minute Friday routine

The report is cheap only if writing it is cheap. The routine that works:

1. 5 min: copy last week's report — it already contains the in-flight items and the numbers baseline.
2. 10 min: update statuses and dates. If an item has slipped twice in a row, it moves to Blocked with a name attached.
3. 10 min: pull the numbers from wherever they live (dashboard, bank, ticket count) — paste values, no narrating.
4. 5 min: read it once as a new hire would. Any line that needs a follow-up conversation becomes Monday's agenda.

Do it in the same calendar slot every week. The first report takes 45 minutes; by the fourth, the team stops noticing the effort.

The one-sentence rule

Every line in the report must survive being forwarded to an investor, a customer, or a new hire without context. If a line needs explaining, the explanation IS the update — either write the explanation or delete the line.

---

The Automation Starter Pack ($19) includes the weekly status report as a fill-in template plus a script that pulls your open items into the Monday digest automatically — alongside the intake triage board, access & offboarding checklists, incident skeleton, and the pick-first automation filter. Launch month: 30% off with code HIVE-LAUNCH30.