Stakeholder Register Template

What is a Stakeholder Register?

A stakeholder register lists everyone with an interest in a piece of work, what they care about, how much influence they hold and how often you will update them. It matters because the person who derails a project in month four is usually someone nobody told about it in month one. Writing the list down turns communication from something you remember to do into something scheduled.

Project and programme managers keep one from initiation onward, but so do people who would never call themselves project managers: a headteacher planning building works, a charity director applying for funding, a founder raising a round. It matters most where the work touches groups outside your reporting line — regulators, unions, residents, a client's finance team, an outsourced supplier. Consultancies build one during discovery, because the register is how they find out who can actually approve payment.

A register holds personal data, and often opinions: a note on someone's attitude or influence is still information about an identified person. Where the UK or EU GDPR applies, that individual can ask to see what you hold, which is reason enough to write assessments you would be comfortable reading aloud. Other regimes — Canada's PIPEDA, Australia's Privacy Act, India's Digital Personal Data Protection Act, US state privacy laws — set their own access and retention rules, so check the one that covers you. Separately, some projects carry statutory consultation duties that a register does not discharge.

The register records who to talk to; it does not decide what you tell them, and it is no substitute for actually talking. A neat grid with the communication column filled in has no effect until somebody sends the update. It is also not an approval list — appearing on it gives nobody a veto, and the small set of people who can genuinely stop the project should be marked separately. And it does not capture negotiation: the reasons someone objects belong in a note, not in a column.

What to put in a Stakeholder Register

These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.

How to write a Stakeholder Register

1. List every group, not just individuals

   Start wide: internal teams, external suppliers, customers, regulators, neighbours, funders, employee representatives. Where a group has no single contact, name the group and then the person you will actually ring. Missing a group entirely is the failure that hurts; you can always merge rows later. Fifteen to forty entries is normal for a project running a few months.

2. Record interest and influence separately

   Interest is how much the outcome affects them. Influence is how much they can change it. The two are independent, and the combination sets your effort: high influence with high interest gets a call; high influence with low interest gets a short briefing so they do not become interested at the worst moment; low and low gets the newsletter.

3. Write what each one actually wants

   Not their job title — their position. 'Wants the migration finished before the November audit and does not mind which supplier we use' tells you how to write the update. 'Head of Finance' tells you nothing you did not already know. Where you are guessing, mark it as a guess and confirm it in the first conversation you have with them.

4. Set a channel and a frequency

   Against each entry, put how they will hear from you and how often: monthly email, fortnightly call, quarterly steering meeting, or exceptions only. Then put those in the diary. The column exists to be turned into recurring calendar invitations; a register whose communication plan never leaves the spreadsheet has done none of the work it was written for.

5. Review after every major change

   People move, sponsors change, suppliers are replaced, a regulator opens a consultation. Set a standing check — at each phase gate, or monthly — and update the register then. Date each version. Prune it as well: keeping a contact who left the organisation a year ago is how a confidential status report ends up in a stranger's inbox.

Common mistakes

• Listing only the people who report into the project, then discovering in month four that a department nobody consulted holds a veto over the launch date.
• Recording job titles instead of what each person actually wants, which leaves every update written for a generic audience and read by nobody.
• Writing blunt personal assessments in the notes column, forgetting that in several jurisdictions the person named can request a copy of what you hold about them.
• Filling in a communication frequency without putting the meetings in a calendar, so the plan exists on paper and nothing is ever sent.
• Keeping stale contact details, so status reports go to someone who left and the person now doing that job hears about the project as a rumour.

Frequently asked questions

This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.

Related templates

All templates · Management templates