Change Management Communication Plan: Template, Examples and Steps

Change management communication decides whether a change is understood or resisted. Changes often stall for the same reasons: employees hear about them from colleagues before their manager, the reasons for the change are never explained, and the only channel used is an all-staff email that is skimmed and forgotten. A change management communication plan fixes this by setting out who needs to hear what, from whom, through which channel and when, before the first announcement goes out. This guide explains what to include, gives a ready-to-copy plan template and example messages, and shows how the plan fits beneath your wider internal communications strategy and internal communication plan.

What is a change management communication plan?

A change management communication plan is a schedule of the messages needed to take employees through a specific change, from the first announcement to the point where the new way of working is normal. For each phase it lists the audience, the key message, the sender, the channel, the timing, how employees can respond and who owns each message.

It differs from a general internal communication plan in two ways. It covers one change rather than a whole year, and it is built around the stages people move through as they adjust, so the messages change as the project moves from announcement to go-live and beyond.

Why does change management communication matter?

Employees cannot support a change they do not understand. Clear communication explains why the change is happening, what it means for each person and what they need to do, and it gives people a way to ask questions. Without it, rumour fills the gap, managers are caught unprepared and adoption slows, even when the change itself is sound.

Who sends each message matters as much as what it says. In Prosci research on best practices in change management, 58% of employees said they prefer to hear about the personal impact of a change directly from their supervisor, while most want to hear the business reasons from the chief executive. A good plan therefore splits each change into the why, which comes from senior leaders, and the what it means for me, which comes from line managers.

Who should communicate change to employees?

Senior leaders should explain why the change is happening and how it connects to the direction of the business. Line managers should explain what it means for their team and each person in it. The project team should cover the practical detail: dates, training and support. Internal communications coordinates timing, channels and consistency across all of them.

Change management communication plan template

Copy the template below into a spreadsheet and add one row per message. The example rows show a typical change, the move to a new expenses system, across five phases. Replace them with your own change, audiences and dates, and keep the columns.

How to create a change management communication plan in seven steps

A plan for a medium-sized change usually takes a week or two to draft. Most of that time goes on steps 1 to 3, because the messages are only as good as your understanding of who is affected and how.

1. Define the change in one paragraph. Write down what is changing, why, when, and what will be different for employees afterwards. If the project team cannot agree this paragraph, the communication will not be consistent either.
2. Map the affected audiences. List each group the change touches and how much: some teams will change how they work every day, others only need to know it is happening. Note how each group works and which channels they can actually see, especially staff without a desk or email address.
3. Agree senders and brief managers first. Confirm who announces the change and who explains it locally. Give line managers the full picture, talking points and an answer sheet before their teams hear anything.
4. Write the core messages. Draft the why, the what and the what it means for me once, then reuse that wording across every channel so employees hear one version of the story.
5. Choose channels for each message. Use broad channels such as the newsletter for context, and targeted, hard-to-miss channels such as desktop alerts for deadlines and actions. Ask for an acknowledgement where employees must confirm they have read a policy or completed a step.
6. Build feedback routes into every phase. Give people a way to ask questions and raise concerns at each stage: a question form, manager meetings, help desk tickets or a short pulse survey. Publish answers to common questions so the same concern is not raised a hundred times.
7. Schedule, measure and adjust. Put every message into the template with a date and owner, track reach and acknowledgement, and review feedback weekly during the change. Adjust the next messages based on what people are still asking.

Change management communication examples

The example messages below follow the expenses system change in the template. Adapt the details and keep the structure: reason first, then impact, then action.

Manager briefing note

All-staff announcement

Go-live desktop alert

Post-change feedback request

How do you handle resistance in change communication?

Treat resistance as information rather than opposition. Ask employees what concerns them, answer honestly, including when the answer is not yet known, and show what changed as a result of their feedback. Most resistance comes from uncertainty about personal impact, so make sure line managers can explain what the change means for each role.

Track the questions and concerns you receive by audience and theme. If one team raises the same concern repeatedly, the issue is usually missing information or a manager who has not been briefed, and a targeted message to that team will do more than another all-staff update.

What are common change management communication mistakes?

The most common mistakes are announcing before managers are briefed, explaining what is changing without explaining why, relying on a single all-staff email, communicating only at the start and the end, and offering no way to ask questions. Each one leaves a gap that rumour and frustration fill, which slows adoption of the change.

• Managers hear last: if employees know more than their manager, the manager cannot answer questions and loses credibility.
• No reason given: people accept disruption more readily when they understand the problem the change solves.
• Email only: an announcement buried among other emails will be missed by many, and staff without a company email address will not see it at all.
• Silence in the middle: long gaps between announcement and go-live let uncertainty grow. Short, regular updates keep the change visible.
• No feedback route: without a way to raise concerns, employees raise them with each other instead.

Delivering change communication with Heed

A change plan relies on reaching each audience through a channel they will actually see, and on knowing who has read the messages that matter. Heed is an internal communications platform that manages desktop alerts, desktop tickers, lock screens, screensavers, digital signage, mobile push, SMS and email from one console. Messages can be targeted by department, location or role using Active Directory and single sign-on, and mandatory messages can require a named, timestamped acknowledgement, so you can see which teams have read a go-live notice before the deadline rather than estimating from email open rates.

For the embed phase, Heed Survey delivers short pulse surveys straight to employees' screens, so you can measure how the change has landed. Heed is available as a true on-premises installation or with regional cloud hosting, and is backed by ISO 27001 certification. If the change is unplanned, such as an outage or incident, see our crisis communication strategy guide.

Planning a major change? Book a demo to see how Heed delivers each phase of your change communication to the right employees and shows who has read it.