← Insights

Projects

A communication plan people actually follow

July 2026 · 6 min read

Almost every project writes a communication plan, and almost every one is abandoned by week three. It is written in a burst of good intentions at kickoff - a tidy grid of who gets told what - filed in a shared drive, and never opened again. The updates then happen the way they always did: when someone remembers, or when someone complains. Which means the plan did not fail because it was wrong. It failed because it was static, and a static plan cannot tell you what is due today.

A communication plan people actually follow is not a better-worded grid. It is one that runs its own rhythm - so that keeping it is easier than ignoring it.

Start with the four columns that matter

Before any automation, get the thinking right. Every line of a comms plan answers four questions. Who hears it - the audience, whether that is the steering group, the delivery team or an affected department. What they hear - the message, pitched at their level, because a board update and a stand-up are not the same content. How it reaches them - the channel, email or meeting or report or dashboard. And how often - the cadence, from a weekly stand-up to an annual review.

The single most common mistake is pitching the wrong content at the wrong audience: drowning executives in operational detail they will not read, or starving the delivery team of the context they need. Match the message to the audience first, and everything else is scheduling.

Cadence is the part that slips

The four questions are easy to answer once. The hard part - the part that kills the plan - is the fourth one over time. A weekly update and a monthly report and a quarterly review all live on the same plan, each on its own clock, and holding all those clocks in your head is exactly the job humans are worst at. So the updates drift: the weekly becomes fortnightly, the monthly gets skipped in a busy month, and by the time anyone notices, a stakeholder is annoyed and trust has leaked away.

The fix is to give each cadence a length in days behind the scenes - weekly is 7, fortnightly 14, monthly 30, quarterly 90, annually 365 - and let the plan calculate the next-due date from the day each update last went out. This one design choice is what makes weekly comms actually work. A plan that thinks only in whole months cannot schedule a stand-up; a plan that counts in days can carry a weekly and an annual on the same sheet, each with its own honest countdown.

Let the plan flag itself

Once next-due is a calculation rather than a memory, status becomes automatic. Each line reads its next-due date against today and labels itself: on track, due soon, or overdue. Now the plan is doing the remembering. You are not scanning a grid trying to reconstruct what you owe whom; you open it and the overdue lines are already coloured, sorted, waiting. The board is never stale, because status is a formula off the last-sent date, not a column you keep forgetting to refresh.

Roll that up and two views do the managing. A dashboard - total comms, and how many are overdue, due soon and on track - gives the one-glance health of your communications. A forward schedule - what is overdue, what falls due in the next seven, fourteen and thirty days - is your actual worklist for the week. You stop reacting to complaints and start working ahead of them.

Building one that survives

• Keep it to the communications that matter. A plan with forty lines is as unfollowable as no plan. List the updates that genuinely need a rhythm, not every message you might ever send.
• Match message to audience deliberately. Right content, right people - the rest is just timing.
• Record the send date every time. The whole engine runs off it; a next-due date is only as good as the last-sent date behind it.
• Open the schedule before every check-in. Let the plan tell you what is due rather than trusting yourself to remember it.

A comms plan is working when nobody is remembering it - the next-due dates, the overdue flags and the weekly worklist are all calculated, and keeping the plan is less effort than letting it slip.

That is the whole difference between a plan that is written and a plan that is followed. The written one relies on discipline you will not always have; the followed one relies on a countdown that never forgets. Build the second kind and your stakeholders stop wondering when they will next hear from you - because the answer is always on the sheet, and always on time.