Write a Project Status Report That Supports Decisions

Start with the reader and the decision

A status report should help the right people understand where the project stands and what needs attention. Before writing, identify the audience, reporting period and decisions they can make. A sponsor may need a decision on scope or resources. A delivery team may need an agreed action or handover.

APM describes a status report as a description of the current position of an activity, work package or project. This RDE exercise adds a practical question: what should the reader understand or do after reading the report?

Report against an agreed baseline

State the reporting date and the plan you are comparing against. Describe what was expected, what actually happened and what remains forecast. Separate completed work from work in progress. An activity starting is not evidence that its output has been accepted.

For a fictional training-platform project, the team expected to complete an accessibility review this week. The review has started but two pages remain unchecked. Report the incomplete review clearly instead of calling it complete because the meeting took place.

Explain the reason behind a status colour

If your organisation uses red, amber and green, apply its agreed definitions. Include a short explanation alongside the colour so readers do not need to infer the meaning. Do not invent a universal threshold or change the definition to make a report look better.

For the fictional project, an amber status could reflect a forecast delay awaiting a decision. State the cause, potential effect and proposed response. If the evidence is incomplete, say what needs checking and who will check it.

Separate facts, forecasts and decisions

Use three distinct statements: what is known, what is expected, and what decision or action is needed. A forecast is a reasoned expectation rather than a completed result. Identify important assumptions behind it.

For example: two pages remain unchecked; the reviewer expects to finish on Thursday if access is restored; the project manager needs the access issue resolved by Tuesday. These statements make responsibility and timing visible.

Keep actions and exceptions visible

Summarise important milestones, risks, issues and dependencies without copying the whole register. Link to the controlled records where your organisation permits it. Give each requested action an owner and a date. Escalate through the agreed route when the decision exceeds your authority.

Close with the next reporting date and any decisions recorded since the previous report. Your practice task: rewrite an update that says everything is on track into a short report containing evidence, one forecast and one specific action.

Source and practice note

APM provides the underlying status-report and monitoring terminology. This resource is an original RDE practice aid. The examples are fictional. Adapt it to your organisation and obtain the appropriate decision authority.

APM project management glossary

Cover image: AI-generated illustrative scene created specifically for this resource.