Weekly Status Report Template

Free weekly status report template with TL;DR, highlights, progress, risks, next steps, metrics, and help-needed sections for clear weekly team updates.

What's included

  • Executive-friendly TL;DR section at the top
  • Highlights list for wins, impact, and visible progress
  • Workstream table with status, progress, and notes
  • Challenges and risks section with mitigation context
  • Next-week priority list ordered by importance
  • Help-needed section for specific stakeholder asks
  • Metrics table for week-over-week comparison
  • Notes area for decisions, lessons, and context

Preview

Weekly Status Report - Week of [YYYY-MM-DD]

Author: [Your name]
Team / Project: [Team or project]
Reporting period: [Start] to [End]
Audience: [Manager, team, stakeholders]

TL;DR

[One or two sentences: what got done, what is coming next, and anything urgent. Put the most important message first.]

Highlights

  • [Big win or milestone]
  • [Customer, team, or business impact]
  • [Another accomplishment worth noticing]

Progress This Week

WorkstreamStatusProgressNotes
[Project / workstream 1][On track / At risk / Blocked][What moved forward][Context]
[Project / workstream 2][On track / At risk / Blocked][What moved forward][Context]

Challenges & Risks

  • [Risk]: [Impact], [mitigation], [owner]
  • [Blocker]: [What is blocked and what help is needed]

Plans for Next Week

  1. [Top priority - the one thing that makes next week a win]
  2. [Second priority]
  3. [Third priority]

Help Needed

  • [Specific ask] - from [person/team], by [date], because [reason]

Metrics

MetricThis WeekLast WeekTrend
[Metric 1][#][#][Up / Down / Same]
[Metric 2][#][#][Up / Down / Same]

Notes & Context

[Optional: staffing changes, decisions made, lessons learned, or context that helps readers understand the week.]

How to use this template

  1. Write the body before the TL;DR — Start with progress, risks, and plans so you know what matters. Then compress the week into a short TL;DR that busy readers can understand quickly.
  2. Use specific outcomes — Replace vague phrases like "made progress" with concrete outcomes, numbers, shipped work, or decisions. Specifics make the report credible and easier to act on.
  3. Surface risks early — A good status report does not hide problems. Name the impact, the mitigation plan, and the help needed while there is still time to respond.
  4. Make asks easy to answer — Help-needed items should name who you need, what you need, and by when. Clear asks get faster responses than broad requests for support.
  5. Send it on a predictable schedule — Choose the same day and time each week. Predictability trains readers to expect the report and helps you build a clean reporting habit.

Frequently asked questions

What should a weekly status report include?

A weekly status report should include accomplishments, progress against priorities, risks or blockers, plans for next week, and any help needed. This template also includes a TL;DR and metrics table so managers and stakeholders can scan it quickly.

How long should a weekly status report be?

Aim for one page or about five minutes of reading time. The TL;DR should be understandable in 30 seconds. If the report gets too long, move details into linked notes and keep the main update focused on decisions, progress, and risk.

Who should receive a weekly status report?

Send it to your direct manager, project stakeholders, and any teams that depend on your work. Avoid sending it to people who cannot use the information. A smaller, relevant audience is more likely to read and respond.