Internal communication plan: what goes in the document, what belongs in the channel — a one-page example (2026)

Most internal communication plans fail the same way: the document tries to do the channel's job. It lists the messages, drafts the announcements, schedules the all-hands, and then sits in a folder while the actual communication happens somewhere else, in a channel nobody mapped. Six months later the plan describes an organisation that no longer exists, and the channel holds the only record of what people were really told.

The split is the whole method. The plan is a document: the audiences, the channel assigned to each, the cadence, the owners, the date it is checked again. The communication is the channel: the announcements, the decisions with their reasons, the questions and the answers, the recap of the all-hands. The document is opened a few times a year; the channel every day. Put the right things in each and the plan stays short enough to be true.

This guide is the craft first — what an internal communication plan is, what goes in the document and what belongs in the channel, how to write one in an afternoon — then a template you can copy, a filled-in example for a company of sixty-four people on three sites, the documented place the plan lives in the tools you already pay for, and one way the plan's rows become channels the whole organisation reads.

What an internal communication plan is — and what it isn't

An internal communication plan answers, for every group inside the organisation, five questions: what they need to hear, through which channel, how often, from whom, and where the record of it lives. It is a table, not an essay. It is also easy to confuse with four neighbouring documents, and the confusion is why plans get long.

The project-level table, with the client and the agency as rows, is the communication plan template; the rules of working apart are in the remote work policy template; the meeting side is meeting cadence, and the one meeting every row of this plan shares is the all-hands. The internal communication plan sits above them: it is the one page that says, for the whole organisation, which channel carries what.

What goes in the document

Nine lines per audience, plus two rules at the bottom. Leave one out and the organisation fills the hole with habit — usually the habit of asking the manager.

1. Objectives. Three at most, each with a way to see whether it happened: "every policy change is announced with its reason before it takes effect", "a question from the floor is answered within a working day". An objective without a way to check it is a wish.
2. Audiences. Groups inside the organisation who need the same things at the same rhythm: all staff, managers, a site or a shift, a country office, new hires, the leadership team. Name real groups. An organisation on more than one site usually has one audience more than it thinks: the people who read in a different language than the one the company channel is written in.
3. What they need to hear. Decisions, policy changes, results, hires and departures, what is coming — in the words that audience uses. The plant needs to know what the office decided that touches the floor; the managers need to know it a day earlier, so they can answer.
4. Channel. One primary channel per audience, named by its real name: the company channel, the Monday managers' call, the shift briefing. If an audience has two channels, say which one is the record and which one is the alert.
5. Cadence. A rhythm the audience can set a clock by: the day a decision is made, weekly on Monday, the first Thursday of the month. "As needed" is a cadence only for the escalation row.
6. Owner. One name per row. The owner does not write every message; the owner is the person who notices when the cadence was missed.
7. Format. The shape of the message: an announcement with its reason, a three-line status, a briefing note, a recap with decisions. Format is what lets a new owner take over a row without inventing it again.
8. Where the record lives, in which language. The place a person who was not there reads what was said: the channel history, the all-hands recap, the onboarding channel. This is the column that decides whether a hire in month four can find what everyone was told in month one.
9. Feedback route. How a question from any audience reaches the person who can answer it, and how fast: a thread under the announcement, a question to the shift lead who posts it to the managers' channel the same day.

Below the table, two rules: the language rule — which language each channel is written in and how a reader in another language gets the message — and the review date, when the plan is checked against what actually happened.

What belongs in the channel

Four things the document should never hold, because the moment it does, people stop opening it:

• The announcements themselves. The plan says "policy changes go to the company channel with the reason"; the channel holds the policy change and the reason.
• Decisions and why they were taken. A decision recorded only in the slides of the all-hands is a decision the plant never saw.
• Questions and answers. The thread under the announcement is where the plan's feedback route runs. The answers belong next to the question, not in a separate FAQ document that someone maintains until they leave.
• The record. The recap of the all-hands, the weekly managers' note, the shift briefings of the last month. The plan names where they live; the channel is where they live.

The test is one sentence: if somebody has to open the plan to find out what was decided, the plan is doing the channel's job — and the channel is not doing it.

How to write one

An afternoon is enough if the organisation already exists.

1. List the audiences before the channels. Start from groups of people who need to hear things, not from the tools you own. An organisation that starts from tools ends with "everything goes in the company channel" and an audience — the second shift, the country office — that reads it two days late.
2. For each audience, finish the sentence: "They need to hear X so that they can Y." If the sentence will not finish, the audience does not need a row; they need access to the record.
3. Write the objectives last, not first. Three, with a check for each. Objectives written before the table are a strategy; written after it, they are what the table has to deliver.
4. Pick one primary channel per row by where the record ends up. An announcement read aloud at the shift briefing and never written anywhere has no channel.
5. Set the cadence to the audience's clock. The managers hear the day before the floor does. The second shift reads the briefing at 14:00, not at 6:00.
6. Put a name in the owner column. The owner can delegate the writing. The owner cannot delegate noticing the gap.
7. Write down where each channel's history is readable, and in which language. If the honest answer is "in the channel, in the language it was written in", write that; it is the sentence most plans leave unsaid, and the one that quietly excludes people.
8. Fix a review date and a place for the plan itself. The plan lives where the organisation's record lives — pinned in the company channel, not in a folder on the shared drive. After the first quarter, cross out the rows nobody kept.

The one-page template

Copy the block, replace the italics.

Internal communication plan — organisation name
Owner of the plan: name · Review date: date
Objectives: three at most, each with how you will know it happened
Language rule: the language each channel is written in, and how a reader in another language gets the message

Audience	What they need to hear	Channel	Cadence	Owner	Format	Where the record lives
All staff	decisions, policy changes, results, hires	the company channel; the all-hands	the day a decision is made; monthly	name	announcement with the reason; recap	channel history; the all-hands recap
Managers	what is coming, a day before everyone else	the managers' channel; weekly call	weekly; the day before any all-staff announcement	name	three lines; call recap	channel history
A site or shift	what touches the floor: shifts, safety, targets	the site channel; the shift briefing	daily; weekly summary	name	briefing note	channel history
A country office	everything all staff hears, plus what is local	the office channel; fortnightly call	same day as all staff; fortnightly	name	three lines; recap	channel history
New hires	who is who, where things are, the rules that bite in week one	the onboarding channel; two check-ins	day one, week one, week four	name	onboarding note; check-in	channel history; the check-in recap
Leadership	numbers, risks, decisions pending	the leadership channel; weekly call	weekly	name	decision log; recap	channel history

Feedback route: how a question from any row reaches the person who can answer, and how fast.
Not in this plan: customers, suppliers, the agency — those are rows of a project plan; direct messages; personal matters.

Seven columns and nine rows at most. If the table runs onto a second page, two of the audiences are the same audience.

A filled-in example: sixty-four people, three sites

A manufacturer of sixty-four people. The head office in Bologna holds the leadership, sales and administration; a plant twenty kilometres out runs two shifts; a sales office in Barcelona opened in March with seven people. The office writes in Italian, Barcelona in Spanish, and on the plant floor a third of the people read Romanian or Arabic first. Until the plan, announcements went by email from the CEO to the managers and from there to the floor by word of mouth; the Barcelona office learned about the new expense rules from a supplier.

Internal communication plan — Officine Marchetti
Owner of the plan: Chiara (CEO) · Review date: first Monday of January, April, July and October
Objectives: every policy change is announced with its reason before it takes effect; the managers hear it a day before the floor; a question from any channel is answered in its thread within one working day.
Language rule: the company channel and the plant channel are written in Italian, the Barcelona channel in Spanish; each reader gets the message in their own language, or the owner adds a translation underneath.

Audience	What they need to hear	Channel	Cadence	Owner	Format	Where the record lives
All staff (64)	What changed and why: decisions, policies, hires, the quarter's numbers	#tutti channel; monthly all-hands call	Announcement the day a decision is made; all-hands first Thursday of the month	Chiara	Announcement with the reason; all-hands recap	#tutti history; the all-hands recap
Managers and shift leads (9)	What is coming, so they can answer questions before they are asked	#manager channel; weekly call Monday 9:00	Monday; and the day before any all-staff announcement	Chiara	Three lines; call recap	#manager history
Plant, both shifts (38)	Shift changes, safety, production targets, what the office decided that touches the floor	#stabilimento channel; the briefing at the board	Briefing posted by 6:00 and 14:00; weekly summary Friday	Luca (plant manager)	Briefing note; a photo of the board	#stabilimento history
Barcelona office (7)	Everything all staff hears, plus what is specific to Spain: rules, pricing, support	#barcelona channel; fortnightly call with the sales lead	Same day as #tutti; fortnightly Tuesday	Marta (office lead)	Three lines; call recap	#barcelona history
New hires (first 30 days)	Who is who, where things are, the rules that bite in week one	#benvenuto channel; a check-in in week one and week four	Day one, week one, week four	Giulia (HR)	Onboarding note; check-in	#benvenuto history; the check-in recap
Leadership (4)	Numbers, risks, decisions pending	#direzione channel; weekly call Tuesday	Weekly	Chiara	Decision log; recap	#direzione history

Feedback route: a question under an announcement is answered in its thread within one working day by the owner of the row; a question raised at the board goes to the shift lead, who posts it in #manager the same day.
Not in this plan: customers, suppliers and the design agency (rows of the project plans); one-on-ones; personal leave; anything about pay.

Three things to notice. The managers' row is written a day ahead of the all-staff row, so the first question from the floor meets someone who already knows the answer. The plant row runs on the plant's clock — two briefings, not one, because there are two shifts — and its format is a note and a photo, because that is what the board at the plant actually is. And the language rule does not say "Italian"; it names the readers in Romanian, Arabic and Spanish, which is what makes the "where the record lives" column true for thirty-eight people on the floor and seven in Barcelona.

Where the plan lives in the tools you already use

The plan assigns channels, so it only works if the channels can carry what the rows need: an announcement every reader opens, a thread for the questions, a record a hire in month four can read. Documented behaviour only, from the vendors' own pages, checked in the month named:

Two things are the same in all four. The announcement is stored in the language it was written in, and translation — where it exists — happens on the reader's side and is visible to that reader. And none of the four vendor pages above describes a record of the all-hands that each reader opens in their own language: the record is a document in one language, or nothing, unless somebody writes it.

How the rows become channels

InterMIND is a communication space that sits next to Microsoft 365, Google Workspace and Slack, and the plan above maps onto it row by row: each audience is a channel, and the channel holds the communication the document only maps.

The whole channel is in each member's language, and the history reads that way. Chiara writes the announcement in Italian; the shift lead at the plant reads it in Romanian, the Barcelona office in Spanish, and the original is a toggle away — the chat is translated per reader, so the language rule at the bottom of the plan needs no second author. The thread under the announcement, where the questions arrive, reads the same way. At the monthly all-hands, the announcement or the quarter's numbers go on everyone's screen next to the video tiles with Share to conference: the sharer edits it live while the room watches, and every participant reads it in their own language. When the call ends, the recap — summary, decisions, action items with owners — arrives by email, as a message in the channel and as a link in the calendar event, and every signed-in member reads it in their own language; the channel keeps the recap of every session, so the "where the record lives" column is one place. An announcement drafted in an HR tool or a payroll system can land in the channel by email: every channel can have its own address, created by the channel's host, and a message sent to it appears as a regular message with the sender named and attachments kept — one way, email in, nothing sent back. A Telegram group the plant already runs can be mirrored into a channel with the same name, one way as well. What each platform keeps after a call, and how to keep it, is in how to keep a meeting transcript and summary after the call.

The rows at the edge of the organisation cost nothing, and nobody needs a second account. An internal plan still has people at its edge: the agency that runs the onboarding video, the accountant, the adviser the works council brings. They are added to their channel by email: a registered user is in the channel immediately; anyone else gets an invitation by email and joins on sign-up to a free account, with the channel's history readable from the first day. Someone who only needs one call — a candidate, a trainer — joins by link as a guest: no account, from a phone, in the browser, hearing the meeting live in their own language. There is no record for a guest afterwards; the free account is what makes the record reachable. Channel participants outside the team and meeting guests are always free.

You pay only for the people who use it. On a paid plan the host pays for the members active in the previous 28 days — the people who joined a meeting, wrote in a chat or asked Mia; members who go quiet keep their access at no cost. Sixty-four people on the plan are sixty-four members, and each renewal counts only those who joined a call, wrote or asked Mia in the window.

• See the channel chat translated per reader — each member writes in their language and reads the others in theirs.
• Try the live demo — no signup; speak, and hear the room translated per listener.

An internal communication plan as a craft survives every tool: somebody still has to decide who hears what, and keep the cadence. What doesn't have to survive is the second document nobody writes down — the one that says who forwards the announcement to the floor, who translates it, and where the recap of the all-hands went.

FAQ

What is an internal communication plan?

An internal communication plan is a one-page table that says, for each group inside an organisation, what they need to hear, through which channel, how often, from whom, and where the record lives. It covers all staff, managers, sites or shifts, country offices, new hires and the leadership team, and it is reviewed on a fixed date against what actually happened. The plan is the map; the announcements, decisions and answers themselves belong in the channels it names.

What should an internal communication plan include?

Nine things per audience: the objectives the plan serves; the audience; what they need to hear; the channel; the cadence; the owner; the format; where the record lives and in which language; and the feedback route — how a question reaches the person who can answer it, and how fast. Below the table, two rules: the language each channel is written in and how a reader in another language gets the message, and the review date.

How do you write an internal communication plan?

List the audiences before the tools. For each, finish the sentence "they need to hear X so that they can Y". Pick one primary channel per audience by where its record ends up, set the cadence to the audience's clock — managers a day before the floor, the second shift at 14:00 — put one name in the owner column, write down where each channel's history is readable and in which language, write the objectives last so they describe what the table delivers, fix a review date, and after the first quarter cross out the rows nobody kept.

What is an example of internal communication?

A policy change announced in the company channel the day it is decided, with the reason and a thread for questions; the managers' three-line note the day before; the shift briefing posted at 6:00 and 14:00; the recap of the monthly all-hands with its decisions and owners; the onboarding note a new hire reads on day one. Each is a row of the plan; the plan itself is not one of them.

What is the difference between an internal communication plan and a communication strategy?

A strategy says why the organisation communicates and what it wants people to believe or do; it changes rarely and is written in sentences. A plan is the operational table — who, what, where, how often, from whom — that makes the strategy happen, and it is reviewed quarterly. A plan without a strategy still works; a strategy without a plan is a document.

How often should an internal communication plan be reviewed?

Quarterly for a standing organisation, and at every change of audience: a new site, a new country office, a group of hires who read a different language. The review is short: cross out the rows nobody kept, add the audience that appeared, and check that the record each row names is still where people actually look.

Sources: Microsoft Support, Translate a message in Microsoft Teams, checked August 2026, and Take meeting notes in Microsoft Teams, checked October 2026; Google Chat Help, Translate messages in Google Chat, checked August 2026; Google Meet Help, Take notes for me and Languages supported, checked October 2026; Slack, Pricing, Customize data retention, Export your workspace data and Guide to AI features in Slack, checked August 2026; WhatsApp, How to export your chat history, Privacy Policy and Introducing message translations, checked August 2026.