Monitor Communications in PMBOK 8 — Complete Guide

Article updated in March 2026 for the PMBOK® Guide — Eighth Edition.

Monitor Communications in PMBOK 8 — Complete Guide

Formerly known as: Monitor Communications (PMBOK 6)

A project team had been sending weekly status reports to all stakeholders for six months. The reports were accurate, well-formatted, and consistently on time. At the six-month review, the sponsor asked about the status of a specific deliverable that had been prominently featured in three consecutive status reports. The sponsor had no recollection of the information. Further investigation revealed that the sponsor’s team had been auto-filing the status reports to a folder that was never read. The reporting had been consistent; the communication had been completely ineffective.

This is the failure that Monitor Communications in PMBOK 8 is designed to detect and correct. Monitor Communications is the process of ensuring the information needs of the project and its stakeholders are met. The key benefit of this process is the optimal information flow as defined in the communications management plan and the stakeholder engagement plan. This process is performed throughout the project.

The distinction between Manage Communications and Monitor Communications parallels the distinction between Manage Stakeholder Engagement and Monitor Stakeholder Engagement: Manage executes the activities; Monitor assesses whether those activities are achieving their intended outcomes. Sending communications is an activity. Ensuring that information needs are actually met is an outcome. Monitor Communications is the process that maintains focus on the outcome, not just the activity.

For PMP candidates, this is Stakeholders Process 7 of 7. For practitioners, it is the quality assurance function for the project’s entire information ecosystem — the mechanism that ensures communications are not just produced and distributed, but actually received, understood, and meeting the information needs they were designed to meet.

• 1. What Is the Monitor Communications Process
• 2. Why Use the Monitor Communications Process
• 3. Inputs, Tools & Techniques, and Outputs (ITTO)
• 4. Step-by-Step Application Guide
• 5. When to Apply This Process
• 6. Real-World Examples
• 7. Templates and Downloads
• 8. Five Common Errors
• 9. Tailoring This Process
• 10. Process Interactions
• 11. Quick-Application Checklist

1. What Is the Monitor Communications Process

According to the PMBOK® Guide — Eighth Edition, Monitor Communications is the process of ensuring the information needs of the project and its stakeholders are met. The key benefit of this process is the optimal information flow as defined in the communications management plan and the stakeholder engagement plan. This process is performed throughout the project.

The process assesses whether information is flowing as planned — whether stakeholders who need specific information are receiving it, understanding it, and using it to inform their decisions and actions. When monitoring reveals that information needs are not being met (information is not reaching its intended audience, or information is reaching its audience but is not being understood or acted upon), Monitor Communications triggers the adjustments to communications methods, formats, channels, or frequency needed to close the gap.

Monitor Communications is closely linked to Monitor Stakeholder Engagement: communication effectiveness and stakeholder engagement are mutually reinforcing. Stakeholders who are not receiving the information they need become disengaged; stakeholders who are disengaged stop reading or attending the communications directed at them. Poor communications monitoring and poor engagement monitoring tend to co-occur and compound each other.

2. Why Use the Monitor Communications Process

Direct benefits

• Information gap detection: Systematic monitoring identifies information gaps — stakeholders who are not receiving critical information, information needs that the communications plan has not addressed, or communication channels that are not reaching their intended audience. Information gaps that are identified early can be corrected before they affect stakeholder decisions or project outcomes.
• Communication effectiveness improvement: Monitoring provides the feedback loop that allows continuous improvement of communication quality, format, and timing. A status report format that is consistently ignored can be redesigned; a meeting format that consistently runs over time can be restructured; a communication channel that stakeholders are not using can be replaced with one they will use.
• Stakeholder information satisfaction: Monitoring stakeholder information satisfaction — are stakeholders’ information needs actually being met? — is directly connected to stakeholder engagement. The PMBOK 8 Check Results for the Stakeholders domain explicitly includes reviewing the communications management plan periodically and tailoring it appropriately based on the needs of stakeholders. Monitor Communications is the process that drives this periodic review.
• Plan alignment validation: As the project evolves, the information needs in the communications management plan may no longer reflect actual stakeholder needs. Monitor Communications validates that the plan remains aligned with reality, and triggers plan updates when drift is detected.

3. Inputs, Tools & Techniques, and Outputs (ITTO)

Inputs explained

Project documents — Project communications: The actual communication artifacts produced and distributed during the project — status reports, meeting minutes, presentations, announcements, repository updates. Reviewing these communications as inputs to monitoring allows assessment of: was the communication plan actually executed (were all planned communications produced and distributed)? Were communications accurate and complete? Were communications appropriate for their intended audience? Were communications distributed through the right channels to the right people?

Work performance data: In the communications monitoring context, work performance data includes measurable indicators of communication system performance: email open rates (if available from the communication system), meeting attendance rates, document access frequency in the project repository, response times to information requests, and feedback submission rates from stakeholder communication channels. These data points provide objective indicators of communication effectiveness that supplement the qualitative assessment from observation and conversation.

Project management plan — Communications management plan: The communications plan is the performance standard against which monitoring assesses actual communication activity and outcomes. Were the committed communication activities executed on schedule? Is the communication format serving its intended purpose? Are the information sensitivity controls being observed? The plan defines what communications effectiveness looks like; monitoring assesses whether that standard is being met.

Tools & Techniques explained

Interpersonal and team skills — Observation/conversation: The most direct and often most valuable communications monitoring technique is structured observation and informal conversation with stakeholders and team members. Direct questions (“Is the weekly status report giving you the information you need to make the decisions I’m asking you to make?” or “Are you finding the project repository organized in a way that lets you find what you need?”) provide communications effectiveness feedback that no passive monitoring metric can provide. Observations in meetings (are participants referencing the distributed pre-read? are decisions being made on accurate current information? are attendees confused about issues that should have been communicated to them?) provide behavioral indicators of whether communications are achieving their intended effect.

Project management information system: The PMIS provides technical monitoring capabilities: access logs that show who is accessing which documents (and who is not accessing documents they should be reading), communication distribution records that confirm delivery, version history that shows whether documents are being maintained, and system usage metrics that indicate whether the PMIS itself is being used as the primary information repository or whether shadow systems and informal channels are replacing it.

Data representation — Stakeholder engagement assessment matrix: The same tool used in stakeholder monitoring is applicable to communications monitoring: mapping current information satisfaction levels against desired information satisfaction levels for each stakeholder. A stakeholder who has moved from Neutral to Resistant may be communicating (through their behavior if not explicitly) that their information needs are not being met. Communication monitoring should integrate with engagement monitoring to detect these co-occurring indicators.

Outputs explained

Work performance information: The processed output of communications monitoring — the assessment of whether information needs are being met, which communication channels and formats are effective, what communication gaps exist, and what changes are recommended. Work performance information from communications monitoring is a component of the overall project status reporting to the sponsor and includes: communication plan compliance (are all planned communications being executed?); communication effectiveness assessment (are key communications achieving their intended outcomes?); identified communication gaps or failures; and recommended adjustments to communications methods, formats, or channels.

Change requests: When communications monitoring identifies that the communications management plan requires material changes — new communication channels are needed, existing formats need significant revision, new stakeholder information needs require additional communication commitments — formal change requests are raised to update the plan formally rather than allowing informal plan drift.

Project management plan updates: Minor adjustments to the communications management plan (format refinements, frequency adjustments, channel additions) that fall within the project manager’s authority can be implemented without formal change requests but should be documented as plan updates. The stakeholder engagement plan may also require updates when communications monitoring reveals engagement-related information gaps.

4. Step-by-Step Application Guide

Step 1 — Define communications effectiveness criteria

Before monitoring can be effective, there must be a clear definition of what “effective communication” looks like for each communication type. Define effectiveness criteria for key communications: for the sponsor status report, effectiveness means the sponsor can make the weekly decision requested without requiring follow-up calls. For team meeting minutes, effectiveness means all action items are documented, assigned, and tracked to completion. For the early access community update, effectiveness means measurable community engagement (responses, reactions, referrals). Without criteria, monitoring is subjective assessment; with criteria, it is evidence-based evaluation.

Step 2 — Monitor communication plan execution compliance

Verify that all planned communications are being produced and distributed on schedule. Track communication compliance on a simple dashboard: which communications were due this period, which were delivered on time, which were late, and which were missed. Consistent non-compliance is a leading indicator of either insufficient capacity (the responsible parties cannot produce communications at the planned frequency alongside their other commitments) or insufficient value (communications that no one values tend to deprioritize themselves). Both root causes require action.

Step 3 — Assess communication effectiveness through stakeholder feedback

Collect structured feedback from key stakeholders on communications effectiveness. A brief periodic survey (3-4 questions, maximum 5 minutes to complete) can generate valuable data: “Is the weekly status report giving you the information you need?” “Are there information needs that are currently not being addressed?” “Is the current meeting cadence appropriate for your involvement level?” These questions should be asked at project milestones or phase boundaries if not regularly, and whenever monitoring observations suggest potential communication effectiveness problems.

Step 4 — Analyze PMIS usage patterns

Review project management information system usage data: who is accessing the project repository, which documents are being accessed, and whether the PMIS is the primary information source for team members and stakeholders or whether shadow systems are developing alongside it. Shadow systems (parallel spreadsheets, duplicate email chains, informal shared drives that bypass the official project repository) are a symptom of PMIS inadequacy — either the system is too difficult to use, not accessible to the people who need it, or not containing the information stakeholders actually need.

Step 5 — Identify and address communication failures

For any communication failures identified (information not reaching intended audience, critical information not understood, communication commitments not executed), conduct a root cause analysis and implement corrective actions. Was the failure due to channel selection (using email for time-sensitive information when the recipient’s email volume means they check it twice a week)? Was it due to format (using dense text for an audience that needs visual communication)? Was it due to timing (sending information after the decision moment had already passed)? Address the root cause, not just the symptom.

Step 6 — Update communications and engagement plans

Translate monitoring findings into plan updates. A communications management plan that is updated based on monitoring evidence is a continuously improving management tool. A communications management plan that is maintained unchanged despite clear evidence that elements are not working is a governance failure.

5. When to Apply This Process

• Throughout execution, on a defined assessment cadence: Communications monitoring should have a defined schedule, aligned with project milestones or reporting periods. At minimum, a formal communications effectiveness review should occur at each phase boundary. More frequent informal monitoring — through observation, conversation, and PMIS usage review — should be continuous.
• When stakeholder engagement issues surface: Stakeholder disengagement, resistance to project communications, or complaints about information overload or under-communication are all triggers for a focused communications monitoring review.
• After significant project changes: Scope changes, team changes, sponsor changes, and major risk events all create potential communication gaps between the current communications plan and the changed project reality. Each significant project change should trigger a communications plan compliance check.

6. Real-World Examples

Example 1: Project Phoenix — Website Launch

Context: PM Alex Morgan, PMP. 90-day website launch for TechCorp. Budget: $72,250.

How Monitor Communications was applied: Alex’s communications monitoring was embedded into the sprint retrospective process. At each biweekly retrospective, one of the standing questions was: “Is there any project information that team members or stakeholders need but are not currently receiving?” This simple question surfaced two actionable insights over the project’s lifecycle. At sprint 4, the QA engineer mentioned that she was not receiving API documentation from the development team in advance of her testing cycles — she was testing integrations without full documentation, which was causing inefficiency. At sprint 9, the sales director’s assistant raised (via the sales director) that the launch preparation instructions for the sales team had not yet been communicated — the team was assuming launch preparation information would be communicated when the marketing director remembered to forward it.

Both issues were addressed immediately: API documentation sharing became a sprint ceremony deliverable (developer to QA handoff, confirmed in sprint planning), and launch preparation communications for the sales team were added to the formal communications plan with a scheduled distribution date three weeks before go-live. Neither gap was visible from the communications plan itself — they were only visible through active monitoring.

Example 2: Project ProjectAdm — SaaS PM Platform

Context: PM Eduardo. 18-month SaaS platform development.

How Monitor Communications was applied: Eduardo conducted a quarterly communications effectiveness review with three components. Component 1: PMIS usage audit — reviewing which project documents were being accessed, by whom, and how recently. At month 9, the audit revealed that the compliance documentation section of the repository had not been accessed by any team member in 47 days, even though active compliance work was in progress. Investigation revealed that the compliance work was being tracked in a parallel spreadsheet maintained by the lead developer — a shadow system that had emerged because the PMIS’s document organization made compliance documents difficult to find. Eduardo restructured the repository’s compliance section and retired the shadow spreadsheet, consolidating all project information into the single authoritative source.

Component 2: Stakeholder satisfaction pulse (three-question survey to all active stakeholders every quarter). At month 12, the board of advisors’ average satisfaction with the strategic briefing format was 3.2/5.0, with specific feedback that the briefings covered operational details but not enough strategic positioning information. The quarterly briefing format was revised to open with a 10-minute “strategic landscape” segment (competitive developments, market signals, strategic implications) before the operational review. Board satisfaction in the month 15 survey: 4.6/5.0.

Component 3: Communication plan compliance review (were all planned communications executed on schedule?). The month 6 review identified that the early access community update was being published 2-3 days late consistently due to the single-person dependency on Eduardo for final approval. A delegated approval process was established: the lead developer could approve community updates for release; Eduardo would review the next business day and raise corrections if needed. On-time publication rate improved from 61% to 94%.

7. Templates and Downloads

• Project Communications — Software Development — Includes communications monitoring checklist and stakeholder feedback survey templates.
• Stakeholder Engagement Plan Template — Includes communications effectiveness section for integration with engagement monitoring.
• Status Report Template — Includes communications status section for regular reporting on communication plan compliance.

8. Five Common Errors

Error 1: Monitoring communication activity volume rather than information need satisfaction

The most common communications monitoring error is measuring how many communications were produced and distributed rather than whether those communications satisfied the information needs they were designed to meet. A high volume of communications that stakeholders are not reading or acting on is a communication failure, not a communication success.

Error 2: Relying on passive observation rather than active feedback collection

Passive observation (noting whether stakeholders seem engaged in meetings) is an insufficient substitute for direct feedback collection. Stakeholders who have communication complaints often do not volunteer them — they quietly disengage or develop workarounds. Active feedback collection (direct questions about information satisfaction) surfaces issues that passive observation consistently misses.

Error 3: Ignoring PMIS usage data as a monitoring signal

Project management information system usage data is one of the most objective indicators of communications effectiveness. Document access logs, repository usage patterns, and shadow system development are all measurable signals of whether the official communication infrastructure is serving its intended purpose. Ignoring this data source leaves communications monitoring incomplete.

Error 4: Detecting communication failures but not implementing corrective actions

Communications monitoring that produces findings but no corrective actions is analysis without management value. When monitoring identifies that a communication format is not effective, a channel is not reaching its audience, or a specific information need is not being met, the immediate obligation is to implement a corrective action — not to note the finding and continue the ineffective practice.

Error 5: Treating communications monitoring as separate from engagement monitoring

Communication effectiveness and stakeholder engagement are inseparable. Stakeholders who feel their information needs are not being met tend to disengage; disengaged stakeholders stop actively consuming communications. Communications monitoring and engagement monitoring should be integrated activities, each informing the other, rather than separate parallel processes that operate without cross-referencing their findings.

9. Tailoring This Process

• Project duration: Short projects (under 3 months) may conduct communications monitoring only at project midpoint and at close. Longer projects should conduct formal monitoring reviews at each phase boundary, with continuous informal monitoring throughout.
• Stakeholder complexity: Projects with a small, stable, well-aligned stakeholder group can use lightweight communications monitoring: a simple question at the end of each status meeting (“Is there information you need that you’re not currently getting?”) may be sufficient. Large, complex, multi-cultural stakeholder environments require more structured, multi-method monitoring approaches.
• Digital-first environments: Projects operating primarily through digital collaboration tools have access to quantitative usage data that can supplement qualitative assessment. Leverage PMIS analytics, collaboration platform usage statistics, and email open rates (where available) to provide data-driven communications effectiveness indicators.
• Agile projects: The retrospective ceremony in agile frameworks is the natural home for communications monitoring in sprint-based projects. A standing retrospective item on communication effectiveness — both within the team and with external stakeholders — integrates monitoring into the rhythm of agile execution without requiring separate formal review sessions.

10. Process Interactions

• Manage Communications (Stakeholders Process 6): Monitor Communications assesses the effectiveness of the communication activities that Manage Communications executes. Together they form the execution-control cycle for project communications, mirroring the Manage/Monitor pattern in stakeholder engagement.
• Plan Communications Management (Stakeholders Process 5): Monitoring findings drive updates to the communications management plan. The quality of the plan continuously improves through the monitoring-feedback loop.
• Monitor Stakeholder Engagement (Stakeholders Process 4): The two monitoring processes share data and insights — communication effectiveness monitoring informs engagement level monitoring, and vice versa. They should be executed as integrated activities.
• Risk Domain: Communication failures identified through monitoring may require risk register entries: a key stakeholder not receiving critical information is a risk to decision quality; a communication channel failure at a critical project moment is a risk to timeline and stakeholder alignment.
• Initiate Project or Phase: Phase boundary communications — notifications, gate review presentations, authorization requests — are high-stakes events where communications monitoring findings from the current phase inform communications improvements for the next phase.
• Integrate and Align Project Plans: Communications plan updates from monitoring must be integrated with the overall project management plan through the integrated change control process.
• PMBOK 8 Process Index: Complete process map for all 11 Finance and Stakeholders domain processes and their interactions.

11. Quick-Application Checklist

• ☐ Communications effectiveness criteria defined for each key communication type
• ☐ Communication plan execution compliance reviewed — all planned communications delivered on schedule
• ☐ Stakeholder feedback collected on information satisfaction
• ☐ PMIS usage data reviewed — shadow systems identified and addressed
• ☐ Document access patterns analyzed for information consumption evidence
• ☐ Meeting effectiveness assessed — agenda compliance, decision quality, action item tracking
• ☐ Communication failures documented and root-caused
• ☐ Corrective actions implemented for identified communication failures
• ☐ Communications management plan updated based on monitoring findings
• ☐ Stakeholder register updated with communications-related observations
• ☐ Integration with engagement monitoring completed — shared findings reviewed
• ☐ Lessons learned documented for significant communications monitoring insights

Call to Action:

References

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Eighth Edition. Newtown Square, Pennsylvania, USA: Project Management Institute, 2025.

PMBOK Guide 8: The New Era of Value-Based Project Management. Available at: https://projectmanagement.com.br/pmbok-guide-8/

Disclaimer

This article is an independent educational interpretation of the PMBOK® Guide – Eighth Edition, developed for informational purposes by ProjectManagement.com.br. It does not reproduce or redistribute proprietary PMI content. All trademarks, including PMI, PMBOK, and Project Management Institute, are the property of the Project Management Institute, Inc. For access to the complete and official content, purchase the guide from Amazon or download it for free at https://www.pmi.org/standards/pmbok if you are a PMI member.