The Project Communication Plan: A Field Checklist
Ask any project manager whether their project has a communication plan and they will say yes. Ask whether that plan is actively maintained and actually followed, and the answer is usually more hesitant. Communication plans fail not because teams do not write them, but because they write the wrong things — generic matrices that describe process rather than decisions, and that nobody reads after week one.
This checklist covers what a working communication plan actually needs to contain, how to structure it for different audiences, and the practical habits that keep it alive.
The Core Questions Your Plan Must Answer
Before listing communication artefacts, answer these questions for every stakeholder group:
Who needs what information? Not all stakeholders need the same content. A sponsor needs headline status, decisions required, and financial performance. A working-group member needs task-level detail, blockers, and upcoming commitments. Conflating the two produces reports that satisfy neither.
How often? Frequency should match the rate at which decisions need to be made, not the project manager's comfort level. Weekly status updates to a sponsor who has a monthly decision cycle waste time. Daily standups for a team that works in two-week sprints may add overhead without value.
In what format? Written reports, live meetings, dashboards, emails, and one-pagers each serve different purposes. Written reports create a record; meetings create alignment. Choose the format that serves the purpose, not the one that is easiest to produce.
Through what channel? Know where your stakeholders actually pay attention — email, a project management tool, a shared drive, a messaging platform — and use that channel rather than the one that is most convenient for the project team.
Managing Upward, Outward, and Within the Team
Communication on a project moves in three directions, and each requires a different approach.
Upward communication — to sponsors, governance bodies, and executives — must be concise, decision-focused, and forward-looking. Executives are not interested in what happened last week; they want to know whether the project is on track, what decisions they need to make, and what risks are approaching. A one-page status report with a RAG rating, a three-bullet summary, and a clear 'decision required' section outperforms a detailed narrative every time.
Outward communication — to client counterparts, partner organisations, or regulators — requires more care about tone, timing, and what is appropriate to share. Agreements on information handling should be part of the project initiation documentation, not improvised when a sensitive issue arises.
Team communication — standups, working sessions, retrospectives — should be frequent enough to maintain shared situational awareness but structured enough that meetings have a purpose and an outcome. A standup that turns into a problem-solving session has failed its original purpose; defer the deeper conversation and schedule a working session.
Escalation vs. Information: Knowing the Difference
One of the most common communication failures on projects is the confusion between escalation and information sharing. Escalation means a decision or action is required from a higher level of authority — it should be explicit, time-bound, and followed up. Sharing information means a stakeholder is being kept informed but no action is required from them.
Mixing the two erodes trust. If every status report is full of issues 'for awareness', sponsors learn to ignore them. When a real escalation arrives, it does not get the attention it needs. Reserve the escalation channel for genuine escalations, and keep your information updates clean and brief.
Practical Tips for Keeping the Plan Alive
Put a named owner against every communication artefact — not 'the project team', a specific person
Set a calendar reminder to review and update the plan at the end of every project phase
After major scope or stakeholder changes, treat the communication plan as a deliverable that needs to be updated
Ask stakeholders directly whether the communications they receive are useful — most will tell you honestly if you ask
When something goes wrong, send a brief factual update proactively rather than waiting to be asked; silence is always interpreted as bad news
The difference between reporting and communicating is intent. Reporting deposits information; communicating creates shared understanding. A project communication plan that is built around the latter will serve the project far better than one that optimises for frequency and format alone.
XNM Consulting delivers complex projects with structured governance and communication frameworks built in. Learn more about our programme and project delivery services.