I.8 — Plan and Manage Communication

I.8 · Last updated: 24/08/2026

Where this task sits

I.8 — Plan and Manage Communication is the final task in the People domain of the 2026 ECO. The domain carries 33% of the exam across eight tasks.

It has six enablers:

• Define a communication strategy
• Promote transparency and collaboration
• Establish a feedback loop
• Understand reporting requirements
• Create reports aligned with sponsors and stakeholder expectations
• Support reporting and governance processes

Three of the six concern reporting. The ECO describes communication not as a conversational skill but as an organizational flow.

🔴 Do not trust the number

This number both changed hands in 2026 and saw its old subject move to another domain:

• In 2021, I.8 was negotiate project agreements. In 2026 that topic sits inside II.5 — Plan and Manage Procurement and now lives in the Process domain.
• In 2026, I.8 is planning and managing communication.

So an older question tagged "I.8" is most likely about negotiation — and because the topic changed not only number but domain, anyone building a study plan around domain weights gets it wrong twice. The same double shift affects I.7.

Domain I came down to eight tasks in 2026; older numbers ran at least as far as I.12. Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

Communication is a third of the Stakeholders domain

PMBOK® 8 has no separate performance domain for communication — it sits inside Stakeholders. But three of that domain's seven processes are communication outright (PMBOK® 8, Guide p.9):

Plan Communications Management (planning) · Manage Communications (executing) · Monitor Communications (monitoring and controlling)

The trio covers the ECO task title's "plan and manage" and adds a third verb: monitor. Communication is not set up and left; its effect is measured.

Where the plan comes from is written down too: among the outputs of Identify Stakeholders are updates to the communications management plan (PMBOK® 8, Guide p.71). The communication strategy derives from stakeholder analysis — you cannot build one without knowing who needs what. See I.4 — Engage Stakeholders.

The three communication methods

The most frequent distinction on this task, and the book defines all three separately (PMBOK® 8, Guide p.152):

• Interactive communication — a multidirectional exchange of information in real time between two or more parties. Meetings, phone calls, instant messaging, some forms of social media, and videoconferencing.
• Push communication — sent or distributed directly to specific recipients who need the information. This method ensures the information is distributed but does not ensure that it reaches or is understood by the intended recipient. Letters, memos, reports, emails, faxes, voicemails, blogs, and press releases.
• Pull communication — used for large, complex information sets or large audiences, requiring recipients to access content at their own discretion, subject to security procedures. Web portals, intranet sites, eLearning courses, lessons learned databases, or knowledge repositories.

The caveat inside the push definition decides exam answers: sending an email is not communicating. The option that says "I informed them, I sent an email" does not establish that the information landed.

The feedback loop

The ECO makes "establish a feedback loop" its own enabler. The book's counterpart is in the communication model.

A communication model is a description, analogy, or schematic used to represent how the communication process will be performed for the project. Models can represent the process in its most basic linear form (sender and receiver) or in a more interactive form that encompasses the additional element of feedback (PMBOK® 8, Guide p.153).

The two additional steps in the interactive model are (PMBOK® 8, Guide p.154):

• Acknowledge — upon receipt of a message, the receiver may signal receipt, but this does not necessarily mean agreement with or comprehension of the message — merely that it has been received.
• Feedback/response — when the received message has been decoded and understood, the receiver encodes their thoughts and ideas into a message and transmits it back to the original sender. If the sender perceives that the feedback matches the original message, the communication has been successful.

Those two steps are the full definition of a "feedback loop." And the distinction between acknowledgment and understanding is the measure that eliminates "I got a read receipt" answers.

Reporting requirements

The ECO's three reporting enablers connect to the project's measurement side.

Work performance reports are an output of the Monitor and Control Project Performance process, whose tools include project dashboards, visual controls, and information radiators (PMBOK® 8, Guide p.27).

Those three work differently, matching the three methods above: a dashboard is pulled, a radiator is pushed, a meeting is interactive.

What gets reported is settled in advance: specific work performance metrics for scope, schedule, budget, and quality are defined at the start of the project as part of the project management plan (PMBOK® 8, Guide p.144). For the measurement side in detail, see II.9 — Evaluate Project Status.

The ECO's last enabler ties reporting to governance: support reporting and governance processes. Two of governance's three core components are already signaling and feedback mechanisms — see III.1 — Define and Establish Project Governance.

Transparency and collaboration

The ECO's second enabler asks not for a tool but for a posture, and its counterpart is on the principles side.

For the Build an Empowered Culture principle, the project environment should promote mutual trust, and there should be full clarity on individual roles, responsibilities, team agreements, and guiding processes. These factors enable individuals to work together and produce synergistic effects from their interactions (PMBOK® 8, Standard p.53).

The approach shifts the expectation too: in projects using adaptive or hybrid approaches, the need for ongoing feedback is greater because project teams are exploring and developing product elements within specific increments due to ambiguity and complexity (PMBOK® 8, Standard p.25).

The Guide gives examples from both ends: on one side daily coordination meetings and dedicated communication platforms for real-time collaboration; on the other, formal project updates disseminated by biweekly email on a large-scale ERP project (PMBOK® 8, Guide p.76).

Translated for the exam: "more communication is better" is wrong. The right answer tailors the form of communication to the approach and the stakeholder.

Why this is the domain's last task

The People domain draws a circle, and this task closes it.

The domain opens with a common vision (I.1), teaches managing conflict (I.2) and leading the team (I.3), then turns outward: engage stakeholders (I.4), align their expectations (I.5), sustain that alignment (I.6). It then makes knowledge transferable (I.7) — and ends with the carrier of all of it, communication.

The ordering is also a reading key: on People domain questions, the right answer is almost never a technical move on its own. The entire domain measures who you talk to, when, and in what form.

The Guide's shortest summary of the domain says the same: while having relevant technical project management skills is important, possessing the interpersonal and leadership skills to work effectively with stakeholders is just as important, if not more so (PMBOK® 8, Guide p.67).

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p.X
• A Guide to the Project Management Body of Knowledge — cited as Guide p.X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page explains the book; it does not replace it.