Change management closure: what the ACMP Standard lets you sign off

What does the ACMP Standard mean by closing a change management effort?

It means a documented, approved handover: the change team shows what the change achieved, records what it learned, and passes ownership of the results to the people who will run them every day.

This site follows Leanova Academy, an official ACMP® QEP™, and the course material it teaches is built on the Standard. In the ACMP Standard for Change Management, second edition (2025), the fifth process group is called “Close the Change Management Effort” (section 5.5). Its stated purpose is to record what it takes to close the change and to mark a clear move into maintenance or sustaining activities. The group description adds that these processes measure results against expected benefits and capture the continuous improvement that comes out of post-project analysis.

The group is short: three processes (5.5.1, 5.5.2 and 5.5.3), the last two split into three sub-processes each. If you have not yet seen the whole structure, our overview of the Standard places it among the five groups, and the Standard itself is available from the ACMP’s Standard page.

5.5.1: how do you evaluate the outcome against the objectives?

You compare what happened with what you said you would achieve at the start, then record the verdict and review it with the leaders involved.

Process 5.5.1, “Evaluate the Change Outcome Against the Objectives”, asks for the extent to which the intended benefits and improvements were realised. The Standard lists the actions as needed: compare the results so far with the change objectives set at the beginning, compare them with the project or program objectives when project management is in use, document whether objectives were met, missed or exceeded, and review the findings with the appropriate leaders and stakeholders.

Its inputs are the Change Goals and Objectives, the Measurement and Benefit Realization Plan and the Sustainability Plan. Its output is a single document, the Change Outcome Evaluation Report. The plans in that input list come from earlier groups, which is why a weak goal statement in 5.1.5 or a vague measurement plan in 5.3.1.7 (see our article on the plan group) shows up here as an evaluation nobody can defend.

A fictional example makes the point. A regional council moves its permit requests onto a new online portal. The objective written in the case for change was that 80 percent of requests would be filed online within six months. At closure, 71 percent are. The report records the objective as missed, notes that the shortfall sits almost entirely in one district without reliable broadband, and says so plainly. A report that rounded 71 up to “on target” would be easier to write, and useless for the next district.

5.5.2: what makes a lessons learned evaluation worth running?

It is worth running when the right people are in the room, when it examines the approach and not only the result, and when its recommendations end up somewhere the next team will look.

The Standard gives this process more space than any other in the group, and it breaks it into three steps. In 5.5.2.1 the change management lead identifies who should take part: team members, key stakeholders, the project sponsor, leaders and affected staff or customers. The Standard says the lead normally runs the evaluation together with the project manager when that is possible. In 5.5.2.2 the group reviews the objectives, each phase, each workstream against its own outcomes, and the ways of working. It also decides which designs and strategies should become internal good practice. In 5.5.2.3 the lead writes it up so that future initiatives can use it.

The Standard suggests guiding questions for that document: which activities are repeatable and successful, how future initiatives could go as well or better, what advice would help future teams, and which individual successes deserve recognition. It also expects a Remediation Plan for key issues, and a place in a knowledge management database or shared storage where other practitioners can find the lessons.

The inputs are the Case for Change and the updated Change Management Plan with its criteria and measures for success. The outputs are the Lessons Learned Evaluation Document and the Remediation Plan.

The Standard also says the exercise has a second effect. It reinforces the team’s commitment to sustaining the change and gives people a two-way channel on how well the change has been embedded. In practice that means the session works best before the team disperses and while the sponsor is still attending. Waiting three months is the usual way to lose both.

5.5.3: what must happen before the effort can formally end?

Three things: approval from the right authority, a signed transfer of ownership, and the release of the remaining resources.

Process 5.5.3 is “Gain Approval for Closure, Transfer of Ownership, and Release of Resources”. Its purpose, as the Standard puts it, includes sustainability accountability and recognising success, so it covers more than paperwork.

• 5.5.3.1, approval for closure. The steering committee, senior sponsor or client confirms that the closure conditions are met. Those conditions are an evaluation of outcomes against objectives within the agreed scope, a report of lessons learned, a document showing the outcomes passed to the operational owners, and a plan to release what is left of the change resources.
• 5.5.3.2, transfer of ownership. Ownership and sustainability accountability for every outcome (processes, technology, organisation) moves from the change resources to the stakeholders’ operational resources. The Standard asks for written agreement from both parties, and for future strategy plans to be handed over too when they are part of the outcomes.
• 5.5.3.3, release of resources. Change resources are freed for other change efforts.

The inputs include the Change Goals and Objectives, the Lessons Learned Evaluation Document, the Measurement and Benefit Realization Plan and the Resource Release Approval. The outputs are a Final Summary Report, the Change Initiative Closure and the Agreement on Transfer of Ownership.

Here is the whole group on one page.

Process	Question it answers	Inputs named in the Standard	Outputs named in the Standard
5.5.1 Evaluate the Change Outcome Against the Objectives	Did we reach what we set out to reach?	Change Goals and Objectives; Measurement and Benefit Realization Plan; Sustainability Plan	Change Outcome Evaluation Report
5.5.2 Design and Conduct Lessons Learned Evaluation	What should the next team know?	Case for Change; criteria and measures for success; Change Management Plan (updated)	Lessons Learned Evaluation Document; Remediation Plan
5.5.3 Gain Approval for Closure, Transfer of Ownership, and Release of Resources	Who owns the result now, and who has agreed?	Change Goals and Objectives; Lessons Learned Evaluation Document; Measurement and Benefit Realization Plan; Resource Release Approval	Final Summary Report; Change Initiative Closure; Agreement on Transfer of Ownership

The Standard states that these input and output lists are commonly accepted examples, not exhaustive ones, and that inputs and outputs do not map one to one. Treat the table as a starting checklist and adapt it to the size of the change.

Does closing the change management effort mean the support stops?

No: closing marks a handover to sustaining activities, and the Standard deliberately places responsibility for those activities with the operational owners rather than with the change team.

The group’s purpose speaks of a transition to maintenance or sustaining activities, and 5.5.3.2 requires that sustainability accountability be transferred. Closure therefore asks a harder question than “is the project finished?”. It asks whether someone with the authority and the budget has accepted responsibility for keeping the new behaviour in place. The Sustainability Plan, built in 5.3.1.8 and carried out in 5.4.1.8, is one of the inputs to the evaluation in 5.5.1, so the evidence of staying power is meant to be examined at this point, not assumed.

For a practitioner’s view of what happens in the weeks after go-live, Leanova Academy’s blog has a useful piece on sustaining change after go-live, with hypercare and reinforcement. It sits comfortably on the other side of the closure line described here.

One more point from the Standard’s introduction to section 5: the processes are not forced into a strict sequence, and any of them can be repeated. A programme delivered in waves can therefore close wave one while wave two is still in execution. Group 5.4 on executing the plans and its process 5.4.2 for modifying them explain the cycle you leave when you close.

What goes wrong at closure, and how do you avoid it?

The usual failures are closing on a date rather than on conditions, writing lessons nobody reads, and handing over without a named owner.

A second fictional case shows all three. A retailer rolls out a new stock system to 40 stores. The project closes on the planned date, the change team is reassigned the same week, and the lessons session is dropped because everyone is busy. Two months later, store managers have gone back to their spreadsheets in 11 stores. Nobody owns adoption, and nobody can say why the other 29 stores did well.

The Standard’s structure guards against each failure. Closure conditions in 5.5.3.1 turn the date into a checklist. The Lessons Learned Evaluation Document and the Remediation Plan turn opinion into something filed and findable. The written agreement in 5.5.3.2 puts a name against each outcome. Some practical habits help:

• Fix the closure conditions at the planning stage, when the Measurement and Benefit Realization Plan is written, not in the final week.
• Book the lessons session before the team is reassigned, and invite affected staff, not only the project core.
• Write the transfer agreement in plain language and have the operational owner read it before the meeting where it is signed.
• Hold back a small, named part of the resources until the Resource Release Approval is in hand.

How does the closing group relate to the CCMP exam?

It is part of the Standard on which the CCMP exam is based, and since 1 April 2026 the exam follows the second edition.

The ACMP does not publish a weighting of topics in the Standard, so we cannot say how many questions touch group 5.5, and we would distrust anyone who claims a figure. What the text does show is that closure shows up in more places than the group itself: in Annex B, 5.5.1 sits under measurement and benefit realization, 5.5.3 under leadership and sponsorship engagement, and 5.5.2 under change initiative scope. Our article on the annex and the subject groups shows how to use that mapping when you revise. For the format of the exam itself, see the CCMP exam format and pass mark.

The ACMP requires 21 hours of training aligned with the Standard before you can apply. Leanova Academy’s self-paced CCMP exam prep course is a QEP course of that length, and its price was US$595 when we last checked, on 7 October 2026. Check the current price on the course page before you buy.

Frequently asked questions

Is “Close” the same as “Complete” in the Standard?

In the second edition (2025) the fifth group is called “Close the Change Management Effort”. If you meet the word “Complete” in older material, treat it as a different wording from an earlier source and check which edition it describes.

Who runs the lessons learned evaluation?

According to the Standard, the change management lead conducts it, working with the project manager when possible. The group should include team members, key stakeholders, the sponsor, leaders and affected staff or customers.

Can a change be closed if it missed its objectives?

Yes. The Standard asks you to document whether objectives were met, missed or exceeded, and the remediation plan records what should be done about the gaps. Closure requires approval and a transfer of ownership, not a perfect score.

Is the Standard a mandatory checklist?

No. The ACMP presents it as voluntary guidance, it does not certify organisations against it, and practitioners choose the processes their change needs. The three closure processes are most useful as prompts for a conversation with your sponsor.

Next step: take a change you are running now, write down its closure conditions in three lines, and share them with your sponsor this week.

Was this article helpful?

 

Be the first to rate this article.