Closing in PM²: Closing the Project Without Losing Value and Knowledge
Twelfth article in the “Learning PM² Through a Project” series
The RfC Gate authorises entry into Closing, but it does not automatically finish the project. The Closing Phase ensures that closure is formalised, residual responsibilities are clear and gained experience is not lost.
Closing answers: “Can we declare the project complete, transfer what remains to operations and learn from what happened?”
Closing Is More Than Delivering
A project may have released every deliverable and still have closure work to perform.
| Delivery completed | Closing completed |
|---|---|
| The solution has been produced and accepted | Performance and results are summarised |
| Release has occurred | Residual actions have an operational owner |
| Transition and initial support are active | Lessons and recommendations are captured |
| Artefacts, logs and decisions are archived | |
| Administrative and governance closure is formalised |
The difference matters because many projects finish with release while leaving support, benefits, open actions and knowledge without ownership.
Objectives of Closing
The phase serves to:
- confirm that the project has reached the state needed for closure;
- summarise performance against scope, time, cost and quality;
- verify transition and Business Implementation;
- assign residual and post-project actions;
- capture Lessons Learned and recommendations;
- archive artefacts, logs, evidence and decisions;
- formally communicate completion to stakeholders.
Project-End Report: The Final Project Summary
The Project-End Report is the phase’s main artefact. It should not be a bureaucratic document written at the last minute: it consolidates information produced and updated throughout the lifecycle.
It typically summarises:
- initial objectives and delivered outputs;
- performance against scope, schedule, cost and quality;
- major changes, risks, issues and decisions;
- acceptance and transition status;
- Business Implementation and early adoption results;
- Lessons Learned;
- recommendations and post-project actions;
- archive and administrative-closure confirmation.
For Smart Bookings, the report can show whether planned features were delivered, how much budget was used, which difficulties caused delays and whether pilot gyms use the system. It can also assign residual actions to the product team, such as improving notifications or measuring class occupancy during subsequent months.
Lessons Learned: Turning Events into Improvement
Lessons Learned are not merely notes about what went well or badly. A useful lesson has at least four parts:
- what happened;
- what effect it had;
- why it happened or which condition enabled it;
- what to do differently in future.
| Weak observation | Useful Lesson Learned |
|---|---|
| “Testing came late.” | “Because acceptance criteria were not defined during Planning, UAT started late. Future projects will approve criteria before Executing.” |
A lesson is useful only when it is shared, traceable and converted into a reusable behaviour or practice.
The Lessons Log Does Not Begin at Closing
Lessons should be collected throughout the project in the Lessons Log. Closing consolidates them, selects the most important ones and makes their recommendations visible.
Waiting until the end leads to incomplete memories and assessments distorted by the latest issue.
Recommendations and Post-Project Actions
A project may close even when some benefits will occur later. This requires residual actions not to remain in a void.
Every post-project action should have:
- a clear description;
- an owner;
- a verification date or condition;
- a link to a benefit, risk or recommendation;
- an operational monitoring approach.
For Smart Bookings, “measure the reduction in empty places for three months” is not a project activity if the project is closing. It must become an explicit responsibility of the product owner, business owner or designated operations function.
Administrative Closure and Archiving
Closure also includes less visible but essential work:
- archive final artefact and log versions;
- retain acceptance evidence and decisions;
- close contracts, orders, access or temporary resources where relevant;
- transfer documentation to operations and support;
- update repositories and organisational knowledge;
- communicate closure to interested parties.
Archiving does not mean hiding documents. It means retaining them so that they can be found for audit, support, maintenance and future projects.
Project Closure and Product Life
PM² asks an essential question: “Is there life after the project?”
The answer is almost always yes.
| Project | Product or service |
|---|---|
| Is temporary | Continues in operations |
| Produces outputs and enables change | Is used, maintained and evolved |
| Has formal closure | Has subsequent operating costs and benefits |
| Transfers responsibilities | Receives operational ownership |
For Annotatio, the project may end after Smart Bookings is introduced. The product continues to receive support, measure usage, correct defects, evolve features and generate benefits.
Governance of Closing
| Role | Typical contribution |
|---|---|
| Project Manager | Coordinates closure, report, archiving and residual actions |
| Business Manager | Verifies adoption, Business Implementation and benefit actions |
| Project Owner | Validates success against objectives and approves closure within authority |
| Solution Provider | Confirms handover, delivery quality and residual technical ownership |
| PSC | Reviews results, recommendations and closure decision |
| AGB | Receives or approves decisions beyond PSC authority where necessary |
Closing is not only the PM’s task. The PM coordinates it, but business and provider must confirm that the project leaves clear responsibilities behind.
Practical Case: Closing Smart Bookings Well
The first release is accepted and pilot gyms use it. Before closing, the team:
- compares results, budget and timing with baselines and objectives;
- confirms that support and operational ownership are assigned;
- transfers two out-of-scope improvements to the product team;
- records a lesson about involving pilot gyms earlier;
- prepares the Project-End Report;
- brings report, residual actions and recommendations to the PSC;
- archives artefacts and communicates completion.
The project can therefore close without pretending that the product is “finished”.
Do Not Confuse
| Pair | Difference |
|---|---|
| RfC and Project Ended | RfC authorises Closing; Project Ended follows completion of Closing. |
| Lessons Log and Project-End Report | The Log captures lessons during the project; the Report consolidates them and links them to recommendations. |
| Project closure and product end | The project ends; product, support and benefits continue. |
| Residual action and forgotten issue | A residual action is explicitly assigned; a forgotten issue has no governance. |
| Archiving and abandonment | Archiving preserves retrievable knowledge; abandonment makes it unusable. |
Test What You Remember
- What is the main Closing artefact?
- When should Lessons Learned be captured?
- What makes a Lesson Learned useful?
- Who should own a post-project action?
- Why does Project Ended not mean product end?
Answers
- The Project-End Report.
- Throughout the project, in the Lessons Log.
- It connects event, effect, cause and future action.
- An explicitly assigned operational owner.
- Because support, usage, evolution and benefits continue in operations.
Flashcards
Q: Which artefact summarises performance, lessons and recommendations?
A: Project-End Report.
Q: When are Lessons Learned recorded?
A: Continuously, in the Lessons Log.
Q: What does RfC authorise?
A: Entry into Closing.
Q: To whom should post-project actions be assigned?
A: To an operational owner.
Q: Does Closing end the product lifecycle?
A: No. It ends the project; the product continues in operations.
Exam-Style Question
Which activity most clearly belongs to Closing?
A. Defining the project’s initial budget.
B. Preparing a detailed work-package plan.
C. Consolidating Lessons Learned and assigning post-project actions.
D. Developing an undelivered output.
Correct answer: C. Budget and planning belong to Initiating/Planning; development belongs to Executing.
In the Next Article
In the next article, we will address the overarching Monitor & Control process, starting with reporting, deviations and corrective decisions.
Essential Sources
- European Commission, PM² Project Management Methodology Guide v3.1.
- European Commission, PM² Project Management Methodology – Highlights, 2025 Edition.