II.9 — Evaluate Project Status

II.9 · Last updated: 11/10/2026

Measuring the project and keeping its records, in one task

II.9 — Evaluate Project Status is the ninth task in the Process domain of the 2026 ECO, which carries 41% of the exam. The task has eight enablers, and they fall into two groups of four. The first group is about measurement:

• Develop project metrics, analysis, and reconciliation
• Assess current progress
• Measure, analyze, and update project metrics
• Communicate project status

The second group is about artifacts:

• 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

Half of the enablers going to artifact management is no accident. The reason lies in how the task came about.

Two older tasks merged

What sets II.9 apart is less a change of number than the fact that two separate jobs were brought together in one task. In the 2021 ECO, II.12, manage project artifacts, was a task in its own right. In 2026 that work stopped standing alone and was placed inside status evaluation, and the four artifact enablers come from there.

The reasoning behind the merger is easy to follow. You can know a project's status only to the extent that you measure it and keep a record of it, so artifact management works as the infrastructure of status evaluation. Keep in mind as well that II.5, II.6, II.8, and II.10 in the Process domain now point to different topics. When mapping older material, go by the title; the broader picture is in what changed in the 2026 PMP exam.

Data, information, and reports

The most useful distinction on this task rests on these three terms, and the book defines each one separately.

Work performance data covers the raw observations and measurements identified during the activities carried out to perform the project work. The book treats this data as the lowest level of detail from which other processes derive information. Its examples include work completed, key performance indicators, technical performance measures, actual start and finish dates of schedule activities, story points completed, the number of change requests and defects, and actual costs (PMBOK® 8, Guide p.143).

Work performance information is that same data, collected from the controlling processes and analyzed by comparison with project management plan components, project documents, and other work performance details. The book sets an important condition in the same place, which is that the 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). The book defines them as the physical or electronic representation of work performance information, compiled to generate decisions, actions, or awareness (PMBOK® 8, Guide p.144).

A quick way to separate the three on the exam is to think of the raw number as data, the number read against the plan as information, and the form that reaches a stakeholder as a report. "The team worked 120 hours this week" is data, while "we are 12 percent behind plan" is information. The condition in the second definition matters too. Since metrics are defined at the start of the project, a metric picked later on, while the project is running and to suit the situation, cannot be the basis of a sound status evaluation.

The process that tracks status

The ECO's measurement enablers correspond to a single PMBOK process. Monitor and Control Project Performance is the process of tracking, reviewing, and reporting the overall progress of the project to meet the performance objectives defined in the project management plan (PMBOK® 8, Guide p.26). The Guide ties it to measurement explicitly, saying it relies on the continuous tracking, review, and reporting of project metrics to keep the project aligned with its performance objectives (PMBOK® 8, Guide p.27).

The tools of the process include project dashboards, visual controls, and information radiators (PMBOK® 8, Guide p.27). Visual charts can carry more than progress. An impediment list, for example, can show the obstacle in the way of the work, how severe it is, and what is being done to remove it (PMBOK® 8, Guide p.214).

Six ways a metric can mislead

The Guide names six pitfalls to watch for in measurement (PMBOK® 8, Guide p.28), and each one has a counterpart on the exam.

The Hawthorne effect is the observation that the very act of measuring something influences behavior. Measuring only the number of deliverables a team produces can push the team toward producing many deliverables, at the expense of those that would satisfy the customer more.

A vanity metric shows data without giving any information that helps with a decision. Counting a website's page views is less useful than counting its new visitors.

Demoralization sets in when targets cannot be reached and the team keeps failing them until morale drops. The book accepts stretch goals, but it adds that people want to see their hard work recognized and that unrealistic goals backfire.

Misusing the metrics takes several forms, such as focusing on less important metrics instead of the ones that matter most, trying to look good on short-term measures at the expense of long-term ones, or doing easy work out of sequence to improve the indicators.

Confirmation bias is the human tendency to look for and see information that supports views already held, which leads to false interpretations of data.

Correlation versus causation is the mistake of reading two variables that move together as one causing the other. In the book's example, someone looks at projects that are behind schedule and over budget and concludes that the budget was overrun because of the delay. Other factors that were not considered are probably involved, such as skill in estimating, the ability to manage change, or whether risks were actively managed.

Communicating status

One of the measurement enablers asks you to communicate status, which is a separate job from measuring it. The book's tool list shows that this does not come down to one report format, since dashboards, visual controls, and information radiators reach different audiences in different ways (PMBOK® 8, Guide p.27). Who receives which information through which channel belongs to another task, I.8 — Plan and Manage Communication.

What this task contributes follows from the metrics being defined at the start of the project (PMBOK® 8, Guide p.144). What gets reported does not change according to who wants to hear it or when; it is reported as the plan agreed. In a scenario where the sponsor does not want to hear bad news, softening the report is therefore the wrong move, and the expected answer is to communicate the agreed metric as it stands.

Tailoring the artifacts

The ECO asks you to identify and tailor the artifacts a project needs, and that tailoring is this task's share of the book's general approach to tailoring. The Guide recommends using "just enough" process, methods, templates, and artifacts to achieve the desired outcomes, with the right amount set by the business environment, regulatory requirements, the need for innovation, market conditions, team size, the degree of uncertainty, and project complexity (PMBOK® 8, Guide p.34). The same page also sets a limit. In organizations with established process governance, tailoring has to stay aligned with the organization's policy and strategy. The governance side is covered in III.1 — Define and Establish Project Governance.

The enabler about continually assessing the effectiveness of artifact management carries the same idea further. Which artifacts the project keeps is not settled once and then left alone, and the choice is revisited as the project goes on.

Accessibility as an enabler of its own

One of the four artifact enablers is devoted entirely to accessibility, which shows how much weight the ECO gives the subject. The reasoning comes from knowledge management. Project outcomes improve and continuous improvement is fed when valuable insights are captured, shared, and used (PMBOK® 8, Guide p.26). An artifact that has been written but cannot be reached by the person who needs it has, in practice, the same effect as one that was never written.

That link connects status evaluation to continuous improvement, the subject of III.6 — Continuous Improvement.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ 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

All citations on this page come from the second book, the Guide. The numbers are the book's printed page numbers.

This page describes the book; it does not replace it.