Status Reports | Progress, Risks & Decisions
Write status reports that inform stakeholders without overwhelming them. Focus on progress toward goals, risks, blockers, and key decisions needed.
7 min read
Status reports that list every task completed are noise. Reports that only show "green" until everything is on fire are dangerous. Effective status reports give stakeholders the information they need to make decisions and maintain confidence, without wasting everyone's time.
Status Report Problems
| Bad Reports | Good Reports |
|---|---|
| Activity lists | Progress on goals |
| Always green | Honest assessment |
| Surprise bad news | Early warning |
| No context | Business impact |
| No asks | Clear decisions needed |
Report Structure
Executive Summary Format
STATUS REPORT STRUCTURE
═══════════════════════
┌─────────────────────────────────────────────────────────┐
│ PROJECT STATUS - Week of March 18 │
├─────────────────────────────────────────────────────────┤
│ Overall: 🟡 YELLOW (was Green) │
│ Timeline: 🟢 On track │
│ Budget: 🟢 On track │
│ Risk: 🟡 Medium │
└─────────────────────────────────────────────────────────┘
SUMMARY (2 sentences):
Authentication milestone completed on time. API performance
issue discovered requires 2-day investigation, no timeline
impact expected.
PROGRESS THIS WEEK:
├── ✓ User login flow complete and tested
├── ✓ OAuth integration deployed to staging
├── ⏳ Password reset in progress (80%)
└── ○ Session management starting Monday
CONCERNS:
├── 🟡 API response time degraded (investigating)
└── 🟡 QA capacity tight next week
DECISIONS NEEDED:
└── OAuth provider selection by Mar 22 (see options doc)
NEXT WEEK:
├── Complete password reset
├── Begin session management
└── Performance testing results
Status Indicators
STATUS INDICATOR DEFINITIONS
════════════════════════════
OVERALL STATUS:
🟢 GREEN - On track, no significant issues
🟡 YELLOW - Risks present, mitigation in progress
🔴 RED - Off track, needs intervention
WHEN TO USE EACH:
GREEN:
├── Meeting or ahead of schedule
├── No major blockers
├── Risks are low and managed
└── Stakeholders need not worry
YELLOW:
├── Risks that might impact timeline
├── Issues being actively worked
├── Need stakeholder awareness
└── Might need future decisions
RED:
├── Will miss commitment
├── Need immediate help
├── Significant scope/timeline change
└── Escalation required
RULE: If you're uncertain, go yellow.
Surprising stakeholders with red is worse.
Report Content
What to Include
CONTENT GUIDELINES
══════════════════
ALWAYS INCLUDE:
├── Overall status with trend
├── Progress on key milestones
├── Current risks and blockers
├── Decisions needed
├── Next steps
└── Timeline check
INCLUDE WHEN RELEVANT:
├── Budget status
├── Resource changes
├── Scope changes
├── External dependencies
├── Customer feedback
└── Metrics/KPIs
NEVER INCLUDE:
├── Every task completed (too detailed)
├── Technical jargon (know audience)
├── Blame for problems
├── Vague status ("going well")
├── Surprises (raise early instead)
└── Decisions already made (just state them)
Progress Reporting
PROGRESS: GOOD VS BAD
═════════════════════
BAD (activity list):
"This week we:
- Had 3 meetings
- Fixed 12 bugs
- Merged 8 PRs
- Updated documentation"
GOOD (progress on goals):
"Authentication milestone: 80% complete (was 60%)
├── ✓ Login flow: Complete
├── ✓ OAuth: Complete
├── ⏳ Password reset: 80%
└── ○ Sessions: Starting next week
On track for March 29 target."
BAD (vague):
"Making good progress on development."
GOOD (specific):
"Completed 48 of 55 points (87%) with
3 days remaining. Sprint goal achievable."
Risk Reporting
RISK REPORTING FORMAT
═════════════════════
RISK: API Performance Degradation
Impact: 🟡 Medium
- Could delay load testing milestone
- May require additional dev time
Status: Investigating
- Root cause identified: N+1 query
- Fix estimated: 2 days
Mitigation:
- Fix being prioritized this sprint
- Will not impact launch date
- Contingency: Can launch with reduced capacity
Decision Needed: None
Owner: @mike
Next Update: March 20
─────────────────────────────────────────
RISK: QA Capacity Constraint
Impact: 🟡 Medium
- Testing might not complete on time
Status: Monitoring
- Current QA: 2 people
- Needed for final phase: 3
Mitigation Options:
1. Shift developer to QA assist
2. Extend timeline 2 days
3. Reduce test scope
Decision Needed: By March 22
Owner: @sarah
Report Types
Weekly Status Report
WEEKLY STATUS TEMPLATE
══════════════════════
To: Stakeholders
Subject: [Project] Weekly Status - Week of [Date]
## Status Summary
| Area | Status | Trend |
|----------|--------|-------|
| Overall | 🟢 | → |
| Timeline | 🟢 | → |
| Budget | 🟢 | → |
| Quality | 🟢 | → |
## Key Accomplishments
- [Milestone/goal achieved]
- [Milestone/goal achieved]
## Concerns & Risks
- [Risk + mitigation]
## Decisions Needed
- [Decision + deadline + owner]
## Next Week Focus
- [Priority 1]
- [Priority 2]
## Metrics
- Sprint: 48/55 points (87%)
- Bugs: 3 open (down from 7)
- Velocity: 52 pts/sprint
Milestone Report
MILESTONE REPORT TEMPLATE
═════════════════════════
# Milestone: User Authentication
STATUS: 🟢 COMPLETE (on time)
## Summary
Delivered complete authentication system including
login, OAuth, password reset, and session management.
## Deliverables
| Item | Status | Notes |
|-------------------|----------|--------------------|
| Login API | ✓ Done | Deployed to prod |
| OAuth (Google) | ✓ Done | Deployed to prod |
| Password Reset | ✓ Done | Deployed to prod |
| Session Mgmt | ✓ Done | Deployed to prod |
| Documentation | ✓ Done | In product wiki |
## Metrics
- Planned: 12 days
- Actual: 12 days
- Story points: 48 completed
## Lessons Learned
- OAuth integration simpler than expected
- Password reset required more edge cases
- Early QA involvement prevented late fixes
## Next Milestone
User Profile Management - Starting March 25
Automating Reports
GitScrum Report Data
USING GITSCRUM FOR REPORTS
══════════════════════════
DATA FROM GITSCRUM:
├── Sprint progress (points completed)
├── Task completion rates
├── Blockers (tasks with blocked label)
├── Overdue items
├── Burndown/up charts
└── Cycle time metrics
AUTOMATED WEEKLY DIGEST:
─────────────────────────────────────
Sprint 23 Progress Report
Dates: Mar 18-24
VELOCITY:
├── Completed: 32/55 points (58%)
├── Remaining: 23 points
├── Projected: On track ✓
TASK STATUS:
├── Done: 12 tasks
├── In Progress: 5 tasks
├── Blocked: 1 task ⚠
BLOCKERS:
└── [TASK-123] Waiting for API specs
View full dashboard: [link]
─────────────────────────────────────
Best Practices
For Status Reports
Anti-Patterns
STATUS REPORT MISTAKES:
✗ Always green until disaster
✗ Activity lists instead of progress
✗ Burying bad news in details
✗ No trend indicators
✗ Technical jargon for non-tech audience
✗ Too long (no one reads)
✗ Surprising stakeholders
✗ No decisions or asks