How to Create a Change Management Plan
A change management plan turns assessment findings, project information, and organizational needs into a coordinated set of actions for preparing and supporting the people affected by a change.
The planning should not start with a standard list of communications, training sessions, stakeholder meetings, and other activities. Start by identifying what affected people and groups actually need. Then determine the best way to meet those needs and turn those decisions into specific actions.
Start With the Need, Not the Activity
Stakeholder and impact findings tell you where attention may be required. Planning begins by translating those findings into specific needs. Only then should you decide whether communication, engagement, training, manager support, leadership action, coaching, job aids, or other methods are the best response.
What Is a Change Management Plan?
A change management plan is the working document used to organize and manage the actions needed to prepare and support people through a specific organizational change.
It brings the support required for the change into one coordinated plan, with specific actions, timing, ownership, dependencies, and measures.
The plan should be detailed enough to manage the work from week to week without becoming so complicated that maintaining the document becomes a separate job.
A change management plan is different from the project plan. The project plan manages delivery of the technical, operational, or organizational change. The change management plan manages the actions needed to help affected people prepare for and work successfully with that change. The two plans should be coordinated, but they serve different purposes.
What You Need Before You Start
You do not need every detail of the initiative finalized before planning begins. You do need enough information to identify the important needs and avoid building the plan around assumptions.
A Clear View of the Change
Understand what is changing, what is in scope, which parts of the organization are affected, and the major implementation milestones that will influence the plan.
Change Impact Findings
Understand what will change for affected roles and teams and the significance of those changes. A Change Impact Assessment is a key source for these planning inputs.
Stakeholder Findings
Understand which stakeholders require attention based on factors such as influence, impact, disposition, and their role in helping or hindering the change. A Stakeholder Analysis provides these inputs.
Timing and Constraints
Know the major project dates, available resources, organizational constraints, and other changes affecting the same people. These factors determine what can realistically be delivered and when.
The assessments provide information. The plan is where you decide what to do with that information.
What Should a Change Management Plan Include?
Most plans work best as a tracker with one row for each significant action. The exact fields can vary, but the structure should make the reasoning behind the action visible and give the team enough information to manage it.
Scroll horizontally to see all columns →
| Field | What It Captures | Question It Answers |
|---|---|---|
| Finding | The impact, stakeholder issue, constraint, or other finding behind the need. | What led us here? |
| Audience | The people or group the need applies to. | Who needs support? |
| Need | What the audience needs to understand, do, decide, provide, or receive. | What needs to be true? |
| Priority | The relative importance or urgency of the need. | How much attention does this require? |
| Method | The type of response selected to meet the need. | What is the best way to address it? |
| Action | The specific activity or deliverable that will be completed. | What exactly are we going to do? |
| Timing | The date, timeframe, or project milestone that determines when the action occurs. | When does it need to happen? |
| Owner | The person responsible for making sure the action is completed. | Who is accountable? |
| Dependencies | Decisions, information, project deliverables, or other actions required first. | What could affect delivery? |
| Success Measure | How you will determine whether the need was addressed. | How will we know whether it worked? |
| Status | The current state of the action, such as planned, in progress, complete, delayed, or cancelled. | Where does this stand? |
| Notes | Relevant decisions, assumptions, changes, or follow-up information. | What else should someone know? |
You may need additional fields for location, budget, resources, delivery format, or other initiative-specific information. Keep the structure as simple as the work allows. The purpose of the tracker is to help manage the plan, not create administrative work that adds little value.
If you use a change management plan template, adapt it to the needs of your project rather than allowing a fixed set of fields or activities to determine how you plan the work.
Common Methods for Meeting Change Needs
The methods below are common options, not an exhaustive list. Your project may require other methods based on the type of change, the people affected, organizational conditions, timing, and the needs you identify. Choose the method or combination of methods that best fits your project and addresses each need.
Scroll horizontally to see all columns →
| Method | When It Helps | Common Options |
|---|---|---|
| Communication | People need information, context, clarity, or direction. | Emails, newsletters, intranet updates, town halls, presentations, signage, FAQs, videos, manager talking points |
| Stakeholder Engagement | You need input, alignment, decisions, involvement, or direct attention to concerns. | Interviews, workshops, focus groups, working sessions, listening sessions, stakeholder meetings, feedback sessions |
| Leadership and Sponsorship | The change needs visible direction, decisions, reinforcement, or organizational support. | Sponsor messages, leadership meetings, town halls, leader talking points, executive updates, participation at key events |
| Manager Support | Managers need to prepare their teams, answer questions, reinforce expectations, or provide local support. | Manager briefings, toolkits, talking points, FAQs, team discussion guides, manager check-ins, escalation channels |
| Training and Practice | People need knowledge or skills to perform their work differently. | Instructor-led training, virtual training, e-learning, demonstrations, simulations, hands-on practice, knowledge checks |
| Coaching | Individuals or small groups need targeted help adapting or applying the change. | One-on-one coaching, group coaching, peer coaching, manager coaching, follow-up sessions |
| Job Aids and Resources | People need practical support while performing the new work. | Quick-reference guides, checklists, process maps, step-by-step instructions, cheat sheets, FAQs, knowledge-base articles |
| Change Agent Support | Local representatives can help reinforce the change and provide two-way feedback. | Change agent meetings, local briefings, team check-ins, feedback collection, office hours, peer support, issue escalation |
| Barrier Removal | A concern, obstacle, competing priority, process issue, leadership gap, or resistance is getting in the way of the change. | Listening sessions, targeted meetings, issue resolution, clarification, leadership intervention, process fixes, workload adjustments, escalation, individual follow-up |
| Implementation and Adoption Support | People need help as they begin working in the new way. | Office hours, floor support, help channels, drop-in sessions, refresher training, peer support, issue tracking, follow-up communications |
How to Create a Change Management Plan
Build the plan by moving from identified findings to needs, and then from those needs to specific actions that can be delivered and managed.
Set the Planning Boundary
Start by defining exactly what this plan will cover.
Confirm the initiative, affected business areas, locations, implementation period, and any phases or project boundaries that matter to the change management work.
Then organize the stakeholder, impact, project, and constraint information you already have so it can be used consistently throughout the plan. Separate confirmed information from assumptions or decisions that are still changing.
Identify the Needs Created by the Change
This is the most important planning step.
For each significant impact or stakeholder finding, determine what the affected person or group needs in order to prepare for, support, or work successfully with the change.
A useful way to think about the need is to ask:
- What do they need to understand?
- What do they need to be able to do differently?
- What decisions or input are needed from them?
- What concerns, obstacles, or uncertainties need to be addressed?
- What support will they need as the change is implemented?
Write the need as an outcome, not as an activity.
For example, “send an email to Accounts Payable” is an activity. “Accounts Payable employees need to understand the new invoice approval process and when it takes effect” is a need.
Similarly, “train users” is an activity. “Accounts Payable employees need to be able to complete the new invoice workflow before implementation” is a need.
Prioritize the Needs
Not every need deserves the same level of attention.
Use the available stakeholder, impact, timing, and project information to determine where the greatest change management effort is required.
A need may require more attention because:
- the change to the role or team is significant;
- the affected group is important to successful implementation;
- a stakeholder has substantial influence over others;
- a decision or action is time-sensitive;
- many people are affected;
- several changes are affecting the same group at once; or
- failure to address the need could create a significant adoption problem.
The purpose is not to create another complicated scoring model. It is to make deliberate choices about where attention and resources should be concentrated.
Determine the Best Way to Meet Each Need
Only after the needs are clear should you decide how to address them.
Use the common methods above as possible options, but do not limit the plan to them. Select the method or combination of methods that best fits the need, the project, and the people affected.
The choice should follow the need. Someone who needs to understand why a process is changing requires a different response from someone who must learn how to perform a new process or from a stakeholder whose concerns could affect an important decision.
Turn the Response Into Specific Actions
Once you have chosen the method, define exactly what will happen.
A useful plan action should be specific enough that another person could understand what needs to be delivered without having to interpret a vague label.
Manager communication
Conduct a 60-minute briefing with Accounts Payable managers covering role impacts, implementation timing, key messages, and the questions employees are likely to ask.
Train Accounts Payable
Deliver role-based invoice-processing training with hands-on practice for Accounts Payable users two weeks before implementation.
At this stage, also determine what success should look like. The measure should connect to the need, not simply confirm that the activity occurred.
Sequence the Actions and Confirm Delivery
Now look at all of the actions together.
Determine when each one should occur, who will own it, what resources it requires, and what it depends on.
Timing should follow what affected people need and when they need it. Managers may need preparation before their employees receive a major communication. Employees may need to understand a new process before detailed training begins. Training may depend on the future process or system being stable enough to teach.
Also review the plan from the audience’s perspective. Several reasonable activities can become excessive when they all reach the same group during the same period.
Confirm that every significant action has:
- a realistic timeframe;
- one accountable owner;
- the necessary resources;
- known dependencies; and
- a place in the overall implementation schedule.
Review, Approve, and Maintain the Plan
Before treating the plan as ready, review it as a whole rather than one action at a time.
Look for:
- important needs that have no response;
- actions that do not connect to a clear need;
- high-priority groups receiving too little support;
- duplicate or overlapping actions;
- poorly timed activities;
- actions without clear ownership;
- unresolved dependencies; and
- planned actions that exceed available capacity.
Once the plan is agreed, treat it as a working document. Update it when project timing changes, new impacts emerge, feedback identifies an unmet need, or implementation results show that the original response is not enough.
The purpose is not to preserve the original plan. It is to keep the plan aligned with what the change actually requires.
Worked Example: From Finding to Action
Consider an organization implementing a new ERP system. The example below shows how several findings can be translated into needs and then into different change management actions.
This is a simplified example, not a complete change management plan template. It shows only the fields needed to demonstrate how a finding becomes a need, method, and action. A working plan would typically include the additional fields described above, including audience, priority, owner, dependencies, status, notes, and any initiative-specific information.
Scroll horizontally to see all columns →
| Finding | Need | Method | Action | Timing | Measure |
|---|---|---|---|---|---|
| Accounts Payable employees will use a substantially different invoice workflow. | Employees need to be able to complete the new workflow accurately before implementation. | Training, practice, and job aid | Deliver role-based process and system training with hands-on practice and a workflow job aid. | Two weeks before implementation | Employees successfully complete the practice workflow. |
| Accounts Payable managers will be the first source of employee questions but are unclear about several role impacts. | Managers need to understand the impacts and be prepared to explain them to their teams. | Manager preparation | Conduct a manager briefing covering role impacts, implementation timing, key messages, and likely employee questions. | Before the first employee briefing | Managers report that they can explain the change and answer common questions. |
| A Finance leader has high influence but continues to question the proposed process. | The leader’s concerns need to be understood and resolved before broader leadership communication. | Direct stakeholder engagement | Hold a working session with the sponsor and Finance leader to review concerns, decisions, and remaining issues. | Before leadership communication is finalized | Outstanding issues are resolved or assigned for decision. |
| Employees understand the system change but are unclear about when the new process becomes mandatory. | Employees need clear direction on the implementation date and what changes on that date. | Communication and manager reinforcement | Provide a role-specific implementation briefing followed by team-level manager discussions. | Three weeks before implementation | Employees can identify when the new process begins and what they must do differently. |
| Users are expected to encounter process questions during the first few weeks of using the new system. | Employees need a quick way to get help while applying the new process. | Implementation support | Provide scheduled office hours and a defined path for escalating recurring process questions. | Beginning at implementation | Recurring issues are identified and addressed within the agreed response time. |
Where Planning Fits in the Change Process
Change management planning is Step 5 of the Change Adaptive change management process. It turns assessment findings into coordinated actions by determining what is needed, for whom, and when. The plan then guides implementation and is updated as new information emerges.
Develop the Change Management Strategy and Plan
Current Step What actions are needed, for whom, and when?See the Change Management Process for the full eight-step process and how the phases work together.
Build a Stronger Change Communication Plan
Communication is one of the methods you may use to address needs identified in the plan. The Ultimate Guide to Developing Change Communication Plans provides a practical framework for building the messages, audiences, channels, timing, feedback mechanisms, and activities needed for the communication work.