1 Executive summary
Lead with outcomes, changes, and exceptions—not a diary of activities.
2 Delivery and commitments
| Measure | Current position |
|---|
| Key milestones | |
| Scope changes | |
| Dependencies | |
| Next week’s priorities | |
4 Top risks and mitigations
Risk 1
Risk 2
5 Decisions and support required
6 Improvement actions
✓ Rules for good weekly reporting
- Report outcomes and exceptions, not a diary of activities.
- Include changes from the previous reporting period.
- Every amber or red status explains why, what happens next, and who owns the response.
- Distinguish committed dates from forecasts and estimates.
- Link to source systems instead of duplicating detailed technical evidence.
- Avoid misleading completion percentages when remaining work or uncertainty is significant.
- Treat a missing update as a visibility problem—not proof that a team is healthy or unhealthy.