Status Report
What is a Status Report?
A status report is a recurring summary for stakeholders covering progress since the last update, overall health, risks, decisions needed and next steps. It lets people outside the daily work stay informed without attending every meeting.
Updated November 2026 · 3 min read
A status report is a short, regular update that tells stakeholders where a project, program or initiative stands: progress since the last report, current health, risks and issues, decisions needed and what comes next. Its purpose is to give people who are not involved day to day enough information to stay aligned, spot problems early and act when needed, without having to attend every meeting. It is also called a progress report or status update, and is often sent weekly.
A good status report is easy to scan in a minute, honest about problems and specific about what the reader needs to do. A poor one lists activities, hides bad news in long paragraphs and leaves the reader unsure whether anything is wrong.
What to include in a status report
| Section | What it covers |
|---|---|
| Overall status | A single rating, often red, amber or green, with a one-sentence reason |
| Summary | Two or three sentences on where things stand |
| Progress | Milestones reached and key work completed since the last report |
| Schedule, scope and budget | Current position against plan, with variances explained |
| Risks and issues | What could go wrong or has gone wrong, impact, owner and mitigation |
| Decisions and help needed | Specific asks of stakeholders, with deadlines |
| Next steps | What will happen before the next report |
Ratings are only useful when everyone agrees what they mean. See RAG status for common definitions.
Types of status reports
- Project status report. Weekly or biweekly for a single project with a defined end.
- Program or portfolio report. Rolls up several projects for leadership, usually as a dashboard with exceptions highlighted. See portfolio dashboard.
- Product or team update. Progress on roadmap items, metrics and upcoming releases.
- Executive summary. A one-page or one-paragraph version for senior leaders.
How to write a status report
- Know the audience. Executives need status, risks and decisions; team leads may need more detail.
- Lead with the bottom line. Put the overall status and the most important point first.
- Use data from the source. Pull progress from the work tracking system rather than estimating from memory.
- Explain changes. If the status changed, say why. If a date moved, give the new date and the cause.
- Make asks explicit. Name who needs to decide what, by when.
- Keep the format consistent. The same structure each time lets readers find what changed quickly.
A status report example
Consider a hypothetical weekly report for a billing system migration:
- Status: Amber. Data migration testing is two weeks behind because the vendor's test environment was delivered late.
- Progress: 31 of 50 planned tasks complete (62%). Customer data mapping signed off.
- Budget: $260,000 of $400,000 spent (65%), roughly in line with the 62% of tasks completed.
- Risk: If testing slips another week, the cutover moves past the quarter-end close. Owner: migration lead. Mitigation: running two test cycles in parallel.
- Decision needed: Finance to confirm by Friday whether a cutover in the first week of the new quarter is acceptable as a fallback.
- Next week: Complete test cycle 1, start user acceptance testing for invoicing.
A reader learns in under a minute that the project is at risk, why, and what is needed from them.
Common pitfalls
- Watermelon reporting. Green on the outside, red inside: reporting green until a problem can no longer be hidden destroys trust in every future report.
- Activity instead of progress. "Held five meetings" says nothing about whether the work is on track.
- Burying the ask. A decision request on page three is often missed.
- Too long. If the report takes ten minutes to read, most stakeholders will skim the first line only.
- Manual compilation. Reports assembled by hand from several tools take hours and drift from the real data.
Status reports are one part of a broader communication framework and often follow a communication calendar. For projects, they connect to project governance, where reported risks and decisions are acted on.
Related terms: highlight report.
Frequently asked questions
What should a project status report include?
A useful status report opens with an overall rating, often red, amber or green, plus a one-sentence reason and a short summary. It then covers progress since the last report, position against schedule, scope and budget, risks and issues with owners, specific decisions or help needed with deadlines, and the next steps before the following report.
How often should a status report be sent?
Project status reports usually go out weekly or every two weeks for the life of a single project with a defined end. Program and portfolio reports roll several projects up for leadership, and executive summaries condense the same information into a page or a paragraph. Whatever the cadence, keep the structure identical each time so readers can spot changes quickly.
What is watermelon reporting in a status report?
Watermelon reporting is a status report that looks green on the outside while the project is red inside. Teams keep reporting green until a problem can no longer be hidden, and the sudden switch destroys trust in every later report. Shared definitions for each RAG status and honest explanations whenever a rating changes help prevent it.
Related terms
RAG Status
Red, amber or green: a quick read on whether work is on track.
Portfolio Dashboard
Status, spend, risk and progress across the whole portfolio in one view.
Project Governance
The roles and decision rights that guide projects from approval to close.
Highlight Report
A short, regular PRINCE2 report on a project's progress and risks.