Project Status Report: Definition, Sections and Cadence
A project status report is the periodic summary of where a project stands: overall and dimensional RAG, progress since the last report, what is planned next, milestone position against baseline, financials, and the risks, issues and decisions needing attention. It is normally weekly at team level and monthly for governance, and it goes out on a fixed day.
What it contains
| Section | What it answers |
|---|---|
| Header | Project, reporting period, author, date, distribution |
| Overall status | One RAG rating with a one-line reason |
| Dimension status | Schedule, cost, scope, resource, quality, risk — each rated separately |
| Progress this period | What completed, stated as outcomes rather than activity |
| Planned next period | What is expected to complete, so the next report can be checked against it |
| Milestones | Baseline, forecast and actual dates for the next few checkpoints |
| Financials | Spend to date, committed, forecast at completion against budget |
| Risks and issues | Only the ones the reader can affect, each with an owner and next action |
| Decisions required | What is being asked for, from whom, and by when |
| Dependencies | Commitments owed by other teams, with dates |
How it is used
The report serves two audiences with one document, which is why the ordering matters. A delivery reader wants progress and blockers; a governance reader wants status, financials and the ask. Putting the RAG summary and the decisions required at the top serves both — the second reader can stop after half a page.
Cadence is normally weekly for the team-level report and monthly for the governance version, with the weekly reports being the source of the monthly one rather than a separate exercise. The weekly status report holds the one-page Excel version with a worked example alongside it; the status report deck covers the same content in a format that survives being forwarded to an executive; and the one-pager reduces it to a single slide. What belongs in each section, and how long the report should be, is covered in the status report guide. Where the report is the input to a governance forum rather than a distribution list, the ordering shifts again — see the steering committee report guide.
Where it goes wrong
- Activity instead of outcome. "Continued work on the interface" tells the reader nothing about position.
- Green until it is red. A status that holds green for eleven weeks and turns red in week twelve was not being reported; it was being managed.
- No dates on risks. A risk with an owner and no next action or date is a note, not a control.
- Length. Beyond about two pages, the sections that matter get read by fewer people each week.
- Irregular issue. A report that arrives on Tuesday, then Friday, then not at all, stops being read even when it is accurate.
- No ask. A report that requests nothing gives senior readers no reason to open it.
- Rewritten from scratch weekly. Where the report is not generated from the trackers, the numbers in it and the numbers in the log diverge within a month.
Related terms
Highlight report — the PRINCE2 equivalent, produced for the project board at an agreed frequency. Exception report — raised outside the cycle when a tolerance is forecast to be breached. RAG status — the rating scheme the report is built around. Milestone — the object schedule status is measured from. SteerCo pack — the governance-facing assembly of the same content.
Questions
How often should a project status report go out?
Weekly at team and workstream level, monthly for governance. The day matters as much as the frequency: a fixed slot makes the report part of the week rather than an interruption to it.
How long should a status report be?
One page for the weekly, up to two for a governance version. If more detail is needed, it belongs in an appendix that readers can ignore without losing the position.
Who writes the project status report?
The project manager, from data the workstream leads supply. Where the report is compiled from a shared tracker rather than written afresh, the numbers stay consistent with the underlying logs.
What is the difference between a status report and a highlight report?
Largely terminology. Highlight report is the PRINCE2 term for the periodic report from project manager to project board; status report is the general term and its audience is usually broader.