PM Excellence Academy
Module 6 of 12 · Communication Planning
Your Planning Process already mapped who needs what, and when. Communication Planning turns that map into a plan for how the team, the consultants, and the client will stay aligned — the plan you carry into the kickoff.
Illustrated module guide · the complete walkthrough · companion to the Quick ReferenceThe problem
Both project managers walked out of Module 5 with a clean plan — scope broken down, priced, sequenced, staffed. One of them also planned how the team would communicate. The other assumed that would take care of itself.
Three weeks in, the second PM’s structural consultant is detailing to a floor plan that quietly changed at a coordination meeting nobody scheduled. The client first hears about a two-week slip when they call to ask about something else.
Nothing in the work plan was wrong. What was missing was a plan for the talking.
A design project is a relay of information between people — and between firms.
The Planning Process sequenced the flow of information between disciplines. But disciplines are people: in your studio, in the consultants’ offices, and across the table from the client. When no one plans how information moves between those people, the technical plan goes stale in the gaps — and you find out at the milestone, not the moment.
?Pause & predict.
A PM emails the full work plan to the team, the consultants, and the client and says “reach out with questions.” What did they just fail to plan?
Floods every channel and CCs the world — mistakes message volume for alignment, so the signal gets lost.
Goes dark in the work — assumes silence is fine and lets consultants design to stale assumptions.
Over-communicates comfort to the client — softens bad news and buries the decision the client actually needs to make.
Designs the cadence up front — the right message, to the right audience, on a set rhythm, with decisions on record.
The reframe
This module is not about being a better talker. It is about building a plan for the talking — the same discipline you just used on the work.
Effective project communication doesn’t depend on charisma. It has the same four properties every time, and every one of them is something you plan, not something you improvise:
You don’t rise to the level of your communication skills. You fall to the level of your communication plan.
The link
The Planning Process didn’t only schedule work. It exposed every point where information must pass between people — every handoff, every interface, every milestone, every decision gate. Read the plan back, and the communication requirements fall right out of it.
| What the Planning Process produced | The communication it requires | |
|---|---|---|
| Pull-plan handoffs — the swim-lane “needs” and “provides” | → | Standing coordination between the disciplines and firms that hand off to each other |
| Consultant interfaces — who provides what, by when | → | A consultant coordination cadence, with a named owner for each interface |
| Milestones — 30 / 60 / 90% deliverables | → | Client review touchpoints, scheduled to the milestone dates |
| Decision gates surfaced by pulling backward | → | Planned client decision conversations — with lead time and options prepared |
| Resource / labor plan — who is staffed, when | → | The internal team roster and its check-in rhythm |
| Earned Value Plan — the measurement baseline | → | The status-reporting cadence, and what gets reported to whom |
Remember Oakhaven. Part B’s pull plan proved that the owner must select a mechanical system about three weeks before 30% Design Development. In communication terms, that single fact is an instruction: schedule a client decision conversation — options ready, cost of delay stated — three weeks ahead of the milestone. The work plan set the date. The communication plan makes the conversation happen.
?Pause & predict.
Part B’s pull plan showed the owner must pick a mechanical system three weeks before 30% DD. In communication terms, what does that one fact tell you to plan?
The method
Every requirement you just derived serves one of three audiences. Plan each one separately — because each needs something different from you.
For each audience, the plan fixes five attributes. That is the whole method — structured communication, applied audience by audience:
| Audience | Cadence | Channel | Decision rights | Record | Owner |
|---|---|---|---|---|---|
| Internal team | Weekly pulse + rolling look-ahead | Stand-up / working session | Approach within scope | Action log | Project Manager |
| Consultant team | Biweekly coordination | Coordination meeting + issue log | Interface & handoff commitments | Minutes + interface log | Project Manager |
| Client | Milestone reviews + decision gates | Formal review; PM as single voice | Scope, fee, and schedule changes | Written summary + decisions | PM (single voice) · PiC |
Make it visible
The cheapest, least dramatic move in the whole module is deciding — before the project starts — who decides what, who is merely informed, and how a problem climbs. Most project conflict is really an un-planned decision right surfacing at the worst possible moment.
| Decision | Decides | Recommends | Informed |
|---|---|---|---|
| Change to scope, fee, or schedule | Client | PM + Principal-in-Charge | Team + consultants |
| Design approach within scope | PM / discipline lead | Team | Principal-in-Charge |
| Consultant deliverable at risk | PM (escalates on impact) | Consultant lead | Client, on lead time |
Then plan the escalation path, and the trigger that fires it:
Escalate on impact to scope, schedule, or fee — and derive the triggers straight from the plan’s constraints. The binding constraint you found in Part B (the over-booked person, the gating decision) is exactly what you plan to raise early, before it becomes a missed date.
?Pause & predict.
A consultant will miss a handoff that gates the 60% milestone. Your communication plan is doing its job if…
The close
Everything above collapses onto a single page: the three audiences, each with its cadence, channel, decision-rights, record, and owner; the decision-rights map and escalation path; and the key client decision dates lifted straight from the work plan. That page is the Communication Plan.
It isn’t filed. It is the second half of what you present at the kickoff — Module 7 — where the plan for the work and the plan for the communication go in front of the team, the consultants, and the client together, so everyone leaves knowing not just what the project is, but how it will talk.
Module 6 throughline
A work plan says what happens. A communication plan says how the team stays aligned while it happens — read it off the work plan, segment it by audience, and carry it into the kickoff.
Back to our two projects. The PM whose consultant never detailed to a dead floor plan — whose client was never surprised — didn’t communicate better. She planned the communication. Same skill, different outcome, because the plan existed before the pressure did.
The Planner opens with the Oakhaven plan you committed in Module 5 and walks you audience by audience — cadence, channel, decision-rights, records — to a one-page Communication Plan you can post and carry into the kickoff. Open the Communication Planner →
Take one live project’s next milestone. Pull one decision gate off its plan, and write the single line of your communication plan it demands: who you’ll talk to, when, and what decision the conversation must produce.