Stakeholder Register and Engagement Plan Template

Stakeholder register with interest, influence, attitude, power/interest grid, engagement gaps, actions and communication preferences

Manajemen ProyekStandarstakeholder registerDiperbarui 20 Okt 2026

Buka di editorUnduh .md

Cara menggunakan: Use from initiation and review at every stage gate. Fill the register and the current versus desired engagement first, then plan actions for the largest gaps. Main pitfall: subjective or personal wording in a document the stakeholders may read.

Pratinjau

Stakeholder Register and Engagement Plan: [Project name]

Register of the people and groups who affect or are affected by the project, with their interest, influence and attitude, and a plan for moving their engagement from where it is to where it needs to be. Based on common project management practice. Replace every [bracketed] value and every row marked Example.

Field	Value
Document ID	[SR-PROJECT-001]
Project	[Project name]
Version	[0.1]
Owner	[@project-manager]
Access	[Restricted to core team]
Review cadence	[Monthly and at each stage gate]
Last reviewed	YYYY-MM-DD

1. Identification method

Stakeholders were identified through [a charter review, an organisation chart walkthrough, interviews with the sponsor and workstream leads, and a review of similar past projects]. The list covers decision makers, delivery teams, affected users, support functions, suppliers and external bodies.

2. Assessment scales

Each stakeholder is assessed on the scales below.

Attribute	Scale
Interest	High / Medium / Low: how much the outcome affects them
Influence (power)	High / Medium / Low: ability to change direction, resources or acceptance
Attitude	Champion / Supportive / Neutral / Sceptical / Opposed
Engagement level	Unaware / Resistant / Neutral / Supportive / Leading

Current engagement is marked C and desired engagement D in the engagement matrix.

3. Stakeholder register

The register lists each stakeholder with their role, assessment and key concerns.

ID	Stakeholder	Role / organisation	Interest	Influence	Attitude	Key concerns	Owner
STK-01	Example: Chief operating officer	Sponsor	High	High	Champion	Cost per onboarding, regulator view	[@pm]
STK-02	Example: Branch network managers (12)	Operations	High	Medium	Sceptical	Staff workload during rollout, loss of customer contact	[@change-lead]
STK-03	Example: Compliance officer	Second line of defence	Medium	High	Neutral	KYC evidence and audit trail	[@ba]
STK-04	Example: IT operations	Service owner after go-live	Medium	Medium	Supportive	Supportability, on-call load	[@tech-lead]
STK-05	Example: Identity verification vendor	Supplier	Medium	Medium	Supportive	Volume commitments, integration timeline	[@procurement]
STK-06	[Stakeholder]	[Role]	[H/M/L]	[H/M/L]	[Attitude]	[Concerns]	[@owner]

4. Power and interest grid

The grid groups stakeholders by influence and interest; the quadrant sets the default engagement approach.

	Low interest	High interest
High influence	Keep satisfied: STK-03 Compliance officer	Manage closely: STK-01 COO, STK-02 Branch managers
Low influence	Monitor: [stakeholders]	Keep informed: STK-04 IT operations, STK-05 Vendor

The same grid is shown as a diagram for presentations.

5. Engagement assessment matrix

The matrix shows the engagement gap that the plan must close.

Stakeholder	Resistant	Neutral	Supportive	Leading
STK-01 COO			C	D
STK-02 Branch managers	C		D
STK-03 Compliance officer		C	D
STK-04 IT operations			C D
[Stakeholder]

6. Engagement plan

Actions are scheduled to move each stakeholder from current to desired engagement.

Stakeholder	Objective	Actions	Key message	Timing	Success indicator	Owner
STK-02	Example: Resistant to supportive	Co-design workshop; pilot in two branches; share pilot results	Fewer manual checks, more time for customer advice	Weeks 3 to 10	Pilot managers present results to peers	[@change-lead]
STK-03	Example: Neutral to supportive	Early review of KYC evidence design; sign-off checkpoint	Audit trail is stronger than the paper process	Design stage	Compliance sign-off at G2 without conditions	[@ba]
[ID]	[Objective]	[Actions]	[Message]	[Timing]	[Indicator]	[@owner]

7. Communication preferences

Preferences are recorded so communication reaches people in the form they actually use.

Stakeholder	Preferred channel	Frequency	Level of detail	Language / accessibility needs
STK-01 COO	One-page summary by email, monthly meeting	Biweekly	Headline and decisions	None
STK-02 Branch managers	Team call plus intranet page	Weekly during rollout	Practical impact on staff	[Local language]
STK-03 Compliance officer	Formal review documents	At design milestones	Full detail	None
[Stakeholder]	[Channel]	[Frequency]	[Detail]	[Needs]

8. Review and change log

The register is reviewed [monthly]; changes are summarised below.

Date	Reviewed by	Changes
YYYY-MM-DD	[@pm, @change-lead]	Example: STK-02 moved from Resistant to Neutral after pilot workshop
YYYY-MM-DD	[@name]	[Changes]

Standard and licence note

Based on common project management practice for stakeholder identification, analysis and engagement planning. This template is original text written for this collection. Template licence: MIT.

Templat terkait

Manajemen Proyek