This guide covers everything you need to know about the stakeholder register in PMBOK 8. The stakeholder register is the comprehensive database of all individuals, groups, and organizations with an interest in the project — it documents who the stakeholders are, what they care about, how much influence they have, and what their current relationship with the project is.
What Is the Stakeholder Register?
The stakeholder register is a project document that records identifying information, assessment information, and stakeholder classification for each person or group that may affect or be affected by the project. It is created during the Identify Stakeholders process and updated throughout the project as new stakeholders are discovered, existing stakeholders’ interests or influence levels change, or the project’s stakeholder landscape evolves.
The stakeholder register is more than a contact list. It captures each stakeholder’s interests (what outcomes do they care about?), level of influence (how much power do they have over the project?), and involvement (how actively are they engaged?). This assessment enables the project manager to prioritize stakeholder engagement efforts and tailor communications to each stakeholder’s needs and preferences.
Because the stakeholder register contains sensitive assessments of stakeholder attitudes and influence, it is typically a confidential document shared only with the project manager and key team leads.
Stakeholder Register in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the stakeholder register belongs to the Stakeholders Performance Domain and is produced during the Identify Stakeholders process. It is the foundational document for all stakeholder management activities, providing the information base for the stakeholder engagement plan and the communications management plan.
The stakeholder register feeds into the stakeholder engagement plan (informing engagement gap analysis), the communications management plan (defining communication preferences for each stakeholder), and risk management (identifying stakeholders whose resistance represents a project risk).
Key Elements of the Stakeholder Register
A well-structured stakeholder register typically includes:
- Stakeholder ID and Name — unique identifier and full name or group name
- Role and Organization — job title, department, and organizational relationship to the project
- Contact Information — preferred communication channels and contact details
- Interests and Expectations — what outcomes this stakeholder wants from the project
- Level of Influence — the stakeholder’s ability to affect project decisions or outcomes
- Engagement Level — current attitude toward the project (unaware/resistant/neutral/supportive/leading)
- Communication Preferences — preferred format, frequency, and channel for project communications
Stakeholder Register Example — Project Phoenix
The Project Phoenix stakeholder register documented 12 stakeholders across four categories: Sponsor (Riley Park, COO — High influence, Leading), Client/End User (Sarah Chen, TechCorp CEO — High influence, Neutral transitioning to Supportive), Core Team (Alex Morgan, Sam Lee, John Tran, Maria Santos, Daniel Reyes at BrightFrame), and Extended Stakeholders (David Kim IT Operations, Priya Kapoor resource manager, the TechCorp marketing team, and CloudHost Pro account manager).
Sarah Chen’s register entry noted her primary interest as “website performance driving lead generation recovery” and her communication preference as “visual demos and concise summaries — no technical jargon.” This informed Alex’s decision to produce biweekly product demos rather than written technical updates for Sarah, which proved highly effective at maintaining her engagement. The register was updated four times during the project as two new extended stakeholders were identified and David Kim’s engagement level was reassessed from Resistant to Neutral.
You can download the complete filled-in example below — it shows exactly how the stakeholder register was built and used in a real project.
Download Free Stakeholder Register Template and Example
We have prepared two free resources to help you build a stakeholder register for your own projects:
- Download the Stakeholder Register Template — PMBOK 8 (blank, ready to fill in)
- Download the Stakeholder Register Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Stakeholder Register — Best Practices and Common Mistakes
Identify stakeholders broadly at the start of the project — it is far easier to remove a stakeholder from active management than to discover mid-project that a critical influencer was overlooked. Include both internal and external stakeholders, including regulatory bodies, user groups, and affected departments. Review and update the register at each major phase gate; stakeholder landscapes change significantly between initiation and execution.
The stakeholder register is most effective when it is maintained as a living document with regular assessment updates, not as a static list created once and never revisited. Teams that skip or rush stakeholder identification often find themselves surprised by resistance from groups they had not considered.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Project Management