Communication plan template: audiences, channels, cadence on one page

Most communication plans are written once, for a project charter or an onboarding pack, and never opened again. The reason is rarely the plan. It is that the plan describes channels the team does not actually use, cadences nobody keeps, and audiences — the client, the contractor in another country, the new hire who reads a different language — who were never going to see the channel the plan assigned them. A plan that works is short enough to be checked against reality every month, and honest about where its record ends up.

This guide is the craft first: what a communication plan is, what belongs in it, how to write one in an hour. Then a template you can copy, a filled-in example for a distributed team of about twenty people in three countries with a client on the outside, the documented place the plan lives in the tools you already pay for, and one way the plan stops being a document and becomes a channel.

What a communication plan is — and what it isn't

A communication plan answers five questions for every audience the team has to keep informed: what they need to know, through which channel, how often, from whom, and where the record of it lives. It is a table, not an essay. The columns are fixed; the rows are the audiences.

It is easy to confuse with four neighbouring documents, and the confusion is why plans get long.

The meeting side of this is in meeting cadence; the rules of working apart are in the remote work policy template. The communication plan sits between them: it is the one page that says, for the whole team and everyone around it, which channel carries what. The organisation-wide version — what all staff, managers, sites and new hires hear, and what belongs in the plan document against what belongs in the channel — is the internal communication plan.

What to include: audiences, channels, cadence

Eight elements, in the order they go into the table. Leave one out and the plan has a hole that the team fills with habit.

1. Audience. A group of people who need the same things at the same rhythm: the team itself, the manager above it, the client, the contractors, the wider company. Name real groups, not roles from an org chart nobody looks at. A distributed team usually has one audience more than it thinks: the people who read in a different language than the one the channel is written in.
2. What they need to know. Decisions, progress, risks, requests — in the words the audience uses. A client needs to know what changed and what it costs; the team needs to know what was decided and who owns it. Writing this column honestly is what keeps the plan from becoming "everyone gets everything".
3. Channel. One primary channel per audience, named by its real name: the #project channel, the Monday email, the fortnightly call. If an audience has two channels, say which one is the record and which one is the alert.
4. Cadence. How often, as a rhythm the audience can set a clock by: daily, weekly on Monday, fortnightly after the review, at every release. "As needed" is a cadence only for one row, the escalation row.
5. Owner. One name per row. The owner does not write every message; the owner is the person who notices when the cadence was missed.
6. Format. The shape of the message: a three-line status, a recap with action items, a document, a call. Format is what lets a new owner take over a row without inventing it again.
7. Where the record lives. The place a person who was not there reads what was said: the channel history, the shared drive folder, the recap. For a distributed team this is the column that decides whether the plan survives contact with time zones, and whether a reader who joined in month four can find what was agreed in month one.
8. Review date. When the plan is next checked against what actually happened. Monthly for a project in flight, quarterly for a standing team.

Two more things belong at the bottom of the page rather than in the table: the escalation rule — who is told, how fast, by which channel, when something breaks — and the language rule: which language each channel is written in and how a reader in another language gets the content. Most plans leave the second one unsaid, and it is the one that quietly excludes people.

How to write one

An hour is enough if the team already exists; two if the project is new.

1. List the audiences first, channels second. Start from people who need to know things, not from the tools you own. A team that starts from tools ends with a plan that says "Slack for everything" and an audience — the client, the contractor — that is not in Slack.
2. For every audience, write one sentence: "They need to know X so that they can Y." If you cannot finish the sentence, the audience does not need a row; they need access to the record.
3. Pick one primary channel per row. The test is where the record ends up: a decision made in a call and never written anywhere has no channel.
4. Set the cadence to the audience's rhythm, not yours. A client who reviews on Fridays wants the status on Thursday. A team across nine time zones wants a written daily note more than a daily call.
5. Put a name in the owner column. The owner can delegate the writing. The owner cannot delegate noticing the gap.
6. Say where each channel's history is readable, and in which language. This is the row-by-row version of the language rule. If the answer is "in the channel, in the language it was written in," write that down; it is the most useful honest sentence in the whole plan.
7. Fix a review date and a place for the plan itself. The plan lives where the team's record lives — pinned in the team channel, not in a folder nobody opens.
8. Check it after the first month. Cross out the rows nobody kept. A plan with six rows that are true beats one with twelve that are aspirational.

The one-page template

Copy the block, replace the italics.

Communication plan — team or project name
Owner of the plan: name · Review date: date
Language rule: the language each channel is written in, and how a reader in another language gets the content

Audience	What they need to know	Channel	Cadence	Owner	Format	Where the record lives
The team	decisions, blockers, who owns what	the team channel	daily note; weekly call	name	three lines; recap	channel history
The manager / sponsor	progress against the plan, risks, asks	status email or thread	weekly on Monday	name	one-page status	the thread; the status folder
The client	what changed, what it costs, what is next	client channel or call	fortnightly	name	recap with action items	the client channel's history
Contractors / partners	scope, deadlines, handovers	the shared channel	at every handover	name	written brief	the channel; the shared folder
The wider company	what the team shipped, what it needs	all-hands or newsletter	monthly	name	three bullets	the all-hands recap

Escalation: who is told, how fast, through which channel, when something breaks.
Not in this plan: direct messages, personal matters, anything that is somebody else's record.

Seven columns is the whole plan. If a row needs an eighth, it is two audiences.

A filled-in example: a distributed team with a client on the outside

A product team of nineteen people: eleven in Spain, five in Romania, three in Argentina. A manager in Madrid, a sponsor on the leadership team, a client in Germany who reviews every second week, and a design agency on a six-month contract. The team writes in Spanish and English; the Romanian colleagues read Romanian first; the client writes German.

Communication plan — Project Marea
Owner of the plan: Lucía (project lead) · Review date: first Monday of each month
Language rule: the team channel is written in Spanish or English; the client channel in English; each reader gets the content in their own language, or the author adds a translation underneath.

Audience	What they need to know	Channel	Cadence	Owner	Format	Where the record lives
The team (19)	What was decided, what is blocked, who owns what today	#marea channel	Written daily note by 10:00 CET; weekly call Tuesday	Lucía	Three lines; recap with action items	#marea history and the recap of each call
Manager + sponsor	Progress against the quarter, two risks, one ask	Status thread in #marea	Monday, before 12:00	Lucía	One-page status	The thread
Client (Germany)	What changed, what it costs, what is next	#marea-client channel; review call	Fortnightly call Thursday; written update the day before	Marius (account lead)	Recap with action items; change note	#marea-client history
Design agency	Scope, deadlines, handovers, feedback	#marea-design channel	At each handover; weekly comment pass Wednesday	Ana (design lead)	Written brief; comments on the file	#marea-design history; the shared folder
Wider company	What shipped, what the team needs from others	Monthly all-hands; the company channel	Monthly	Lucía	Three bullets	The all-hands recap

Escalation: a blocker that costs more than a day goes to Lucía by direct message the same hour; a client-facing incident goes to Marius and the client channel within two hours, in writing, before any call.
Not in this plan: one-on-ones, personal leave, anything about pay.

Three things to notice. The team has two channels toward the outside — the client's and the agency's — and each has its own record, so nobody forwards. The cadence column is written in the audience's clock: the client reviews on Fridays, so the update lands Thursday. And the language rule is explicit about where translation happens, because the three readers in Romania and the client in Germany are not an afterthought; they are rows.

Where the plan lives in the tools you already use

A communication plan assigns channels, so it only works if those channels can hold the audiences it names — the client who is not in your tenant, the agency on a different Slack, the colleague who reads another language. Documented behaviour only, from the vendors' own pages, checked in the month named:

The dash means we found no vendor page that documents a cross-organization channel in the way the plan needs it, and we would rather leave a cell empty than fill it from memory.

Two things are the same in all four. The record is readable in the language it was written in, and translation — where it exists — happens on the reader's side and is visible to that reader only. And the external row of the plan is the hardest to fill: the client and the agency arrive through a second account, a tenant setting or a phone number, not through the channel itself. The chat side of this is covered in how to translate WhatsApp chats and how to export a WhatsApp chat; the meeting side in live translation in Microsoft Teams and live translation in Google Meet.

How the plan becomes one channel

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 is the record.

The whole channel is in each member's language, and the history reads that way. The chat is translated per reader — Lucía writes in Spanish, the colleague in Cluj reads it in Romanian, the client in Hamburg reads it in German, and the original is a toggle away. During the Tuesday call, the daily note or the Monday status goes 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 review date in the plan means opening the channel, not searching four inboxes. A status written somewhere else can land in the channel by email: every channel can have its own address, a message sent to it appears as a regular message with the sender named and attachments kept, and a copy of each recap can go to any address — a CRM or a tracker — so the external rows of the plan reach the system of record without forwarding. A longer record is in how to keep a meeting transcript and summary after the call.

The external rows cost nothing, and nobody needs a second tenant. The client and the agency 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 joins by link as a guest — no account, from a phone, in the browser — and hears the meeting live in their own language; there is no record for a guest afterwards, and 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. A nineteen-person team with a client and an agency pays for the nineteen, and only in the months they are active.

• 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.

A communication plan as a craft survives every tool: somebody still has to decide who needs to know what, and keep the cadence. What doesn't have to survive is the second plan nobody writes down — the one that says who translates for whom, and who forwards the recap to the people the channel could not hold.

FAQ

What is a communication plan?

A communication plan is a one-page table that says, for each audience a team has to keep informed, what they need to know, through which channel, how often, from whom, and where the record lives. It covers the team itself and everyone around it — manager, client, partners, the wider company — and it is reviewed on a fixed date against what actually happened.

What should a communication plan include?

Eight things per row: the audience; what they need to know; the channel; the cadence; the owner; the format; where the record lives; and the review date for the plan as a whole. Below the table, two rules: escalation — who is told, how fast, by which channel — and language — which language each channel is written in and how a reader in another language gets the content.

How do you write a communication plan?

List the audiences before the tools. For each, finish the sentence "they need to know 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 rhythm, put one name in the owner column, write down where each channel's history is readable and in which language, fix a review date, and after the first month cross out the rows nobody kept.

What is an example of a communication plan?

A nineteen-person product team in Spain, Romania and Argentina with a client in Germany: a written daily note by 10:00 and a Tuesday call for the team, a Monday status thread for the manager, a fortnightly Thursday call with a written update the day before for the client, a weekly comment pass for the design agency, three bullets at the monthly all-hands — each row with an owner, a format and the place its record lives. The full version is in the example above.

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

A strategy says why the organization communicates and what it wants audiences to believe or do; it changes rarely. A plan is the operational table — who, what, where, how often, from whom — that makes the strategy happen for one team or one project, and it is reviewed monthly or quarterly.

How often should a communication plan be reviewed?

Monthly for a project in flight, quarterly for a standing team, and at every change of audience — a new client, a new partner, a hire who reads 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 Learn, Shared channels in Microsoft Teams, Guest access in Microsoft Teams and Collaborate with external participants in a shared channel, checked October 2026; 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, and Meeting agenda template, checked October 2026; WhatsApp, How to export your chat history, Privacy Policy and Introducing message translations, checked August 2026.