Closure is the last task in the outline and it tends to be the last thing anyone studies, when there is little time left and less appetite. Bad split, because that task decides whether months of work end up as something the organisation uses, or as something the team drags along for years.
Let me start with an uncomfortable question. When did your last project really end? Not the day you turned the milestone green, but the day someone other than you took charge of what you had delivered. If those two dates are not the same, you already know what this is about.
Let’s start with where this task lives
In the July 2026 outline, the Process domain weighs 41 per cent, the largest of the three blocks, as we covered in the exam walkthrough. That domain has ten tasks and the tenth is called manage project closure, with four enablers.
The first asks you to obtain project stakeholder approval of project completion. The second asks you to determine the criteria to successfully close the project or phase. The third asks you to validate readiness for transition, and in brackets the outline names the handover to the operations team or the move to the next phase. The fourth asks you to conclude the activities to close the project or phase, and in brackets it names final lessons learned, retrospectives, procurement, financials and resources.
The outline clarifies it in its introduction. Enablers are illustrative examples of the work associated with the task and are not meant to be an exhaustive list, so reading them as a sequence is a study device and not a rule.
The four enablers are those of the official PMP examination content outline, July 2026 edition.
The order in the outline is jarring, and that is the clue
And now the part that costs. The outline puts approval before criteria, and that is backwards from how closing actually works, because criteria are agreed at the start and approval arrives at the end.
Still, it is not an oversight, it follows from the list enumerating work rather than steps. What the exam wants to know is whether you understand that one without the other is useless, since an approval with no criteria is a conversation with no referee, and criteria with no formal approval are a document nobody signed.
Emad E. Aziz puts it in a paper published by PMI in 2015, within the proceedings of its global congress. Obtaining approval from the sponsor and the customer eliminates later debate and scepticism, and he singles it out as a piece of great importance in avoiding scope creep. It is worth noting what that implies, because the first enabler is not an exit formality, it is the defence against a scope that stretches once nobody is watching.
Every phase is a port of call
Closure does not happen once at the end, it happens every time something finishes, and that is why three of the four enablers name the project or the phase.
Aziz holds that closure must happen at the end of the project and at every phase as well, in phase-gate reviews, which also show up as stage gates, kill points and transition points. Think of it as a port of call. The ship ties up, someone looks at the chart again and only then does it sail, because you do not correct course in the middle of the ocean. At the phase gate the business case gets looked at again, and the outcome can only be one of three, terminating the project because it no longer holds, proceeding exactly as planned, or modifying it to fit conditions that changed.
That third way out is the one almost nobody considers, and it is the mirror of what the project charter signs off, which opens what the phase gate reviews.
Validating the transition is not handing over and walking away
The third enabler generates plenty of questions, because the word transition reads quickly. Validating that it is ready means checking that whoever will operate the product has the training, the tools and the documentation, and that they have taken on that responsibility.
Think of the last thing your team put into production. Who answers the phone if it breaks on a Saturday at eleven at night? If that is still someone from your project, the transition was never validated, whatever the record says.
Aziz describes two typical ways of failing here. One is the project that never ends, where the organisation keeps asking the project team to operate and maintain the deliverable. The other is the orphan product, handed over with no training and no commitment from the other side, ending up with nobody answering for it.
Concluding the activities, where the work hides
The fourth enabler is the catch-all. Among its examples is procurement, with its administrative closure and its exam traps, which we develop in the post on procurement and contract types.
There are also lessons learned, which Aziz reduces to two questions, what was done well and should be documented so it can be repeated, and what could have been done better and in what way. They fit in half an hour and they are the first thing to fall off the calendar, perhaps because they do not benefit the project that is ending but the one coming behind it.
Back to the exam
The stem tells you the team finished the deliverables, the client accepted them in writing and the sponsor wants to close this week, while operations reports it has not received the documentation or the training. The options offer you closing anyway because the scope was met, escalating to the sponsor, documenting the gap in lessons learned, or validating that the transition is ready before concluding the closure.
The last one is the outline’s and it is the uncomfortable one, because it forces you to delay a closure already won politically. A met scope and a signed acceptance are not enough, and without a validated transition you have a product about to be orphaned with a closure record on top.
Back to the question I opened with. A project does not end the day you deliver, it ends the day someone else can carry on without you. The rest is signing the paper and turning out the light on your way out.
Join the waitlist
At The PM Architect we write the PMBOK study guides in five languages, with real classroom cases and exercises that come with an explanation. They will be free. Leave your email on the home page and we’ll let you know the moment they’re ready.
