Change Communications Plan
A five-page change communications plan for a fictional shared project intake rollout, with a phased playbook, sample messages, schedule, feedback routing, and role approvals. Clone it to coordinate what each audience needs to know and do.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Professional services · Information technology · Financial services · Healthcare administration
Overview
The Change Communications Plan is a fictional five-page intranet site built around Northstar Services’ rollout of a shared project intake process. Its overview page explains the change in plain language and provides sample launch copy. Companion pages organize the phase playbook, planned messages and timing, feedback routing, and role approvals. Together, they give employees and team leads a starting point for understanding what is changing, where to find the next step, and how questions reach the initiative team.
Use this template when a process or service change needs more than one announcement: for example, when different audiences need different messages, communications must be timed around a launch, or feedback and approvals need clear owners. The hub-and-spoke navigation keeps the overview brief while directing readers to the planning details they need. Before rollout, confirm the process description, actual launch date, approved intake link, channels, owners, and escalation route. Treat the Northstar copy as illustrative sample content, not a verified description of your organization.
This is not a substitute for a change impact assessment, project schedule, training materials, emergency communications protocol, or legal review. It does not send messages or capture feedback automatically; connect the pages to approved tools if you need those functions. Do not publish the example unchanged or rely on a calendar entry without checking its audience, channel, timing, and approver. If a change has distinct audiences or significant operational risk, create audience-specific guidance and obtain the required internal reviews before sending.
Standards & compliance context
- Treat the sample copy as a planning example and obtain internal legal, privacy, records, or regulatory review when the change affects obligations in those areas.
- Use only approved links and communication channels, and confirm their access settings match the intended employee audience.
- Keep an appropriate record of message approvals and published versions if your organization’s records-retention policy requires it.
- For audience-restricted pages, follow WCAG 2.1 AA accessibility practices, including meaningful link text, readable structure, and accessible alternatives for visual information.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Change Communications Hub
Start here for the change summary and links to the planning pages employees and rollout owners need next.
-
Make project requests easier to start and route
A rollout communication hub for Northstar Services employees, team leads, and the initiative team. Fictional Northstar Services example: this plan introduces one shared intake process for new project requests.
-
The change in one minute
What employees need to know Northstar Services is introducing a shared project intake process so requests can be submitted consistently, reviewed, and routed to the appropriate next step. Sample launch message Starting Monday, submit new project requests through the shared intake process. Include the outcome you need and any timing constraints you already know. The intake team will review each request and route it to the appropriate next step. Before sending, confirm the actual launch date and link to the approved intake route.
-
Go to a planning page
Use the page that answers your next question. Message Calendar Planned messages, audiences, channels, owners, and timing. Phase Playbook What to communicate before, during, and after launch. Feedback and Escalation Where questions and process friction are routed. Roles and Approvals Who drafts, reviews, approves, and publishes messages.
Message Calendar
Check the planned audience, channel, owner, and timing for each communication before it is sent.
-
Planned messages, in sequence
An authored rollout schedule This is the campaign team's planning schedule, not a personal or live calendar. The relative timing below is a fictional example; confirm dates, channels, and owners before scheduling.
-
Sample message schedule
Relative timing keeps the example useful until launch dates are confirmed. Phase Timing Audience Channel Owner role Message focus Before Two weeks before launch Team leads Manager briefing Rollout owner Explain the change, key dates, and where to direct questions. One week before launch All employees Company news post Communications partner Introduce the shared intake process and show the approved route. During Launch day Launch announcement State what changes today and what information to include in a request. After One week after launch Employees and team leads Team meeting talking points Team lead Address recurring questions and reinforce the intake route. Four weeks after launch Follow-up news post Share themes heard, clarify common friction, and restate the next step.
-
Sequence messages so managers are ready
Brief managers first Send the manager briefing before the employee announcement. That gives team leads time to understand the change and direct basic questions to the right route before employees receive the launch message. Keep one accountable owner per message Keep one accountable owner beside each scheduled message and record the approved channel and publication date in the working plan.
Phase Playbook
Follow the rollout phases to coordinate preparation, launch, and follow-up communications in the right sequence.
-
Communicate before, during, and after the change
Build awareness before launch, make the first action clear on launch day, and use follow-up messages to reinforce the process and address what employees report.
-
A sample three-phase sequence
Before — prepare Brief team leads, publish the employee announcement, and explain where to submit a new project request. Two weeks to one day before launch During — launch State that the shared process is now the route for new requests. Show the approved intake link and the details requesters should include. Launch day After — reinforce Share answers to recurring questions, clarify points of confusion, and remind employees how to submit a request. One to four weeks after launch
-
Change the message as the rollout progresses
The launch message explains the new action; the reinforcement message responds to what people need after trying it. Launch message Starting Monday, use the shared intake process for new project requests. Include the outcome you need and any timing constraints you know. Say what changes and when. Name the first action. Point to the confirmed intake route. Reinforcement message If you are starting a new project request, use the shared intake process. Include the outcome and known timing constraints so the intake team can route it.
-
Make the action specific
Vague: “Please follow the new process.” Clear: “Use the shared intake process for new project requests. Include the outcome you need and any timing constraints you know.” The clearer version identifies who should act, when the process applies, and what information to provide.
Feedback and Escalation
-
Turn a question into useful feedback
Describe the task and the point of friction Useful feedback says what the person was trying to do, where they got stuck, and what they expected to happen. For example: “I was submitting a request for a new reporting project. I was unsure whether the outcome field should describe the report or the decision it supports.” Avoid including confidential project details in a broad discussion channel.
-
Sample feedback handoff
A practical route for collecting and sorting themes Share the issue An employee raises a question or describes a point of friction with their team lead. Group recurring themes The team lead records the issue in the rollout feedback summary and groups it with similar questions. Route to the right owner The rollout owner sends process questions to the intake process owner and message gaps to the communications partner. Close the loop The relevant owner updates the guidance or prepares a clarification for the next planned communication.
-
Route feedback by what needs attention
Feedback type First recipient Routing owner Next action Unsure how to submit a request Team lead Rollout owner Route the process question to the intake process owner. Unclear wording or missing launch detail Route the message gap to the communications partner for clarification. Repeated difficulty with a process step Group similar examples and ask the intake process owner to review the step. Request does not appear to reach the right next step Record the point where routing became unclear and review it with the intake process owner.
Roles and Approvals
-
Give every message one accountable owner
Review for process accuracy, clear language, and release readiness In this fictional rollout, each message has one accountable owner who coordinates the draft and publication. The process owner checks that instructions match the shared intake process; the communications partner checks that the message is clear for its audience; the rollout owner gives final approval for scheduled campaign messages.
-
Sample role and approval matrix
Role names describe responsibilities, not named individuals. Role Contribution Review or approval responsibility Rollout owner Maintains the campaign plan and coordinates timing across phases. Accountable owner; gives final approval for campaign messages. Communications partner Drafts or edits audience-specific messages and confirms the channel fits the message. Reviews clarity, audience fit, and consistency across communications. Intake process owner Confirms the described request steps and information required. Reviews process accuracy before a message is approved. Team lead Shares team questions and recurring feedback with the rollout owner. Reviews whether manager-facing guidance is usable; does not approve every company-wide message.
-
Sample approval handoff
Draft The accountable message owner prepares the audience, purpose, channel, timing, and draft wording. Check process details The intake process owner confirms that the described route and request details match the intended process. Review communication The communications partner checks that the action, audience, and timing are easy to understand. Approve and schedule The rollout owner approves the message and confirms its scheduled channel and publication timing.
How to use this template
- Clone the site and replace Northstar Services and the sample intake process with the name and plain-language description of your approved change.
- Set the confirmed launch date, approved destination links, audience groups, communication channels, and support route on the relevant planning pages.
- Assign a communications owner, process-content approver, message senders, feedback owner, and decision-maker for escalations.
- Review the phase playbook and message calendar with audience representatives, then revise each message so it states what changes, when it changes, and what the reader must do.
- Before each communication, verify its audience, channel, timing, destination link, and approval; publish or send it through your approved tools.
- After launch, review incoming questions and feedback with the named owners, update inaccurate or stale pages, and communicate any approved changes.
Best practices
- Keep the overview focused on the change, effective date, required employee action, and route to more detail.
- Give every calendar entry a named owner, intended audience, channel, send timing, and approval status.
- Use the phase playbook to distinguish preparation, launch, and follow-up communications rather than repeating the same announcement.
- Verify the intake link and support route from an employee’s perspective before distributing a message.
- Assign feedback to a role or team and state how urgent or unresolved questions are escalated.
- Write sample messages in direct language and identify the action employees should take after reading.
- Remove example dates, roles, and process details that do not apply instead of leaving fictional instructions in the live site.
- Review all pages whenever the launch plan changes, and show readers which page or contact is the current source of truth.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does the Change Communications Plan template include?
The fictional Northstar Services site organizes a shared project intake rollout across five pages. It includes an overview and sample launch copy, a phase playbook, a message calendar, feedback routing, and role approvals. Replace the example process and details with your own before publishing.
Is this template suitable for every type of organizational change?
It is designed for a change that requires coordinated, phased employee communications, especially a new process or service with defined audiences and actions. The shared intake example is a starting point, not a ready-made plan for a merger, emergency, or policy change. For those situations, adapt the pages to the change's specific risks, decision owners, and required communications.
Who should own and run the communication plan?
Assign an initiative communications owner to maintain the calendar, message drafts, and page links. Process or project leads should verify what is changing and approve operational instructions, while team leads can relay relevant messages and gather questions. Name a decision-maker for unresolved or sensitive issues before launch.
How often should the plan and message calendar be reviewed?
Review the plan whenever a launch date, process step, audience, or owner changes. During rollout, check upcoming messages at a regular cadence—weekly is a practical starting point—and confirm each is still accurate before it is sent. After launch, keep only follow-up communications that answer active questions or explain a real next step.
Does using this template make a change compliant with regulations?
No. It is a communications planning aid, not legal, privacy, or regulatory approval. Have the appropriate internal owner review messages that affect regulated work, employee rights, personal data, records retention, or contractual obligations. Add required notices and approval steps for your organization and jurisdiction.
What is the most common rollout mistake this template helps prevent?
A frequent pitfall is sending a launch announcement before the actual launch date, approved intake route, and support path are confirmed. The sample message explicitly calls for checking the date and link before sending. Also avoid leaving feedback without a named owner or publishing a calendar entry with no audience or channel.
How should we customize the fictional Northstar Services example?
Replace Northstar Services, the shared intake process, sample dates, links, audience descriptions, and role assignments with approved details for your change. Keep the phase sequence only if it matches your rollout; remove steps that do not apply rather than leaving misleading example content. Test every destination link and have process owners review the final messages.
Can this plan connect to our messaging, calendar, or feedback tools?
The template provides planning content and links; it does not by itself send messages, sync calendars, or collect feedback. Link to your organization’s approved communication calendar, intake route, and feedback channel, and confirm access for each intended audience. If you use live components or integrations, configure their data sources and permissions separately.
Why use a plan like this instead of coordinating messages ad hoc?
A shared plan keeps audiences, timing, channels, message owners, approvals, and feedback routes visible in one navigable site. Ad-hoc coordination can leave teams unsure which version is current or where questions should go. The template helps establish a common reference, but it still needs an assigned owner and regular updates.
Related templates
Go deeper on the topic
-
Asynchronous communication is any exchange where the sender and receiver are not in the same moment — written messages, recorded video, shared docs, threaded...
-
Change management is the structured discipline for moving people, processes, and organizations through transitions — new systems, new structures, new...
-
Collaboration is the coordinated work of two or more people toward a shared outcome — arguing, deciding, producing, and shipping. It is not the same as...
-
Communication is the movement of information from one person or group to another — announcements, updates, instructions, questions, acknowledgements....
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Change Communications Plan ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.