II.5 — Plan and Manage Procurement

II.5 · Last updated: 24/08/2026

Where this task sits

II.5 — Plan and Manage Procurement is the fifth task in the Process domain of the 2026 ECO. The domain carries 41% of the exam.

After II.1, it is the second most enabler-heavy task in the ECO — ten of them:

• Plan procurement · Execute a procurement management plan · Select preferred contract types · Evaluate vendor performance · Verify objectives of the procurement agreement are met · Participate in agreement negotiations · Determine a negotiation strategy · Manage suppliers and contracts · Plan and manage the procurement strategy · Develop a delivery solution

Two of the ten are about negotiation. That is a piece added to this task from outside in 2026 — the reason is in the next section.

🔴 Do not trust the number — and note a domain move

This task's number changed hands, and it also absorbed work from another domain.

• In 2021, II.11 was plan and manage procurement. In 2026 that topic is II.5.
• In 2021, II.5 was plan and manage budget and resources. That task split in two in 2026: II.4 — Plan and Manage Resources and II.6 — Plan and Manage Finance.

So an older question tagged "II.5" is most likely about budget or resources, not procurement.

On top of that comes a domain move: in 2021, I.8 — negotiate project agreements was a task in the People domain (that number now belongs to communication). In 2026 negotiation moved into this task, and therefore into the Process domain. That is why the ECO carries two separate negotiation enablers here.

Match on the title, never the number; for the general shape of the trap see what changed in the 2026 PMP exam.

In PMBOK® 8, procurement is no longer a performance domain

This is one of the eighth edition's most striking structural decisions, and it bears directly on anyone studying procurement.

PMBOK® 8 gathers technical ways of working into seven performance domains: Governance, Scope, Schedule, Finance, Stakeholders, Resources, and Risk. Procurement is not among the seven.

The Guide states it plainly: procurement management is the discipline of selecting, contracting, and supervising vendors to perform outsourced work. Procurement management is a complementary discipline to project management and is explored in Appendix X4 (PMBOK® 8, Guide p.15). The same sentence repeats in the project documents section (PMBOK® 8, Guide p.123).

The consequence: while the ECO keeps procurement as a full task with ten enablers, PMBOK moved it out of the main body into an appendix. That asymmetry is worth knowing while you study — the weight is in the ECO, the detail is in the appendix.

The Guide also names who holds oversight: oversight of outsourcing efforts can be performed by the project management team and/or a dedicated procurement department within an organization (PMBOK® 8, Guide p.15).

"Make or buy" is now a governance decision

The PMBOK counterpart of the ECO's "plan the procurement strategy" and "develop a delivery solution" enablers is a process the eighth edition added to the Governance domain.

Plan Sourcing Strategy is the process of deciding whether to use internal or external resources for different parts of a project, considering organizational culture, specialized skills, resource capacity, risk, and the overall value proposition (PMBOK® 8, Guide p.16).

That the process sits in the Planning focus area of the Governance domain is meaningful: make-or-buy is not a procurement detail but a governance decision made as the plan is built. See II.1 — Develop an Integrated Project Management Plan and Plan Delivery.

The Guide also gives a reason behind the decision: organizations sometimes make a buy decision to outsource if they do not have the in-house infrastructure or technology (PMBOK® 8, Guide p.66).

Contract type is a risk-distribution decision

The ECO says "select preferred contract types." The book gives four fundamental models, and gives them from both the client and contractor perspectives (PMBOK® 8, Guide p.251):

• Fixed-price contract — a predetermined fee against a clearly defined scope of work, transferring cost risk to the seller while offering budget predictability for the buyer. Client: budget certainty, but possibly higher prices due to risk premiums. Contractor: profit potential if managed efficiently, but bears the risk of cost overruns.
• Cost-reimbursable contract — payment for the seller's actual costs plus a fee typically representing profit. Used when scope is uncertain or the project is high risk. Client: flexibility, but risk of cost escalation. Contractor: reduced financial risk, but potentially limited profit.
• Time and materials (T&M) contract — a hybrid arrangement containing aspects of both; the buyer pays for actual time and materials plus a profit margin. Often used for smaller projects, maintenance work, or when scope is not clearly defined at the outset. Client: flexibility, but requires close monitoring to control costs.
• Target-cost contract — sets a target cost with provisions for sharing cost savings or overruns between buyer and seller. Used to encourage efficiency and cost control while maintaining flexibility; common in large infrastructure and complex manufacturing projects.

The Guide's tailoring note sums up the criterion: procurement tailoring involves selecting the appropriate contract type based on risk distribution and cost certainty, which may have multiple implications for the project's financial side. It is important to tailor the financial processes together with the procurement strategy to minimize the risk of cost overruns (PMBOK® 8, Guide p.66).

Translated for the exam: the answer to "which contract type" comes not from price but from how clearly scope is defined and where you want the risk to sit.

Emerging trends in contract management

After the fundamental models, the book adds a current section.

While the fundamental contract types — fixed-price, cost-reimbursable, and T&M — remain the foundation of project procurement, several emerging trends driven by advancements in AI and automation are reshaping how these contracts are structured, executed, and managed. AI-powered contract analysis tools now enable more accurate risk assessments, faster negotiation processes, and better compliance monitoring (PMBOK® 8, Guide p.252).

That is the tooling side of the ECO's "evaluate vendor performance" and "verify objectives of the agreement are met" enablers.

Negotiation: two enablers arriving from Domain I

Two of the ECO's ten enablers concern negotiation, and in 2021 they were a task in the People domain.

The book's definition is broad: negotiation is a discussion aimed at reaching an agreement. It is used to achieve support or agreement that supports the work of the project or its outcomes, and to resolve conflicts within the team or with other stakeholders. Negotiation among team members is used to reach consensus on project needs, and it can build trust and harmony (PMBOK® 8, Guide p.183).

So negotiation is not only haggling with a seller; the ECO moving it into the procurement task does not narrow the subject, it adds a people skill to the procurement side.

When a dispute arises, the book lists the alternative dispute resolution (ADR) methods (PMBOK® 8, Guide p.253): negotiation (direct discussions between parties without third-party intervention), mediation (a neutral third party facilitates discussions), arbitration (an arbitrator or panel hears both sides and makes a binding decision), and dispute review boards.

The ordering is meaningful for the exam: it runs from least formal to most formal, and the right answer is usually the one nearest the top of the list.

The counterpart of the ECO's "determine a negotiation strategy" enabler sits on the procurement side too: ranking all proposals by weighted evaluation scores can be used to select a single seller to be asked to sign a contract and to establish a negotiating sequence (PMBOK® 8, Guide p.250).

Supervising the vendor and the agreement

Three ECO enablers look at what happens after the contract is signed: evaluate vendor performance, verify the agreement's objectives are met, and manage suppliers and contracts.

The Guide's audit tool applies here: quality audits may be scheduled or random, and may be conducted by internal or external auditors; they can also confirm the implementation of approved change requests, including updates, corrective actions, defect repairs, and preventive actions (PMBOK® 8, Guide p.148).

One edge case is worth noting: the book explicitly mentions the situation where the performing organization serves as a vendor to a sponsor organization (PMBOK® 8, Guide p.123). On procurement questions, which side of the table you sit on is not always fixed.

About the citations

All page numbers above refer to A Guide to the Project Management Body of Knowledge, 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

Every citation on this page is from the second book, the Guide. The numbers are the book's printed page numbers.

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