Change Communication Plan Template
Steffen Rosenögger, Founder of CapmePublished November 8, 2026
Communication plan template for change management communication: one row per message, its sender, live or recorded, and where people can ask questions.

In short
- The template has one row per message: audience, sender, live or recorded, deadline and where questions go.
- Senior management explains the reasons. The direct manager explains what changes for each person.
- No recording goes out until the plan says when and where people can ask questions.
Anyone filling in a communication plan template for a change should sort the messages first and pick the channels second. Anything that only has to arrive is recorded and watched by a date. Anything that needs dialogue stays live, and for every message the plan names where the conversation takes place. The people reading it are tired: 85% of communication leads in Germany, Austria and Switzerland see acute change fatigue, yet 67% still plan to step up internal communication, according to the Communications Heatmap 2025 by FTI Consulting and Quadriga Hochschule Berlin (19 February 2026, 600 respondents).
Change management communication is everything an organisation says during a change, to whom, from whom, through which channel, and how people can answer. "Transparency does not mean pouring out every detail," says Susanne Arndt of FTI. "Anyone who confuses communication with a flood of information risks employees simply switching off" (both translated). Change fatigue: warning signs and causes shows how to measure the load per person.
Which change messages can be recorded?
The test question for every change message: can the recipient still change anything about it, or do they only need to know it? Why something is changing, what has been decided, when it happens and what changes for their group: all of that only needs to be known, so it can be recorded. A message needs a conversation when people will object to it, negotiate over it or react with fear and anger. For recurring meetings, the guide Which meetings can go async? asks the same question.
With a recording, everyone hears the same wording, the late shift and the part-timers included, and anyone who did not follow the reasoning watches it again.
What does a communication plan template look like?
A communication plan template is a table with one row per message and six columns: message, audience, sender, live or recorded, by when, and where the dialogue happens. A made-up example: a machinery manufacturer with 600 employees is introducing a new ERP system, with go-live in five months. 260 office staff will use it every day; 340 in production will enter their bookings at a terminal.
| Message | Audience | Sender | Live or recorded | By when | Where the dialogue happens |
|---|---|---|---|---|---|
| Informing the works council about the ERP, works agreement (Betriebsvereinbarung) | Works council | Managing director, head of HR | Live | Before any other row | Meeting with the works council |
| Why the ERP is coming, what is settled | All managers, then the 260 office staff | Managing director | Live for managers, then recorded | Week 1, watched by Friday | Q&A with the managing director, Tuesday of week 2 |
| Timeline, training, who the key users are | 260 office staff | Project lead | Recorded | Week 2, watched by Friday | Project channel, office hours on Thursdays |
| What changes in the division | The division's office staff | Division head | Recorded | Week 2, watched by week 3 | Department meeting in week 3, 30 minutes of questions only |
| What changes for you personally | Each employee | Direct manager | Live, one to one | By the end of week 4 | The conversation itself |
| Production: new bookings at the terminal | 340 in production | Foreman (Meister) | Live in the shift briefing | Week 3, every shift | Shift briefing and key users on the line |
| Bad news, such as a postponed go-live | Managers first, then all 600 | Managing director | Live for managers, recorded the same day | Within 24 hours | Team meetings the next day |
| Message | Audience | Sender | Live or recorded | By when | Where the dialogue happens |
|---|---|---|---|---|---|
| Informing the works council about [change] | Works council | [Management, HR] | Live | Before any other row | [Meeting: date] |
| Why [change] is coming, what is settled | [Managers first, then everyone] | Senior management | [Live / recorded] | [Watched by] | [Q&A: date, room, person] |
| What changes in [area] | [Staff in area, head count] | [Head of area] | [Live / recorded] | [Watched by] | [Team meeting: date] |
| What changes for you personally | Each employee | Direct manager | Live, one to one | [Date] | The conversation itself |
| [Next message] | [Group, head count] | [Reasons: senior management; consequences: direct manager] | [Live / recorded] | [By when] | [Date, place, person] |
The template fits whichever model the change follows; change management models: ADKAR, Kotter, Lewin compares the three.
The communication cascade guide explains why employees want the reasons from senior management and the consequences from their own manager, and how to brief managers across several levels. If a layer goes, so does a sender: see the hourglass organisation.
Managers hear bad news live first, so none of them learns it from their own team. Production gets everything through the foreman, because hardly anyone on the line has time for a video.
The same table works for other changes, with one extra row. For communicating employee survey results, that row is "results per team". AI literacy training under Art. 4 needs "proof of training", and a four-day week needs "which standing meetings go". For a team of 15 in one office the plan is overkill: one live round reaches everyone, and the questions come straight away.
In Capme, the recorded part becomes one meeting per division
Capme is a meeting platform that replaces status meetings with recordings, and the videos are stored in the EU. Rows 2 to 4 of the table become one meeting per division, each with an agenda, speakers, a deadline and an audience list:
- The project lead organises three meetings: Sales (140 people), Purchasing and Logistics (70), Finance and Administration (50). An audience list holds up to 200 addresses.
- Each agenda has three topics, each with a speaker and a target length: the managing director on "Why we are changing ERP" (5 minutes), the project lead on "Timeline and training" (5), the division head on "What changes for us" (4). The description says "Please watch by Friday" and gives the time and place of the Q&A.
- The speakers' deadline is Wednesday. Each speaker gets an email with a link to their topic and records in the browser. The managing director records once and attaches the same video to his topic in the other two meetings.
- The project lead sees which videos are in and presses "Remind everyone" if needed. The 260 viewers get an email only when she publishes; in the publish dialog she switches on "Remind attendees to watch", after 3 days. Viewers watch the three topics on one page in agenda order.
- On Friday the project lead sees "watched", "1/3 watched", "opened" or "not opened" for each person. If an admin sets the workspace to "Totals only", she sees totals without names (what admins see).
Capme has no comments, Q&A feature, transcripts or AI summaries, so questions go to the Q&A session and department meeting in the last column. In the example Capme does nothing for the 340 people in production, who keep hearing it from the foreman.
You pay per speaker; viewers are free. On Team, the five speakers in the example cost 5 x €12 = €60 net per month. For larger companies that want their own storage and single sign-on there is Business, from 10 speakers.
Record the reasons once, show them in every division
The managing director records once, and every division watches by Friday. Try it for 14 days, no credit card.
Which change communication must stay live?
Anything people will want to answer on the spot stays live, and in a German company that starts with the works meeting.
- The works meeting (Betriebsversammlung). Under § 43 BetrVG the works council calls one every calendar quarter, during working hours (§ 44), and since April 2023 in person again (the video rule in § 129 BetrVG has lapsed). There the workforce questions senior management.
- Personal news: a new role, a transfer, a job that is going. For the order and the legal framework, see Communicating job cuts.
- Negotiations with the works council, because tone and timing count there too.
- The Q&A after a contested announcement. The all-hands as a recording with a live Q&A shows how to split a company-wide address.
- The first hour after bad news, at least for the managers who have to pass it on.
As of November 2026; not legal advice.
Week one: the change team books the Q&A slots before the first message goes out
- Copy the template and collect every message for the next four weeks, one row per message.
- Ask of each row: can the recipient still change anything? Yes means live.
- Fill in the sender: reasons go to senior management, personal consequences to the direct manager.
- For every recorded row, book a slot for questions, with a room and a time.
- Inform the works council before the first message and settle whether watch progress is shown per person or only as totals.
- Brief the managers live before their team sees anything.
- For each row, set the day on which someone checks whether the message has landed, and who follows up.
Frequently asked questions
- Does the works council have to approve the communication plan?
- Not the plan itself. It can have co-determination rights over the change, such as an ERP that processes user data, and over tools that can evaluate behaviour, per-person watch progress included (Introducing a video tool: what the works council co-determines). Involve it before the first message.
- How do I reach employees without a company email address?
- Through their manager, live in the shift or team briefing. Senior management's recording can be played there for everyone together, followed by questions. A notice on the board gives the date and place of the Q&A.
- How many messages can a workforce take per week?
- There is no reliable figure. Our rule of thumb: at most one new mandatory message per group per week, with everything else bundled. If several changes run in parallel, they belong in one shared plan.