In brief

A useful status report explains current health, material change and the action or decision needed next. Build the report, improve weak reporting or explore the Project Status Report template.

1. What a project status report is

A project status report is a time-bound view of delivery performance and outlook. It helps sponsors, governance groups and delivery leaders understand progress, variance, material risks and issues, decisions and immediate priorities.

The report should reflect the approved baselines and reporting rules used by the project. Status labels only become useful when readers understand their meaning and the evidence behind them.

2. When to report

Report at a rhythm that supports decisions. The reporting period, data cut-off and intended audience should be clear. Use additional exception reporting when a material matter cannot wait for the next cycle.

3. Common status report mistakes

  • repeating activity completed without explaining progress towards outcomes or milestones
  • using red, amber or green labels without evidence or agreed definitions
  • reporting a past position while hiding a deteriorating forecast
  • listing every risk and issue instead of selecting material items
  • omitting decisions because the team hopes to resolve them informally
  • changing figures between reports without explaining the movement

4. How to write a project status report

  1. Set the reporting context. State the period, cut-off date and approved baseline used.
  2. Summarise overall health. Explain the evidence behind the current view and whether it has changed.
  3. Report milestone progress. Show completed, upcoming and forecast milestones, including material variance.
  4. Explain cost and resource pressure. Use the measures appropriate to the project's approved controls.
  5. Highlight risks and issues. Select items that affect objectives, tolerances or decisions.
  6. State decisions and support needed. Name the decision-maker and the date by which action is needed.
  7. Finish with the forward look. Identify priorities and pressure points for the next period.

A concise explanation is more useful than a favourable label. For example: “Testing remains on track, but supplier access must be confirmed by Friday to protect the planned rehearsal date.”

5. How PMOEasy helps

The Project Status Report template provides an editable reporting structure. The RAID Log template can hold the supporting risks, assumptions, issues and dependencies referenced in the report.

6. Make reporting easier to act on

Explore the Project Status Report template.

For consistent project and portfolio reporting, view the Reporting Bundle.