Change Communications Plan
A phased intranet site for coordinating change messages before launch, during launch week, and through reinforcement, with owners, timing, channels, approvals, and feedback routes.
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: Enterprise Technology · Healthcare Operations · Higher Education · Financial Services · Public Sector
Overview
The Change Communications Plan is a site template for turning a change initiative into an executable communication sequence. The example is built around the Northstar Service Desk rollout and organizes work across pre-launch readiness, launch execution, reinforcement and feedback, and measurement and governance. The home page gives change leaders, communicators, managers, and project partners a single orientation point before they move into phase-specific pages.
Use this template when several audiences need different messages across several channels and the rollout depends on coordinated timing. It helps teams record who needs to know what, what action is expected, which channel carries the message, who owns publication, which approvals are required, and where questions or incidents go next. The structure supports progressive disclosure: quick links orient readers first, while deeper pages hold message calendars, manager materials, launch checkpoints, feedback routes, and decision ownership.
Do not use it as a substitute for a project plan, detailed editorial calendar, incident-management system, or regulatory approval record. Keep those systems as the source of truth when they already exist, and link to them from this site. This template is most useful as the communication hub-and-spoke layer that makes the operational spine visible: accountable owners, cadence, escalation path, audience definitions, and the current employee action.
Standards & compliance context
- Route messages affecting privacy, security, employment conditions, accessibility, or regulated operations through the organization's required control owners before publication.
- Restrict audience-specific pages and linked documents according to least-privilege access, especially when feedback includes personal, health, employment, or incident information.
- Provide an accessible page experience by using meaningful headings, descriptive link text, keyboard-operable controls, sufficient contrast, and alternative text in line with WCAG 2.1 AA expectations.
- Keep an approved record of material communications and decisions in the designated system of record when retention, audit, or records-management requirements apply.
- Do not use employee feedback collected through this site for a new purpose without checking the applicable privacy notice, consent, and data-handling requirements.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Clone the site, replace the Northstar example with your initiative, and confirm the target audiences, change milestone, launch date, and accountable change lead.
- Populate the pre-launch readiness page with audience impacts, manager talking points, message drafts, channel owners, approval gates, and links to training or support content.
- Assign each launch communication to a named role, verify its publication channel and timing, and rehearse the same-day escalation route before launch week.
- Run launch communications according to the sequence, recording publication status, employee questions, support demand, and any message that requires correction.
- Schedule reinforcement messages such as tips, office hours, success stories, and targeted reminders based on observed adoption barriers and audience feedback.
- Review reach, understanding, open issues, and decisions on the measurement and governance page, then archive or retire stale launch content while keeping the current support route visible.
Best practices
- Write every message around one observable employee action, such as opening the new Service Desk portal, completing training, or using the published support route.
- Give each communication one accountable owner and one backup role, rather than assigning ownership to a department name alone.
- Use the pre-launch page as an approval gate by recording audience impact, approver, due date, and publication status before a message enters the launch sequence.
- Separate manager enablement from employee announcements so managers receive talking points, expected questions, escalation guidance, and links they can use in team conversations.
- Publish launch timing in the audience's working context, including time zone, channel, dependencies, and what happens if the preceding message or system event is delayed.
- Photograph or record evidence of issues only through approved systems and link the resulting support or incident record instead of copying sensitive details into the communications site.
- Use reinforcement content to address real questions and behavior gaps, not to repeat the original announcement without a new employee action.
- Review every page after the change stabilizes and remove obsolete dates, superseded instructions, and duplicate links so the site does not become a stale-content trap.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What scope of change does this communications plan cover?
This template is designed for a defined change initiative, such as the Northstar Service Desk rollout shown in the example. It covers audience readiness, launch execution, post-launch reinforcement, measurement, governance, and feedback handling. For a portfolio with several unrelated changes, create a site for each major initiative and connect them through a department or company hub.
Who should own and maintain the site?
A change lead or communications lead should own the site and keep the plan current. Channel owners, project partners, managers, and support teams contribute dates, message drafts, approval status, and escalation updates. Assign one accountable owner for every important communication so gaps do not remain hidden between teams.
How often should the plan be reviewed?
Review it weekly during preparation, daily during launch week, and at each scheduled reinforcement checkpoint after launch. Update timing when a dependency, release date, or audience risk changes. Keep the measurement and governance page active after launch until open issues, unanswered questions, and stale messages have owners.
Can this template support regulated or high-impact changes?
It can provide the communication structure, but it does not replace legal, privacy, security, labor, accessibility, or regulatory review. Add the required approval gates, evidence links, retention rules, and audience restrictions for your organization. Have the relevant control owner approve messages before publication when the change affects regulated processes or sensitive data.
What is a common mistake when using a change communications site?
A frequent mistake is listing channels and dates without defining the employee action, message owner, approval status, or route for questions. Another is treating launch as the finish line and omitting reinforcement. Write each message around what the audience must understand or do, then connect it to a support route and a measurable follow-up.
How much can I customize without losing the template's structure?
You can replace the Northstar example with your initiative, audiences, milestones, channels, owners, and support routes while retaining the phased navigation. Add or remove message rows and audience-specific pages as needed. Keep the hub-and-spoke pattern: a landing page for orientation, phase pages for execution, and a governance page for decisions and measurement.
Can this plan connect to other workplace tools?
Yes. Link to approved message drafts, project schedules, manager toolkits, training pages, service portals, survey forms, analytics views, and issue trackers. Use descriptive link labels and verify permissions before publication. Where an external tool is the system of record, state its owner and update cadence on the relevant page.
How should we roll this out to managers and communicators?
Start by cloning the site for one initiative and populate the audience, milestone, owner, channel, and feedback fields. Walk message owners through the pre-launch readiness page, then rehearse the launch sequence and escalation path. After launch, review feedback and reach together, remove obsolete instructions, and publish a short decision log for unresolved items.
How is this better than an ad hoc spreadsheet or message thread?
A spreadsheet can track dates, but it often separates timing from audience guidance, approvals, employee actions, and feedback routes. This site gives contributors a navigable working plan with pages for preparation, launch, reinforcement, and governance. It also gives employees and managers a clearer place to find the current message, next step, and support path.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
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.
