Change management
Change management plan: what goes in it, how to write one and how it applies to an AI rollout
A plain guide for owners and project leads who need a written plan for a change in how people work. It ends with how the same plan applies when the change is a new AI tool.
A change management plan is a written document that says what is changing, who it affects, how people will be told and helped, who approves it, how it is tested, and how it is undone if it goes wrong. A short plan answers eight core questions: what changes, why, who is affected, who decides, how people are prepared, how it is tested, how it is rolled back, and how you will know it worked. The plan is only useful if named people own each part. For an AI tool, add one more question: what a person still checks before anything the tool produces is used.
plain answer
What is a change management plan?
It is the written answer to a simple worry: when we change how work is done, how do we stop it from going badly? The change might be a new system, a new process, a new policy or a new tool. The plan names the change, the people it touches, the steps to move them across, and the person who can say yes or no at each step.
People use the term in two ways. In IT it often means controlling changes to systems, with approvals and rollback. In the wider business it means helping people adopt a change, with communication and training. A good plan covers both, because a technically sound change that nobody adopts has still failed.
how to
What are the parts of a change management plan?
Most plans work with these parts, each one short enough to fit on a page.
1. The change and the reason
One paragraph on what is changing and the problem it solves, in words an affected person would use.
2. Scope
What is in, what is out, and which teams or sites are touched.
3. People affected
For each group, what changes in their day and what they might worry about.
4. Roles
An owner for the plan, a sponsor who can settle disputes, an approver for each step, and a named contact people can ask.
5. Communication
What people hear, from whom, and when, before, during and after the change.
6. Training and support
What people need to learn, where they get help in the first weeks, and who answers questions.
7. Testing and timing
A small first group, then a wider group, with a date to review before each step.
8. Rollback
The exact conditions that stop the change and the steps that put things back.
9. Measures
How you will know it worked, chosen before the change starts, and who looks at them.
how to
How do you write a change management plan, step by step?
We recommend writing it in this order, because each step feeds the next.
1. Describe the change in two sentences
Ask someone outside the project whether they understand it.
2. List who is affected and talk to a few of them
Do this before you write anything else. Their objections are better found now than after launch.
3. Name the owner, the sponsor and the approvers
In our view, a plan with no names is a wish.
4. Decide the smallest safe first step
For example, one team for two weeks.
5. Write what people will be told and when
Include the support they get in the first weeks.
6. Write the rollback in plain steps
Check that someone could follow it under pressure.
7. Choose the measures and the review dates
Set them before the change starts.
8. Get the approvers to read the plan and say yes in writing
Keep a copy with the plan.
9. Keep the plan open after launch
Record what actually happened, because the next plan starts from it.
ai rollout
How does a change management plan apply to an AI rollout?
The same parts apply, with a few additions that matter for AI tools. Scope should say which tasks the tool may be used for and which it may not. The people section should include those who will review the tool's output, because they carry new work. Training should cover how to check a result, not just how to use the tool. Rollback should say what happens to work already produced if the tool is switched off.
A team also needs a rule for what a person checks before an AI output is used, and an owner for that rule. Our governed approach to AI agents is set out on our agentic AI governance page, and our articles on change management for Copilot rollouts show how phases, ownership and training fit together for one specific tool.
kriv fit
Where does Kriv AI fit?
Kriv AI works with teams that are bringing AI tools into everyday work. We can help you write the plan, run the first small rollout and train the people who will use and review the tool. Scope and price are set after a short discovery call.
Straight answers
Frequently asked questions about Change management plan: what goes in it, how to write one and how it applies to an AI rollout
How long should a change management plan be?
As short as the change allows. For a small change, one or two pages that name the owner, the people affected, the first step and the rollback is enough. A bigger change needs more detail, but every part should still be readable in one sitting.
Who should own a change management plan?
One named person who runs the plan day to day, with a sponsor who can settle disagreements. Approvers for each step should be named in the plan.
What is the difference between a change management plan and a project plan?
A project plan covers the work of building or buying the change. A change management plan covers how people and systems move across to it: communication, training, testing, approval and rollback. Most changes need both.
Do I need a rollback plan?
We recommend one. Write the conditions that stop the change and the steps that put things back, then check that someone could follow them under pressure.
Is a change management plan different for AI tools?
The parts are the same. Add which tasks the tool may be used for, who checks its output before use, and what happens to work already produced if it is switched off.
Talk to the team that would do the work
Bring your requirements to a working session with the person who'll actually deliver.
Book a Discovery Call