Weekly Status Report Template

A simple format your team will actually use

Turn updates into alignment (without chasing people)

Weekblast collects weekly updates automatically, keeps a searchable history, and gives your team visibility in minutes.

Get started free See how it works

FAQ

How long should a weekly status report be?
Short. Three to five bullet points per section is the target. If it takes more than 10 minutes to write, it's too long. The goal is signal, not volume.
What should a weekly status report include?
At minimum: what was completed, what's blocked, and what's planned for next week. Some teams also include a mood or confidence indicator, but the three core sections are enough for most.
How do you get the whole team to actually send their status report?
Two things: make it easy to submit, and acknowledge it when they do. If writing a report feels like busywork that nobody reads, people stop. Tools like WeekBlast reduce friction and keep a visible record.
Should the weekly status report be sent to the whole team or just managers?
Both. Managers need it for visibility and decision-making. Team members benefit from reading each other's updates too - it cuts down on duplicate work and "what are you working on?" messages.
See how Weekblast works →

A good weekly status report answers three questions: what got done, what's in the way, and what's coming next. The format below is simple enough that people will actually fill it out, and specific enough that managers will actually read it.

The Template

Copy this format and share it with your team. Ask everyone to fill it out once a week.

Weekly Status Report
Week of: [Date]
Name: [Your Name]

COMPLETED THIS WEEK
- [What you finished or shipped]
- [Another completed item]
- [Another completed item]

IN PROGRESS
- [What you're actively working on]
- [Another in-progress item]

BLOCKERS / NEEDS ATTENTION
- [What's slowing you down or needs a decision]
- [Who or what you're waiting on]

NEXT WEEK
- [Top priority for next week]
- [Other planned work]

NOTES
- [Any context worth sharing - decisions made, risks flagged, etc.]

Filled Example

Here's what a completed weekly status report looks like for an engineer:

Weekly Status Report
Week of: March 10, 2026
Name: Alex Chen

COMPLETED THIS WEEK
- Shipped the new onboarding flow to production
- Fixed the session timeout bug that was blocking QA
- Reviewed and merged 4 PRs from the backend team

IN PROGRESS
- Refactoring the auth middleware (60% done)
- Draft spec for the notifications redesign

BLOCKERS / NEEDS ATTENTION
- Need design sign-off on the notification spec before I can proceed
- Waiting on infra to provision the staging environment for the new service

NEXT WEEK
- Finish auth middleware refactor
- Start notifications implementation once spec is approved

NOTES
- The onboarding flow is seeing a 12% better completion rate in early data
- Flagging that the staging bottleneck may push the service launch by a week

Tips for Making It Stick

  • Keep it short - 3 to 5 bullet points per section is enough
  • Send it on the same day every week so it becomes a habit
  • Don't editorialize - bullet points beat paragraphs
  • Call out blockers explicitly so they don't get buried

Skip the Manual Work

WeekBlast collects weekly status reports automatically. Team members send a blast, managers read it in a shared feed. No chasing, no formatting, no lost emails.

Try WeekBlast free and replace the manual template with automatic weekly updates.

BLAST

Ready to light the fuse?

Join 10,000+ workers tracking their week.