What Is a Stakeholder Register?

A Stakeholder Register is a project document that records identified stakeholders and their relevant information — interests, involvement, potential impact, and current engagement level. In PMBOK 8, stakeholder identification is a continuous process throughout the project, not a one-time initiation activity. The Stakeholder Register is the output of the Identify Stakeholders process and the primary input to the Stakeholder Engagement Plan. It captures both internal and external stakeholders, and it distinguishes between their current engagement level (unaware, resistant, neutral, supportive, leading) and the desired engagement level needed for project success — the gap between these two states drives the engagement strategy.

What's Inside This Stakeholder Register Example

This Stakeholder Register example covers Project Phoenix — MCG's $72,250 website launch, March 17 to June 13, 2025. The spreadsheet documents 14 identified stakeholders:

• Riley Park — COO/Sponsor, High Power / High Interest, Desired: Leading, Initial: Supportive
• Alex Morgan — PM, High Power / High Interest, Leading (project team)
• MCG IT Lead — Infrastructure owner, Medium Power / High Interest, Desired: Supportive
• MCG Sales Director — Primary beneficiary of website leads, Medium Power / Medium Interest, Initial: Neutral, Desired: Supportive
• MCG Marketing Manager — Content and brand owner, Medium Power / High Interest, Desired: Supportive
• BrightFrame Account Manager — Vendor lead, Low Power / High Interest, Desired: Supportive
• MCG CFO — Budget approver, High Power / Low Interest, Desired: Supportive
• MCG Staff (end users) — CMS users post-launch, Low Power / Medium Interest, Desired: Neutral-to-Supportive
• Plus 6 additional stakeholders including external press contact, hosting provider, plugin vendors, and MCG board member with oversight interest

Each stakeholder entry includes: name, role, organization, contact information, major requirements, main expectations, potential influence, and engagement classification.

How Alex Morgan Used This Stakeholder Register

Alex Morgan built the initial Stakeholder Register during project initiation and updated it at each phase gate. Three stakeholder management insights from the register shaped execution:

• MCG Sales Director (initially Neutral): The Sales Director's initial neutrality was a risk — the website was being built partly to improve lead quality for the sales team, but the Sales Director was not engaged. Alex added a Sales Director briefing to the Week 3 plan, presenting the website's lead generation features directly. By Week 4, the Sales Director was reclassified as Supportive and became an advocate for the project during an internal budget review in Week 8.
• MCG CFO (High Power / Low Interest): The CFO needed accurate financial reporting but not project detail. Alex tailored all CFO communications to a one-page financial summary — never a full status report. This appropriate-level communication maintained CFO confidence without consuming their limited attention bandwidth.
• MCG Staff (end users): Initial engagement was low-interest/neutral. Alex scheduled a CMS training session in Week 12, two weeks before launch, which moved staff engagement from Neutral to Supportive. Staff readiness on launch day — zero escalation calls about CMS usage — was a direct outcome of this stakeholder management action.

Download and Customize

This Stakeholder Register example is available as a free download. Use it as a reference to build your own stakeholder register, or start with the blank template and populate it for your project's stakeholder landscape.

• Download the Stakeholder Register Template — PMBOK 8 (blank, ready to use)
• Read the article: Stakeholder Register in PMBOK 8 — Guide and Best Practices

Stakeholder Register Example: Key Takeaways

The most actionable feature of Project Phoenix's Stakeholder Register was the gap between current and desired engagement levels. The MCG Sales Director gap (Neutral -> Supportive) prompted a targeted Week 3 briefing that turned a passive stakeholder into an active advocate by Week 8. That advocacy paid dividends during an internal budget review that could have jeopardized the project. Stakeholder management is not about making everyone happy — it is about identifying which engagement gaps pose the highest risk to project success and closing those gaps with deliberate, targeted communication. The Stakeholder Register is the map. The engagement plan is the route. Execution is what changes the engagement level.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.