# Project status report template: lead with the decision a sponsor needs

Write a concise sponsor update that separates baseline, forecast, evidence, risk and the decision needed. Includes weak and stronger examples.

Canonical: https://project.responseshift.academy/project-status-report-template/
Publisher: Response Shift
Updated: 2026-10-31

## Report the future consequence

A status report helps a reader decide where attention or authority is needed. An activity diary can be accurate and still conceal a missed commitment. Start with the delivery forecast and the decision required, then provide the evidence that supports them.

Define what your status colours mean. In the fictional example, amber means the commitment is threatened but a time-bound recovery option remains available; red means the current forecast misses it without an approved remedy. These are teaching definitions, not universal standards.

## Worked example: replace a reassuring update



| Weak update | Stronger update |
| --- | --- |
| Installation is progressing well. Testing is next. | Forecast completion is day 12 against the day-11 baseline. Configuration gained three days; two days of buffer are consumed. |
| We are monitoring supplier delays. | The delivery lead will confirm rental availability by day 4. Without confirmation, the one-day slip remains. |
| Sponsor support would be useful. | Sponsor: approve rental cost up to 1,500 units by day 4, or accept a one-day opening delay. Figures are illustrative. |

## Keep the baseline visible

Show the last authorised baseline and today’s forecast side by side. A forecast changes as evidence changes. A baseline changes through the agreed control process. Relabelling a late forecast as the plan erases the very information the sponsor needs.

Separate facts, estimates and decisions. “Supplier has confirmed dispatch” is evidence. “Installation should recover a day” is an estimate with assumptions. “Approve overtime” is a decision that needs an owner and deadline.

## Copyable one-page update



```text
Reporting date / period / owner:
Overall status and agreed definition:
Baseline finish / current forecast / variance:
Baseline budget / forecast cost / variance:
Completed and accepted since last report:
Next milestone and acceptance condition:
Top issue or risk / response owner / due date:
Decision requested / options / recommendation:
Latest useful decision date / effect of no decision:
Evidence and assumptions:
```

- [Download the template (Markdown)](https://project.responseshift.academy/project-status-report-template/project-status-report-template.md)
- [Download the worked example (CSV)](https://project.responseshift.academy/project-status-report-template/project-status-report-example.csv)

## Cut detail without cutting truth

Keep supporting task detail in the schedule and issue log. The update should link to it rather than reproduce every row. A sponsor can then inspect the evidence without losing the central decision.

Before sending, read only the first three sentences. Can the reader tell whether the commitment is credible, what changed and what you need? If not, revise the opening. Do not let a green overall label override a material cost, quality or safety exception.

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)

- [APM: project controls background](https://www.apm.org.uk/resources/what-is-project-management/what-is-project-controls/)
