Status Report Template
A structured weekly status report template with project health indicators, completed work, upcoming tasks, blockers, and metrics — designed for teams that value clarity over ceremony.
STATUS REPORT — [Project Name]
Week of [Date] | Author: [Name] | Health: [Green / Yellow / Red]
1. Summary
[One-paragraph summary: overall status, biggest win, biggest risk. This is the TL;DR for people who read nothing else.]
2. Completed This Week
• [Task/deliverable completed + outcome]
• [Task/deliverable completed + outcome]
• [Task/deliverable completed + outcome]
3. Planned for Next Week
• [Task + owner + expected completion]
• [Task + owner + expected completion]
• [Task + owner + expected completion]
4. Blockers & Risks
• [Blocker: description + impact + who can unblock]
• [Risk: description + likelihood + mitigation plan]
5. Key Metrics
• [Metric]: [value] (target: [target])
• Timeline: [% complete] | Budget: [% spent]
• Decisions needed: [What you need, from whom, by when]
How to Use This Template
Track progress all week
Keep a running list of completed tasks and emerging blockers throughout the week. Trying to remember everything on Friday leads to incomplete, inaccurate reports.
Start with health status
Set the tone immediately: green (on track), yellow (minor risks), or red (significant blockers). This primes the reader for the detail that follows.
Be specific about blockers
Name the blocker, the impact, and who can resolve it. Vague blocker descriptions like "waiting on feedback" do not get resolved. Specific ones do.
Close with asks
Every status report should end with what you need: decisions, resources, approvals, or nothing. Make it easy for readers to help you move forward.
Customize in Dewx
Inside Dewx, tell Dew: "Write this week's status report for the marketing project." Dew pulls completed tasks, open items, and blockers from the CX Hub, formats them into a clean report, and sends it to your stakeholder list. Set a weekly schedule and Dew handles it every Friday automatically.
Related Templates
Frequently Asked Questions
What should a weekly status report include?
A weekly status report should cover overall project health (green/yellow/red), work completed this week, work planned for next week, blockers and risks, key metrics or milestones, and any decisions or help needed. The goal is to give readers a complete picture in under two minutes.
How long should a status report take to write?
A good status report should take 15-20 minutes to write, not an hour. If it takes longer, you are either including too much detail or not tracking progress during the week. Keep a running log of accomplishments and blockers throughout the week so the report writes itself on Friday.
Should I include good news and bad news in a status report?
Always include both. Sharing only good news erodes credibility when problems eventually surface. Sharing only bad news creates a perception of failure even when the project is mostly on track. Balance accomplishments with honest risk assessment — this is what builds trust with stakeholders over time.
How does Dewx help with status reports?
Inside Dewx, tell Dew: "Write this week's status report for the product launch." Dew pulls completed tasks, open blockers, and metrics from the CX Hub and generates a structured report. Set a recurring schedule and Dew compiles and sends it every Friday at 4pm.
Status Reports, Automated
Simple, Transparent Pricing
Starting at $29/mo for solopreneurs. $79/mo for teams. All features included.
View pricingWeekly Reports on Autopilot
Dew writes your status report from task and project data every Friday — so you spend the afternoon shipping, not reporting.
Try Dewx FreeStop Writing Status Reports From Scratch
Dewx compiles your weekly status from task data, metrics, and blockers. Consistent format, automatic delivery, zero manual effort.