Stakeholder Register
What It Is
A stakeholder register is a living document that captures everyone who has an interest in or influence over a project — internal or external, supportive or resistant. It is the foundation of any stakeholder engagement strategy.
When to Use It
- At project initiation, before planning begins
- When onboarding to an existing project with unclear ownership
- When a project expands in scope and touches new teams or functions
- Any time you sense misalignment and need to map who actually has a stake
Field Definitions
- Interest — What does this person care about? What outcome do they want?
- Influence — How much power do they have to shape decisions or block progress?
- Impact — How much does the project affect them?
- Current Engagement — Where they are now: Unaware / Resistant / Neutral / Supportive / Leading
- Desired Engagement — Where you need them to be by project end
- Owner — Who on your team manages this relationship?
Engagement Levels
| Level | Description |
|---|---|
| Unaware | Does not know the project exists |
| Resistant | Aware but opposed |
| Neutral | Aware but indifferent |
| Supportive | Aware and in favour |
| Leading | Actively championing the project |
Tips
- Start broad, then filter. List everyone you can think of first, then assess influence and impact to prioritize where to spend energy.
- High influence + low support = highest risk. These stakeholders need a dedicated engagement plan.
- Revisit regularly. Stakeholders shift — especially at major milestones, org changes, or when scope changes.
- Keep it honest. A register that sugarcoats engagement levels is useless. Note resistance plainly so it can be addressed.
Register
| ID | Name | Role / Title | Organization | Interest | Influence | Impact | Current | Desired | Owner | |
|---|---|---|---|---|---|---|---|---|---|---|
Engagement:UnawareResistantNeutralSupportiveLeading
Influence / Impact:H — HighM — MediumL — Low