Weekly Status Report Template: The 6-Line Format That Survives a Reorg

Most status reports fail for a boring reason: they report activity instead of change. "Worked on onboarding flow. Met with design. Continuing QA." Nobody reading that knows anything they didn't know Monday. Six weeks later, when someone asks why onboarding slipped, the answer is buried in a thread nobody can find.

This template fixes that. It's six lines, it takes under ten minutes, and it holds up when your VP forwards it to someone who wasn't in the room.

The six-line template

Copy this into your doc, wiki, or email body:

WINS: [1–2 things that shipped or moved measurably]
RISKS: [what could break the date, with a name and a date]
DECISIONS NEEDED: [the ask, the owner, the deadline to decide]
NEXT WEEK: [3–5 outcomes, not tasks]
METRICS: [one number that matters, with direction]
BLOCKERS: [what's stuck, who can unstick it, since when]

That's it. No preamble, no "hope you're well," no screenshot of a Jira board.

Why six lines and not a dashboard

Dashboards answer "what is the state of everything?" A weekly report answers "what changed, and what do you need from me?" Those are different questions. When you merge them, you get a 40-row table that leaders skim and forget.

The six-line format forces three things:

1. A judgment call. You have to decide what mattered this week. That's the work. Picking is the value you add.
2. A named risk. "Timeline at risk" is noise. "Auth migration will miss the 14th unless platform approves the schema change by Wednesday — Priya owns it" is a report.
3. A number. One metric, moving or not. If nothing moves for three weeks, that itself is the story.

Filling it in: a worked example

Here's a real-shaped example for a mid-size feature launch:

WINS: Checkout redesign hit 100% rollout Tue. Conversion +1.8pts vs. control (n=41k).
RISKS: Payment provider sandbox is flaky; load test blocked since Mon. If not resolved by Thu, we delay the stress test, not the launch.
DECISIONS NEEDED: Approve $4k for third-party load testing vendor by Wed EOD. Owner: Dana.
NEXT WEEK: Finish stress test, draft rollback plan, brief support team on new error states.
METRICS: Checkout completion 71.2% (up from 69.4% last week).
BLOCKERS: Sandbox access — escalated to vendor Tues, no response yet.

Notice what's absent: a list of meetings, a percentage-complete bar, a paragraph of context. The reader gets the win, the risk, the ask, and the number in fifteen seconds. If they want detail, they ask.

The three mistakes that kill weekly reports

Mistake 1: Reporting tasks, not outcomes. "Wrote spec, reviewed designs, attended standup" tells the reader you were busy. "Spec approved, design review scheduled for Thursday" tells them where the project is. If a line doesn't change what the reader knows or does, cut it.

Mistake 2: Vague risks. "Scope creep risk" is not a risk, it's a mood. A risk has a trigger, an owner, and a date: "If legal doesn't sign off on the data-retention clause by the 22nd, we slip the beta." That sentence gets acted on. The vague one gets nodded at.

Mistake 3: Burying the ask. If you need a decision, it goes in its own line near the top, with the decision-maker named and a deadline. Don't tuck it into paragraph four of a "context" section. Busy readers scan; make the ask scannable.

When to use a longer format

Six lines is right for a weekly cadence to a manager or a cross-functional group. It's wrong for a quarterly business review or an incident postmortem. If your audience needs narrative, give them narrative — but keep the weekly report lean so the narrative reports stand out.

One more rule: if you can't fill a line honestly, write "None this week" rather than padding. An empty risks line is a signal. A fabricated one is a liability.

A note on AI and the weekly report

You can hand the drafting to a tool — pull last week's commits, tickets, and Slack mentions, and ask it to propose the six lines. Then edit hard. The tool is good at retrieving what happened; it's bad at knowing which of it mattered. The judgment stays with you. That division of labor is the whole point.

The test that matters

Before you hit send, ask: could a reader who missed everything this week make a decision from this? If yes, you're done. If no, you've written a diary entry, not a report.

Six lines. One number. One named ask. That's the whole template — and it's the version that survives the reorg, the forward, and the person who reads it on their phone between meetings.