A communication plan is a short table that sets out who needs what information, when, how often, and through which channel — so the right people stay informed without everyone drowning in updates. It is the document that stops a project running on rumour and forwarded emails. You can download a free, editable UK template in Word and Excel below, with a worked example filled in. No email address required.
Key takeaways
- A communication plan answers five questions for each audience: who needs to hear, what they need, why, through which channel, and how often.
- The seven columns: audience, message, purpose, channel, frequency, owner, and format. That is the whole structure — everything else is detail.
- It flows directly from your stakeholder analysis: how much power and interest a person has decides how much they hear, and how formally.
- For a small project, a one-page plan is plenty. A formal, multi-page version is for large or regulated work — do not over-build it.
- Download the free Word and Excel template below — blank, plus a filled UK small-business example. Nothing to sign up for.
What is a communication plan?
A communication plan is a simple table that records, for every group involved in a project, what you will tell them, why, how, and how often. Its job is to make communication deliberate rather than accidental. Without one, the loudest person gets the most updates and the quiet-but-important sponsor finds out about a slipped deadline at the worst possible moment.
It is sometimes called a communications plan, a project communication plan, or a stakeholder communication plan. They describe the same document. On a small project it lives on a single page; on a large programme it can run to several, with an escalation route and an approval step. The structure does not change — only the depth.
A note on jargon: a stakeholder is anyone affected by, or able to affect, your project. A channel is how a message travels — an email, a meeting, a phone call, a dashboard, a noticeboard. The cadence or frequency is how often you communicate. We define the rest as we go.
What should be in a communication plan? The 7 columns
Ask “what goes in a communication plan?” and the practical answer is seven columns. Build your table with these headings and you have a plan that works for a corner shop or a council programme.
- Audience / stakeholder. Who you are communicating with — name the group or the person. “The sponsor, Anna” is more useful than “management”.
- Message / what. The information they need: progress, a decision required, a risk, a launch date.
- Purpose / why. Why they need it — to decide, to act, to stay reassured, or to be kept in the loop. This column stops you sending updates nobody uses.
- Channel / how. Email, a meeting, a call, a shared dashboard, a printed notice. Match the channel to the audience, not to your own habit.
- Frequency / when. Weekly, fortnightly, monthly, or at milestones. Be specific: “fortnightly, on Fridays” beats “regularly”.
- Owner. The one person responsible for actually sending it. A message with no owner does not get sent.
- Format. A written summary, a verbal update, a slide, a one-line message. Keep it proportionate to the audience.
How does it relate to stakeholder analysis?
This is the link most guides miss, and it is the one that makes a communication plan actually work. A communication plan is the second half of a job that begins with stakeholder analysis. The analysis works out who matters and how much; the communication plan turns that into a schedule of who hears what.
In a stakeholder analysis you place each person or group by their power (how much they can affect the project) and their interest (how much they care). Those two levels set the rule for the comms plan: high-power, high-interest people get frequent, detailed, written updates; low-power, low-interest people get an occasional light touch. You are not deciding the cadence from scratch — you are reading it off the grid you already built.
If you have not done a stakeholder analysis yet, do that first; it is half an hour of work and it makes the communication plan almost write itself. Our stakeholder analysis template gives you the power-and-interest grid to start from.
A filled example: a UK small business
Most communication-plan examples online describe a software rollout at a large firm. Here is a complete one for a real UK situation: a small homeware shop, Wren & Willow (an illustrative example, not a real firm), relaunching its tired website as a proper online shop. Notice how few rows it needs.
| Audience | What & why | Channel | Frequency | Owner |
|---|---|---|---|---|
| Sponsor (Anna, owner) | Progress, spend and risks, so she can steer and approve. | Written one-page update | Fortnightly | Ravi (PM) |
| Shop staff | What is changing and what they need to do, to stay ready for launch. | Stand-up meeting | Weekly | Ravi (PM) |
| Web agency | Decisions, content and feedback, to keep the build on track. | Video call | Weekly | Ravi (PM) |
| Suppliers | Product data and images needed, to populate the shop. | As needed | Anna | |
| Customers | The launch date and opening offer, to bring them to the new shop. | Email + social media | At launch | Marketing |
Five rows settle the whole project’s communication. Anna knows she will get a written update every fortnight; the agency knows there is a weekly call; customers hear once, at the right moment, rather than being pestered. That is a communication plan doing its job.
Do you need a formal plan, or will one page do?
Not every project needs a multi-page communication plan. For a cost-conscious founder or a small team, the honest question is how much structure the work actually warrants. Often a one-page plan is plenty.
The rule of thumb: if a handful of people sit near you and the work is quick, a couple of lines in a message carry the same effect with less ceremony. If several groups are involved, money is at stake, or the work runs for weeks, write a proper one-page plan. Only large, regulated or public-sector programmes need the formal version with an escalation route and sign-off.
How often should you communicate, and who owns the plan?
How often: match the frequency to how much each audience needs and can absorb. A sponsor who steers the project wants a fortnightly written summary; a delivery team wants a short weekly check-in; a wide audience of customers or staff wants an occasional, well-timed message rather than a constant stream. Over-communicating trains people to ignore you as surely as under-communicating leaves them in the dark.
Who owns it: the project manager owns the communication plan — they keep it current and make sure each update actually goes out. Individual rows can have different owners (marketing sends the customer email; the sponsor handles a key supplier), but one person holds the plan as a whole. Review it at each milestone: audiences and their needs change as a project moves from build to launch.
What channels should you use?
Pick the channel for the audience, not for your own convenience. As a rough guide: a written update or email for anything someone may need to refer back to or forward; a meeting or call for decisions and discussion; a shared dashboard for a team that wants self-serve status; a short message for quick, low-stakes nudges; and a printed notice or noticeboard for staff who are not at a desk. Most small projects use two or three channels, no more. The test is simple: would this audience actually see and act on a message sent this way.
Download the free UK communication plan template
Free, editable, no email required. Each file includes a blank plan and the filled Wren & Willow example above, so you can see exactly how it is used.
- Word template (.docx) — the seven-column table, ready to type into, blank plus the filled example. Download Word version
- Excel template (.xlsx) — the same columns with drop-down lists for channel and frequency, a frozen header, and a blank and example tab. Download Excel version
UK English, A4, designed for small businesses. Made by a practitioner, not a software vendor — there is nothing to sign up for.
A communication plan works best alongside the documents either side of it. Start with our stakeholder analysis template to decide who hears what; the project charter template sets the project’s direction and names the sponsor; and the project plan template holds the schedule the updates report against.
Frequently asked questions
What is a communication plan?
A communication plan is a short table that sets out who needs what information, why, through which channel, and how often, on a project. Its purpose is to make communication deliberate, so the right people stay informed without everyone being buried in updates.
What should be in a communication plan?
Seven columns: audience (who), message (what), purpose (why), channel (how), frequency (how often), owner (who sends it), and format. Each row covers one audience. That structure is the same whether the plan is one page or several.
What is the difference between a communication plan and a stakeholder analysis?
A stakeholder analysis works out who matters and how much, by plotting each person’s power and interest. A communication plan turns that into a schedule of who hears what, when, and how. The analysis comes first and feeds the plan: a person’s engagement level sets their update frequency and channel.
How often should you communicate on a project?
Match the frequency to each audience. A sponsor typically wants a fortnightly written update; a delivery team wants a short weekly check-in; a wide audience such as customers or staff wants occasional, well-timed messages. Over-communicating trains people to ignore you, so be deliberate rather than constant.
Who owns the communication plan?
The project manager owns the plan overall — keeping it current and making sure each update goes out. Individual rows can have their own owner, such as marketing sending the customer email, but one person holds the plan as a whole and reviews it at each milestone.
What channels should a communication plan use?
Use a written update or email for anything that may be referred back to, a meeting or call for decisions, a dashboard for self-serve status, a short message for quick nudges, and a noticeboard for staff away from a desk. Most small projects use two or three channels in total.
What is a project communication plan?
A project communication plan is the same document applied to a specific project: it lists the project’s audiences, what each needs, and the channel and frequency for reaching them. “Communication plan”, “communications plan” and “stakeholder communication plan” all describe this same table.
This article is general guidance on project documentation, not formal project-management certification material or legal advice. The Wren & Willow example is illustrative. Adapt the template to your organisation’s own governance requirements. Updated 14 June 2026.
