Project status report: what it contains and how to read it

A status report exists to support decisions, not to prove work was done. What makes it useful is not length: it is the presence of the numbers that explain where the project is going — and an honest statement of what is not known.

What it must contain

• Economic status, not just spending. Budget, actual costs, commitments and forecast to completion: variance is only visible when these four numbers are compared.
• Verifiable progress. What has been completed and on what basis it is claimed: not a gut-feel percentage.
• Top risks and open decisions. The three risks that can change the outcome, with owners and countermeasures; the decisions expected and from whom.
• Missing data declared. If a number is unavailable, the report says so: a picture with declared holes is more reliable than one that looks complete.

How to read it in five minutes

1. Look at variances before activities: where do budget or schedule deviate?
2. Ask for the evidence behind every variance: which source does that number come from?
3. Check the missing data: what is still unknown, and who knows it?
4. Close on decisions: which choice is expected from this review, and from whom?

A concrete example

I prepared a sample status report (PDF, with clearly fictional data): it shows the structure described here — economic status with variances, progress, risks, decisions and declared missing data.

Need a report right now? The free Project Status Report generator produces a structured draft in minutes.

Generate a summary from the data in ControlRoom Free

ControlRoom Free uses the plan, tasks, budget and cost data available in the project for its cockpit and evidence-based AI reviews. It includes 3 PDF/PPTX export files in total per account, as a one-time quota. It does not calculate forecasts/EAC or include structured risk or decision registers: the methodological example on this page may contain sections beyond the available product.