Stakeholder Register: The Central Repository for Stakeholder Identification and Analysis

PMBOK v8 Definition

The Stakeholder Register is a project document that contains the identification, assessment, and classification of project stakeholders. It is the primary output of the Identify Stakeholders process and is maintained throughout the project lifecycle. The Stakeholder Register includes information such as stakeholder identification details, power/interest classifications, engagement requirements, and influence levels.

Process Group: Initiating | Knowledge Area: Project Stakeholder Management

Why It Matters for the Exam

The Stakeholder Register appears frequently on the PMI exam because it serves as the foundational document for all stakeholder engagement activities. Questions test your understanding of what information belongs in the register versus other documents like the Stakeholder Engagement Plan or Communications Management Plan. Expect scenario-based questions asking which document to update when stakeholder information changes.

Key Points to Remember (for the exam)

Primary Output: The Stakeholder Register is the output of Identify Stakeholders process
Key Inputs: Project charter, business documents (business case, benefits management plan), agreements, and enterprise environmental factors
Key Tools: Stakeholder analysis (data analysis), stakeholder mapping/representation (data representation), and expert judgment
Content Types: Identification info, assessment info, and stakeholder classification
Common Confusion: The Stakeholder Register is a project document, NOT a component of the project management plan
Update Frequency: The register is a living document updated whenever new stakeholders are identified or existing stakeholder information changes
Classification Methods: Power/interest grid, power/influence grid, influence/impact grid, or salience model

Typical PMI Exam Example

A project manager is initiating a new software development project. During stakeholder identification, she discovers that the VP of Marketing has high interest but low power over project decisions. The quality assurance manager has high power and high interest. Where should the project manager document these classifications?

Answer: The Stakeholder Register, using stakeholder mapping/representation tools.

PMI Exam Traps

Trap: Confusing Stakeholder Register with Stakeholder Engagement Plan
Reality: The Register captures WHO stakeholders are and their classification; the Plan describes HOW to engage them
Trap: Thinking the Stakeholder Register is part of the project management plan
Reality: The Register is a project document, separate from the management plan components
Trap: Assuming stakeholder identification happens only once at project start
Reality: Stakeholder identification is iterative; the register is updated throughout the project
Trap: Confusing inputs of Identify Stakeholders with outputs
Reality: Key inputs include the project charter and business documents; the Stakeholder Register is the output

Important PMI Connections

Related Concept	Relationship Type	Exam Attention Point
Stakeholder Engagement Plan	Input to / Updates from	The register feeds stakeholder classification into the engagement plan
Communications Management Plan	Input to Identify Stakeholders	Stakeholder communication needs derived from register classifications
Issue Log	Related project document	Stakeholders in the register may raise issues documented in the issue log
Lessons Learned Register	Related project document	Lessons about stakeholder management feed back into future identification
Project Charter	Key Input	The charter identifies the project sponsor and key stakeholders initially

Quick Review Questions

Which process produces the Stakeholder Register as its primary output?
What are the three main categories of information contained in the Stakeholder Register?
Is the Stakeholder Register a component of the project management plan or a project document?
When should the Stakeholder Register be updated during the project lifecycle?
What data representation technique is commonly used to classify stakeholders in the Stakeholder Register?

PMBOK v8 Reference

Section 2.4.3, Facilitate and Support (principles guiding stakeholder engagement)

Process: Identify Stakeholders (Initiating Process Group, Project Stakeholder Management Knowledge Area)

Inputs: Project charter, business documents (business case, benefits management plan), project management plan (communications management plan, stakeholder engagement plan), project documents (change log, issue log, requirements documentation), agreements, enterprise environmental factors, organizational process assets

Tools & Techniques: Expert judgment, data gathering (questionnaires and surveys, brainstorming), data analysis (stakeholder analysis, document analysis), data representation (stakeholder mapping/representation), meetings

Outputs: Stakeholder Register, change requests, project management plan updates, project documents updates