I.4 — Engage Stakeholders

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

Stakeholder work was split into three tasks

I.4 — Engage Stakeholders is the fourth task in the People domain of the 2026 ECO, a domain that carries 33% of the exam. It does not stand on its own. In 2026 PMI divided stakeholder work into three consecutive tasks: I.4 brings stakeholders into the process, I.5 aligns their expectations, and I.6 manages those expectations from then on. Three of the domain's eight tasks being given to stakeholders says a good deal about how much weight the subject carries on the exam.

The ECO lists six enablers for this task:

• Identify stakeholders
• Analyze stakeholders
• Analyze and tailor communication to stakeholder needs
• Execute the stakeholder engagement plan
• Optimize alignment among stakeholder needs, expectations, and project objectives
• Build trust and influence stakeholders to accomplish project objectives

The number held, the scope grew

There is good news here for anyone working from older material. The number still points to the same subject in 2026, so an old question tagged "I.4" really is about engaging stakeholders. Two caveats apply all the same.

The first is that the task has grown. "Collaborate with stakeholders", a separate task in 2021 (numbered I.9 in question banks), is now counted inside I.4, which brings old I.9 material within this page's subject as well.

The second, and the more dangerous, is that the neighboring numbers did not hold. Domain I came down to eight tasks in 2026 while the old numbering reached at least I.12, so the difference had to be taken from somewhere. The two numbers right next door show how. In 2021, I.5 was about training and I.6 about building a team, and both now live inside I.3 — Lead the Project Team.

So the comfort of "I.4 stayed put" should not spread to the rest of the domain. When you map older material to the new ECO, look at the title and ignore the number. A domain-by-domain breakdown of the trap is in what changed in the 2026 PMP exam.

In PMBOK the Stakeholders domain also holds communication

In PMBOK® 8 the matching area is the Stakeholders performance domain, which carries seven processes (PMBOK® 8, Guide p.9):

Identify Stakeholders · Plan Stakeholder Engagement · Plan Communications Management · Manage Stakeholder Engagement · Manage Communications · Monitor Stakeholder Engagement · Monitor Communications

A careful look at the list shows that three of the seven are about communication. Those three are PMBOK's counterpart to the ECO pulling communication out as a task of its own (I.8). The way the processes run from planning through execution to monitoring also shows that stakeholder work lasts for the whole project. It is far more than an identification exercise done once at the start and then filed away.

Who counts as a stakeholder

The Guide's list of examples draws the boundaries of the task clearly: suppliers and vendors, customers, end users, regulatory bodies, local communities, family, sponsor, governing bodies, project management offices, steering committees, the project manager, the project management team, and the project team (PMBOK® 8, Guide p.68, Figure 2-31).

Finding family and local communities on that list shows that the book does not limit the idea of a stakeholder to the parties who signed a contract.

Nor does it put a ceiling on scale. A project may have a small group of stakeholders or potentially millions. Different stakeholders can come onto the scene in different phases, and the influence, power, or interests of existing ones may change as the project unfolds (PMBOK® 8, Guide p.67).

The Guide keeps the circle wide in another way too. Effective identification, analysis, and engagement cover stakeholders internal and external to the organization, including those who are supportive, those who stay neutral, and opponents who do not support the project (PMBOK® 8, Guide p.67).

That last point often decides an exam question. An opposing stakeholder is never struck off the list. They are written onto it, and the engagement plan is shaped around them.

Identifying and analyzing

The first two enablers find their counterpart in PMBOK's first process, Identify Stakeholders.

Its tools include stakeholder analysis and document analysis, and on the data representation side stakeholder mapping/representation. Its main output is the stakeholder register, and alongside it the process produces updates to the requirements management plan, the communications management plan, the risk management plan, and the stakeholder engagement plan (PMBOK® 8, Guide p.71).

Two plans on that output list deserve attention, because identifying stakeholders feeds the communication and engagement plans directly. The enabler about tailoring communication to stakeholder needs grows out of exactly that link.

The mapping methods themselves are covered in the next task; see I.5 — Align Stakeholder Expectations.

Carrying out the engagement plan

The ECO makes executing the stakeholder engagement plan a separate enabler, and its counterpart is the Manage Stakeholder Engagement process. The tool list shows how much of this is work with people. It includes communication skills such as feedback; interpersonal and team skills such as conflict management, cultural awareness, negotiation, observation/conversation, and political awareness; and, besides those, ground rules, expert judgment, and meetings (PMBOK® 8, Guide p.74).

The input list says just as much about how tightly the process is tied to the rest of the project. The change log, issue log, lessons learned register, stakeholder register, risk register, status report, and project schedule all feed into it (PMBOK® 8, Guide p.74), because stakeholder engagement draws on everything else that is happening in the project.

The Guide also names the key skills to develop in this domain and puts two of them forward, negotiation and conflict management (PMBOK® 8, Guide p.67). The page that treats the conflict side in detail is I.2 — Manage Conflicts.

Trust and clarity first, influence after

The last enabler carries two verbs, and the book has a counterpart for each.

The Build an Empowered Culture principle in The Standard approaches the subject from the top. Stakeholders determine the success of projects; the stakeholders and team members on a project are key to its success and should be empowered across many dimensions (PMBOK® 8, Standard p.53).

The principle's condition is trust. The project environment should promote mutual trust among stakeholders and team members, and there should be full clarity on individual roles, responsibilities, team agreements, and guiding processes (PMBOK® 8, Standard p.53).

"Influence" in this sense has nothing to do with manipulation. The sequence the book sets up starts with trust, continues with clarity, and ends in collaboration, and influence is what that chain produces on its own.

The Guide also says plainly that technical skill is not enough by itself. 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).

The stakeholder register is never finished

This is the most frequently overlooked side of the task, and the book settles it clearly. The activities of identification, prioritization, and engagement should be reviewed and updated routinely, or at least when the project progresses through phases (PMBOK® 8, Guide p.67).

The reason is on the same page. Stakeholders' influence, power, and interests change as the project goes on, and different stakeholders appear in different phases.

The distinction often decides an exam question, because an answer stating that the stakeholder register was prepared at the start is incomplete. A complete answer also says when the register will be revisited.

Monitoring engagement and closing the gap between the current and the desired level of engagement belong to a separate task; see I.6 — Manage Stakeholder Expectations.

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.