Change Management Plan Template Excel (Filled Example)
9 min read ยท 2026-11-18
A good change management plan template excel file has six tabs: summary, stakeholders, impact assessment, communication plan, training plan, and risks and adoption. Every row names who is affected, what changes for them, who owns the action, the due date, and how you will know it worked.
Most free templates give you empty columns and stop there. This guide fills in every tab for one real kind of project: moving a sales team from spreadsheets to a CRM. Each row has a named owner and a date. You also get the 12-week plan the rows belong to and the one page to show leadership.
The roadmap at a glance
Goal: Roll out a business change, such as a new CRM, so people actually use it, with every group informed, trained and supported. Duration: 12 weeks
Prepare (Weeks 1-2)
Agree on why the change is happening and who it touches before anyone announces it.
- Write the change summary: what changes, why, start date, sponsor and owner.
- List every affected group in the stakeholder tab, including managers and support teams.
- Score each group's impact as high, medium or low in the impact tab.
- Get the sponsor to sign off on the scope and the success measures.
Milestone: Signed change summary and a complete stakeholder list.
Communicate (Weeks 3-4)
Tell each group what changes for them, in their own terms, before training starts.
- Fill the communication tab with one row per message, audience, channel and sender.
- Brief managers first so they can answer questions from their teams.
- Run a kickoff session and record the questions people ask.
- Open one channel for questions and name the person who answers them.
Milestone: Every high-impact group has received at least two messages.
Train (Weeks 5-7)
Give each role the skills it needs, matched to the tasks it will really do.
- Build the training tab by role, not by feature.
- Schedule short sessions plus a written guide for each role.
- Name a champion in each team to help colleagues after the sessions.
- Check attendance and follow up with anyone who missed a session.
Milestone: All affected users trained, with attendance logged.
Deploy (Weeks 8-9)
Switch over in a controlled way and fix problems fast.
- Run a pilot with one team for a few days before the full launch.
- Log every issue in the risk tab with an owner and a fix date.
- Hold a short daily check-in during go-live week.
- Confirm the old process or tool is retired on the agreed date.
Milestone: Full go-live with no open critical issues.
Reinforce (Weeks 10-12)
Make the new way of working stick and prove the change delivered.
- Track adoption measures every week in the adoption tab.
- Coach the teams that lag behind and update the guides.
- Collect feedback and record lessons learned.
- Present the results to the sponsor and close the plan.
Milestone: Adoption targets met and the plan formally closed.
What goes in a change management plan template in Excel
Each tab should answer one question. Put the tabs in the order people will use them. Use the same group names on every tab so filters and lookups match.
Two Excel features save time. Add a data validation list to the status, impact and attitude columns so entries stay clean and you can filter every high-impact row in one click. Add conditional formatting to the due date column so late actions turn red without anyone checking by hand.
- Summary: change name, description, reason, sponsor, change owner, start date, go-live date, success measures, approval status.
- Stakeholders: group, role, people affected, influence, current attitude (supportive, neutral, resistant), what they need, owner.
- Impact assessment: group, process affected, what changes, impact level, new skills needed, action, owner, due date.
- Communication plan: message, audience, channel, sender, date, status, feedback received.
- Training plan: role, skills needed, format, session date, trainer, attendance, follow-up owner.
- Risks and adoption: risk, likelihood, impact, mitigation, owner, review date, status, plus one weekly row per adoption measure.
Filled change management plan example: a CRM rollout, row by row
Here is the whole file filled in for a sales team of account executives, sales managers, finance and IT support. Week 1 is the first week of the project.
The names are examples. Swap in your own people, but never leave the owner column empty.
Summary tab
The summary tab is the first thing the sponsor signs. Keep it to the facts below.
- Change: replace sales spreadsheets with a shared CRM.
- Reason: deals live in separate personal files, so the weekly forecast is slow to build and hard to trust.
- Sponsor: Sarah, head of sales. Owner: Mark, sales operations manager.
- Start: week 1, Monday. Go-live: week 8, Monday. Plan closed: week 12, Friday.
- Success measures: every new deal logged in the CRM, and the weekly forecast pulled from the CRM only by week 10.
- Approval: signed by Sarah, week 2, Thursday.
Stakeholder tab
One row per group, with its impact, its current attitude, what it needs and the person who owns the relationship.
- Account executives: high impact, neutral. They need fast deal logging on mobile. Owner: Mark. Review: week 2, Tuesday.
- Sales managers: high impact, supportive. They need pipeline reports for their weekly meeting. Owner: Sarah. Review: week 2, Tuesday.
- Finance: medium impact, neutral. They need a forecast export at month end. Owner: Priya, finance analyst. Review: week 2, Wednesday.
- IT support: low impact, supportive. They need admin access and a known-issues list. Owner: Tom, IT lead. Review: week 2, Wednesday.
Impact assessment tab
One row per process that changes, with the new skill, the action that covers it, the owner and the due date.
- Account executives, logging a new deal: entered in the CRM instead of a personal sheet. Skill: create and update opportunities. Action: 45-minute session and a one-page guide. Owner: Mark. Due: week 6, Friday.
- Sales managers, weekly pipeline review: run from a CRM dashboard instead of merged files. Skill: filter and read pipeline views. Action: dashboard built and walked through. Owner: Mark. Due: week 7, Wednesday.
- Finance, month-end forecast: exported from the CRM. Action: export template agreed and tested. Owner: Priya. Due: week 7, Friday.
Communication tab
Notice who sends the first message: Sarah, the sponsor, not the project team. People listen to the person they report to. Managers hear it three days before their teams, so they can answer questions.
- Why we are moving and what changes for you. Audience: sales managers. Channel: managers' meeting. Sender: Sarah. Date: week 3, Monday.
- Same message for account executives. Channel: team meeting plus an email recap. Sender: Sarah. Date: week 3, Thursday.
- Training dates and how to book. Audience: all users. Channel: email. Sender: Mark. Date: week 4, Tuesday.
- Go-live reminder and where to get help. Audience: all users. Channel: email and team chat. Sender: Sarah. Date: week 7, Thursday.
Training tab
Training is planned by role, with a named trainer and a follow-up owner for anyone who misses a session.
- Account executives: logging deals and updating stages. Format: 45-minute session plus a guide. Trainer: Mark. Dates: week 5, Tuesday and Thursday. Follow-up for anyone absent: Mark, week 6, Monday.
- Sales managers: dashboards and forecast. Format: 60-minute session. Trainer: Mark. Date: week 5, Wednesday.
- Finance: forecast export. Format: 30-minute walkthrough. Trainer: Priya. Date: week 6, Wednesday.
- Champions: one account executive per team, named by Sarah by week 4, Friday.
Risks and adoption tab
Each risk gets a likelihood, a mitigation, an owner and a review date. The adoption rows start at go-live and are filled every Friday.
- Reps keep their old spreadsheets in parallel. Likelihood: high. Mitigation: managers run the week 9 pipeline review from the CRM only. Owner: Sarah. Review: week 9, Monday.
- Imported deal data has duplicates. Likelihood: medium. Mitigation: clean the import file and test it on the pilot team. Owner: Tom. Review: week 7, Tuesday.
- Mobile logging is too slow. Likelihood: medium. Mitigation: a short mobile form tested during the pilot. Owner: Mark. Review: week 8, Wednesday.
- Adoption rows, every Friday from week 8: share of new deals logged in the CRM, active users against users trained, support questions this week, old spreadsheets still in use. Owner: Mark.
How to present this plan to leadership on one page
Leadership will not read six tabs. They want a single page built from the same file.
Put the decision at the top, not the bottom. If the meeting gets cut short, the ask is still on the table. When a date moves, update the Excel file first, then rebuild the page, so both versions always match.
Your team, a client or HR need a different cut of the same file. Your team wants to know what changes on Monday and where to get help. A client wants the dates and the name of their contact. HR needs the affected roles and the training plan.
- The change in one sentence: what changes, for whom, and why now.
- The cost of doing nothing: one line on what keeps going wrong if nothing changes.
- The five phases on one timeline, with the go-live date and the closing date marked.
- Impact by group: high, medium or low, one line each.
- The top three risks, each with its owner.
- The success measures and the week you will report on them.
- The decision you need: sign-off, budget, or a date to confirm.
Change log, change request and other formats, in short
A change management plan covers people: how they move from the old way to the new one. A change log records every change made to a project. A change request is one form asking to change scope, budget or dates, approved before work starts. Keep those in separate files.
Excel is for tracking the plan week by week. Use Word for the signed reference copy and PowerPoint for the leadership page above. Don't paste the whole spreadsheet into a slide.
How to manage resistance and measure adoption
Resistance tells you something. Use the attitude column to spot resistant groups early, then ask what they would lose. The answer is usually specific: a report they rely on, extra clicks, or the fear of looking slow in front of their manager.
Answer each concern with a row in the plan: a custom view, a shortcut, or a champion who sits with them during go-live week. Give it an owner and a review date, like any other risk.
Read adoption from the system itself, not from surveys alone. If adoption stays flat after go-live, that shows you which team needs coaching before old habits set in.
Common mistakes to avoid
- Listing departments instead of roles hides who really changes their daily work, so split each department by role.
- Announcing the change before managers are briefed leaves them without answers, so brief them a few days ahead.
- Training on features instead of tasks slows adoption, so build each session around the three or four tasks a role does every day.
- Leaving the owner column empty or writing "team" means nobody acts, so every row gets one person's name.
- Declaring success at go-live lets old habits come back, so keep the plan open through the reinforce phase.
- Leaving dates as "TBC" means the row never gets done, so give every row a date.
Frequently asked questions
What should a change management plan include?
A summary of the change, the affected stakeholders, an impact assessment, a communication plan, a training plan, and risks with adoption measures. Add the sponsor, the owner and the approval status. Without success measures, you cannot tell whether the change worked.
How do you create a change management plan in Excel?
Create one tab per question: summary, stakeholders, impact, communication, training, and risks and adoption. Use the same group names across tabs, add dropdown lists for status and impact, and color late due dates. Fill in the stakeholder tab first, because every other tab depends on it.
Who should own each row of the plan?
One named person, never a team. The sponsor usually owns the first messages and the biggest risks. The change owner runs training and adoption tracking. Managers own whatever their teams must stop doing the old way.
How long does a change management plan take to run?
It depends on the size of the change and the number of people affected. A tool rollout for one team often fits in about three months, from preparation to reinforcement. Larger organizational changes run longer and usually move phase by phase across departments.