Stakeholder Register

Maintain a controlled list of project stakeholders, their interests and relationship owners.

This Excel template contains prepared working sheets and completion notes on a separate sheet. Enter your project data and review the completed workbook before use.

Prepare project brief

The form prepares a separate brief; it does not fill the Word or Excel file.

Read product descriptions in your language. The Word and Excel template files are in English.

Stakeholder Register · Document preview — Selected page preview · XLSX

Learning

How to use this template

When you need it

Use this register when a project needs a maintained record of people and organizations with relevant interests, responsibilities, or influence, especially where relationship ownership and communication channels must remain clear as participants change.

What it helps you decide

It gives the team a practical reference for who is affected and who manages each relationship, helping prevent overlooked parties, misdirected communications, and outdated assumptions about roles or engagement needs.

How to complete it

Assign Stakeholder ID, Name / organisation, Role / relationship, and Internal / external using confirmed project information rather than inferred titles or outdated contact lists.
Record Interest / need, Project impact, and Engagement requirement from evidence or clearly identified assumptions, keeping the description relevant to the actual project relationship.
Confirm Contact / channel and Relationship owner, then set Review date so changed responsibilities, contact details, and engagement needs are checked throughout project delivery.

Who prepares and reviews it

A stakeholder coordinator or project manager normally maintains it with client, discipline, and interface leads. Relationship owners validate entries, while access and review arrangements follow the project's actual confidentiality requirements and management responsibilities.

A mistake to avoid

Collecting names without assigning relationship owners can create a complete-looking register while leaving nobody responsible for confirming needs or maintaining the relevant engagement route.

Illustrative example

Illustrative example: a utility diversion affects a factory's operations team and a municipal road authority. The register records separate interests, channels, and relationship owners. When the factory appoints a new operations lead, the review updates the contact before an access decision is communicated through an obsolete route.

Explore the wider topic

Document contents

Stakeholder ID
Name / organisation
Role / relationship
Internal / external
Interest / need
Project impact
Engagement requirement
Contact / channel
Relationship owner
Review date

Required inputs

Project name, location, company, document number and revision
Actual project scope, source records and responsible roles

Practical tools.
Professional judgment.

Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.