Closing is the process group teams skip because they are already mentally on the next project. Work that 'just stops' leaves access open, invoices floating, and a customer who is not sure whether to clap. Formal close is a professional act, not a cake.
What closing actually includes
Close the project or phase: confirm that accepted deliverables are complete, complete contractual close-out, release resources, archive records, and update organisational process assets. If any of those are missing, you have paused, not closed.
Final acceptance is not a demo with applause. It is the documented handshake against the acceptance criteria you should have written in planning. 'They have been using it for weeks' is evidence of occupancy, not of close. Get the signature. Then stop spending.
Phase close is initiating's twin. You hand over what this phase produced, capture what you learned, and re-authorise the next phase if the work continues. Treating a multi-phase programme as one endless execute is how lessons arrive three years late, wearing a different project name.
Lessons learned that someone might read
Write lessons as cause, effect, and advice — not as 'communication could have been better,' which is the corporate equivalent of weather. 'The vendor environment slipped two weeks because the access request sat with Security; next time raise the request at charter and put Security on the stakeholder register' is a lesson.
Hold the session before the team evaporates. People are honest while the bruises are fresh and silent once they have a new Slack channel. Facilitation matters: silent write first, then cluster. The loudest person does not get to author the organisation's memory.
Store them where the next PM will look — the process-asset library, the PMO, the team wiki you actually search. A lessons file on a laptop that is about to be wiped is how organisations pay for the same surprise twice and call it culture.
Handover and the unglamorous admin
Operations need more than a binary. They need runbooks, known defects, support contacts, and a named owner for the first month of 'it is live and on fire.' A handover meeting without artefacts is a story. Stories do not page anyone at 2 a.m.
Admin close: accounts, licences, access, leftover budget, and the procurement trail. Leaving contractor access open is not generosity. It is a finding. Leaving money unreconciled is how finance invents a new stakeholder: you, next quarter.
Tell the organisation it is finished. Stakeholders who are not told will continue to send requests into a team that no longer exists. Closure is a communication, not only a checklist. Then resist the urge to keep a 'tiny bit of support' that becomes an unpaid second project.
Course complete — what's next
Closing accepts the work, hands it over, releases people and money, archives the record, and writes lessons someone can use. Process groups gave you a model for authorise–plan–do–check–close. The exam also uses domains and situations; this course did not promise a pass, and neither does a tidy close-out pack.
You now have a working map of the PMBOK process model. Use it to place the next decision on a live project: which group am I in, and what does 'done' look like here? That question beats memorising a poster.