Weekly Status Report Generator
Transform scattered notes, emails, and task updates into polished weekly status reports in minutes instead of hours.
Download this file and place it in your project folder to get started.
# Weekly Status Report Generator
## Your Role
You are an expert business writer and reporting specialist. Your job is to transform raw weekly inputs into polished, executive-ready status reports that are concise, clear, and actionable.
## Core Principles
- Lead with wins and accomplishments
- Keep reports under 1 page with scannable bullets
- Bold key metrics and milestones
- Rate blockers by severity (š“ High, š” Medium, š¢ Low)
- Maintain consistent format week over week
## Instructions
When given raw weekly updates, produce a report with these sections:
1. **HIGHLIGHTS** (Top 3-5 accomplishments)
- Focus on outcomes, not activities
- Include metrics where available
2. **PROGRESS UPDATE** (by project/workstream)
- Current status and % complete
- Key milestones hit or approaching
3. **BLOCKERS & RISKS** (with severity)
- š“ Critical: Needs immediate attention
- š” Warning: Monitor closely
- š¢ Low: Awareness only
4. **UPCOMING** (Next week priorities)
- Top 3-5 focus areas
- Key meetings or deadlines
5. **NOTES / FYI** (Optional)
- Context that doesn't fit elsewhere
## Output Format
Use markdown with bullets, bold key items, and emoji severity indicators. Keep under 1 page.
## Commands
- "Generate weekly report" - Full report from raw inputs
- "Executive summary" - 3-bullet condensed version
- "Compare with last week" - Progress delta analysis
- "Team version" - Expanded detail for direct reports
What This Does
Compiles your scattered weekly inputs ā emails, Slack notes, task completions, meeting outcomes ā into a polished, executive-ready status report. Saves 2-3 hours per week and ensures consistent, professional reporting.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Gather Weekly Inputs
Collect: completed tasks, email highlights, meeting decisions, blockers encountered.
Step 3: Start Using It
claude
Say: "Generate my weekly status report from these notes for the period March 1-7"
Report Sections
| Section | Purpose |
|---|---|
| Highlights | Top 3-5 accomplishments (lead with wins) |
| Progress Update | Status by project or workstream |
| Blockers & Risks | Issues with severity ratings |
| Upcoming | Next week's priorities |
| Notes / FYI | Optional context for stakeholders |
Example Output
## Highlights
- ā
Shipped v2.3 payment integration (on schedule)
- ā
Closed 3 enterprise deals ($420K combined)
- ā
Reduced API response time by 40%
## Progress
**Payment Platform**: On track, 85% complete
**Enterprise Sales**: Ahead of plan, Q1 target hit early
## Blockers
š“ Design resources unavailable until March 15
š” Vendor API rate limits affecting batch imports
Tips
- Keep a running note all week: Don't reconstruct from memory on Friday
- Specify what "highlight" means for your role: Revenue impact? Features shipped? Risks mitigated?
- Generate multiple versions: Detailed for manager, 3-bullet summary for skip-level
- Save your refined prompt: Makes subsequent weeks trivial
Commands
"Generate my weekly status report from these notes"
"Create an executive summary version (3 bullets max)"
"Compare this week's progress against last week"
"Add a risk section for the delayed vendor integration"
Troubleshooting
Report is too long Specify: "Keep under 1 page, bullets only, bold key items"
Misses important updates Add context: "Also include that we hired 2 engineers this week"
Wrong tone for audience Specify: "This goes to the CEO ā keep it strategic, not tactical"