Change Management Communication Plan Template (With AI Prompts)
Copy a change management communication plan template for reorgs, new systems and policy changes, with a worked example and AI prompts to draft each message.
For HR

What is a change management communication plan?
A change management communication plan is a short document that says who needs to hear what about a change, from whom, through which channel, and when. It also says how you will find out whether people understood and how you will answer their questions. It applies to reorgs, new software, policy changes, office moves and anything else that alters how people work. The template below fits on two pages and is ready to copy.
TL;DR
- A good plan answers five questions for every audience: what is changing for them, why, when, what they must do, and where to ask.
- Sequence matters more than polish. Leaders hear first, then managers, then everyone else, and managers need their materials before the all-staff message goes out.
- The template has eight parts: change summary, audiences, key messages, sequence, channels and owners, manager kit, feedback loop and measures.
- AI is good at first drafts of messages, manager FAQs and audience versions of the same news. It is bad at facts, dates, legal wording and anything involving individual people.
- HR owns the people impact, communications owns the craft and channel, and the change or project lead owns the facts. Write down who signs off before drafting anything.
- Never paste confidential details (names in a layoff list, unannounced deal terms) into an AI tool your company has not approved.
What goes into the template?
Copy this into a document. Each section is short on purpose. If a section takes more than a few lines, you are probably writing the message instead of planning it.
CHANGE COMMUNICATION PLAN
1. CHANGE SUMMARY
- What is changing (one sentence, plain words):
- Why it is changing (the real reason, one or two sentences):
- Start date / key dates:
- Who is affected (groups and rough headcount):
- Who decided, and who is the visible sponsor:
- What is NOT changing (say this explicitly):
- Open questions we cannot answer yet:
2. AUDIENCES
| Audience | How they are affected | Likely reaction | What we need from them |
|----------|----------------------|-----------------|------------------------|
| Executive team | | | |
| Senior leaders | | | |
| People managers | | | |
| Directly affected employees | | | |
| Indirectly affected employees | | | |
| Other stakeholders (works council, legal, IT, vendors, customers) | | | |
3. KEY MESSAGES
- Core message (the one thing everyone should remember):
- Why now:
- What it means for you (by audience):
- What happens next:
- Where to ask questions:
- Tone notes (what to avoid saying):
4. SEQUENCE AND TIMELINE
| When | Audience | Message / activity | Channel | Owner | Sign-off |
|------|----------|--------------------|---------|-------|----------|
| T minus 2 weeks | Execs | Alignment and rehearsal | Meeting | | |
| T minus 1 week | Senior leaders | Briefing + Q&A | Meeting | | |
| T minus 2 days | Managers | Manager kit + briefing | Call + doc | | |
| T (announcement) | All affected | Announcement | Email + live session | | |
| T plus 1 day | All | Follow-up + FAQ | Intranet | | |
| T plus 1 week | All | Progress + answers to top questions | Email | | |
| T plus 30 days | All | Check-in, what we learned | Pulse survey + update | | |
5. CHANNELS AND OWNERS
- Primary channel (where the official answer lives):
- Live channel (meeting, town hall, team huddle):
- Question channel (inbox, form, Slack channel):
- Who answers questions, and within how many business days:
- Sign-off chain (who approves wording, in order):
6. MANAGER KIT
- 5-sentence summary managers can say out loud
- FAQ (10 to 15 likely questions with approved answers)
- "If asked X, say Y" for hard questions
- What managers must NOT say or speculate about
- Escalation: who to send questions they cannot answer
7. FEEDBACK LOOP
- How we collect questions (form, manager reports, live Q&A):
- Who reviews them and how often:
- How answers get published:
- How we change the plan if confusion shows up:
8. MEASURES
- Reach: did the message get to everyone? (attendance, read rates)
- Understanding: can people explain the change? (pulse question, manager reports)
- Action: did people do what we asked? (system logins, forms completed)
- Sentiment: how are people feeling? (survey, question themes)
- Review dates:
How do you fill it in, step by step?
Work in this order. It is not the order of the document, and the order is the point.
- Write the change summary last-minute-proof. Get the facts from the change lead, in writing. If a date or decision is not final, put it under "open questions." Do not let drafts guess.
- Name the "what is not changing." In reorgs and policy changes, people fear the worst version. If pay, benefits, location or reporting lines are unchanged, say so. If you do not know yet, say that too.
- List audiences by impact, not by org chart. A team that must change its daily process is a different audience from a team that only needs to know. Managers are always their own audience.
- Write the core message once. One sentence people can repeat. Everything else supports it.
- Build the sequence backwards from the announcement. Work out who must know before whom. Managers should never learn about the change at the same time as their team.
- Assign an owner and a sign-off for every row. Typically HR owns messages about people impact (roles, pay, policy), communications owns tone, channel and timing, and the change lead owns accuracy about the system or process. Legal reviews anything touching employment terms.
- Build the manager kit before the announcement. This is the part most plans skip, and it is where most confusion gets fixed.
- Set the feedback loop before launch. Decide who reads incoming questions, how often, and where answers get posted.
What does a filled-in example look like?
Here is a condensed example for a common change: replacing the company's expense reporting tool with a new one. The company is fictional, about 6,000 employees. The numbers are illustrative.
Change summary
- What: On the first of next quarter, all expense claims move from the old tool to a new one. Old claims must be submitted before the cutoff date.
- Why: The old tool's contract ends, and the new one connects directly to corporate cards so people stop typing in receipts.
- Who is affected: Every employee who submits expenses, plus finance approvers.
- Not changing: The expense policy, spending limits and reimbursement timing.
- Open question: Whether contractors will be included at launch.
Audiences (excerpt)
| Audience | How they are affected | Likely reaction | What we need |
|---|---|---|---|
| Frequent travelers | Daily use, new mobile app | Worried about reimbursement delays | Complete training before cutoff |
| Occasional submitters | Rare use | Will forget until they need it | Know where to find a 2-minute guide |
| Finance approvers | Approval flow changes | Concerned about audit trail | Attend a working session |
| Managers | Questions from teams | Annoyed at extra work | Share the kit, escalate unknowns |
Core message: "Expenses are moving to a new tool on [date]. Policy and reimbursement times stay the same. Submit old claims by [cutoff], and use the 2-minute guide for anything new."
Sequence (excerpt)
| When | Audience | Activity | Channel | Owner |
|---|---|---|---|---|
| T minus 3 weeks | Finance leadership | Walkthrough and sign-off | Meeting | Finance lead |
| T minus 2 weeks | Approvers | Working session | Live demo | Finance + IT |
| T minus 1 week | Managers | Kit and briefing | Call + doc | HR partner |
| T minus 3 days | All employees | Announcement | Email + intranet | Internal comms |
| T plus 1 week | All | "Top 5 questions" update | Internal comms | |
| T plus 30 days | All | Pulse check, fixes | Survey | HR + Finance |
Notice what is absent: no town hall, no executive video. A low-drama change needs a light plan. A reorg that affects roles needs live sessions, a visible sponsor and much more manager preparation. Scale the template to the stakes, not to your enthusiasm.
How do you adapt the plan for a reorg, a new system or a policy change?
The template stays the same. The emphasis shifts.
| Change type | What to emphasize | Common mistake |
|---|---|---|
| Reorg | Reporting lines, who decides what, what is staying the same, timing of individual conversations | Announcing to everyone before affected individuals have heard it in person |
| New system | Training, a cutover date, where to get help, what happens to old data | Announcing the tool and forgetting the support path |
| Policy change | The reason, the effective date, examples of what is now allowed or not, who to ask about edge cases | Posting the policy text and calling it communication |
| Leadership change | Continuity, who decides what in the interim, what the new leader will do first | Silence between the announcement and the new leader's first message |
For reorgs that include job losses, the plan needs legal and HR sign-off on every step, and the individual conversations come first. Do not use a general template as a substitute for your company's process for those situations.
Where can AI help with the plan?
AI is useful at the drafting stage. It turns one set of facts into several audience versions quickly, and it is good at generating questions you did not think of. Give it the facts and the template, and it gives you something to edit rather than a blank page.
Prompt 1: Draft the plan from your facts
You are helping an internal communications and HR team write a change
communication plan. Use the template structure below. Do not invent
facts, dates or names. Where information is missing, write
"[NEEDED: ...]" and list it at the end.
Change: [what is changing in plain words]
Reason: [why]
Key dates: [dates]
Affected groups: [groups and rough headcount]
Not changing: [list]
Sponsor: [role]
Company culture notes: [e.g., formal, direct, skeptical of corporate speak]
Template sections: change summary, audiences (with likely reactions and
what we need from each), key messages, sequence and timeline working
backwards from announcement date [date], channels and owners, manager
kit contents, feedback loop, measures.
Flag the three biggest risks to this rollout.
Prompt 2: Write audience versions of the same message
Here is the approved core message and facts:
[paste]
Write three versions of the announcement:
1. For all affected employees (under 200 words, plain language, starts
with what it means for them)
2. For people managers (includes what to say, what not to say, and where
to escalate)
3. For senior leaders (includes talking points and likely hard questions)
Do not add facts that are not in the text above. Do not use phrases like
"we are excited to announce." Keep the tone [direct / warm / formal].
Prompt 3: Build the manager FAQ
Based on these facts: [paste]
List the 15 questions employees are most likely to ask, including the
uncomfortable ones (job security, workload, why now, why wasn't I told
sooner). For each, draft an answer using only the facts provided. If the
facts do not support an answer, write "[NEEDED FROM LEADERSHIP]" instead
of guessing.
Prompt 4: Stress-test your draft
Read this announcement as a skeptical employee who has seen three
reorganizations. List: (1) every sentence that sounds evasive, (2) every
question left unanswered, (3) any phrase that could be read as a
promise we haven't made. Then suggest a plainer rewrite of each.
What should you check in what AI gives you?
- Every fact, date and number. AI will fill gaps with plausible-sounding details. The "[NEEDED]" instruction helps, but read for invented specifics anyway.
- Promises. Phrases like "no one will be affected" or "this will not change your workload" may appear because they sound reassuring. Remove anything leadership has not committed to.
- Tone. AI drafts drift toward upbeat corporate language. If employees are anxious, cheerful copy reads as dismissive.
- Legal and employment wording. Notice periods, severance, consultation obligations and benefits language belong to HR and legal, not a draft generator.
- Consistency. If you generate several versions, compare them side by side. Small contradictions between the manager version and the all-staff version cause real trouble.
Where should you not trust AI with change communication?
Do not use it to decide who hears what first, to judge how a specific group will react, or to write individual conversations about someone's job. Those depend on your people and your history, and the cost of getting them wrong is high.
Also check your company's rules before pasting anything. Unannounced restructuring details, employee names and personal data should only go into tools your company has approved for that kind of information. If in doubt, replace specifics with placeholders like "[Team A]" and fill them in afterward.
How do you know if the plan is working?
Check at three points. Before launch, ask a handful of managers to explain the change in their own words. If they cannot, the message is not ready. In the first week, read the questions coming in. Repeated questions mean the announcement left a gap, so post an answer in the primary channel and tell managers. At 30 days, check whether people did the thing you asked (logged in, completed the form, attended the session) and ask one or two direct questions in a short survey, such as "I understand what is changing and why."
Do not rely on email open rates alone. They tell you the message arrived, not that it landed.
Who owns what between HR, communications and the change lead?
This is where plans stall, so decide it in the first meeting.
| Role | Owns | Signs off on |
|---|---|---|
| HR | People impact, manager preparation, individual conversations, employee relations risk | Anything about roles, pay, benefits, policy meaning |
| Internal communications | Message craft, channel choice, timing, calendar across other announcements | Tone, clarity, sequence |
| Change or project lead | Facts about the system, process or timeline | Accuracy |
| Sponsor (executive) | The "why," visible presence | Final message |
| Legal | Employment and regulatory wording | Where required |
Put the sign-off chain in the plan with a turnaround time for each step. Delays in approval are the most common reason announcements go out late or watered down.
Could you build a tracker for this instead of juggling documents?
A change like this produces a lot of moving pieces: audience lists, message versions, sign-off status, incoming questions and published answers. Many teams spread these across a document, a spreadsheet and an inbox. With Remy, you can describe a small internal tool in plain English, such as a change tracker with a sign-off status per message, a question intake form for employees, and a dashboard showing open and answered questions by team. Remy builds it as a full-stack app with sign-in and a database, so access can be limited to the people running the change. You own the result instead of renting another subscription.
Frequently Asked Questions
How long should a change management communication plan be?
Two pages is enough for most changes, plus the manager FAQ as a separate document. If the plan runs longer, check whether you are drafting the messages inside it. Keep the plan as the structure and store the messages elsewhere.
When should you tell employees about a change?
As soon as you can say something accurate and useful, and after the people most affected have heard it directly. Waiting for every detail is tempting, but silence tends to fill with rumor. It is fine to say what you know, what you do not yet know, and when you will update them.
Who should send the announcement?
The person employees would expect to hear from, usually the executive sponsor or the head of the affected area, not HR or communications. Those teams write and prepare it, but the message should come from someone with authority over the decision. For changes that affect individual roles, the person's own manager should speak with them first.
Can AI write the whole communication plan?
It can produce a solid first draft if you give it clear facts and the template, and it saves real time on versions and FAQs. It cannot know your organization's politics, your legal obligations or how your employees will react. Treat its output as a draft that HR, communications and the change lead each review.
What is the most common mistake in change communication?
Announcing to everyone at once without preparing managers. Employees go to their manager first with questions. If managers have no answers and no one to ask, trust drops quickly. Build the manager kit and brief managers before the announcement.
Useful for
How we source, write, and correct our articles. Editorial standards
Related articles

Vendor Evaluation Template: A Software Scorecard You Can Copy

How to Measure AI ROI at Work (With a Calculator)

How to Write a Professional Email with AI (Prompts That Work)
