itsual Status Report
Overview
Status reports should answer: Where are we? Are we on track? What needs attention? What decisions are required?
When to Use
- Project or program status updates
- Weekly / bi-weekly / monthly reports
- Steering committee or leadership updates
- Cross-team progress communication
Recommended Structure
- Snapshot (overall status, RAG/health, date)
- Highlights / progress this period
- Key metrics or milestones
- Risks, issues, and blockers
- Decisions needed
- Plan for next period
- Appendix (detail) if required
Principles
- Put the most important information first
- Use consistent status indicators (RAG, trends)
- Separate facts from asks
- Be honest about problems early
- Keep the main view to 1–2 pages when possible
Verification
- Overall status is obvious in seconds
- Risks and decisions needed are impossible to miss
- Progress claims are specific and evidence-based