II.10 — Manage Project Closure

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

Closure gathers the loose ends of the other tasks

II.10 — Manage Project Closure is the last task in the Process domain of the 2026 ECO. The domain carries 41% of the exam and consists of ten tasks, and the ECO attaches four enablers to this final one:

• 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 parenthesis in the fourth item sums up what the task is like. Closure is a series of jobs that pull together the open ends of other tasks, from procurement and finance to resources and knowledge management, and no single act completes it.

The old "II.10" was about change management

II.10 is one of the most misleading numbers in the ECO, because both the number and the domain changed. In 2021, II.10 meant managing project changes, and that topic now sits in III.3 — Manage and Control Changes, which belongs to a different domain, Business Environment. In 2026, II.10 is project closure, a topic whose old number was II.17.

An older question tagged "II.10" is therefore far more likely to be about change management than about closure. Map by the title. The general shape of the numbering trap is laid out in what changed in the 2026 PMP exam.

How a project comes to an end

Closure makes sense only once you know the ways a project can end, and the book's answer goes well beyond "when the work is done". According to The Standard, a project usually ends when one or more of the following conditions are met (PMBOK® 8, Standard p.7):

• its objectives have been achieved
• a governing body, the sponsor, or the project team decides that the objectives will not or cannot be met
• funding, human, or physical resources are exhausted or no longer available
• changes in strategy, priorities, or the external environment mean the need for the project no longer exists
• the project is terminated for other reasons, such as legal, regulatory, or compliance issues

Four of the five conditions describe something other than a successful finish. The closure task therefore applies to more than successful projects. A cancelled project gets closed as well, and the same enablers apply to it.

The same page contains a sentence that prepares the ground for the handover side of closure. Although projects are temporary, their deliverables often persist after the project has ended (PMBOK® 8, Standard p.7).

The closing process and its three jobs

In PMBOK the counterpart of this task 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, and its definition names three jobs, archiving knowledge, completing planned work, and releasing resources for new projects or operations (PMBOK® 8, Guide p.17). Those three line up with the parenthesis in the ECO's fourth enabler. Lessons learned fall under archiving, procurement and financial closeout fall under completing planned work, and resources fall under releasing.

The process inputs show why closure is a job of collection (PMBOK® 8, Guide p.31). They include the project charter, all components of the project management plan, project documents (the 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, and risk report), accepted deliverables, the business case and benefits management plan, agreements, procurement documentation, and organizational process assets. The outputs include updates to the lessons learned register, the final product, service, or result transition, the final report, and updates to organizational process assets.

Accepted deliverables appearing among the inputs also reveals a sequence, since closure comes after the deliverables have been accepted. Acceptance itself is the job of the Validate Scope process on the scope side, covered in II.2 — Develop and Manage Project Scope.

Transition, or who takes the product after the project

The ECO's third enabler asks you to validate readiness for transition, and the book has a named output for it. Final product, service, or result transition is the handover of a product, service, or result delivered by the project to another group or organization that will operate and maintain it (PMBOK® 8, Guide p.120). The Standard also says this is typically the point at which the project is handed over to operations, which sustain and use its results (PMBOK® 8, Standard p.10).

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

For that reason the question "are we ready for transition?" is verified at closure, and its answer has to be built long before. If readiness requirements were never planned at the outset, there is little left to make up for at the end. The organizational side is covered in III.7 — Support Organizational Change.

Final lessons learned and retrospectives

Lessons learned and retrospectives come first in the ECO's list of closing activities. The book's tool for this is the after-action review, a simple, structured process for analyzing what happened, why it happened, and how the participants and those responsible for the project could do it better (PMBOK® 8, Guide p.145).

The record of that work is the lessons learned register, a document or repository in which knowledge gained during a project, phase, or iteration is recorded so that it can improve the future performance of the team and the organization. Lessons from earlier projects can be used in the current one, and in the end they are added to the organization's lessons learned repository (PMBOK® 8, Guide p.123).

The flow runs both ways, and that matters. Closure produces new knowledge and also draws on what earlier projects learned. The full loop is covered in III.6 — Continuous Improvement.

Closing out procurement and finance

The parenthesis in the fourth enabler names two items separately, procurement and financials. Procurement reaching into closure is visible from the inputs of Close Project or Phase, which include agreements and procurement documentation (PMBOK® 8, Guide p.31). Confirming that the agreement's objectives were met is an enabler of the procurement task in the ECO, covered in II.5 — Plan and Manage Procurement.

On the financial side, closure means closing the accounts of funding and reserves. The Monitor and Control Finances process makes sure the deliverables stay financially viable throughout the life cycle (PMBOK® 8, Guide p.62), and closure is the final point of that cycle. The details are in II.6 — Plan and Manage Finance.

These two items set a frequent trap on the exam. The project work may be finished, yet as long as a purchase order is still open or a financial obligation has not been closed, the project does not count as closed.

The closing criteria are set at the start

The ECO's second enabler, determining the criteria for a successful close, is easy to overlook because it is not really work done at closure. On the initiating side the Guide says that project authorization, typically (though not always) through a project charter, creates a direct link between the project, the business case, and the organization's strategic goals (PMBOK® 8, Guide p.17). One of the core components of effective governance is setting target metrics that are aligned with the organization's strategic goals (PMBOK® 8, Guide p.13).

The question "when does this project count as finished?" is therefore answered at the beginning. Most closure questions on the exam have their roots there too, because without defined acceptance criteria the acceptance itself stays uncertain.

The ECO's first enabler, stakeholder approval, goes back to the same starting point. Involving sponsors, customers, and other stakeholders during initiation creates a shared understanding of success criteria (PMBOK® 8, Standard p.70). The approval obtained at closure is the return on that shared understanding, and it closes the Process domain by tying it back to where it began, with the plan.

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

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 describes the book; it does not replace it.