VanillaPM
Sign in Get started free Dashboard
Free template

Communications plan template

A free communications management plan template in Word and Markdown, with a ready-made communications matrix — audience, what they need, method (interactive, push or pull), channel, frequency, owner and feedback.

Download Word (.docx) Download Markdown (.md) Free · no sign-up · opens in Word, Excel, Google Docs/Sheets and LibreOffice

What's inside

  1. PurposeWhat this plan covers and who keeps it up to date.
  2. Stakeholder communication needsFor each stakeholder or group: what they need to know, how often, and in what form.
  3. Communications matrixOne line per planned communication (table below).
  4. Feedback and confirmationHow you will know a message was understood, not just sent.
  5. Escalation pathWho to go to, and how fast, when a communication issue needs a decision.
  6. ReviewWhen the plan is reviewed (every phase, or when the stakeholder register changes).

Includes a ready-made table with 8 columns: Communication · Audience · What they need · Method (interactive / push / pull) · Channel · Frequency · Owner · How feedback comes back.

What a communications plan is

The communications plan says who needs to know what, when, how, and from whom, so that the right information reaches the right people without anyone drowning in it. Its core is the communications matrix: one line per planned communication.

When to use it

  • After the stakeholder register exists: you can't plan communication for people you haven't identified.
  • Whenever the stakeholder register changes (a new regulator, a new lender, a change of sponsor).
  • At each phase, because what people need to hear changes as the project moves.

How to fill it in

Start from the stakeholder register and write one matrix line per communication, not per person. For each line, decide the method:

  • Interactive: a meeting, a call, a workshop. Two-way; use it when understanding or agreement matters.
  • Push: a report or an email sent out. It proves the message was sent, not that it was read.
  • Pull: a dashboard or a shared page people look up when they need it. Good for large audiences.

Then say how feedback comes back. On the Coral Ridge sample, the community town hall is held in Bangla, and questions are logged and answered at the next meeting; the environmental monitoring pack goes to the regulator monthly and their acknowledgement is the feedback.

Common mistakes

  • Push for everything. Sending a report isn't the same as being understood.
  • One line per person. You'll end up with a plan nobody maintains. Group people who need the same thing.
  • No owner. A communication without an owner stops happening after a few weeks.
  • Forgetting opponents. Stakeholders who resist the project need a channel too, often the most.

Try the communication channels calculator to see why adding people makes communication harder so quickly.

See it used on a real project: P8 · Plan and manage communication