II.10 — Manage Project Closure

II.10 · Last updated: 24/08/2026

Where this task sits

II.10 — Manage Project Closure is the final task in the Process domain of the 2026 ECO. The domain carries 41% of the exam across ten tasks.

It has four enablers:

• Obtain project stakeholder approval of project completion
• Determine criteria to successfully close the project or phase
• Validate readiness for transition (e.g., to operations team or next phase)
• Conclude activities to close the project or phase (e.g., final lessons learned, retrospectives, procurement, financials, resources)

The parenthetical in the fourth is worth noting: closure is not one action but a sequence that collects the tails of several other tasks.

🔴 Do not trust the number

II.10 is one of the most misleading numbers in the ECO, because both the number and the domain changed:

• In 2021, II.10 was manage project changes. In 2026 that topic is III.3 — Manage and Control Changes, and it now lives in a different domain (Business Environment).
• In 2026, II.10 is project closure. This topic was II.17 in 2021.

So an older question tagged "II.10" is most likely about change management, not closure.

The confusion is not theoretical either: in off-the-shelf question banks the tag "II.10" turns up on both change and closure questions. Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

When does a project end

To understand the closure task correctly you first have to know how a project ends — and the answer is not "when the work is done."

The Standard says a project usually ends when one or more of the following conditions are met (PMBOK® 8, Standard p.7):

• The project's objectives have been achieved;
• A governing body, the project sponsor, or the project team has determined that the objectives will not or cannot be met;
• Resources (funding, human, or physical) are exhausted or no longer available;
• Due to changes in strategy, priorities, or the external environment, the need for the project no longer exists; or
• The project is terminated for other reasons such as legal, regulatory, or compliance issues.

Four of the five are something other than successful completion. Translated for the exam: the closure task is not only for successful projects. A cancelled project is closed too — and the same enablers apply.

The same page adds one more thing: although projects are temporary, their deliverables often persist beyond the project's conclusion (PMBOK® 8, Standard p.7). That is where the transition half of closure comes from.

The closure process and its three jobs

The corresponding PMBOK process sits in the Closing focus area of the Governance performance domain.

Close Project or Phase is the process of finalizing all activities related to the project or phase, including archiving knowledge, completing planned work, and releasing resources for new projects or operations (PMBOK® 8, Guide p.17).

Those three jobs map onto the parenthetical in the ECO's fourth enabler: lessons learned is archiving, procurement and financial closeout is completing planned work, and releasing resources is the third item.

The process inputs show why closure is a job of collection: all components of the project management plan, project documents (assumption log, basis of estimates, change log, issue log, lessons learned register, milestone list, project communications, quality control measurements, quality reports, requirements documentation, risk register, risk report), accepted deliverables, business documents (business case, benefits management plan), agreements, procurement documentation, and organizational process assets (PMBOK® 8, Guide p.31).

The accepted deliverables input is critical: closure comes after the deliverables are accepted. Acceptance itself is the work of the Validate Scope process on the scope side — see II.2 — Develop and Manage Project Scope.

Transition: who gets the product after the project

The ECO's third enabler says "validate readiness for transition," and the book has a named output for it.

Final product, service, or result transition: a product, service, or result, once delivered by the project, may be handed over to a different group or organization that will operate and maintain it (PMBOK® 8, Guide p.120).

Preparation for the handover, however, happens at the start of the project. Among requirement types the Guide lists transition and readiness requirements: temporary capabilities such as data conversion and training needed to move from the current, as-is state to the desired future state (PMBOK® 8, Guide p.130).

Translated for the exam: "are we ready for transition" is not answered at closure, it is verified at closure. If the readiness requirements were never planned, there is nothing left to do about it at the end. For the organizational side, see III.7 — Support Organizational Change.

Final lessons learned and retrospectives

The ECO names lessons learned and retrospectives first among closure activities.

The book's tool here is the after-action review (AAR): a simple, structured process used to analyze what happened, why it happened, and how it can be done better by the participants and those responsible for the project or activity (PMBOK® 8, Guide p.145).

The lessons learned register is a project document or repository used to record knowledge gained during a project, phase, or iteration so that it can be used to improve future performance for the team and the organization. Lessons learned from previous projects can be used in the current project and entered into the lessons learned repository (PMBOK® 8, Guide p.123).

The two-way flow there matters: closure does not only produce knowledge, it also consumes knowledge from earlier projects. For that full loop, see III.6 — Continuous Improvement.

Procurement and financial closeout

The parenthetical in the ECO's fourth enabler names two items separately: procurement and financials.

That procurement reaches closure is visible in the inputs of Close Project or Phase, which list agreements and procurement documentation (PMBOK® 8, Guide p.31). Verifying that the agreement's objectives were met is its own enabler over on the procurement task — see II.5 — Plan and Manage Procurement.

On the financial side, closure means closing out reserves and funding. The Monitor and Control Finances process watches that deliverables maintain their financial viability throughout the life cycle (PMBOK® 8, Guide p.62); closure is that cycle's end point. For detail, see II.6 — Plan and Manage Finance.

Translated for the exam: the project work may be finished, but with an open purchase order or an unreleased reserve the project is not closed.

The closure criteria are set in advance

The ECO's second enabler is easy to skim past: determine criteria to successfully close the project or phase.

This is not work done at closure. On the initiating side the Guide says: authorization — typically, but not always, via a charter — establishes a direct link between the project, the business case, and the organization's strategic goals (PMBOK® 8, Guide p.17). Defining success metrics is likewise one of the three core components of governance (PMBOK® 8, Guide p.13).

So "when is this project considered finished" is answered at the beginning, not the end. That is why most closure questions on the exam send you back to initiation: with no acceptance criteria there can be no acceptance.

Finally, stakeholder approval — the ECO's first enabler. Involving sponsors, customers, and other stakeholders during project initiation creates a shared understanding of success criteria (PMBOK® 8, Standard p.70). The approval at closure is the payoff of that shared understanding established at the start.

About the citations

The page numbers above refer to the PMBOK® 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

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

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