Critical Path
Dan Sunil monogram
PMI standard template · Excel, Word & PDF · Toolkit only

Stakeholder Register Template (PMI Standard Excel, Word & PDF)

8 min read · Reviewed August 2026 by Dan Sunil Kumar

A stakeholder register lists everyone who can affect your project or is affected by it, how much power and interest each of them holds, and the engagement each one gets as a result. Paired with an engagement plan — the channel, cadence and owner per row — it turns "keep everyone informed" into something a team can actually execute.

The column that earns its place is the stance gap: where each stakeholder is today versus where the project needs them to be. If the two match, there is no engagement work to do. If they differ, that row is your communication plan for the next month.

PMI standard alignment
Standard followed
PMBOK Guide 7th ed. / PMI Practice Standard for Project Governance
Performance domain
Stakeholders
Process group
Initiating
Knowledge area
Stakeholder Management

The Excel, Word & PDF files for this template are part of the paid PM Delivery Toolkit — there is no free download. The full walkthrough, worked example and section guidance below stay open to read.

Get the stakeholder register in the toolkit

When to use it

  • You are in initiation and need to know who signs, who approves and who resists.
  • Communication is happening, but the same people keep saying they were not consulted.
  • Approvals arrive late because approvers were treated as a general audience.
  • A change or rollout affects a large user population whose adoption decides success.
  • A new sponsor or reorganisation has changed who holds the power.

Every section, and what good looks like

  1. Section 1

    Name or group

    The individual where a person decides, the group where a population is affected.

    10-25 rows for a mid-sized project — enough to be honest, few enough to maintain.

  2. Section 2

    Role and interest in the project

    Their formal role, and one line on why the outcome matters to them.

    Their interest is written from their point of view, not the project's.

  3. Section 3

    Power and interest ratings

    High, medium or low for each — power is the ability to fund, stop or redirect; interest is how much the outcome affects them.

    Ratings are deliberate enough that not everyone lands in the same box.

  4. Section 4

    Quadrant

    Manage closely, keep satisfied, keep informed or monitor — derived from the two ratings.

    The quadrant visibly changes the cadence in the next column.

  5. Section 5

    Current and target stance

    Where they stand today (supportive, neutral, sceptical, blocking) and where they need to be.

    At least one row admits scepticism — a register where everyone is supportive is fiction.

  6. Section 6

    Engagement approach

    What you will actually do to close the stance gap.

    Names a mechanism — design reviewer, pre-brief, floor-walker — not just "communicate".

  7. Section 7

    Channel, cadence and owner

    Where the conversation happens, how often, and who on the team owns it.

    A frequency and a named owner on every row; "as required" appears nowhere.

A filled-in example

Six rows from a real engagement plan, showing how the power/interest quadrant changes the effort each stakeholder gets.

Worked stakeholder register example
Sponsor (finance director)High power, high interest — manage closely. Supportive today, needs to be an active advocate. Bring decisions rather than updates, pre-brief before each steering meeting. Weekly 30-minute 1:1, owned by the project manager.
Regional ops managers (×6)Medium power, high interest — keep informed. Neutral to sceptical today, need to be actively supportive. Two of them join as design reviewers; every decision affecting their teams is published. Fortnightly ops forum, owned by the change lead.
IT securityHigh power, low interest — keep satisfied. Neutral, and neutral-but-responsive is enough. Book the review slot early and send the artefacts unprompted. Review meeting at each gate, owned by the tech lead.
Contact-centre agents (~120)Low power, high interest — keep informed. Anxious today, need to be confident and trained. Two-week comms drip, floor-walker support in week one, a feedback channel that gets real answers. Weekly huddles and intranet, owned by the change lead.
Vendor account managerMedium power, medium interest — keep satisfied. Supportive, and needs to stay there. Hold them to the written rate-limit commitment; joint risk review before cutover. Weekly delivery call, owned by the integration lead.
Group PMOMedium power, low interest — monitor. Report in their format on their dates so there are no surprises at gates. Monthly standard report, owned by the project manager.

Mistakes that make a stakeholder register useless

  • Listing job titles with no named person, so nobody can be pre-briefed or asked.
  • Rating everyone high power and high interest, which is the same as having no register.
  • Omitting the sceptics because the register gets shared — keep the stance column honest, and control who sees it.
  • No target stance, so engagement has no measure of success.
  • Cadence written as "as required", which reliably means never.
  • Writing it once in initiation and never revisiting it after a reorganisation or sponsor change.
  • Treating an affected user population as an audience for announcements rather than a group whose adoption decides the outcome.
Paid toolkit

26 more artifacts, ready to fill in

The PM Delivery Toolkit packages the RAID log, status pack, estimation and earned value workbooks, capacity planner, agile sprint tools and 150 PMP-style questions — Word, Excel and print-ready PDF.

  • Status pack and steering deck with RAG logic built in
  • Estimation and EVM workbook: CPI, SPI and EAC calculated
  • Capacity planner with an over-allocation heatmap
  • Agile set: sprint planning, user stories, retros, backlog, WSJF
What’s inside all 26 artifacts

One payment · lifetime updates · 14-day refund. Files unlock on your download page as soon as payment clears.

Questions people ask

What is a stakeholder register?
A table of everyone who can affect or is affected by a project, with their role, interest, power and interest ratings, current and target stance, and the agreed engagement approach, channel, cadence and owner.
What is the difference between a stakeholder register and a stakeholder analysis?
The analysis is the thinking — rating power and interest and placing people in quadrants. The register is the living document that records the result and the engagement plan attached to it.
How does the power/interest grid work?
High power and high interest means manage closely; high power and low interest means keep satisfied; low power and high interest means keep informed; low on both means monitor. The quadrant sets how much of the team's time each stakeholder gets.
How many stakeholders should a register have?
For a mid-sized project, 10-25 rows. Fewer usually means groups are missing; many more means individuals are being listed where a group would do, and the register will not be maintained.
Is a stakeholder register confidential?
The stance columns are candid, so treat the full version as internal to the project team and sponsor. Share the engagement plan — channel and cadence — more widely, since people are entitled to know how they will be involved.
How often should it be updated?
Review it at every stage gate and whenever the organisation, sponsor or scope changes. New approvers appear and sceptics convert; a register untouched since initiation misleads at go-live.

Read next

Other PMI-standard templates

Every one has the same walkthrough, worked example and PMI mapping, and every file ships inside the PM Delivery Toolkit.

Keep going on the site

The hubs and tools that pair with this stakeholder register.

Free tips

Get five PM habits that quietly save projects

Baselines, critical path discipline, RAID logs that people read, range estimating and status packs sponsors act on — sent straight to your inbox, free.

One email, no spam, unsubscribe any time.