Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Transformation management and PMO

Building a project communication plan, from audiences to measurement

In brief

A project communication plan is the document that sets, for each audience affected by a project, what it is told, by whom, through which channel and on what date, and how to check that the message has been understood. Management Square describes here how to build it in five steps (audiences, messages, channels, schedule, measurement), with what each produces and who is accountable for it.

Page contents

A project communication plan is the document that sets, for each audience affected by a project, what must be said to it, by whom, through which channel and on what date, together with how to check that the message has been understood. It is built in five steps, in this order: audiences, messages, channels, schedule, measurement. The order matters, because each step works on what the previous one has produced.

The table below summarises what each step produces and who is accountable for it.

Step What it produces Who is accountable
Audiences The list of audiences, with what changes for each and what the project expects of it The project manager, with the change management lead
Messages An approved common core, then a version for each audience The sponsor for the core, each business department for its teams
Channels The matrix that links each message to a channel, a sender and a feedback route The person who maintains the plan, with internal communications
Schedule Dated actions, tied to the project’s milestones The project manager
Measurement A few indicators per audience and the adjustments decided The project manager, before the steering committee

Audiences first, divided according to what changes for them

The organisation chart is a poor starting point: two teams in the same department can experience the project in opposite ways, one gaining a tool, the other inheriting additional data entry. An audience, in the sense of the plan, is a group of people for whom the project changes the same thing and of whom it expects the same thing.

Most projects have several kinds: those who decide (sponsor, steering committee), those who contribute (business experts, technical teams, suppliers), those who will use the result, with their managers, and those who will feel its effects without using it (support desk, operations, employee representatives).

The step produces a list that shows, for each audience, what the project takes away from it, what it brings, what it asks of it and by when. If the project has an impact analysis and a stakeholder map, the list follows directly from them. The project manager is accountable for it, with the person in charge of change management if there is one. A line headed “all employees” indicates that the work remains to be done.

Messages written for each audience, on a common core

The core answers three questions, the same for everyone: why this project, what it replaces, on what dates. It is short, written once and approved by the sponsor. The sponsor, the managers and the project team then give the same version of the facts.

The version for each audience answers four further questions: what changes for you, from when, what you have to do, whom to contact. What remains to be decided is announced as such, with the date on which the answer will be known. A real drawback for an audience is also stated, with the reason that justifies it: the people concerned will find out anyway.

The project team writes; each business department approves and carries the messages intended for its teams. The step produces the core, the messages for each audience and a list of questions and answers, added to as the project progresses.

A channel, a sender and a feedback route for each message

The channel is chosen according to what the message asks of its recipient. To inform, a written medium is enough. To explain, a format is needed in which questions can be asked: team meeting, live presentation, drop-in session. To obtain an action, the message comes from a person with the authority to ask for it, and it carries a deadline.

The sender carries as much weight as the channel. The sponsor carries the why. The direct line manager carries the instructions that change their team’s work, provided they have been informed before the team and have the list of questions and answers. The project team carries the how. In a matrix organisation, where the project has no line authority over the recipients, this relay through management is a precondition for any request for action.

Each top-down channel is given its feedback route: an address, a network of correspondents, question time in a meeting. A named person answers, within an announced time. The questions received enrich the list of answers; those that reveal a flaw in the project are passed to the project manager.

The step produces a matrix: audience, message, channel, sender, feedback route. It is maintained by the person in charge of the plan, with the internal communications department, which knows the existing media and the company’s editorial calendar.

A schedule tied to the project’s milestones

Communication actions are dated in relation to milestones: launch decision, choice of solution, pilot, opening of training, go-live, retirement of the old tool. Tying a message to a milestone rather than a fixed date has an advantage. If the schedule slips, the message slips with it, and the project does not announce a deadline it no longer meets.

The sequence follows a few rules. Managers are informed before their teams. Explanation comes before the invitation to act, whether that means signing up for training or activating an account. After each milestone, a message says what happened, including when the milestone has been postponed.

Outside the project, the same teams receive announcements from other workstreams and go through busy periods. On a programme, a single calendar prevents several announcements from reaching the same team at the same time; maintaining it and arbitrating collisions falls to programme management. The project manager is accountable for the schedule, because it depends on the project schedule they maintain.

Measuring what has been understood and what has been done

Measurement covers three levels. The first is reach: the message has gone out, it has been opened, the meeting has taken place. This level only establishes that the plan has been carried out.

The second is understanding: do people know what changes for them, and when? A few questions put to a sample, feedback from managers and the requests received through the feedback route answer this. Requests about a point that the messages were supposed to settle show that this point has not got through.

The third is action: have the recipients done what was asked of them by the planned date, for example signing up for training or checking their data?

What a poor result triggers is decided in advance: a new message from another sender, a meeting, intervention by the sponsor when a line of management does not relay. The project manager reports on it to the steering committee.

Where the project communication plan stops

The plan informs, explains and collects questions. On its own, it does not change the way people work. That result falls under a broader set-up, that of change management, of which communication is one of the workstreams and whose other workstreams our service page describes.

Nor should the plan be confused with the reports sent to the steering committee, which fall under project governance. The ISO 21502:2020 standard, which provides guidance on project management, separates these subjects into distinct practices: stakeholder engagement (7.12), communication management (7.13), organisational and societal change management (7.14) and reporting (7.15). For communication, it distinguishes planning, distributing information and monitoring the effect of communications.

When the feedback route brings back repeated objections rather than questions, the subject has changed in nature: our article on resistance to change offers a diagnosis.

For a project already launched without a plan, the first step remains the same. Draw up the list of audiences with two or three people from the field, and note for each the next deadline that concerns it: the messages to write first follow from this.

FAQ

Frequently asked questions

Another question? Ask us

What is a project communication plan?

A project communication plan is the document that sets, for each audience affected by a project, the messages to be sent to it, their sender, the channel used and the sending date, together with how to check that the message has been understood. It most often takes the form of a table, kept up to date by the project team from launch to closure.

What does a project communication plan contain?

It contains five elements, built in this order: the list of audiences and what changes for each, a core set of messages adapted for each audience, the matrix that links each message to a channel, a sender and a feedback route, a schedule tied to the project's milestones, and a few indicators of reach, understanding and action. Each line of the plan bears the name of an owner.

Who writes a project's communication plan?

The project manager is accountable for it, because the plan depends on the schedule they maintain. The writing can be entrusted to a project communication officer, to the change management lead or, on a programme, to the programme office. The sponsor approves the common messages, and each business department approves those addressed to its teams.

At what point in the project should the communication plan be built?

From the framing stage, for the list of audiences and the common messages, which depend on the project's objectives and its effects on the teams. Channels and schedule are refined once the project schedule has been established, then revised at each milestone. A plan written as go-live approaches boils down to an announcement, made too late for the teams' questions to have any bearing on the project.

Is a project communication plan enough to get a new tool adopted?

No. The plan informs, explains and collects questions. Changing a way of working also requires an impact analysis by population, user training, the support of front-line managers and monitoring of actual use after go-live. Communication is one of the workstreams of change management, and the communication plan is its instrument.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.