Evaluate Project Status

Introduction

This lesson covers task 9 of the Process domain in the July 2026 PMP Examination Content Outline (Process carries 41% of the exam): evaluate project status. The project manager must establish metrics, analyze and reconcile data, choose and tailor artifacts, keep them accessible, assess progress, and communicate status in a way that triggers the right decisions. Earlier lessons gave you the raw measures (earned value, schedule variance, velocity, risk exposure). This lesson is about turning those numbers into a trustworthy, useful picture.

The exam rarely asks "what is the definition of a dashboard". It asks what a project manager should do when two reports disagree, when a status looks green but the evidence is red, when a stakeholder cannot open an artifact, or when the sponsor asks for a different report format. After this lesson you will be able to define meaningful metrics, reconcile conflicting data, tailor artifacts to the approach and the audience, make them accessible, read dashboards and flow charts, and communicate status honestly with recommended actions.

Learning objectives

• Select project metrics that are tied to objectives and thresholds, and reconcile data from different sources.
• Identify, tailor, create, review, update, and document artifacts for predictive, agile, and hybrid projects.
• Make artifacts accessible to the people who need them, including people with disabilities and remote teams.
• Assess progress with dashboards, burn charts, cumulative flow diagrams, and trend analysis.
• Communicate status with a clear message, an honest rating, and a recommended decision.
• Evaluate whether artifact management is effective and improve it.

1. Project metrics, analysis, and reconciliation

A metric is a measure with a definition, a unit, a data source, a collection frequency, a threshold, and an owner. A number without those attributes is only a figure. The project manager defines metrics during planning, in the measurement approach of the project management plan, and links each metric to an objective: a metric that no decision depends on is waste.

Leading and lagging indicators

A balanced set contains both. A status report that only has lagging indicators arrives after the problem is expensive.

Typical metric families

• Schedule: SV, SPI, float consumption, milestone trend, velocity, cycle time, throughput.
• Cost: CV, CPI, EAC, TCPI, burn rate, reserve consumption.
• Scope and quality: requirements completed, acceptance rate, defect density, escaped defects, rework percentage, definition of done compliance.
• Risk and issues: open risks by exposure, issues by age, blockers per week.
• People: team availability, turnover, engagement, stakeholder satisfaction.
• Value: benefits realized against the benefits plan, customer satisfaction, adoption.

Choose few, and define thresholds in advance. For example: a CPI or SPI below 0.90 is amber; below 0.80 is red and requires escalation.

Reconciling data

Reconciliation means checking that data from different sources describe the same reality before drawing conclusions. Typical conflicts:

• The finance system shows actual cost with a one-month delay, while the team tracks hours daily.
• The schedule says an activity is 80% complete, while the test report shows half of the tests failing.
• The vendor invoices differ from the received-goods records.
• Two team leads count "done" differently.

The right behavior is: identify the difference, find its cause (timing, definitions, error, scope difference), agree one source of truth, and document the rule. Do not average the numbers and do not pick the more flattering one. Where timing differs, accrue costs so that actual cost reflects work performed. Where definitions differ, align on the definition of done and the earned value rule.

Worked example: reconciling a cost conflict

Scenario. The project manager of a retail systems project reads two cost figures at the end of month 5. The project accounting system reports an actual cost (AC) of 410,000. The team time tracking, multiplied by rates, plus the purchase orders received, gives 468,000. The planned value is 450,000 and the earned value is 430,000.

Step 1: do not decide yet. A gap of 58,000 is 12% of the larger figure. Computing CPI with either number gives 430 / 410 = 1.05 (favorable) or 430 / 468 = 0.92 (unfavorable). The conclusion changes completely, so the data must be reconciled first.

Step 2: investigate the source. The accounting system posts vendor invoices only after approval, and a 40,000 hardware delivery plus 18,000 of contractor time are awaiting approval.

Step 3: apply the agreed rule. The cost management plan says actual cost includes commitments for work performed, whether or not invoiced. The right AC is therefore 468,000.

Step 4: recompute. CPI = 430,000 / 468,000 = 0.92. SPI = 430 / 450 = 0.96. The project is over cost and slightly behind.

Step 5: report. Show the reconciled figure, explain the difference, and recommend an action (for example, review the forecast and use the cost reserve process).

Why the other choices are weaker. Reporting 410,000 is optimistic and misleading. Averaging the two figures has no basis. Asking finance to stop invoice approval to "fix" the number manipulates data. Waiting until next month hides a likely overrun.

2. Identify and tailor artifacts

Artifacts are the documents, tools, and records that carry project information: charters, plans, registers, logs, reports, backlogs, boards, dashboards, and decision records. Task 9 expects you to identify what is needed, tailor it, and then create, review, update, and document it.

Tailoring by approach

The project manager chooses the lightest artifact that meets the need. A twelve-page status report for a team that meets daily at an information radiator is wasteful; a single sticky-note board is not enough for a regulated program with contractual reporting.

Principles for tailoring

1. Start from the decision. Ask which decision this artifact informs and who takes it.
2. Start from the audience. Executives need outcomes, exceptions, and decisions; team members need detail and blockers; regulators need evidence.
3. Respect organizational requirements. Organizational process assets, templates, governance, and compliance rules set the minimum.
4. Minimize duplication. One source of truth, with views for different audiences.
5. Review the tailoring. If an artifact is never read, change or stop it.

Create, review, update, document

• Create from templates in organizational process assets, adapted to the project.
• Review with the owners and the users: a risk register is reviewed by the risk owners; a dashboard is reviewed by the people who will use it.
• Update on a cadence that matches the pace of change: daily for a board, weekly for a risk log, monthly for a steering report. An out-of-date artifact is worse than none, because people trust it.
• Document version, owner, date, and location. Keep the history so that decisions can be traced.

3. Artifact accessibility

Accessibility means that everyone who needs an artifact can find it, open it, and understand it. The project manager has to think about several dimensions:

Using red, amber, and green alone fails for people with color-vision deficiency; adding labels such as "Red - critical path delay" solves it. Posting a dashboard on an intranet that vendors cannot reach fails for the vendor team. The project manager may need to set up role-based access so that confidentiality and accessibility are both satisfied.

4. Assess progress

Status tools

Reading a trend rather than a point

A single month of CPI = 0.95 is not alarming. Four months of 1.00, 0.98, 0.96, 0.95 show a decline. A good status evaluation therefore looks at the direction and the rate of change, not only the current value. In control charts, seven consecutive points on one side of the mean signal a non-random cause even if no point crosses a limit (the "rule of seven" used in PMI material).

Worked example: reading a cumulative flow diagram

Scenario. A product team shows this weekly data (stories in each state):

Step 1: look at the bands. "In test" grows from 3 to 14 while "Done" grows from 11 to 18. Development keeps feeding testing faster than testing finishes.

Step 2: compute the flow. Done increased by 7 over three weeks (about 2.3 per week). In test increased by 11. The queue in test grew by 11 (about 3.7 per week), so work arrives in test at about 6 stories per week (2.3 finished plus 3.7 queued) while only 2.3 leave.

Step 3: interpret. There is a bottleneck in testing. Throughput is limited by test capacity, not development capacity.

Step 4: act. Limit work in progress in development, swarm on testing (developers write automated tests or help with test execution), and examine why testing is slow (environment, manual tests, defects). Re-forecast the release from the throughput of 2.3 stories per week, not from development speed.

Step 5: communicate. Tell the product owner that the forecast date is based on the real throughput, and explain the planned fix.

Why the other choices are weaker. Adding more developers increases the queue in test. Telling testers to work overtime may hide the cause. Reporting "development is on track" is accurate but misses the end-to-end flow.

5. Communicate status

Status communication must match the communication management plan and the stakeholder needs: frequency, format, audience, and level of detail.

Content of a good status report

1. Overall rating with a clear definition (green, amber, red) and a trend arrow.
2. Progress against plan: milestones, scope delivered, key metrics.
3. Forecast: expected completion date and cost, with the basis.
4. Top risks and issues, with owners and next actions.
5. Changes approved and pending.
6. Decisions or help needed from the audience, with a date.
7. Next period plan.

Honesty and escalation

The rating must reflect evidence, not hopes. "Watermelon reporting" (green outside, red inside) destroys trust. A project manager reports bad news early, together with the analysis and options. If a threshold is crossed, the escalation path of the governance structure applies. The project manager does not hide a problem from the sponsor while trying to fix it quietly for weeks, unless the issue is inside tolerance and the plan says so.

Tailoring the message

6. Evaluate the effectiveness of artifact management

Artifacts consume effort. The project manager periodically asks:

• Are the artifacts used in decisions? Which ones are ignored?
• Is the information current, correct, and consistent between artifacts?
• Can stakeholders find what they need quickly?
• Does the effort of producing them match their value?
• Did a problem occur because an artifact was missing, late, or wrong?

Collect feedback in retrospectives and stakeholder check-ins, then simplify, merge, or retire artifacts. Capture the changes in lessons learned and organizational process assets so that future projects benefit.

7. Common pitfalls and exam tips

• Pitfall: reporting a single number without a threshold. "SPI is 0.93" means nothing without the rule.
• Pitfall: using inconsistent definitions of done. Percent complete becomes unreliable.
• Pitfall: relying on color alone for status. It fails accessibility.
• Pitfall: updating artifacts only before audits. They become unreliable.
• Pitfall: sending the same long report to everyone. Tailor the message.
• Pitfall: masking bad news. Escalate early with options.
• Pitfall: forcing a predictive report on an agile team. Use their transparent tools.

Exam tip: When two data sources disagree, the first step is to reconcile and verify the data, not to choose the better-looking number or to escalate the discrepancy blindly.

Exam tip: If a question mentions that a stakeholder cannot access or understand an artifact, the answer usually involves adjusting the format or access, not abandoning the artifact.

Exam tip: For agile teams, prefer information radiators and transparent working increments over heavy reports; for governance-heavy hybrid projects, keep formal reports for the baselined parts.

Exam tip: The best status communication includes a recommendation or a decision request, not only data.

8. Mini case study: the green dashboard that hid a problem

Context. A project manager runs a payments platform upgrade with a distributed team in three countries. The dashboard shows green for schedule (SPI = 1.01) and cost (CPI = 1.02). The sponsor is pleased. In a weekly check, the test lead mentions that 35% of the integration test cases are blocked by an unstable environment, and the number of open defects has doubled in two weeks. The earned value rule counts a work package as 100% when development is finished, not when it is tested. A visually impaired product owner says she cannot read the dashboard because status is shown only by colored dots. The vendor team in one country cannot open the shared report because of access rights.

Question. What should the project manager do?

Solution (commented).

1. Recognize that the green status is unreliable. The earned value rule credits unfinished work. Align the earned value rule with the definition of done (include testing), recompute EV, and expect a lower SPI.
2. Reconcile the data. Combine schedule data, test results, defect counts, and environment availability. Document the reconciled view.
3. Add leading indicators. Include blocked tests, defect trend, and environment availability on the dashboard with thresholds.
4. Report honestly. Tell the sponsor promptly that the status is amber or red once recalculated, explain why the earlier numbers looked good, and propose a recovery plan (stabilize the environment, add test capacity, re-forecast).
5. Fix accessibility. Add text labels and a table alternative for the colored status, and provide a screen-reader friendly version for the product owner. Adjust the permissions for the vendor team so they can read the relevant parts.
6. Update the artifacts and the plan. Revise the communications management plan and the measurement definitions through the appropriate change process, and record the lesson.
7. Do not hide the issue until the next steering meeting, change the thresholds to keep it green, or blame the test lead.

Key terms

• Metric: a defined measure with a source, a frequency, a threshold, and an owner.
• Leading and lagging indicator: a predictor of future results versus a record of past results.
• Reconciliation: checking and aligning data from different sources.
• Artifact: a document, tool, or record that carries project information.
• Information radiator: a visible display of current project information.
• Dashboard: a visual summary of key metrics against thresholds.
• Cumulative flow diagram: a chart of work items per state over time.
• Burnup chart: a chart of completed work and total scope.
• Accessibility: the ability of all intended users to find, open, and understand information.
• Watermelon reporting: green status on the surface while the underlying data is red.

Summary checklist

• I can define metrics with thresholds and owners, mixing leading and lagging indicators.
• I reconcile conflicting data before drawing conclusions.
• I tailor artifacts to approach, audience, and organizational requirements.
• I keep artifacts current, versioned, and documented.
• I make artifacts accessible in format, permissions, and design.
• I read trends, burn charts, and cumulative flow diagrams correctly.
• I report honestly, escalate early, and include recommended decisions.
• I review whether artifact management is effective and improve it.

Official sources

• PMI, PMP Examination Content Outline (July 2026): https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
• PMI, About the new PMP exam: https://www.pmi.org/certifications/project-management-pmp/new-exam (opens in a new tab)
• PMI, Project Management Professional (PMP): https://www.pmi.org/certifications/project-management-pmp (opens in a new tab)