II.9 — Evaluate Project Status
II.9 · Last updated: 24/08/2026
Where this task sits
II.9 — Evaluate Project Status is the ninth task in the Process domain of the 2026 ECO. The domain carries 41% of the exam.
It has eight enablers, and they fall into two halves:
The measurement half: develop project metrics, analysis, and reconciliation · assess current progress · measure, analyze, and update project metrics · communicate project status
The artifact half: identify and tailor needed artifacts · help ensure artifacts are created, reviewed, updated, and documented · help ensure accessibility of artifacts · continually assess the effectiveness of artifact management
Four of the eight enablers are about artifact management. The reason is in the next section.
🔴 This task is a merger
What defines II.9 is not a renumbering but two jobs folded into one task.
In the 2021 ECO, II.12 — manage project artifacts was a task of its own. In 2026 that work stopped being independent and moved inside status evaluation. That is why half of the ECO's eight enablers concern artifacts.
The logic is clear enough: you know a project's status only as far as you measure and record it. Artifact management is the infrastructure of status evaluation, not a separate job.
Remember too that within the same domain the numbers II.5, II.6, II.8, and II.10 moved to other topics — match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.
Data, information, reports: three separate things
The most productive distinction on this task, and the book defines each separately.
Work performance data includes the raw observations and measurements identified during activities being performed to carry out project work. The data is often viewed as the lowest level of detail from which information is derived by other processes. It is gathered through work execution and passed to the controlling processes for further analysis. Examples: work completed, key performance indicators (KPIs), technical performance measures, actual start and finish dates of schedule activities, story points (PMBOK® 8, Guide p.143).
Work performance information is work performance data collected from controlling processes and analyzed in comparison with project management plan components, project documents, and other work performance details. That comparison indicates how the project is performing. Specific work performance metrics for scope, schedule, budget, and quality are defined at the start of the project as part of the project management plan (PMBOK® 8, Guide p.144).
Work performance reports are an output of the Monitor and Control Project Performance process (PMBOK® 8, Guide p.27).
Translated for the exam: the raw number is data, interpreted against the plan it is information, and packaged for stakeholders it is a report. "The team logged this many hours" is data; "we are 12% behind plan" is information.
Note the detail in the second definition: metrics are defined at the start of the project. A metric invented after the fact is not status evaluation.
The process that tracks status
The PMBOK counterpart of the ECO's measurement enablers is a single process.
Monitor and Control Project Performance is the process of tracking, reviewing, and reporting the overall project progress to meet the performance objectives defined in the project management plan (PMBOK® 8, Guide p.26).
The Guide links the process to measurement explicitly: it is tied to measurement because it relies on the continuous tracking, review, and reporting of project metrics to ensure alignment with the performance objectives (PMBOK® 8, Guide p.27).
Its tools include project dashboards, visual controls, and information radiators (PMBOK® 8, Guide p.27). Visual charts can also carry information such as an impediment list showing a description of the impediment, its severity, and the actions being taken to resolve it (PMBOK® 8, Guide p.214).
Metric pitfalls: the book's most practical list
The Guide enumerates six pitfalls to watch for in measurement (PMBOK® 8, Guide p.28). It is a list with direct exam counterparts:
- Hawthorne effect — the very act of measuring something influences behavior. Measuring only a project team's output of deliverables can encourage the team to focus on producing a large volume of deliverables rather than ones that would provide higher customer satisfaction.
- Vanity metric — a measure that shows data but does not provide useful information for making decisions. Measuring page views of a website is not as useful as measuring the number of new viewers.
- Demoralization — if measures and goals are set that are not achievable, team morale may fall as the team continuously fails to meet targets. Stretch goals are acceptable, but people also want to see their hard work recognized.
- Misusing the metrics — focusing on less-important metrics rather than the ones that matter most; performing well for short-term measures at the expense of long-term metrics; working on out-of-sequence activities that are easy to accomplish in order to improve performance indicators.
- Confirmation bias — people tend to look for and see information that supports their preexisting points of view, which can lead to false interpretations of data.
- Correlation versus causation — confusing two variables moving together with one causing the other. Seeing projects that are behind schedule and over budget and inferring the schedule caused the overrun is this mistake; other correlating factors are likely at play, such as skill in estimating, the ability to manage change, and actively managing risks.
Communicating status: to whom, how often
One of the ECO's measurement enablers asks not for measuring but for communicating: communicate project status.
The book's tool list shows this is not a single report format: project dashboards, visual controls, and information radiators (PMBOK® 8, Guide p.27). The three work differently — a dashboard is pulled, a radiator is pushed.
Who receives what, in which form, belongs to another task; but the fact that metrics are defined at the start of the project (PMBOK® 8, Guide p.144) settles this task's share: what gets reported is determined by what was agreed in the plan, not by when someone asks for it.
Translated for the exam: when "the sponsor does not want to hear bad news," the right move is not to soften the report but to communicate the metric as the plan defined it.
Tailoring the artifacts
The ECO says "identify and tailor needed artifacts." That tailoring is this task's share of the book's general tailoring principle.
The Guide asks for "just enough" processes, methods, templates, and artifacts to achieve the desired outcomes; how much is enough is determined by the business environment, regulatory requirements, need for innovation, market conditions, team size, degree of uncertainty, and project complexity (PMBOK® 8, Guide p.34).
The ECO's "continually assess the effectiveness of artifact management" enabler continues that: which artifacts to keep is not decided once and left alone but revisited across the project.
The same page carries a caveat: in organizations with established process governance, tailoring should stay aligned with organizational expectations (PMBOK® 8, Guide p.34). For the governance side, see III.1 — Define and Establish Project Governance.
Accessibility is its own enabler
One of the ECO's four artifact enablers is devoted solely to accessibility. It was considered important enough to stand alone.
The logic comes from the knowledge side: capturing, sharing, and utilizing valuable insights enhances project outcomes and drives continuous improvement (PMBOK® 8, Guide p.26). An artifact that was written but cannot be reached may as well not have been written.
That link ties status evaluation to the task on the knowledge side — see III.6 — Continuous Improvement.
About the citations
All page numbers above refer to A Guide to the Project Management Body of Knowledge, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."
⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:
- The Standard for Project Management — cited as Standard p.X
- A Guide to the Project Management Body of Knowledge — cited as Guide p.X
Every citation on this page is from the second book, the Guide. The numbers are the book's printed page numbers.
This page explains the book; it does not replace it.
