Monitor Communications

Six Reports, Zero Awareness

Six status reports. Every Friday, without exception, sent to the full stakeholder distribution list. The project is in week seven, and a key stakeholder, the department head whose team will be most affected by the go-live, is sitting across from you saying "I had no idea this was happening." You sent the reports. They are in your outbox with timestamps. The communication happened. And yet, somehow, it didn't. Monitoring communications is the process that explains how this is possible, and more importantly, what to do about it before a stakeholder is surprised in a steering committee meeting by something that was in the weekly update three weeks running.

Sending Is Not Communicating

The most common failure in project communications is treating sending as equivalent to communicating. It is not. Sending is broadcasting. A message goes out. Communication is a loop: the message reaches someone, they understand it, and they respond in a way that confirms understanding. The status report in the outbox is not a communication event. The stakeholder who read it, understood the implications for their team, and confirmed they have no concerns about the go-live timing, that is a communication event. The difference between those two descriptions is precisely the gap that monitoring communications addresses.

Every communication plan that was built during planning assumed that the communications described in it would actually work. The plan said weekly status reports to the steering committee. It did not say "weekly status reports that get read, understood, and acted on by the steering committee." That second formulation is the actual goal, and the only way to know whether it is being achieved is to check. Monitoring communications means verifying that the information is reaching the people who need it in a form they can use. That is a different and more demanding standard than confirming that the emails were sent.

The Silent Stakeholder

One of the most reliable warning signs in project communications is a stakeholder who goes quiet. They were active in early meetings. They replied to the first few status updates. Now three weeks have passed with no response. There are several possible explanations: they are busy and trust the project is going well, they have a concern and are avoiding the conversation, they have mentally disengaged from the project, or they have not been reading the communications at all. Each explanation requires a different response. Treating silence as contentment is a significant assumption, and it is almost always the wrong one when the silent stakeholder has meaningful influence over the project's outcome.

The appropriate response to a stakeholder who has gone quiet is a direct conversation, not another email on the distribution list. A brief check-in, asking how the project communications are working for them, often surfaces the real picture in under ten minutes. The busy stakeholder will say they've been scanning but not reading in detail. The concerned stakeholder will use the opening to raise something they had not wanted to put in writing. The disengaged one will reveal that the reports arrive at a time when they are not accessible or in a format that doesn't fit how they consume information. All of that is useful. None of it arrives through the status report that prompted no reply.

One distinction worth keeping clear: if the message is not reaching them, the communications plan needs updating. If they understand the message but no longer support the project, the stakeholder engagement approach needs attention. Those are different problems with different responses. Communication failure and engagement failure can look identical from the outside, which is why the direct conversation matters: it lets you tell which one you are actually dealing with.

What You Are Actually Monitoring

Monitoring communications means tracking whether the communication management plan is producing the outcomes it was designed to produce. Are the right stakeholders receiving the right information at the right frequency? Are reports being read or at least acknowledged? Are meeting decisions being documented and acted on? Are action items being followed up at the next meeting, or disappearing after they are assigned? Are escalation paths being used when situations warrant them, or is the team managing upward issues informally in ways that leave the sponsor uninformed?

The question the monitoring process is answering is not whether communications are going out on schedule. It is whether the project's information is reaching the people who need it in a form that allows them to play their role in supporting the project. A stakeholder who needs to make a resource decision and doesn't know the project needs it cannot make that decision. A sponsor who doesn't understand the magnitude of an issue because it was buried in paragraph seven of a twelve-paragraph weekly update cannot respond appropriately. Monitoring is about the result of the communication, not the activity of sending it.

A weekly pass through these signals takes under five minutes and often surfaces a problem before it compounds:

• Are key reports being acknowledged or responded to?
• Are critical updates reaching the right person in a form they understand?
• Are action items being closed, or are the same items aging from meeting to meeting?
• Are meeting decisions documented and referenced in subsequent communications?
• Have any high-influence stakeholders gone silent for more than two reporting cycles?
• Are escalation paths being used when situations require them?
• Are reports being forwarded with questions like "what does this mean?" (a sign the format is not working)?

Warning signs that communication has broken down are usually visible before a stakeholder is surprised in a meeting: a stakeholder asks questions that were answered in writing two weeks earlier; a decision is reopened because the prior decision was not understood by all parties; a high-influence stakeholder stops attending update meetings without explanation; or action items are missed by the same person more than once. Any of these is worth a direct conversation before the next report goes out.

When confirmation that information landed is genuinely important, close the loop deliberately:

When the Plan Is Not Working

If monitoring reveals that communications are not landing effectively, the response is to update the communication management plan. The plan is not fixed. It reflects the best thinking during planning about how to keep stakeholders informed. If that thinking turns out to be wrong about a particular stakeholder or group, the plan should change to reflect what actually works. Maybe the weekly written report is too dense for the audience it is intended to reach. A one-page executive summary with the full report attached might get read where the full report does not. Maybe a key stakeholder group would engage better with a thirty-minute monthly conversation than a written update. Maybe action items need to go out within the hour after a meeting rather than the next day.

The format, the frequency, and the channel are all variables, not fixed commitments. What is fixed is the goal: the right people have the information they need to play their roles in the project. If the current approach isn't producing that outcome for a particular stakeholder, the approach should change. This is not a failure of the original plan. It is a reasonable update based on what monitoring revealed. The PM who adjusts communication methods based on what is actually working is doing exactly what the monitoring process is designed to support.

The outputs of monitoring communications are practical and specific: updates to the communications management plan, recorded changes to stakeholder communication preferences, issue log entries for escalation path failures or unacknowledged critical decisions, action item follow-up additions to the next meeting agenda, and format or frequency changes for reports that are consistently not producing the right response. None of these require a formal document revision. Most require a note in the existing plan and a conversation.

The Smallest Discipline With the Largest Payoffs

Monitoring communications requires less time than almost any other monitoring process on the project. It requires one standing question added to check-ins with key stakeholders: is the information you're receiving giving you what you need? It requires a periodic review of whether action items from recent meetings are being tracked and completed. It requires attention to whether the silent stakeholders in the distribution list have gone too long without engagement. The overhead is small. The payoffs are large, because a stakeholder who is informed and engaged at the right moments is a different kind of supporter than one who is surprised in a steering committee meeting by something that appeared in a report they never read. The loop that closes is the one that protects the relationship, and it takes very little effort to close when the PM makes it a habit.

What's Next

The next chapter, Monitor Risks and Control Procurements, addresses two monitoring processes that are often allowed to slip into passivity: the risk register that was built with care during planning and then left untouched through execution, and the vendor relationship that is managed less formally as the project gets busy and time pressure mounts.

Reflect

• In your current project, how do you confirm that key stakeholders have actually received and understood critical updates, rather than just that the emails were sent? What would change if you checked explicitly once a month?
• Think of a stakeholder who went quiet on a recent project. What turned out to be the reason, and how long did it take to surface? What would a direct conversation in week two have cost versus what you eventually paid to recover the relationship or the decision?
• Which formats in your communication plan are actually being read and acted on, and which are being received but ignored? When did you last verify the difference by asking directly?
• What is the longest an action item has survived without follow-up in your recent projects? What does that number tell you about whether your meeting communications are closing loops or just recording discussions?