The "Invisibility" of Procurement in PMBOK® 8 Change Control: Are we ignoring legal risk?

Governance Organizational Project Management Procurement Management

Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal

By integrating Procurement within the Resource and Stakeholder Performance Domains, the PMBOK® Guide – 8th Edition has effectively removed the explicit link between Change Control and Contractual Compliance.

In your current practice, how do you ensure that a change approved by the CCB (Change Control Board) doesn’t inadvertently violate pre-existing contract clauses, given that the standard change flow no longer mandates a specific 'Procurement Check'?

Are we transforming the Project Manager into a mere 'Resource Manager' and losing sight of their critical role as a 'Contract Manager'?

I’m concerned that this systemic abstraction is creating a significant legal blind spot in project governance.

Posted: Mar 29, 2026 6:15 AM

Lissette Indhira Pimentel Sosa

Community Champion

Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic

Even if it’s not explicitly called out, I treat procurement/legal as a mandatory checkpoint in change control whenever contracts are involved. Any approved change that impacts scope, cost, or timelines should trigger a quick validation against contractual terms.

For me, it's more about how you operationalize it. If that check is missing, it becomes a real risk, not just operational, but legal.

So I don’t see the PM role shifting to a “resource manager,” but rather needing to be more intentional in covering those gaps the framework no longer makes explicit.

Posted: Mar 30, 2026 8:01 PM

Please login or join to reply

The "Invisibility" of Procurement in PMBOK® 8 Change Control: Are we ignoring legal risk?

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters