Project Status Report Template (and Why Green Lies)
A good status report reads in two minutes and can be argued with data. Most don't do either: they're three pages of prose that end in a green status nobody actually calculated. Here's the structure that works — and what to do with the color.
The six sections, in this order
Order matters: the committee reads top to bottom and decides whether it needs to dig deeper. The actionable part comes first.
| # | Section | What it contains |
|---|---|---|
| 1 | Header | Project, PM, sponsor, report date, period covered. Overall status (color) and a one-line headline. |
| 2 | Indicators | CPI, SPI, % complete, budget (BAC), spend to date (AC), and forecast (EAC / estimated date). With trend versus the previous report. |
| 3 | Decisions the committee needs to make | The only thing that demands action today. If it's empty, say so: "No decisions pending this week." |
| 4 | Milestones | The next 3–5, with baseline date, current estimated date, and variance in days. |
| 5 | Risks and issues | Only high-exposure ones (probability × impact), or those open more than 30 days. With owner and action. |
| 6 | Progress this period | What closed, what slipped, and why. Brief. It's context, not the message. |
Everything else — org charts, minutes, full task lists — goes in an appendix nobody opens unless something smells off. The report is what's above.
The header: the headline rules
The first line of the report has to stand on its own and be true. No "The project is progressing as planned" when SPI is 0.84. An honest headline looks like this:
"On cost (CPI 1.02). A 3-week accumulated delay in integration; the UAT milestone moves from March 12 to March 30. Requesting a decision on module C's scope."
If the headline needs more than three sentences, the project has more than one problem and they should be separated.
Why the green status lies
The status color is the most-checked box on the report and the worst-built one. It fails for three reasons:
- Whoever's reporting picks it. A PM who's had a bad week rarely paints themselves red. Green is often an act of optimism or self-protection, not a measurement.
- It has no rule. "Green" means different things on every project and every month. Without a threshold set in advance — CPI and SPI tolerance bands, milestone variance in days — the color is an opinion shaped like data.
- It lags. A project can be green on Monday and in crisis by Thursday. The color describes the past; what governs a committee is the slope of the indicators.
The "boiling frog" pattern. Green, green, green, green… red. A project reported healthy for months and then suddenly sinking was almost never healthy — it was accumulating debt the status color wasn't capturing. If your portfolio has projects that jump from green to red without passing through amber, the problem isn't bad luck — it's how the color gets calculated.
How to make the color actually mean something
Replace the PM's judgment with a rule anyone can reproduce. A simple, sufficient version:
| Color | Condition (any triggers it) |
|---|---|
| Red | CPI or SPI < 0.90 · or a key milestone > 15 days late · or a max-exposure risk with no mitigation. |
| Amber | CPI or SPI between 0.90 and 0.95 · or a milestone 5–15 days late · or an issue open > 30 days. |
| Green | Everything above within limits. And only then. |
With this rule, the color stops being negotiable in the meeting — it's calculated. And the PM can spend the report explaining the cause and the plan, instead of defending the status color.
Cadence and format
- Frequency: biweekly for projects in progress; weekly only while they're red. A daily report is a sign the project is being managed by panic.
- Length: one page. If it doesn't fit, the problem is focus, not space.
- Consistency: the same template for every project in the portfolio. The committee should be able to compare two reports without re-reading the labels.
- Traceability: each report keeps the previous one. The trend across three reports is worth more than the detail in one.
What the template doesn't fix
A good structure doesn't produce good data. The indicators in section 2 are only reliable if there's a frozen baseline and a progress criterion that isn't decided by whoever's reporting. And keeping that section up to date by hand, every two weeks, across several projects, is exactly the work a PMO shouldn't be doing with spreadsheets.
PMOvio generates the report from real data
CPI, SPI, EAC, milestone variance, and the rule-calculated color — per project and across the portfolio, ready for the committee. 15 days free, no card required.
See my portfolio →