Closure is the part of the project most candidates study last and the part most study plans skip. That is a mistake on the current exam, because closure is not an afterthought buried inside a process group. It is one of the named tasks in the Process domain, which carries 41% of the exam, and the activities it describes show up again in the Business Environment domain.
This guide covers what the exam outline actually asks for, the four things the task expects you to be able to do, and the answer patterns that separate a correct closure response from a plausible-sounding wrong one.
What the exam outline says
PMI's Examination Content Outline for the exam that launched in July 2026 lists "Manage project closure" as a Process domain task. Its enablers are specific:
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).
Four verbs, four distinct obligations: approve, define criteria, validate transition, conclude activities. Most closure questions test exactly one of them, and knowing which one is being tested is usually enough to eliminate two options.
The outline also places closure-adjacent work in the Business Environment domain, under "Continuous improvement": "Utilize lessons learned. Help ensure continuous improvement processes are updated. Update organizational process assets (OPAs)." That pairing matters. The exam does not treat lessons learned as paperwork you file at the end. It treats them as an input to the next project, which is why the Business Environment domain owns them.
The four obligations, and what each one tests
Obtain stakeholder approval of completion
The project manager does not declare a project finished. The people who accepted the deliverables do. Questions in this area usually present a project manager who believes the work is complete and a stakeholder who has not said so.
The correct response almost always involves confirming acceptance against agreed criteria rather than asserting completion. Watch for distractor answers where the project manager notifies stakeholders that the project is closed, releases the team, or moves on to the next assignment. Notification is not approval.
Determine closure criteria
Closure criteria are defined early, not improvised at the end. If a scenario shows a team arguing about whether the project is done, the useful question is: what did we agree "done" would look like?
This is where predictive and adaptive projects diverge in wording but not in logic. A predictive project points to acceptance criteria, the scope baseline, and validated deliverables. An adaptive project points to the definition of done and accepted increments. Either way, the answer that reaches for a prior agreement beats the answer that negotiates a new one under deadline pressure.
Validate readiness for transition
The outline calls out transition explicitly, "to operations team or next phase," and this is the obligation candidates most often miss. A deliverable that works is not the same as a deliverable someone else can run.
Transition readiness questions tend to hinge on whether the receiving group has what it needs: documentation, training, support arrangements, access, and a named owner. When a scenario describes a product being handed to an operations or support group, check whether the proposed answer actually equips that group or merely informs it.
| Scenario signal | Weak answer | Stronger answer |
|---|---|---|
| Deliverable accepted, operations not trained | Close the project and report success | Complete knowledge transfer before closing |
| Phase gate approaching, no criteria agreed | Extend the phase | Confirm phase exit criteria with the sponsor |
| Vendor work finished, contract open | Release the vendor team | Close the procurement formally first |
| Benefits not yet measurable | Declare benefits achieved | Confirm the measurement system and owner |
Conclude closure activities
The outline names four categories: lessons learned and retrospectives, procurement, financials, and resources. These are easy to overlook because none of them is about the product.
- Procurement. Contracts close formally. Open claims, final payments, and vendor performance records are part of closure, not loose ends you leave for someone else.
- Financials. Remaining budget is reconciled and released. A project that stops spending is not a project that has closed its accounts.
- Resources. People and equipment are released in an orderly way, which includes performance feedback and returning team members to their functional managers or next assignment.
- Lessons learned and retrospectives. Captured, and then actually put somewhere the organization will read them.
Lessons learned versus retrospectives
The outline lists both, in the same enabler, which tells you something: the exam expects you to know they are related but not identical.
A retrospective is a recurring team practice inside an iterative cadence. Its purpose is to improve the next iteration, and its audience is the team itself. Final lessons learned at closure look wider: what the organization should carry into other projects, recorded in organizational process assets so a future team benefits.
With adaptive and hybrid approaches now making up the larger share of exam content, expect scenarios where a team has been running retrospectives throughout and a question asks what still needs to happen at closure. The answer is usually consolidation: the per-iteration improvements were for the team, and the organization still needs the durable record.
A useful distinction to hold:
| Retrospective | Final lessons learned | |
|---|---|---|
| Timing | Every iteration or phase | At project or phase closure |
| Purpose | Improve the next iteration | Improve future projects |
| Audience | The delivery team | The organization |
| Output | Team action items | Updated organizational process assets |
Closure and value
Closure questions increasingly connect to value rather than to completion. The Process domain also includes "Help ensure value-based delivery," whose enablers include "examine the business value throughout the project" and "verify a measurement system is in place to track benefits."
Read those together with closure and a pattern emerges. Projects often close before their benefits appear. Revenue, adoption, and cost savings land months later. The project manager's obligation at closure is not to claim those benefits but to make sure someone can measure them: a defined metric, a baseline, an owner, and a reporting point after the project ends.
So when a scenario asks what the project manager should do about benefits that cannot yet be observed, the strong answer hands off the measurement, not a conclusion.
Common traps
- Closing without acceptance. Any answer where the project manager unilaterally declares completion is suspect.
- Treating lessons learned as a document. Capturing them is half the task. Updating organizational process assets is the other half.
- Skipping administrative closure. Procurement, finance, and resource release are named in the outline. They are testable.
- Confusing phase closure with project closure. The outline says "project or phase." A phase gate needs its own exit criteria and its own approval.
- Assuming adaptive projects have no closure. Iterative delivery does not remove the obligation to transition the product, close contracts, and record what the organization learned.
How to study this
Spend one session on the four enablers and write, in your own words, the single question each one answers. Then take a handful of closure practice questions and, before looking at the options, decide which obligation the scenario is testing. If you can name it, the right answer usually becomes obvious. If you cannot, that is the gap to study, not the question to memorize.
The exam structure gives you room to do this carefully: 180 questions in 240 minutes, with a case-study section and two 10-minute breaks. Closure items are a small share of that, but they are among the most pattern-driven questions on the test, which makes them some of the cheapest points available.