Stakeholder Register Template: The Charter Section That Drives Communication Plans (2026)

Why the Register Matters

PMBOK lists the stakeholder register as a formal output of the Identify Stakeholders process, treating it as a foundational artefact that feeds the Communications Management Plan, the Risk Register, and the project's overall engagement strategy. The 2024 Pulse of the Profession from PMI consistently identifies inadequate stakeholder engagement as one of the top three causes of project failure across all methodologies. The register is the document that makes engagement deliberate rather than ad hoc.

The pattern most consistently associated with stakeholder-related project failure is missing one high-influence stakeholder (often a regulator, a senior person in an adjacent team, or a vendor account director) or under-engaging a high-interest stakeholder until they organise resistance. A well-maintained register surfaces both risks before they become irreversible.

Eight Register Columns

A minimal register has eight columns. Add more if your organisation requires (e.g. accessibility needs, language preference, escalation path) but do not drop below these eight.

1. Name and role

Specific named individual, with their formal role and the team or function they sit in. Avoid 'Marketing' or 'Finance' as the entry; use the person.

2. Stake in the project

What this stakeholder cares about and why. The most-skipped column. Without it, the rest of the register is just an org chart.

3. Influence (low / med / high)

How much this person can affect the project's outcome or delivery, formally or informally. Includes veto power, budget authority, or social influence.

4. Interest (low / med / high)

How much this person cares about the project's outcome. Often inversely correlated with influence: the people most affected often have the least authority.

5. Communication preference

Channel (Slack / email / face-to-face / formal report), cadence (daily / weekly / monthly / on-event), and level of detail (headline / summary / full detail).

6. RACI on key decisions

For the 5 to 10 most significant decisions, mark this stakeholder as Responsible, Accountable, Consulted, or Informed. RACI overlay extends the register into governance.

7. Risk position

Are they supportive, neutral, or resistant? Resistance is not always bad if it surfaces real concerns. Tracking the position helps identify the engagement plan needed.

8. Engagement plan

Specific actions the PM will take to engage this stakeholder. Not generic ('keep informed') but specific ('1-on-1 fortnightly with named cabinet brief').

The Mendelow Influence-Interest Grid

Aubrey Mendelow's 2x2 grid (Manchester Business School, 1991) is the most widely used stakeholder mapping framework in project management. Plot each stakeholder by influence and interest, then apply the strategy associated with their quadrant.

High influence, High interest

Manage closely

Weekly 1:1, named seat at steering, co-author key documents, surface concerns early.

High influence, Low interest

Keep satisfied

Monthly briefings, escalate only on material risk or budget variance, no detail dumping.

Low influence, High interest

Keep informed

Regular updates, opportunities to comment, treat as project advocates and feedback sources.

Low influence, Low interest

Monitor

Quarterly summary, no proactive engagement unless their position shifts (e.g. promotion or new responsibility).

Filled Register: St Margaret's Hospital Trust Systems Integration

Worked example for an NHS Trust integrating three patient record systems (Cerner outgoing, Epic incoming, plus a legacy bespoke pharmacy system). 8 stakeholders across executive, clinical operations, finance, patient safety, two vendors, and an external regulator.

Project context: St Margaret's Hospital Trust Integration of Three Patient Record Systems

Name and role	Stake	Inf	Int	Channel	RACI	Position and plan
Dr Emma Lockhart Chief Medical Officer	Patient safety during cutover, clinical adoption	High	High	Weekly 1:1 + steering monthly	A (clinical decisions); C (technical decisions)	Supportive but cautious on cutover timing Weekly 30-min 1:1 every Monday 08:00. Personal review of cutover plan before sign-off. Monthly clinical-leadership steering chair.
James Okeke Chief Information Officer	Technical delivery, vendor management, post-cutover stability	High	High	Daily Slack + weekly steering	A (technical decisions); R (vendor management)	Supportive, advocate at the executive team Daily Slack check-in. Weekly tech steering chair. Co-presenter to board on quarterly progress reports.
Marian Tomlinson Director of Nursing	Nursing workflow disruption, training time impact	High	High	Fortnightly 1:1 + ward-level briefings	C (workflow design); I (technical decisions)	Cautious; concerned about training time during current staff shortage Fortnightly 45-min 1:1. Joint co-author of nursing training plan. Walk-the-floor visits every two weeks during cutover.
Mohammed Ali Chief Finance Officer	Budget envelope and contingency drawdown	High	Medium	Monthly steering + variance reports	A (budget variance > 5%); I (delivery decisions)	Neutral; will hold envelope strictly Monthly finance steering. Pre-meet on any variance > 3%. Quarterly board report co-author.
Sarah Henderson Patient and Public Involvement Lead	Patient experience continuity, data privacy	Medium	High	Monthly + ad hoc on incidents	C (patient-facing communication); I (technical decisions)	Supportive but vocal on transparency Monthly briefing. Co-author of patient communication plan. Invited to all cutover dress-rehearsals.
Cerner Account Director Vendor (incumbent system)	Contract closure terms, reference status, future business	Medium	High	Bi-weekly + formal CR cadence	I (CR triage); C (data migration)	Cooperative; commercial interest in clean exit Bi-weekly cadence call with CIO. Formal CR review process. Closure-terms negotiation handled by CIO and Procurement.
Epic Account Director Vendor (target system)	Successful go-live as reference site, contract expansion	Medium	High	Weekly during build, daily during cutover	C (technical decisions); R (implementation)	Highly engaged; reference-customer status motivates Weekly progress call with PM. Embedded implementation lead on-site. Joint risk-and-issue log.
NHS Digital External assurance and information governance	Data sharing compliance, DSPT submission	High (veto on go-live)	Medium	Quarterly + on-submission	A (DSPT compliance); C (data flow design)	Procedural; engaged at submission gates Quarterly governance touch-base. Submission lead time 6 weeks pre go-live. Named IG officer point of contact.

Common Register Mistakes

Listing roles, not named individuals.

"CIO" is not a stakeholder. James Okeke, the current CIO, is. Roles change; named individuals create accountability.

Marking everyone "High" influence.

If everyone is high-influence, the register has no triage signal. The Mendelow strategies depend on differentiation; defeating that defeats the register.

Stale register after month 3.

Stakeholder positions shift. A register reviewed only at charter time and never again creates false confidence and misses emerging resistance.

Frequently Asked Questions

What is the difference between a stakeholder register and a stakeholder map?

A register is a list (typically a table) of stakeholders with detailed attributes for each. A map is a visual representation, most commonly a 2x2 influence-interest grid (Mendelow matrix). The register is the source data; the map is one of many visualisations derived from it. PMBOK lists both as outputs of the Identify Stakeholders process. Most modern PMOs maintain the register as the source of truth and re-generate maps as needed.

How many stakeholders should a register include?

8 to 25 for a typical project. Above 25 you have lost focus and are tracking peripheral relationships. Below 8 you have missed people. The Mendelow research suggests the strongest predictors of stakeholder-related project failure are missing one high-influence stakeholder or under-engaging a high-interest one. A register that includes 'everyone we have ever met' is functionally useless because there is no triage signal.

Where does the stakeholder register go in the charter?

Two options. Option A: include the top 5 to 10 stakeholders directly in the charter and reference the full register as an appendix or living document. Option B: reference the register entirely as a separate artefact. Option A is preferred for charter-time approval because it forces the sponsor to acknowledge the high-influence stakeholders before signing. The full register is then maintained as a living document throughout delivery.

How often should the register be updated?

Reviewed at every steering committee meeting (monthly for most projects). Updated whenever a stakeholder's role, interest, influence, or position changes materially. Most projects find the register needs a substantive update every 4 to 8 weeks because people get promoted, change roles, or shift position as the project progresses. A stale register is more dangerous than no register because it creates false confidence.

What is the Mendelow influence-interest grid?

A 2x2 matrix developed by Aubrey Mendelow at the Conference on Information Systems in 1991 (Manchester Business School), categorising stakeholders by their level of influence (vertical axis) and interest (horizontal axis). The four resulting quadrants suggest different engagement strategies: Manage Closely, Keep Satisfied, Keep Informed, and Monitor. It remains the most widely used stakeholder mapping framework in project management practice.

Should the stakeholder register include external stakeholders?

Yes if they have material influence or interest. Regulators, key vendors, customer representatives, community groups, and major donors all belong in the register if they affect delivery. The boundary is whether their action or inaction could affect the project's success; if yes, they are in. External stakeholders typically need different communication channels (formal letters, scheduled meetings) compared to internal stakeholders.

How does the stakeholder register feed the communication plan?

The communication plan is derived from the register's communication preference and engagement plan columns. Each stakeholder's preferred channel, cadence, and detail level becomes a row in the communication plan. The plan also aggregates: if 12 stakeholders want weekly email summaries, that becomes one weekly email task; if 4 want monthly steering attendance, that becomes the steering cadence. The register without a derived communication plan is incomplete; the communication plan without an underlying register is ungrounded.

Related on this site

Charter objectives section Scope boundaries guide Healthcare charter (uses this register)Government charter (regulator stakeholders)PMBOK charter format How to write a charter