How to Create a Project Management Communication Plan

Estimated reading time: 9 minutes

Overview

A project communication plan sets out who needs which information, how often, and through what channel. Most plans get written once and then ignored, because they live in a document nobody opens while the schedule they describe lives somewhere else. This guide covers what belongs in the plan, six steps to build one, and a sample you can copy. It also looks at what actually changed for four Ganttic customers: RATP Group ADO-IE, which recovered roughly 80 hours a month across its office, G. Christianson Construction, which was running two schedules and getting crossed wires between subcontractors and managers, plus Valmet and Ab Ovo.

Why communication plans fail in practice

Almost every project of any size has one. A project communication plan is the document that records which stakeholders get which information, at what interval, and by which channel, usually with an owner named against each line. Written well, it stops the two failure modes that are likely to cost the most: the client who finds out about a delay from an invoice, and the engineer who sits in four status meetings a week.

The cost of getting it wrong shows up as manual work. Wellingtone’s State of Project Management 2026, a survey of more than 150 organizations fielded through the end of 2025, found that 72% of respondents spend half a day or more every month manually collating project reports, and that half have no access to real-time KPIs.

Those are precisely the hours a communication plan is meant to save.

Teams usually respond by rewriting the document, which rarely helps. The fault line is that the plan and the schedule live in separate places. A communication plan in a shared drive says a weekly status report goes out every Friday, while whether the work it reports on actually moved is recorded in the planner, the tracker or somebody’s head.

Keeping the two in sync becomes a manual job, and manual jobs are the first thing dropped when a project gets busy. The plans that survive are the ones attached to the resource schedule rather than sitting beside it.

What a project communication plan includes

Five columns cover almost every case. Anything beyond them tends to be decoration.

– Audience: Who receives this, by role rather than by name, so the plan survives staff changes. Sponsors, the client, the delivery team and finance usually need different things.

– Information: What they actually get. Progress against milestones, budget position, risks, dependencies and decisions needed are distinct items, and most audiences want two of them rather than all five.

– Channel: Where it goes. A standing meeting, an emailed report, a shared Gantt chart link or a dashboard. The rule of thumb is that anything requiring a decision needs a meeting, and anything reporting status does not.

– Cadence: How often. Tie it to the project rhythm, so a two-week sprint gets a two-week report.

– Owner: One named person per line. A line without an owner is a line that stops happening in week three.

Four of the five are usually easy to fill in from memory. Cadence is where teams argue, because setting it means admitting how fast the work actually moves.

Sample project communication plan template

This project communication plan template is for a mid-sized build with an external client. You can copy the columns and change the rows.

If a row gets dropped, it tends to be the steering group, which is also where the hardest questions arrive from later.

Six steps to build your project communication plan

1. Start from the decisions the project needs: List the decisions the project will need and who makes each one. Communication that does not feed a decision is a status broadcast, and status broadcasts can be a link rather than a meeting.
2. Map the audiences by role: Sponsors, client contacts, the delivery team, subcontractors, finance. For each, write the one thing they would escalate about if they did not hear it. That sentence is their row.
3. Decide what each one gets: Resist sending everyone everything. A sponsor who receives task-level detail stops reading, and then misses the risk item three months later.
4. Set the cadence against the work: Tie reporting to the project’s own rhythm. RATP Group ADO-IE runs workload planning meetings every two months, which suits consulting engagements spread across more than a dozen countries. A construction crew needs weekly.
5. Pick channels people already open: A plan routed through a tool somebody has to remember to check will decay. Shared Views of the live schedule, calendar syncs to Outlook or Google, and scheduled reports all beat a document that needs opening.
6. Name an owner and a review date: Put the plan where the schedule is, give every line one owner, and revisit it at the first milestone. Most plans need one correction early and then hold.

What four teams learned about communication breakdown

RATP Group ADO-IE, the operations and maintenance consulting arm of France’s state-owned transport operator, is deployed in more than a dozen countries.

Until 2023 its planning ran exclusively on shared Excel sheets and PowerPoint reports, with a homemade RATP tool that only covered projects inside France and company systems that were outdated, heavy, and sometimes behind a VPN. For managers checking in from the road, none of it worked. Fred Lavenaire, Head of Bus and Light Railway, describes the purpose of the replacement as a high-level view of who does what.

Their bi-monthly workload planning meetings now run off the live plan, and Lavenaire estimates the office recovers around an hour per person per month, roughly 80 hours in total, mostly from manual input and chasing. Task utilization percentages feed the reporting.

G. Christianson Construction shows the subcontractor version. Four superintendents were running more than 40 active projects across CoConstruct, Google Calendar, Monday and a spreadsheet, and maintaining two separate schedules produced exactly what you would expect: crossed wires between subcontractors and managers. Assistant Superintendent Joshua Rowland’s summary was that they wanted company-wide actions displayed collectively, which is a communication requirement rather than a scheduling one.

Valmet, with roughly 12,000 people, reported that miscommunications and overbookings dropped sharply once everyone who needed the plan could open it online.

Ab Ovo makes the subtlest point: because plans update immediately, responsibility for them became easier to share. Their weekly Friday resource meeting has something current to look at, and each project manager keeps a separate view of their own work.

Where the project communication plan may break down

Cadence set by habit:

Meeting weekly because you always have, rather than because the work moved, wastes the slot. Ganttic’s own guidance is to match meeting frequency to how granular the planning is.

Two sources of truth:

Christianson’s two schedules are the clearest example. A plan maintained in parallel with the real schedule tends to diverge, and the people reading the wrong one find out last.

Reporting that needs assembling:

If a status update means collecting numbers by hand, it slips. RATP Group recovered roughly 80 hours a month after moving off shared Excel sheets and PowerPoint reports.

Everything to everyone:

Copying every stakeholder on everything trains them to stop reading, so the one message that mattered gets missed.

Access friction:

A plan behind a VPN, a login nobody has, or a tool only managers can open is a plan half the audience cannot read. Ganttic charges per resource rather than per user, so viewers cost nothing to add.

Put the plan where the schedule already is

The best version of all of this is to stop maintaining the communication plan as a separate artifact. Build the audiences into the plan people already open.

In Ganttic that means saved Views per audience, so the client sees milestones while the delivery team sees assignments, both from the same data.

Custom data fields hold the owner and the cadence against each project.

Reports handle the recurring sends, calendar sync puts dates where people already look, and the API or Zapier pushes updates into the channels your teams actually use.

Book a demo and we will set the Views up against your own stakeholder list!

FAQ