PM Basics · Stakeholder Management · Template
Stakeholder Register & Communication Plan
Assess stakeholders and plan appropriate communication with Excel and a copyable Confluence template.
Excel
Stakeholder Register & Communication Plan
Two worksheets with dropdowns, an automatic engagement approach and a dynamic 2×2 matrix.
Download Excel ↓Confluence
Copyable template
Copy the formatted template and paste it into a new page in your own Confluence space. Replace the placeholders and fictional examples. You do not need access to my internal Confluence space.
Go to the copyable template →Use it in Confluence
Text and tables can be pasted into Confluence. Add status macros, tasks and links afterwards if needed. Formatting may vary between Confluence editors; there is no automatic synchronisation with Excel.
Wide tables scroll horizontally, including with the keyboard.
1 / Quick guide
Copy this template for a project. All examples are explicitly fictional groups in an IT rollout. Replace or remove them before use.
One master register: Choose Excel OR Confluence as the central source. There is no automatic synchronisation between the templates. Maintain assessments and communication actions only in the chosen register.
2 / Project information
| Item | Entry |
|---|---|
| Project | Fictional IT rollout – replace before use |
| Register owner | Agree an accountable role within the project |
| Review frequency | Review regularly and before key project phases |
| Updated | Enter the date of the last review |
3 / Stakeholder Register & Communication Plan
| Stakeholder / group | Role / interest | Influence | Impact | Stance | Communication needs | Action / channel | Owner | Frequency | Last reviewed |
|---|---|---|---|---|---|---|---|---|---|
| Management | Sponsor / governance | High | Low | Supportive | Status, risks and decisions needed | Concise status report | Project manager | Monthly | Enter date |
| Local leads | Rollout support | High | High | Neutral | Dates, prerequisites and tasks | Rollout coordination meeting | Rollout lead | Every two weeks | Enter date |
| End-user group | Using the new solution | Low | High | Neutral | Changes, training and support | Information and training with questions | Change team | Before each rollout | Enter date |
| Adjacent business team | Monitor interfaces | Low | Low | Neutral | Relevant changes to interfaces | Targeted information when changes arise | Workstream lead | As needed | Enter date |
Fictional examples. For a blank register, remove the example rows and add new rows.
4 / Assessment guide and simple matrix
Influence: High or Low – how much can the group affect decisions or the project?
Impact: High or Low – how strongly does the change affect work or responsibilities?
Stance: Supportive, Neutral or Critical – the current project-related stance, not a personal judgement. Take criticism seriously and understand its reasons.
| Influence / impact | Low impact | High impact |
|---|---|---|
| High influence | Provide targeted information and involve appropriately | Engage closely |
| Low influence | Monitor and inform when needed | Keep well informed and enable feedback |
The matrix provides guidance for engagement. It does not replace professional judgement. This Confluence table is maintained manually; it is not calculated automatically or synchronised with Excel.
5 / Regular review
- Reassess relevant groups, influence, impact and stance.
- Agree specific communication needs, actions, responsibilities and frequency.
- Update before key project phases and when circumstances change; maintain the last review date.
- Prefer groups and roles. Record only necessary information, restrict access appropriately and do not include sensitive or private information.