FirstHR

Communication Plan Template and Worked Example

Six free communication plan templates: the audience, message, channel, owner, and timing grid with a worked example, plus a change management plan.

Nick Anisimov

Nick Anisimov

FirstHR Founder

Core HR
16 min

Communication Plan Templates

Six communication plan templates for small business: the audience, message, channel, owner, and timing grid with a fully worked example, a change management plan, a one page version, a message brief, a recurring calendar, and an incident plan. Editable Excel and Word files, no email form.

I once changed how a team logged their hours in a single message, sent to everybody at once, on a Friday afternoon. By Tuesday I had answered the same four questions eleven times. Two managers had heard about it from their own staff before they heard it from me. One person had not seen it at all, because he does not read email during a shift.

A communication plan would have prevented all three. It is one grid: who needs to hear this, what they need to hear, on which channel, from whom, and when. That is the whole idea, and for a real change at a small company it takes about an hour to fill in.

There are six templates below rather than one, because a single announcement, a change that lands over weeks, a recurring rhythm, and an incident are different problems. Two are Excel workbooks and four are editable Word documents. Free, with no email form in the way.

TL;DR
A communication plan is a grid that gives every audience a message, a channel, an owner, and a date. Fill in five columns per row and you have one. Six free templates below: the grid with a worked example, a change management plan, a one page version, a message brief, a calendar, and an incident plan. No signup.

What a Communication Plan Is

A communication plan is a grid that decides in advance who hears a piece of news, what they hear, on which channel, from whom, and when. One row per audience. Everything else people attach to the term is either the message itself or the rules that surround it.

It is worth separating from the two documents it gets confused with. A communication policy is a standing rule set covering channels, tone, and confidentiality, signed once and reviewed yearly. A plan is for one specific message and it closes when that message has landed.

Why the Default Approach Underperforms
Only 13 percent of employees strongly agree that the leadership of their organization communicates effectively with the rest of the organization (Gallup). At a small company that number is not about polish or production values. It is about a message going out once, on one channel, to a group that reads three different ones.

A Filled-In Communication Plan Example

Here is what a finished plan looks like with real content in it. This is a 24-person services business moving from paper timesheets to a scheduling app over four weeks, and it is the same worked example that ships inside the first template.

AudienceWhat they hearChannelOwnerWhen
Shift managers (4)What is changing, why now, and the five questions their team will ask themMeeting, then a written summaryOwnerTwo weeks before launch
Hourly staff (16)Clock in on the app from Monday. Paper timesheets stop. Pay dates do not changeShift huddle plus a printed sheet by the clockShift managerOne week before, again on day one
Back office (3)Where approved hours come from now, and the new Tuesday payroll cutoffEmail with the new cutoff timesOwnerTwo weeks before launch
New hires starting during rolloutOnly the new process, with no history and no comparisonOnboarding checklist itemShift managerDay one, ongoing
Outside bookkeeperThe new export format and the unchanged Tuesday deadlineEmail with a sample export attachedOwnerThree weeks before launch
EveryoneWhat broke in week one, what is fixed, what is still changingFive lines on the team channelOwnerEnd of week one, then week four

Two things in that grid do most of the work. The managers hear it a week before their team, so they are answering questions rather than reacting to them. And the last row exists at all, which is the row that separates a plan from an announcement.

The Five Columns Every Plan Needs

Audience, message, channel, owner, and timing. A plan missing any one of the five leaks in a predictable way, and the one small businesses drop most often is the owner column, because at twelve people it feels obvious who is sending things.

1
Audience
Not one row for the whole company. Split people by how much this changes their day, because the group whose job changes needs a conversation and the group who just needs to know needs a sentence.
2
Message
What this specific group needs to hear, written from their side. The same announcement reads differently to the person doing the new task and the person who only has to stop asking for the old one.
3
Channel
Where this group actually reads things. Frontline staff and desk staff do not share a channel, and choosing the wrong one is the single most common reason a message goes out and lands nowhere.
4
Owner
One named person per row, and it is not always you. A manager delivering the message to their own team lands better than an owner broadcasting past them, as long as the manager has the answers first.
5
When and how often
A date, not a phase. Then the repeat, because a message sent once has been heard by roughly the people who were paying attention that morning. Two or three sendings is normal for anything that changes behavior.

The Column Most Templates Leave Out

Add a sixth: how people respond. Name a person rather than a shared inbox, say when the route closes, and then report back publicly on what you heard and what you changed. A feedback route that swallows everything gets used once.

This is also the column that separates announcing a change from managing one. If nothing anybody says can alter any part of the plan, then say so plainly rather than staging a consultation, because a team can tell the difference and remembers which one they were given.

Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

Which Template Should You Use?

Start with the grid. Move up to the change plan when the news lands over weeks rather than in one message, and add the calendar when the problem is rhythm rather than a specific announcement.

Communication Plan Grid
The default, spreadsheet
The core grid: audience, what they need to hear, channel, owner, when, frequency, and how they reply. A second tab holds a fully worked example for a system rollout, and a third tells you which channel actually reaches which people.
Change Communication Plan
For one specific change
The longer document for a change that lands over weeks: the message in one paragraph, audience tiers, the sequence, what each group hears, the questions you will be asked with answers written down, a feedback route, and a follow-up schedule.
One Page Plan
A single announcement
The short version for a small team and one piece of news. The paragraph, a six-row grid, who hears it first, three prepared answers, and a pre-send checklist. If it will not fit on the page, you want the change plan instead.
Announcement Message Brief
The thing you actually send
The plan says who hears what. This is the message itself: subject line, the whole news in the first sentence, what is changing, why, what it means for you, what to do, what is not changing, and who to ask. Includes a filled-in example.
Communication Calendar
The recurring rhythm
For the communication that is not an announcement: the daily huddle, the weekly update, the monthly numbers, the quarterly direction. One tab for the cadence with named owners, one for planning twelve months of known dates.
Incident and Crisis Plan
Decisions made in advance
For the day you have no time to write: triggers, who decides, who speaks, backup channels when the normal ones are down, a first-message structure you fill in with facts, the order people are told, and what never goes in writing.
If You Are Announcing Something This Week
Open the one page plan and the message brief together, in that order. Fill the plan first, because deciding who hears what and when is the part that takes real thinking, then use the brief to write the actual words for each audience. It takes about forty minutes for a normal announcement. If, while filling in the grid, you find yourself needing more than six rows or more than two send dates, stop and switch to the change communication plan instead: you are running a change, and the short template will quietly drop the follow-up.

6 Free Communication Plan Templates

Download all six together as a zip file, or take the one you need. Two are Excel workbooks and four are editable Word documents. Fill in the brackets, delete the rows that do not apply, and change anything that does not match how your business actually runs.

Download All 6 Communication Plan Templates
The plan grid with a worked example and the recurring calendar as XLSX, plus the change plan, one page plan, message brief, and incident plan as DOCX, in a single zip.

Template 1: Communication Plan Grid (Spreadsheet)

The default. Audience, what they need to hear, channel, owner, when, frequency, and how they reply, with a status column. A second tab holds the fully worked rollout example above, and a third is a channel guide covering who each channel actually reaches.

Communication Plan Grid
ABCDEFGHI
1AudienceWhat they need to hearChannelOwnerWhenFrequencyHow they respondStatusNotes
2SAMPLE Shift managersWhat is changing, why now, and answers to the questions their team will ask them firstMeeting, then a written summaryOwnerTwo weeks beforeOnce, then weeklyDirect reply to ownerSentThey must not hear it from their own staff
3SAMPLE Hourly staffWhat they do differently on Monday, and what stays the sameShift huddle plus a printed one-pagerShift managerOne week beforeTwiceAsk at the huddleDraftHalf this group does not read email on shift
4
5
6
7
8
9
10
11
12RuleEvery row needs a named owner and a date. A row owned by everyone is owned by nobody

Template 2: Change Management Communication Plan

For a change that lands over weeks. The message in one paragraph, audience tiers, the sequence, what each group hears, written answers to the questions people will ask, a feedback route with a closing date, and a follow-up schedule running to week eight.

Change Management Communication Plan
CHANGE COMMUNICATION PLAN
[Company Name]
The change:
Type: [system / process / policy / structure / location / hours / ownership]
Decision made by: Decided on: [MM/DD/YYYY]
Announced on: [MM/DD/YYYY] Takes effect: [MM/DD/YYYY]
Plan owner:
1. THE MESSAGE, IN ONE PARAGRAPH

Write this before you write anything else. If it takes more than one paragraph,
you do not understand the change well enough to announce it yet.
What is changing: [ ]
Why, in a sentence that would survive being repeated back to you: [ ]
When it takes effect: [ ]
What people have to do differently: [ ]
What is not changing: [ ]
The last line matters more than it looks. In the absence of a boundary, people
assume the change is bigger than it is, and the rumor is always worse than the
announcement.
2. WHO IS AFFECTED, AND HOW MUCH

Tier 1, their job changes materially: [ ]
Tier 2, their job changes slightly: [ ]
Tier 3, they need to know but nothing changes for them: [ ]
Outside the company, they will notice: [customers / vendors / contractors]
Anyone in tier 1 hears it in a conversation, not in a broadcast.
3. SEQUENCE

Order | Who | Format | Date and time
1 | [tier 1, individually] | [in person] | [MM/DD, time]
2 | [managers and team leads] | [meeting] | [MM/DD, time]
3 | [the wider team] | [ ] | [MM/DD, time]
4 | [customers, vendors, partners] | [ ] | [MM/DD]
5 | [everyone again, the follow-up] | [ ] | [MM/DD]
The gap between step 2 and step 3 is short. Managers who find out an hour before
their team can prepare. Managers who find out a week before start leaking.
4. WHAT EACH AUDIENCE HEARS

Audience: [ ]
The message: [ ]
What they will care about that you might not: [ ]
Channel: [ ] Owner: [ ] Date: [MM/DD]
Audience: [ ]
The message: [ ]
What they will care about that you might not: [ ]
Channel: [ ] Owner: [ ] Date: [MM/DD]
Audience: [ ]
The message: [ ]
What they will care about that you might not: [ ]
Channel: [ ] Owner: [ ] Date: [MM/DD]
5. THE QUESTIONS YOU WILL BE ASKED

Write the answers down and give them to whoever is delivering the message.
Include the uncomfortable ones. A manager who improvises an answer to the pay
question creates a second problem you will spend a month undoing.
Q: Does this affect my pay or hours? A: [ ]
Q: Is anyone losing their job? A: [ ]
Q: Why now? A: [ ]
Q: Who decided this? A: [ ]
Q: What happens if it does not work? A: [ ]
Q: [ ] A: [ ]
Q: [ ] A: [ ]
Questions with no answer yet: say that out loud, name a date when there will be
an answer, and then meet it. "We do not know yet, and I will tell you by the
15th" holds. Silence does not.
6. HOW PEOPLE RESPOND

Feedback route: [named person / open session / short form / manager one to one]
Open until: [MM/DD]
Who reads it: [ ]
What we do with it: [ ]
Announced back to the team on [MM/DD]: what we heard, what we changed, and what
we are not changing and why.
7. FOLLOW-UP SCHEDULE

Day 1: [the announcement lands, managers available]
Day 2-5: [questions answered, corrections issued fast]
Week 2: [what is working, what is not]
Week 4: [confirm the change has stuck, or say plainly that it has not]
Week 8: [close the plan, or restart it]
Plan closed on: [MM/DD] by: [ ]
8. HOW YOU WILL KNOW IT LANDED

[ ] Managers can explain it without reading from the message
[ ] The same question is not still arriving in week three
[ ] The behavior actually changed, measured by: [ ]
[ ] Nobody found out from a customer

NOTE: This is a sample template for general information only and is not legal
advice. Some announcements carry legally fixed notice periods and disclosure
requirements that this plan does not decide for you. Confirm what applies to your
business and your state before you set the dates.

Template 3: One Page Communication Plan

For a small team and a single announcement. The paragraph, a six-row grid, the order people hear it in, three prepared answers, and a pre-send checklist. If it will not fit on the page, that is the signal to use template 2 instead.

One Page Communication Plan
ONE PAGE COMMUNICATION PLAN
[Company Name]
What this is about:
Owner: Date: [MM/DD/YYYY]
For a small team and a single announcement. If it does not fit on this page, you
are running a change, not an announcement, and you want the longer template.
THE ONE PARAGRAPH

[What is changing, why, when, what people do differently, and what stays the
same. Five sentences at most. Write it before you fill in the grid below.]
THE GRID

Audience | What they hear | Channel | Owner | When
[ ] | [ ] | [ ] | [ ] | [MM/DD]
[ ] | [ ] | [ ] | [ ] | [MM/DD]
[ ] | [ ] | [ ] | [ ] | [MM/DD]
[ ] | [ ] | [ ] | [ ] | [MM/DD]
[ ] | [ ] | [ ] | [ ] | [MM/DD]
[ ] | [ ] | [ ] | [ ] | [MM/DD]
WHO HEARS IT FIRST

First, in person: [ ]
Then: [ ]
Then everyone: [MM/DD, time]
Outside the company: [ ] on [MM/DD]
THE THREE QUESTIONS

Q: [ ] A: [ ]
Q: [ ] A: [ ]
Q: [ ] A: [ ]
BEFORE YOU SEND

[ ] Every row has a name and a date next to it
[ ] Nobody affected personally is hearing it in a group message
[ ] Managers have the answers before their team has the questions
[ ] There is one channel for the message and one place it lives afterward
[ ] Someone is named for people to reply to
[ ] The follow-up is already on the calendar, not just intended
FOLLOW-UP

Follow-up message due: [MM/DD] Owner: [ ]
Plan closed on: [MM/DD]

NOTE: This is a sample template for general information only and is not legal
advice.

Template 4: Announcement Message Brief

The message itself, one brief per audience. Subject line, the whole news in the first sentence, what is changing, why, what it means for you, what to do by when, what is not changing, and a named person to ask. Comes with a filled-in example you can copy the shape of.

Announcement Message Brief
ANNOUNCEMENT MESSAGE BRIEF
[Company Name]
The plan says who hears what and when. This is the thing you actually send. One
brief per audience, because the same words rarely work for a shift team and for
an outside vendor.
Audience:
Channel: Send date: [MM/DD/YYYY]
Sent by:
THE STRUCTURE

Subject or opening line:
[Say what it is. Not "an important update," and not "a few changes." If the
subject line could belong to any message, it will be opened last.]
The first sentence:
[The whole news, in one sentence. People decide in that sentence whether this
affects them, and everything after it is read through that decision.]
What is changing:
[Two or three sentences. Concrete, with dates and figures.]
Why:
[One or two sentences. A reason people can repeat to each other holds up. A
reason that sounds like a press release gets replaced by whatever they invent.]
What it means for you:
[The part they came for. Write it for the person reading, not for the company.]
What you need to do, and by when:
[A list, with dates. If there is nothing to do, say that plainly, because
otherwise everyone assumes there is something.]
What is not changing:
[Name the obvious fears and close them. Pay, hours, and jobs, when they are not
affected.]
Who to ask:
[A named person, not a shared inbox nobody watches.]
Where this lives afterward:
[The handbook, the shared drive, the pinned message. One place.]
A FILLED-IN EXAMPLE

Subject: Clocking in moves to the app on Monday the 6th
From Monday the 6th, everyone clocks in and out on the scheduling app instead of
the paper timesheet by the door.
We are doing this because the paper sheets get filled in from memory at the end
of the week, which means people get paid for roughly what they worked instead of
exactly what they worked. This fixes that in your favor.
What it means for you: you clock in on your phone at the start of your shift and
out at the end. It takes about four seconds. If your phone is dead or you forgot
it, tell your shift manager and they will enter it for you.
What you need to do before Monday: download the app and sign in once, so we know
it works. Adaeze can help if it does not.
What is not changing: your pay rate, your pay date, your schedule, and who
approves your hours. Nothing about this changes what you are paid.
Questions: ask Adaeze, or bring it to the huddle on Thursday.
BEFORE YOU SEND

[ ] Read the first sentence alone. Does it carry the whole news?
[ ] Read it as the most anxious person on the team would
[ ] Every date and figure checked against the plan
[ ] A named person to reply to
[ ] Anyone personally affected has already heard it in a conversation

NOTE: This is a sample template for general information only and is not legal
advice. Names and figures in the example are illustrative.

Template 5: Communication Calendar (Spreadsheet)

For the communication that recurs instead of announcing something: the daily huddle, the weekly written update, the monthly numbers, the quarterly direction, each with a named owner and a fixed slot. A second tab plans twelve months of known dates. It pairs with a wider internal communication strategy once the rhythm is running.

Communication Calendar
ABCDEFG
1RhythmWhat goes outAudienceChannelOwnerDay and timeStill running
2DailySAMPLE Shift huddle: today’s priorities, anything unusualEveryone on shiftIn person, five minutesShift managerStart of shiftYes
3WeeklySAMPLE What happened last week, what matters this week, one numberWhole teamTeam channel postOwnerMonday, 9amYes
4MonthlySAMPLE How the business is doing, in plain figuresWhole teamAll-hands, 30 minutesOwnerFirst ThursdayYes
5QuarterlySAMPLE What we are trying to do this quarter, and what changedWhole teamAll-hands plus written recapOwnerFirst week of the quarterYes
6Ad hocAnnouncements that cannot wait for the next rhythmDependsPer the channel guideOwnerAs neededYes
7
8
9RuleFour rhythms is enough. A fifth one is the one that quietly stops happening first
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Template 6: Incident and Crisis Communication Plan

For the day there is no time to write anything. Triggers, who decides, who speaks, backup channels for when the normal ones are down, a first-message structure you fill in with facts, the order people are told, and a short list of what never goes in writing.

Incident and Crisis Communication Plan
INCIDENT AND CRISIS COMMUNICATION PLAN
[Company Name]
Plan owner: Last reviewed: [MM/DD/YYYY]
Reviewed with the team on: [MM/DD/YYYY]
The routine plan assumes you have time to write. This one assumes you do not, so
the decisions are made in advance and the only thing left on the day is filling
in facts.
1. WHAT TRIGGERS THIS PLAN

[ ] Injury or safety incident on site
[ ] Fire, flood, power loss, or the building being unusable
[ ] Data breach or the loss of a device with company data on it
[ ] Loss of a system the business cannot operate without
[ ] Severe weather closing a site
[ ] Death or serious illness of someone on the team
[ ] Anything that will be discussed publicly before you have decided what to say
[ ] [ ]
2. WHO DOES WHAT

Decides whether this plan is active: [name] Backup: [name]
Speaks for the company: [name] Backup: [name]
Contacts employees: [name] Backup: [name]
Contacts customers and vendors: [name] Backup: [name]
Keeps the written log: [name] Backup: [name]
Nobody else speaks on behalf of the business. Say that in advance, in writing, so
it is a known rule rather than an instruction issued during the incident.
3. HOW YOU REACH PEOPLE WHEN THE NORMAL CHANNELS ARE DOWN

Primary channel: [ ]
If that is unavailable: [ ]
If that is unavailable: [text message to the current phone list]
Current phone list held by: [name] and [name]
Last verified on: [MM/DD/YYYY]
Verify the list twice a year. An emergency contact list that has not been checked
since the last two people joined is not a list, it is a hope.
4. THE FIRST MESSAGE

Send within [30 / 60] minutes, even when you know very little. A short accurate
message stops the invented one.
"[What has happened, in one sentence.] [Who is affected and what they should do
right now.] [What we do not yet know.] We will send another update by [time], and
until then please [do this / do not do this]. Questions to [name]."
Next update due: [time]. Send it even if nothing has changed, and say so.
5. WHO GETS TOLD, IN ORDER

1. Anyone in immediate danger or directly involved
2. Emergency services, if applicable
3. The rest of the team
4. Customers with work in progress
5. Vendors and partners affected
6. [insurer / landlord / regulator, if applicable]
6. WHAT NOT TO PUT IN WRITING

Speculation about cause, fault, or blame
Anyone’s medical information or personal details
Anything about an injured person beyond what they have agreed you can share
A promise about outcome, timing, or liability
Say what happened and what you are doing. Nothing else, until you know.
7. AFTER

[ ] Final message to everyone, including what happens next
[ ] Written log of what was sent, to whom, and when
[ ] What we would change in this plan, written down within a week
[ ] Contact list re-verified
[ ] Reviewed with the team, and with anyone who joined since

NOTE: This is a sample template for general information only and is not legal
advice. Emergency planning, reporting, and recordkeeping obligations are set by
federal, state, and local rules and vary by industry and headcount. Confirm what
applies to your business before you rely on this document.

How to Write One in an Hour

An hour is realistic for a genuine change, and most of it goes on the message rather than the grid. The order below matters, because the step people skip is the first one and everything downstream then takes twice as long.

1
Write the paragraph first
What is changing, why, when, what people do differently, what is not changing. If this is hard to write, the decision is not finished.
2
Split audiences by impact
By how much their day changes, not by department. A job that changes needs a conversation; a job that does not needs a sentence.
3
Pick a channel per audience
Where those specific people actually read things. One channel carries the message, one place holds the record.
4
Name an owner and a date per row
One person, and not always you. A manager delivering to their own team lands better, provided they have the answers first.
5
Set the order
Anyone affected personally hears it in a conversation, then managers, then the wider team, then anyone outside the company.
6
Prepare the hard answers
Pay, jobs, hours, and why now. Hand the written answers to whoever is delivering the message.
7
Book the follow-up now
Add a row for the repeat with its own date, and put it on the calendar in the same hour. Memory does not deliver this one.

The paragraph is the step worth defending. When it will not come out cleanly, the reason is almost always that the decision itself is unfinished: the date is not fixed, or nobody has decided what happens to the people most affected. Announcing into that gap produces a fortnight of correction messages, and each correction costs more attention than the original.

The second most-skipped step is the channel choice, which people treat as a formality and then default to email. Email is excellent for detail and terrible for urgency, and on a frontline team it is read by a minority. Choosing wrong here is the most common reason a message goes out properly and lands nowhere at all.

Who Hears It First

Anyone whose own job changes materially hears it individually, in a conversation, before anything is broadcast. Everything else follows from that rule, and the sequence below is the order that holds for almost every announcement worth planning.

OrderAudienceWhy they sit hereGap before the next group
1Anyone personally affectedNobody should learn something about their own job from a message addressed to a groupHours, not days
2Managers and team leadsThey get asked first. A manager surprised in front of their team loses credibility, and so do youSame day, or the next morning
3The wider teamThe main announcement, once the people who will answer questions have the answersWithin a day
4Customers, vendors, contractorsAfter the team, so nobody inside hears about their own company from outside itOne to two days
5Everyone againThe follow-up: what broke, what is fixed, what is still moving. The step most plans leave outOne week, then one month

The gap between steps two and three is where plans usually go wrong, in both directions. Too short and managers are reading the announcement at the same moment as their team, which is the same as not telling them. Too long, and it leaks, because a group of people who know something their colleagues do not is not a stable arrangement for a week.

One more rule worth writing into the plan: no group hears bad news that applies only to them in front of everybody else. The all-hands is a good format for direction and results, and a poor one for anything a single team has to absorb in public.

The Change Management Version

A change management communication plan is the same grid plus the arc: audience tiers, a sequence, prepared answers, a feedback route, and a follow-up schedule. You need it when the news lands over weeks rather than in one message, which is most things that alter how people work.

PhaseWhat goes outChannelTiming
Before the announcementIndividual conversations with anyone materially affected, then a manager briefing with the answersIn personOne to five days ahead
The announcementThe paragraph: what, why, when, what you do differently, what is not changingThe channel that reaches the group, plus a written recordDay one
First weekAnswers to what actually got asked, and fast correction of anything that landed wrongWherever the questions are arrivingDays two to five
Weeks two to fourWhat is working, what is not, and what you changed because of feedbackWritten update, shortWeek two, then week four
Close-outConfirmation that this is now simply how things work, or an honest statement that it is notWritten, and into the handbookAround week eight

The close-out row is the one that converts a change into a routine. Without it the change stays permanently in progress, and the practical cost is that people keep half-following the old process because nobody ever said the transition was over.

One warning about tiers. Sorting people into who is affected a lot and who is affected a little is useful for planning and dangerous when it leaks as a list. Keep the tiering in your own copy of the plan, and keep the tone of every message the same regardless of which tier it goes to.

Plan vs Policy vs Calendar

Four documents get called the communication plan, and mixing them is why so many teams have one file that does none of the jobs properly. They differ mainly in what ends them.

DocumentQuestion it answersWritten byEnds when
Communication planWho hears this news, on which channel, from whom, and by whenWhoever is running the changeThe change has landed
Communication policyWhich channel is for what, what tone, what stays confidentialThe employer, onceIt is reviewed, usually yearly
Communication calendarWhat goes out on a recurring rhythm, and who owns each slotWhoever owns internal communicationNever, it repeats
Message briefWhat this one announcement actually says, word for wordThe person sending itIt is sent

Settle the policy first if you have neither. Once a policy says which channel carries what and who may send to the whole company, every plan afterward fills in dates instead of re-arguing those questions.

The calendar deserves its own file for the same reason: it is the only one of the four with no end date. Recurring communication fails differently from announcements, quietly, by being skipped in a busy week and never restarted, which is why it needs a named owner and a fixed slot rather than a plan.

A few announcements come with a legally fixed deadline attached, and the plan has to be built backward from that date rather than around your own preferences. These are the three that catch small businesses most often, and none of them is a reason to skip legal advice.

Three Deadlines That Set the Date for You
Cutting a benefit is one: the administrator of a group health plan must furnish a summary of any modification that is a material reduction in covered services or benefits within 60 days of adoption (29 CFR 2520.104b-3). Large-scale layoffs are another: under the federal WARN Act an employer may not order a plant closing or mass layoff until the end of a 60-day period after serving written notice on employees or their representatives, the state rapid response unit, and the local elected official (29 U.S.C. 2102). The federal version covers employers with 100 or more employees, so most small businesses sit outside it, but several states run their own broader versions. This is general information, not legal advice.

The third is the emergency plan. An OSHA emergency action plan must be in writing and kept available to employees, though an employer with 10 or fewer employees may communicate it orally, and the employer must maintain an employee alarm system with a distinctive signal for each purpose (29 CFR 1910.38). The plan has to be reviewed with each employee when it is first written, when the person is newly assigned, when their responsibilities change, and when the plan itself changes.

That last requirement is a communication schedule in disguise, and it is the reason the incident template above ends with a review step rather than a filing step.

Why Plans Stall Without an HR Department

Every communication plan template written for a large organization assumes a communications function, an approval chain, and time. At twenty people you have none of those, and the same three things go wrong.

Everyone already knows, because the team is small
This is the assumption that produces most of the damage, and it is half true. In a business of twenty people the news does travel on its own, which is exactly the problem: it travels in a version nobody wrote, missing the reason and the boundary. The plan is not there to inform people who have no other source. It is there to make sure the first complete version they hear is yours, and that the person who has to answer for it tomorrow heard it before their own team did.
There is no communications person, so the plan has no owner
At this size the owner is usually the founder, which means the plan competes with running the business and loses. The fix is not to find more time, it is to shrink the plan until it survives a bad week: five rows, one channel per audience, one follow-up date. A one page plan someone actually fills in beats a proper communications framework that gets started on a Sunday and abandoned by Wednesday. Put the follow-up on the calendar the same hour you write the plan, because that is the part memory never delivers.
The announcement goes out once and nothing follows it
Most plans cover the announcement and then stop. Week three arrives, the same question is still being asked, and it reads as resistance when it is just a message that landed on half the team. Build the repeat into the plan as its own row with its own date: what broke, what is fixed, what is still moving. This is also where an HR platform stops being overhead and starts being useful, because the plan, the acknowledgments, and the follow-up tasks sit against real people instead of in a document. Applicant tracking is coming soon to FirstHR.

The practical answer is smaller than it looks: five or six rows, one channel per audience, one named person to reply to, and a follow-up date already on the calendar. If the same questions keep returning after every announcement, that is a channel problem rather than a message problem.

Send It, Track It, Close It

The templates work on their own, printed and filled in. What tends not to work is everything after the send: the follow-up nobody scheduled, the acknowledgment nobody collected, and the announcement that changed a rule but never reached the document holding that rule.

Send from the plan, not from memory
Work down the grid row by row on the dates in it. The moment you start improvising the order, the group that gets skipped is the one that mattered most.
Leave a route back open
Name a person, not a shared inbox, and say when the route closes. Then say publicly what you heard and what you changed, or people stop using it.
Track who has actually seen it
For anything people must act on, a read is not an acknowledgment. Ask for a reply, a signature, or a checked box, and chase the gap the next day.
Put the final version somewhere permanent
The announcement is temporary; the rule it created is not. Move it into the handbook or the policy it changed, so the answer in six months is not a search through old messages.

Four habits cover most of it. Send from the plan rather than from memory. Keep a route back open and report on what you heard. Ask for an acknowledgment on anything people must act on, because a read is not agreement. And move the final version into the place people will look in six months, which is usually the employee handbook rather than a channel that scrolls.

That last part is where FirstHR fits. The announcement and the policy it changed sit in document management with a version history, acknowledgment comes back e-signed with a date against the right person, the self-service portal means people can find the current version without asking, and the follow-up steps in the plan become assigned tasks with owners and due dates. Applicant tracking is coming soon to FirstHR.

To be clear about scope, FirstHR is an onboarding and HR platform, not a messaging tool, not a payroll provider, and not a law firm. It does not run your team channel, decide a notice period, or write the message for you. It holds the record, the signatures, and the tasks around it, so pair it with the channels your team already uses and with a qualified professional on anything with a legal deadline attached. Applicant tracking is coming soon to FirstHR.

Key Takeaways
A communication plan is a grid: audience, message, channel, owner, and timing, one row per audience.
Split audiences by how much the news changes their day, not by department, and give every row a named owner.
Anyone personally affected hears it in a conversation before anything is broadcast, and managers hear it before their teams do.
Add a column for how people respond, name a person rather than an inbox, and say what you changed because of it.
The follow-up row is the one most plans skip, and anything that changes behavior needs sending two or three times rather than once.
Some announcements carry legally fixed deadlines, so build the plan backward from the date. This is general information, not legal advice.

Frequently Asked Questions

What is a communication plan?

A communication plan is a grid that decides, in advance, who hears a piece of news, what they hear, on which channel, from whom, and when. One row per audience. It exists because the default alternative is a single message sent to everyone at once, which reaches the people who happened to be looking at that channel that morning and nobody else. The plan is not a document for the file: it is a working sheet you send from, row by row, on the dates written in it. For a small business it takes about an hour to fill in for a real change, and most of that hour goes on the message itself rather than the grid. This is general information, not legal advice.

What should a communication plan include?

Five columns at minimum: audience, message, channel, owner, and timing. Audience means groups split by how much the news changes their day, not one row labeled everyone. Message means what that specific group needs to hear, written from their side. Channel means where those people actually read things, which differs sharply between frontline and desk-based staff. Owner means one named person per row. Timing means a date plus how many times the message repeats, because anything that changes behavior needs sending two or three times. Add a sixth column for how people reply, with a named person and a closing date, and a plan for anything larger than an announcement should also carry a sequence, prepared answers to the obvious questions, and a follow-up date.

How do you write a communication plan?

Write the announcement in one paragraph before you touch the grid, covering what is changing, why, when, what people do differently, and what is not changing. If that paragraph is hard to write, the decision is not finished and announcing it early will cost you more than waiting. Then list the audiences by how much their day changes, give each one a channel that reaches them and a named owner, put dates against every row, and set the order so anyone personally affected hears it in a conversation before the group message goes out. Write down the answers to the questions you expect, including the awkward ones about pay and jobs. Finally, add the follow-up row and put it on the calendar immediately.

What is a change management communication plan?

It is the longer version used when a change lands over weeks rather than in a single announcement, and the difference is that it plans the whole arc instead of the moment. It covers the same five columns, then adds the parts a one-off announcement does not need: audience tiers by how materially the change affects each person, a sequence that puts individual conversations before any broadcast, written answers to the questions people will ask, a named route for feedback with a date it closes, and a follow-up schedule running out to about week eight. The section that gets skipped most often is the follow-up, which is why the same question is still arriving in week three and being mistaken for resistance rather than for a message that only half landed.

What is the difference between a communication plan and a communication policy?

A plan is for one specific message and it ends; a policy is a standing rule set and it stays. The plan says who hears about the system change, on which channel, and by what date, and it closes once the change has landed. The policy says which channel is used for what, what tone is expected, how quickly people are expected to reply, and what stays confidential, and it is signed once and reviewed roughly yearly. They work together, and the order matters: settle the policy first, because once it establishes which channel carries what and who may send to the whole company, every plan you write afterward fills in dates instead of re-arguing those questions. A calendar is the third document, covering communication that recurs rather than communication that happens once.

Who should hear about a change first?

Anyone whose own job changes materially, individually and in a conversation, before anything is broadcast. Then managers and team leads, because they will be asked first and being surprised in front of their own team costs you their credibility and yours. Then the wider team, ideally within a day of the managers rather than a week, since a long gap between those two steps is what produces leaks. Then customers, vendors, and anyone outside who will notice. Then everyone again as a follow-up, which is the step most plans leave out. The principle underneath the order is simple: nobody should hear news that affects them personally in a message addressed to a group, and nobody should hear about their own company from outside it.

How often should internal communication go out?

Give it a rhythm rather than a frequency target, because a schedule people can predict beats a higher volume they cannot. A practical default for a small business is a short daily huddle where the work is shift-based, a weekly written update covering what happened and what matters next, a monthly session on how the business is actually doing with real figures, and a quarterly conversation about direction. Four rhythms is enough, and a fifth is usually the one that quietly stops happening first. Separately from the rhythm, anything that changes what people do needs sending two or three times rather than once, because a single sending reaches the people who were paying attention that morning.

Are these communication plan templates free to download?

Yes. All six download free, with no email form and no account: four as editable Word documents and two as Excel workbooks, one of which includes a fully worked example you can read before you fill in anything. Downloading all six at once gives you a single zip file with each one inside it separately. That is worth checking elsewhere, because several widely-linked communication plan templates require a free account to open the file inside a vendor product, and template libraries often keep the more complete versions behind an upgrade. Free does not mean finished, though. Fill in the brackets, delete the rows that do not apply, and change anything that does not match how your business actually runs.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial