Skip to content

πŸ“Š Status Reporting ​

Keeping stakeholders informed with clear, actionable project updates.

Report structure ​

Weekly status report ​

markdown
## Project: [Name]
## Period: [Date range]
## Overall status: 🟒 On track / 🟑 At risk / πŸ”΄ Off track

### Accomplishments
- [What was completed this week]

### In progress
- [What's being worked on]

### Blockers
- [What's preventing progress + who can unblock]

### Upcoming
- [What's planned for next week]

### Risks & issues
- [New or updated risks]

### Decisions needed
- [What needs a decision and from whom]

Status indicators ​

ColorMeaningAction
🟒 GreenOn track, no issuesContinue as planned
🟑 YellowAt risk, needs attentionMitigation in progress
πŸ”΄ RedOff track, needs interventionEscalation required

Reporting cadence ​

AudienceFrequencyDepth
TeamDaily (standup)Task level
PM / LeadWeeklyFeature level
SponsorBi-weeklyMilestone level
ExecutiveMonthlyStrategic level

Best practices ​

  • Keep it short β€” one page max
  • Lead with status color, then details
  • Quantify progress (% complete, velocity, burn-down)
  • Highlight decisions needed, not just information
  • Send at a consistent time every week

Pergame Knowledge Base