I.8 — Plan and Manage Communication

I.8 · Last updated: 11/10/2026

Communication and reporting defined as one task

I.8 — Plan and Manage Communication is the last task in the People domain of the 2026 ECO. The domain carries 33% of the exam and holds eight tasks, and this one both closes the domain and ties together everything that came before it.

The ECO lists six enablers for the task:

• 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 are directly about reporting. The ECO sees communication as more than a talent for speaking well. It describes a regular, measurable flow of information that runs from the project out to the organization.

The old I.8 was about negotiation

In 2026 this number changed hands, and its old subject moved to another domain as well. In 2021, I.8 meant negotiating project agreements, a topic that now sits inside II.5 — Plan and Manage Procurement in the Process domain. In 2026, I.8 means planning and managing communication.

An older question tagged "I.8" is therefore most likely about negotiation. Because the topic changed domain too, anyone who builds a study plan around domain weights goes wrong twice, and the same double shift happened with I.7. Domain I came down to eight tasks while the old numbers ran to at least I.12. For the detailed breakdown, see what changed in the 2026 PMP exam.

In PMBOK, communication lives in the Stakeholders domain

PMBOK® 8 has no performance domain of its own for communication. The subject sits inside the Stakeholders domain, and three of that domain's seven processes deal with it directly (PMBOK® 8, Guide p.9). Plan Communications Management belongs to planning, Manage Communications to executing, and Monitor Communications to monitoring and controlling.

The three together cover the "plan and manage" of the task's title and add a further step, monitoring. In the book's view communication is never set up and then left to run by itself, since its effect is also measured.

The book also says where the plan comes from. Among the outputs of the Identify Stakeholders process are updates to the communications management plan (PMBOK® 8, Guide p.71). A communication strategy grows out of stakeholder analysis, because you cannot build one without knowing who needs what. For the other end of that link, see I.4 — Engage Stakeholders.

Three methods of communication

The distinction the exam asks about most often in this task is the one between the three methods of communication the book defines (PMBOK® 8, Guide p.152).

Interactive communication is a real-time, multidirectional exchange of information between two or more parties. Meetings, phone calls, instant messaging, some forms of social media, and videoconferencing belong here.

Push communication sends information directly to the specific recipients who need it. Letters, memos, reports, emails, faxes, voicemails, blogs, and press releases are of this kind. The book is explicit about the limit of the method: push communication ensures that the information is distributed, but it does not ensure that the information reaches the intended audience or is understood.

Pull communication is used for large, complex information sets or for large audiences. Recipients access the content at their own discretion, subject to security procedures, through web portals, intranet sites, eLearning courses, lessons learned databases, and knowledge repositories.

The limit placed on push communication often decides an exam question. An email having been sent proves neither that the message arrived nor that it was understood, which is why an option along the lines of "I informed them by email" usually falls short.

The two steps that make a feedback loop

The ECO lists establishing a feedback loop as an enabler of its own, and the book's counterpart is found in the communication model. A communication model is a description, analogy, or schematic showing how the communication process will work on a project. It can show the process in its simplest, linear form (sender and receiver) or in a more interactive form that includes feedback (PMBOK® 8, Guide p.153).

The two steps the interactive model adds give the full definition of a feedback loop (PMBOK® 8, Guide p.154). The first is acknowledge. The receiver may signal that the message has arrived, which does not mean agreeing with it or grasping it; it shows only that the message was received. The second is feedback/response. Once the receiver has decoded and understood the message, they encode their own thoughts into a new message and send it back to the original sender. When the sender sees that this feedback matches the original message, the communication counts as successful.

The difference between acknowledgment and understanding is the yardstick for eliminating answers of the "I got a read receipt" kind on the exam. What proves that communication took place is the meaning coming back to the sender, and mere delivery proves very little.

When reporting is set up, and against what

The three reporting enablers connect to the measurement side of the project. 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). The book defines the purpose of these reports in a single sentence: as physical or electronic representations of work performance information, they are intended to generate decisions, actions, or awareness (PMBOK® 8, Guide p.144).

What gets reported is decided before the work starts. Work performance metrics for scope, schedule, budget, and quality are defined at the start of the project as part of the project management plan, and performance data is collected throughout the project and compared against that plan (PMBOK® 8, Guide p.144). The measurement side is covered in detail on II.9 — Evaluate Project Status.

The last enabler links reporting to governance. According to the book, effective governance needs three core components: target metrics aligned with the organization's strategic goals, signaling mechanisms or alarm systems for those metrics, and feedback mechanisms that let decision-makers see how their decisions turned out (PMBOK® 8, Guide p.13). Two of the three are directly the work of reporting. For the governance side in detail, see III.1 — Define and Establish Project Governance.

Transparency comes from the culture

The second enabler asks for an attitude more than a tool, and its counterpart lies among the principles. The Build an Empowered Culture principle asks the project environment to promote mutual trust and to provide full clarity on individual roles, responsibilities, team agreements, and guiding processes. Those conditions let people work together and draw synergistic effects from their interactions (PMBOK® 8, Standard p.53).

How intense communication should be depends on the project's approach. According to The Standard, the need for ongoing feedback is greater in projects that use adaptive or hybrid approaches, because the teams are exploring and developing parts of the product within specific increments owing to ambiguity and complexity (PMBOK® 8, Standard p.25).

The Guide gives examples from both ends (PMBOK® 8, Guide p.76). At one end are teams that use daily coordination meetings and dedicated communication platforms for real-time collaboration. At the other is a manufacturing project implementing a large-scale ERP system, which disseminates its formal updates through biweekly email newsletters and monthly town hall meetings to keep the different levels of the hierarchy aligned.

The two examples show why thinking "the more communication, the better" leads you astray on the exam. The right answer is usually the option that fits the form and frequency of communication to the project's approach and the stakeholder's needs.

Why the domain ends with communication

The People domain traces a circle, and this task closes it. The domain opens with a common vision (I.1) and goes on to managing conflict and leading the team. Then it turns outward to engaging stakeholders, aligning their expectations, and keeping that alignment in place. After that it makes knowledge transferable, and it finishes with the thing that carries all of the above, which is communication.

The sequence also gives you a key for reading the exam. In People domain questions the right answer is rarely a technical move standing on its own, since the domain as a whole is measuring whom you talk to, when, and in what form. The Guide puts the idea behind the domain most briefly: relevant technical project management skills matter, yet the interpersonal and leadership skills needed to work effectively with stakeholders are just as important, if not more so (PMBOK® 8, Guide p.67).

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ 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 describes the book; it does not replace it.