Evaluate project status
In the app: Project → Control → Overview (Project status · Trend · Decisions needed) · Knowledge Base → Generate report → Status Report
PMP ECO · Process (41%) · Task Pr9. Read the whole project against its baselines, see which way it's heading, and turn that into the decisions somebody has to make, with their name on them.
What it is
Status evaluation turns raw numbers into something people can act on:
- Work performance data: what happened. Hours, costs, dates, test results, risks raised.
- Work performance information: the data compared with the plan. Variance (SV, CV, days against the baseline), indices (SPI, CPI), the reserve left, coverage.
- Work performance reports: the information organised for an audience, with forecasts and recommendations. The status report is the most common one.
Three ideas make a status evaluation honest:
- Every area, not just the easy ones. Schedule and cost are the headline, but funding, scope, risk, procurement, resources, quality and governance can sink a project that is "on budget".
- Trend over snapshot. A CPI of 0.947 is a number. A CPI that has dropped every month for six months is a story, and it says where the project will be next month.
- Status exists to drive decisions. A report that lists problems without asking anyone to decide anything is a newsletter.
A common way to show status is RAG: red, amber, green. The trap is "watermelon" reporting: green on the outside, red on the inside, usually because a red area got averaged away.
Why it matters
- Sponsors decide from the report, not from the data. If the report hides a red, the decision that would have fixed it isn't taken.
- Trends give lead time. A slow slide caught in month two can be corrected cheaply; the same slide reported at month six is a re-plan.
- Ownership makes action happen. "The HVAC order is late" is information; "the PM awards it this week" is a decision with an owner.
Where you do it in VanillaPM
- Control → Overview → Project status reads every area from the module that owns it (earned value, schedule baseline, reserves, funding, the integrated plan's checks, the risk register) and gives each one a status and a one-line headline with the number that matters. Overall = the worst area: nothing gets averaged away.
- Trend plots SPI and CPI per reporting period against the 0.95 threshold, and the forecast finish against the baseline, period by period.
- Decisions needed lists what the status asks someone to decide, and who: the sponsor, the change control board, or the PM.
- Status report (the button on the card, or Knowledge Base → Generate report) writes it up as a governed, versioned document: summary, status by area, trend, decisions, top risks and open issues, with owners by name. Each report records that period, so the next one shows the trend.
Walked example — Coral Ridge Resort
It's mid-November 2026, a third of the way through. The steering committee meets monthly.
The status is Action required: two areas are red and seven amber.
- Red: risk. The USD 1.75M of contingency left covers only 54% of the USD 3.25M expected loss.
- Red: procurement. The HVAC order is past its order-by date (Pr5).
- Amber: the forecast finish is 12 days late (Pr8), the cost forecast needs management reserve (Pr6), a cash gap opens in November 2027, CR-05 is waiting for a decision, two crews are over capacity, the facade testing has no budget, and the charter is still unsigned.
None of this happened suddenly. Six monthly reports show CPI sliding from 0.995 to 0.947 and SPI from 0.990 to 0.943, and the forecast finish moving 3 days later every month since August. In June, the trend was already the warning.
The workspace — the theory behind each screen
Every screenshot is the actual sample project, not a mock-up.
1 · Status: every area, and the worst one sets the overall
The theory: work performance information. Compare actual performance with the plan in every knowledge area, and make the overall status honest: one red area makes the project red, however good the rest looks.

Reading the screenshot: Project status: Action required, as of 16 Nov 2026. Each area has a dot and the number that matters. Schedule: forecast finish 12 Sep 2028, 12 days after the baseline. Cost: CPI 0.947, heading for USD 45.85M. Funding: a cash gap of up to USD 2.57M. Risk (red): 54% of the expected loss covered. Procurement (red): the HVAC order is late. Resources, Quality, Scope and Governance are amber, each with its reason.
✅ Do report every area, including the ones that are uncomfortable.
❌ Avoid averaging. A green overall with a red inside is a watermelon.
2 · Trend: the direction matters more than today's number
The theory: trend analysis. Plot the indices over successive periods. A steady decline is a signal long before it crosses a threshold, and it forecasts where the next period will land.

Reading the screenshot: six periods, June to November. CPI (amber line) 0.995 → 0.947; SPI (blue) 0.990 → 0.943. Both crossed the 0.95 threshold only this month, but both have fallen every single month. Underneath, the forecast finish against the baseline: on time, on time, +3, +6, +9, +12 days. Nothing has been absorbed; each month added to the last.
✅ Do show at least three periods, so a reader sees a direction, not a point.
❌ Avoid waiting for a threshold. By the time a trend crosses it, the cheap fixes are gone.
3 · The status report: decisions, with owners
The theory: work performance reports. The report organises the information for its audience, adds forecasts, and recommends actions. For a sponsor, the most important section is what they are being asked to decide.

Reading the screenshot: Decisions needed, red areas first: the sponsor decides on topping up contingency, earmarking up to USD 695k of management reserve and signing the charter; the change control board decides the recovery plan and CR-05; the PM awards the HVAC package now; the owner brings equity forward before the cash gap. Then Top risks by expected loss, each with a named owner: the cyclone risk (USD 900,000) with the site engineer, customs delays with the architect, the loan rate with the quantity surveyor.
✅ Do end every status report with the decisions needed, and who makes each one.
❌ Avoid escalating what the PM can decide. Send the sponsor only what needs the sponsor.
Best practices & pitfalls
- Do keep the reporting period regular; trends need comparable points.
- Do forecast: say where the project will finish, not only where it is.
- Do match the report to the audience: a sponsor needs decisions, the team needs the work.
- Pitfall: watermelon reporting. Green outside, red inside, until the day it can't be hidden.
- Pitfall: reporting activity ("12 pours completed") instead of performance ("SPI 0.943").
On the PMP exam
Know the flow work performance data → information → reports, and that variance analysis, trend analysis and forecasting (EAC, ETC, estimated finish) turn data into information. Know that status reports go to stakeholders according to the communications management plan. In scenarios, the best answer analyses the variance and its trend, identifies the cause, recommends a corrective or preventive action, and raises a change request where the baseline is affected. Simply distributing the report, or waiting another period to see if things improve, is rarely the right answer.