How to Write a Weekly Report: Template and Examples

A weekly report answers three questions in this order: what moved, what stalled, and what needs a decision. Keep it under 200 words if nothing changed. Keep it blunt if something did.

Most weekly reports fail because they list activity instead of progress. "Met with design, reviewed spec, updated tickets" tells your manager nothing she didn't already assume. The report exists to save her the cost of asking.

What goes in a weekly report

Four blocks, in this order:

1. What shipped or moved — outcomes, not effort. "Shipped the billing fix" beats "worked on billing."
2. What's blocked — name the blocker and who can clear it. A blocker without an owner is a complaint.
3. What changed in scope or priority — the part everyone forgets. If you dropped something, say so before someone notices.
4. What you need — one ask, specific. "Approve the vendor by Thursday" is actionable. "Guidance on vendor" is not.

Leave out the play-by-play. Your calendar already has it.

A weekly report template you can copy

## This week
- Shipped: [outcome, not task]
- Progress: [thing in motion, % or milestone]

## Blocked
- [ blocker ] — needs [ person/team ] by [ date ]

## Next week
- [ outcome you're committing to ]

## Needs a decision
- [ one specific ask ]

That's it. Five lines covers most weeks. If your report is routinely longer than half a page, you're writing a status document, not a weekly report, and the format is doing you no favors.

Weekly report example

Here's what a real one looks like when the week went sideways:

This week Shipped the invoice export fix — 40 customers were hitting it. Onboarding flow stalled at 60% because the SSO provider changed their token format mid-week; patch is written, waiting on their sandbox.

Blocked SSO integration — needs security review from Priya before Thursday, or we miss the enterprise pilot kickoff.

Next week Get SSO to staging. Hard commitment: export fix shipped.

Needs a decision Approve the fallback auth path by Wednesday if security review slips.

Notice what's missing: no adjectives, no effort narrative, no apology. The reader knows exactly what to do next.

Common mistakes

Writing for your manager's manager. A weekly report that reads like a press release gets skimmed and forgotten. Write for the one person who can unblock you.

Hiding the stall. The week nothing shipped is the week your report matters most. Teams discover problems late because early reports said "on track."

Recapping instead of deciding. If your report never asks for anything, you've turned a decision tool into a diary.

Making it a ritual. Some weeks genuinely have nothing to report. Send three lines. Sending 400 padded words weekly trains everyone to stop reading.

The one thing to change this week

Add the "needs a decision" line. Most templates skip it, and it's the line that makes the other four worth sending.