Change Management Communications Plan: Build One That Works

A change management communications plan is a written schedule that says who tells whom what, through which channel, when, and how you will know the message landed. Build it in five moves: group your audiences, write the core messages, pick channels and a sequence, set up two-way feedback, and review the plan on a fixed rhythm. Most plans fail because they stop at the announcement. This guide covers the full arc, with a sample timeline and a template you can copy today.

TL;DR

• A plan is a living schedule of messages, not a single announcement. Every line names an audience, a sender, a channel, a date and a purpose.
• Group people into tiers (champions, directly affected, awareness only) and tailor each message to what that tier needs to do.
• Send the executive message first, the manager message second and the logistics message last, and repeat the core message through several channels.
• Measure with participation, views and survey responses, and talk to people one-on-one. Update the plan whenever scope, people or timing change.
• Managers carry most of the dialogue. Give them talking points and answers before the first announcement goes out.

Table of Contents

• What a change communications plan is supposed to do
• Step 1: Sort your audiences into tiers
• Step 2: Write the core messages
• Step 3: Choose channels and sequence the messages
• A template you can copy
• Change communication examples
• Collect feedback and measure whether it works
• Keep the plan alive during implementation
• Perspective: why plans fail on the floor
• Put a plan on paper in 90 days
• FAQ
• Sources

What a change communications plan is supposed to do

ServiceNow describes a communication plan as a documented strategy for telling an organization about a change, giving the right people the right project information and benefits at the right time so they actively support it. That definition is useful because it names the three variables you control: people, content and timing.

The Open University lists three objectives worth borrowing: build understanding and trust, change behaviors so the initiative succeeds, and create two-way dialogue with stakeholders. Notice that only the first is about information. The other two are about what people do and whether they feel safe saying what they think.

In a $5M to $50M company this matters more than it does in a large enterprise. You have no internal communications department. The owner, the VP of Operations and a handful of supervisors are the whole channel. If the plan lives only in someone's head, the change reaches the floor as rumor first and policy second.

One distinction saves confusion. AWS separates a communication strategy, which holds high-level goals and methods, from the communication plan, a detailed schedule of delivery dates, audiences, messages and owners that is typically updated weekly. Write the strategy in a paragraph. Spend your effort on the plan.

Step 1: Sort your audiences into tiers

Start with people, not messages. K-State's change communications guide suggests grouping audiences into tiers by role and relationship to the change: champions, people directly involved or impacted, people who need basic awareness, and recipients. Each tier gets its own objectives, sensitivities and role-specific needs.

For an operations change, such as a new dispatch process, a revised pricing approval flow or a new warehouse management system, the tiers usually look like this:

• Sponsors and champions: the owner or CEO, the executive sponsor and a few respected frontline leads. They need the full case and the language to defend it.
• Directly affected: the crews, reps or shift teams whose daily work changes. They need to know exactly what they do differently, starting when.
• Adjacent teams: finance, customer service, purchasing. They need to know what will hit their desks and when.
• Awareness only: customers, vendors or other sites who just need a heads-up.

Then write one line for each tier: what do we want these people to know, feel and do? If the "do" is empty, that tier probably belongs in the awareness group, and a short note will do.

The Government of Jamaica's change playbook adds a point that is easy to skip: build the "what's in it for me" factor into messages based on what you learned about each stakeholder group. A dispatcher cares about fewer double entries. A controller cares about month-end close. Same change, different opening line.

Step 2: Write the core messages

K-State's guide says leaders should cover the core what and why, what is starting, continuing or stopping, why it matters, what is not included, and what information will come later. The last two items do the most work. Saying what is not changing calms the people who assume the worst. Saying what you do not know yet, and when you will, keeps silence from being read as secrecy.

Cornell's IT communication standards say an announcement should answer five questions early: what is changing, who is affected, when it happens, what action is required, and where to find documentation, training, support contacts or office hours. For team updates it recommends a structure of summary, what is changing, why and the benefits, what recipients must do, a chronological timeline, and support resources.

UC Berkeley's toolkit goes further for the first group meeting. It suggests covering the case for change, the future vision, the impact on the team, what is and is not changing, concerns and ideas, a team-specific behavior plan and next steps, including one-to-one meetings and a feedback work team.

A simple message house keeps this manageable:

1. One sentence on why now. The business reason, in plain terms: margin, rework, safety, customer complaints.
2. One sentence on what changes. Concrete, with the process or tool named.
3. Three to five supporting points. What starts, stops and stays; the timeline; what support exists.
4. One sentence on what you need from them. A specific action with a date.
5. One route for questions. A name, a mailbox or a standing time.

Every sender uses the same house. The executive version is shorter and more strategic, and the supervisor version is more operational, but nothing contradicts anything else.

Step 3: Choose channels and sequence the messages

K-State recommends using multiple methods and regularly scheduled channels, such as team meetings, town halls and weekly emails, sequencing messages by audience sensitivity or impact, repeating them over the project lifecycle and adding detail as more becomes known. The same guide states that people typically need to hear an idea about seven times before it sticks, which is the strongest argument for repetition over a single polished announcement.

The Open University's guiding principles point the same way: be visible, be open and honest, treat face-to-face engagement as the primary channel, and stay consistent. Email confirms. Conversations convince.

Who speaks first

The 15Five help center gives a clean sequence for a workplace-software rollout: an executive announcement first, a manager announcement second, and an HR or administrator message last. Its example timeline sends the CEO message three weeks before launch, the manager message two weeks before and the logistics message one week before. Each message explains the reason, what happens first, what people must do and where to ask questions. The pattern transfers well beyond software: purpose from the top, meaning from the direct manager, logistics from whoever runs the details.

The IFMA Change Communication Playbook offers a useful menu of formats, including an organizational announcement, kickoff event, project website with FAQs and a question mailbox, leader talking points, executive briefings, lunch-and-learns and post-change surveys. Pick the few your company can sustain. A weekly email you actually send beats a project website nobody updates.

Matching channel to purpose

Managers deserve special attention. The Open University stresses that they should be equipped with tools and resources to own the dialogue with their specific stakeholder groups. If your supervisors have never had to explain a change they did not design, short leader communication training in how different personality styles hear a message can help them prepare before the first team meeting.

A template you can copy

The Washington Office of Financial Management's playbook recommends recording description, timing, sender, receivers, mode and main messages for every anticipated communication. ServiceNow suggests a project-plan layout with activity, communication objectives, audience, delivery format, timeframe, responsibility and status. Combined, one row of your plan reads like this:

Assign one owner to the whole sheet. ServiceNow's guide advises that the executive sponsor give final approval so the plan stays aligned with leadership, while the change lead and project manager draft and finalize it together.

Change communication examples

Cornell's toolkit includes a real-world announcement: replacing text-message multifactor authentication with an authenticator app. The message identifies who is affected, gives the dates and tells people to install and configure the new app. It is short because it answers the five questions and stops.

Here is a sample for an operations setting, written as an illustration rather than a client case. A 120-person distributor moves from paper pick tickets to a handheld scanning workflow.

Three weeks out, owner to all staff (all-hands plus email recap):

Starting the first week of next month, our pickers move from paper tickets to handheld scanners. We are doing this because mis-picks cost us credits and customer trust every week. Your job is the same. The way you confirm each pick is different. Training happens on your regular shift, and your supervisor will walk you through the schedule next week. We do not yet know the exact date for the second warehouse. We will tell you by the end of this month. Questions go to your supervisor or to the mailbox on the break room board.

Two weeks out, supervisors to their teams (huddle, with a one-page FAQ): what a pick looks like on the scanner, which shifts train when, who the floor "super users" are, and what happens if the scanner goes down.

One week out, project lead to all affected staff and customer service (email plus posted checklist): training slots, login steps, go-live day, who is on the floor for support, and how customer service should answer "why is my order a day late" during week one.

After launch: a short Friday note with what went well, what broke and what changed, plus a five-question pulse survey after two weeks.

The structure never changes: why, what, when, what you must do, where to ask.

Collect feedback and measure whether it works

Communication that only flows downward is a broadcast. K-State's guide suggests collecting feedback through surveys, open Q&A sessions, team meetings and one-on-ones, and tracking clicks or views, attendance and survey responses to see whether communication objectives are being met. Use both numbers and conversation: a 90 percent open rate says nothing about whether the night shift understood the new process.

The UK charity body NCVO notes that clear avenues for two-way feedback, such as workshops, questionnaires or internal channels, help identify resistance and surface new ideas. UC Berkeley's guidance frames the same idea well: communication is not only message delivery. Leaders use group and one-to-one conversations to listen, acknowledge concerns, gauge commitment and tailor support.

A practical measurement set for a midmarket team:

• Attendance at each briefing, by shift or site.
• A three-question pulse every two weeks: "I understand what is changing," "I know what I need to do," "I know who to ask."
• The number and type of questions arriving through the question route. Repeated questions mean a message is unclear.
• Supervisor reports from one-on-ones, collected in a five-minute weekly check-in.

Keep the plan alive during implementation

The GSA's M3 Playbook describes the implementation work plainly: deliver planned messages, monitor feedback, update the communications plan as needed, reassess impacts and readiness, and report in governance meetings. The Interstate Technology and Regulatory Council calls a communication plan a living document that is updated as circumstances change, with interim evaluation to catch follow-up needs such as additional communications or newly identified audiences.

Connecticut's template gives the triggers: update the plan when stakeholders, staff, roles, scope or key objectives change, then approve and redistribute it. For a small leadership team, translate that into a weekly 15-minute review: what did we send, what did we hear, what changes next week?

AWS adds a reason to keep the rhythm steady: a set cadence reduces uncertainty and resistance. People tolerate hard changes better when they know when the next update comes.

If you want the communication plan to sit inside a wider adoption plan, our guides on a 60-day change adoption plan and on avoiding change fatigue show how messages tie to owners and weekly cadences, and our implementation roadmap template gives you the first 90 days on one page.

Perspective: why plans fail on the floor

We have run warehouse operations, home services, solar and consumer products teams, and the pattern is consistent. The announcement is rarely the problem. The problem is the second week, when a supervisor gets asked a question nobody prepared them for, and answers it differently from the supervisor on the next shift.

That is why we treat a communications plan as part of the execution system, not as a memo. Every message is tied to an owner, a date and a behavior we want to see on the floor. Supervisors get the talking points before their teams do. Scorecards and meeting cadences repeat the message every week, so the change does not depend on one speech.

It is also why we do not hand over slide decks. Our engagements are built to put the plan in front of a floor manager on Monday morning and to transfer the habits, so your team can keep running the cadence after we leave. If your strategy is clear but the results are not showing, check the communication chain first. It is usually where the gap sits.

David

Put a plan on paper in 90 days

If your team has a change underway and the messages are not landing, our 90-Day Operations Audit is a fixed-price way to find out why. It is $3,500 and maps your people, processes and performance systems against your goals. It ends with a prioritized action plan your managers can run, including the scorecards and meeting cadences that carry the message after launch.

If the gap is wider than communication, our Strategy Execution Gap page explains how we work with leadership teams between strategy and results. Or start at tkdconsult.com and book a paid discovery call.

FAQ

What should a change management communications plan include?

Include your audience tiers, core messages, channels, senders, timing, feedback methods and a measurement approach. For each planned communication, record the description, timing, sender, receivers, mode and main messages, as the Washington playbook recommends. Add a named owner and a review date so the plan does not go stale.

How far ahead of a change should you start communicating?

Start before the logistics are finished. One published example from 15Five sends the executive message three weeks before launch, the manager message two weeks before and the logistics message one week before. Adjust that to the size of your change, but keep the order: purpose, then meaning, then logistics.

How often should you repeat the message?

More often than feels natural. K-State's guide says people typically need to hear an idea around seven times, so layer the same core message through meetings, written updates and one-on-ones across the project. Vary the format and keep the substance identical.

Who should send change communications?

Let each level say what it is best placed to say. Executives explain why, managers explain what it means for the team, and a project lead or HR handles logistics. Give managers talking points first, because employees will take their questions to them.

How do you know if the communication is working?

Watch participation, views and survey responses, and pair them with conversations. Open Q&A sessions and one-on-ones show whether people understood what they must do. Repeated questions on the same point mean the message needs rewriting.

Sources

• ServiceNow: Organizational Change Management communication plan
• Open University: Change management for hybrid working
• Cornell Evolve IT: Change Communication Standards
• K-State IT: Change Communications Resource Guide
• Government of Jamaica: Change Management Playbook, Stakeholder management
• UC Berkeley: Change Management Toolkit
• AWS Prescriptive Guidance: Change Acceleration
• 15Five Help Center: Who should communicate the rollout and when
• IFMA: Change Communication Playbook
• Washington OFM: Change Management Playbook
• NCVO: Communicating change and consulting stakeholders
• GSA: M3 Playbook Key Task 3.7
• ITRC: Communication Plan Description
• Connecticut DSS: Communications Management Plan Template

Recommended

• Midmarket Ops Managers: Stop Change Fatigue With a 60 Day Action Plan
• Make Change Stick: Midmarket Leaders Put Models to Work in 60 Days
• 60 Day Runway: An Operator Ready Change Adoption Plan
• One Page Implementation Roadmap Template to Run Your First 90 Days