Free Template · Excel · Updated March 2026
Free Stakeholder Register Template
Excel Download
Many project problems are really people problems. A sponsor who loses interest, a client who keeps changing requirements, a manager who holds back resources: you can usually see these coming if you keep a proper register. This Excel template helps you list everyone who matters, map their interest and influence, track their attitude and write a clear plan for each one.
30 pre-numbered rows
STK-001 through STK-030: unique IDs let you reference specific stakeholders across the project management plan and comms plan.
4 validated drop-downs
Interest level, Influence level, Current Attitude and Target Attitude: all validated to keep the register consistent and filterable.
Engagement strategy column
A specific strategy field per stakeholder, the column that makes the register a management tool rather than just a contact list.
Stakeholder Register Template
Free Excel template: instant download
Format
Excel (.xlsx)
Rows
30 pre-numbered stakeholders
Columns
11 fields per stakeholder
Drop-downs
4 validated fields
Compatible
Excel, Google Sheets, LibreOffice
Price
Free: no signup needed
No email required. Instant Excel download.
Quick answer
A stakeholder register lists everyone who can affect or is affected by a project, with their role, interest, influence and engagement level. This free Excel template has 11 columns and 4 validated drop-downs, plus a power/interest grid and an attitude scale.
If you want to learn how to identify, analyse and engage stakeholders, read my stakeholder management guide. This page is for the template: how to fill in each column, a worked example and the mistakes I see most.
01 · What's Included
What's in the stakeholder register template?
The register is one Excel sheet with 30 numbered rows. Four columns use drop-downs so everyone rates people the same way, and you can filter quickly. For example, you can pull out every high-influence stakeholder who is currently resistant.
✦
From my experience: On my UAE construction projects the stakeholder list was never short: the client, the consultant, the main contractor, subcontractors and the authorities, from many different nationalities. I kept the register live and looked at it before every progress meeting, because the person with the most influence at the start was rarely the same person at handover. When I teach this to my PMP students, the mistake I see most is a register filled once at kickoff and never opened again.
| Column | Field | Notes |
|---|---|---|
| ID | Stakeholder Number | Pre-filled STK-001 to STK-030. Reference these IDs in your communications plan and RACI matrix to link planning documents without repeating full names. |
| Name | Full Name | Individual name. Groups ("Finance Team", "IT Department") should be broken into named individuals where possible: groups do not have attitudes or strategies; people do. |
| Organisation | Company / Department | Their home organisation or department. Useful for identifying clusters of stakeholders from the same area who may share common concerns or form a coalition. |
| Role | Project Role / Job Title | Their relationship to the project: Sponsor, Business Owner, End User, IT Architect, External Regulator. Not their HR job title unless it is the same thing. |
| Interest | Drop-down: High / Medium / Low | How significantly this person is affected by what the project delivers. High = their work, priorities or outcomes change substantially. Low = minimal direct impact on their day-to-day. |
| Influence | Drop-down: High / Medium / Low | How much power this person has to affect the project: to approve or block decisions, allocate or withhold resources, change requirements. Not seniority alone: an influential middle manager outranks a disengaged director. |
| Current Attitude | Drop-down: see scale below | How this stakeholder currently feels about the project: Strongly Supportive / Supportive / Neutral / Resistant / Strongly Resistant. Based on observed behaviour and direct conversation, not assumption. |
| Target Attitude | Drop-down: same scale | Where you want this stakeholder to be by the end of the project. Not always "Strongly Supportive", for some stakeholders, moving from Resistant to Neutral is the realistic and sufficient goal. |
| Engagement Strategy | Free text | The specific approach for this stakeholder, not a generic category but a concrete strategy. "Monthly one-to-one with PM to address concerns about data migration" not "Manage closely". |
| Comms Frequency | Free text | How often this stakeholder should receive proactive communication: Weekly / Fortnightly / Monthly / As needed. Links to the communications plan. |
| Notes | Context | Any relevant background: history with the project, known concerns, personal interests, relationships with other stakeholders or sensitivities that affect how engagement should be handled. |
Keep the register confidential. It holds honest notes about people's attitudes and influence. Store it securely, share it only with people who need it to run the project, and never send it to the stakeholders themselves. It is your working tool, not a message to them.
02 · Power / Interest Analysis
How does the power / interest grid work?
Place each stakeholder by Influence (power) and Interest and you get four groups, each needing a different approach. This grid stops you spending too much time on low-priority people and too little on the ones who can hurt the project.
High Influence + High Interest
Key Players: Manage Closely
Strategy: Actively involve and consult
These stakeholders can make or break the project. They care about it deeply and have the power to affect it significantly. Invest the most engagement effort here: regular one-to-ones, early involvement in decisions, proactive issue sharing.
Examples: Project sponsor, business owner, key decision-maker from the customer organisation.
High Influence + Low Interest
Meet Their Needs: Keep Satisfied
Strategy: Keep informed, satisfy concerns
Powerful but not focused on the project. They can block it if something triggers their attention. The engagement goal is to keep them satisfied and prevent them from becoming concerned. Avoid overwhelming them with detail: headline updates only.
Examples: Senior executive sponsor, divisional MD, regulatory authority with oversight.
Low Influence + High Interest
Show Consideration: Keep Informed
Strategy: Communicate regularly, listen
Significantly affected by the project but limited power to change it. These stakeholders generate the most noise when ignored, keep them informed, listen to their concerns and demonstrate that their input is considered even if it cannot always drive changes.
Examples: End users, affected operational staff, customer-facing teams.
Low Influence + Low Interest
Monitor: Minimum Effort
Strategy: Monitor and broadcast
Low priority for active engagement. Keep on the general communications list. Monitor for any change in interest or influence, a change in their role or the project's scope may move them to a different quadrant.
Examples: Peripheral departments, external observers, tangentially affected teams.
People move between quadrants. Someone in "Monitor" can move to "Manage Closely" if the scope grows into their area, if they get promoted, or if something raises their interest. Check every stakeholder's position at each phase gate, not just at the start. The dangerous stakeholders are the ones who moved and whose strategy you never updated.
03 · Attitude Scale
How do you use the attitude scale?
The Current Attitude and Target Attitude drop-downs use a five-point scale. The gap between them tells you how much work each stakeholder needs, and whether that work fits in your timeline.
✦
Strongly Resistant
Actively working against the project
✦
Resistant
Opposing or raising obstacles
✦
Neutral
Neither supporting nor opposing
✦
Supportive
Willing to help when asked
✦
Strongly Supportive
Actively championing the project
Using Current vs Target Attitude
The gap between Current and Target is your workload. Someone who is Resistant now, with a target of Strongly Supportive, needs a lot of steady effort. Someone already Supportive, with a target of Supportive, just needs you to keep things as they are.
Be realistic about targets. Moving a Strongly Resistant stakeholder to Neutral in a 3-month project may be possible. Moving them to Strongly Supportive probably is not. Set the target at the minimum attitude the project needs to succeed, not a dream result.
Keep the Current Attitude column up to date. Review it after every important conversation with that person. An attitude rating from 3 months ago is not an assessment any more. It is a guess.
Worked example
Example: stakeholder register rows for a building project
Here is how three rows might look on a building project in the UAE. This is an example only. In your own register, put a real person's name in the Name column, not just a role.
| ID | Name / role | Interest / Influence | Current to target | Engagement strategy |
|---|---|---|---|---|
| STK-001 | [Name], Resident Engineer (consultant) | High / High | Neutral to Supportive | Weekly submittal review meeting. Send drawings with a clear cover note so comments come back faster. |
| STK-002 | [Name], Civil Defence inspector (authority) | Low / High | Neutral to Neutral | Book inspections early, run our own pre-inspection first, have test records ready on the day. |
| STK-003 | [Name], Building facilities manager (client side) | High / Low | Resistant to Neutral | Invite to MEP walk-throughs before handover. Agree the training plan and O&M manuals list early. |
Mistakes I see when people fill this in
- Groups instead of people. "The consultant" has no attitude. The resident engineer does. Name the person.
- Everyone rated High / High. Then the grid tells you nothing. Be honest about who can really stop the project.
- "Manage closely" as the strategy. That is a quadrant, not a plan. Write what you will do and how often.
- Forgetting the end users. The facilities team who will run the building often has little power during the project but strong views at handover.
04 · FAQ
Stakeholder Register: 4 Common Questions
A stakeholder register lists everyone who has an interest in the project or is affected by it, with what you need to engage each one: role, interest, influence, current attitude, target attitude and engagement plan. In PMBOK 6 it is an output of the Identify Stakeholders process, and you keep updating it through the project. In PMBOK 8, Stakeholders is one of the seven performance domains. Keep the register confidential and never share it with the stakeholders themselves.
Interest measures how much a stakeholder is affected by the project: how significantly their work or outcomes change as a result. Influence measures how much power they have to affect the project: to approve or block decisions, allocate or withhold resources, change requirements. A stakeholder can have high interest but low influence (a deeply affected end user with no authority), or high influence but low interest (a senior executive who can block the project but has other priorities). Mapping both dimensions determines the right engagement strategy for each person, the power/interest grid in Section 02 shows the four resulting strategies.
Stakeholder attitude describes how a stakeholder currently feels about the project. The register tracks two attitude fields: current attitude (based on observation and direct conversation: Strongly Resistant to Strongly Supportive) and target attitude (where the PM needs them to be for the project to succeed). The gap between the two determines the engagement effort required. Be realistic: moving a Strongly Resistant stakeholder to Neutral in 3 months may be achievable; to Strongly Supportive probably is not. The current attitude column must be kept updated, an assessment 3 months old is a guess.
Review it at every phase gate, after any big event (scope change, delay, new sponsor) and whenever someone's attitude clearly changes. New stakeholders often appear after change requests bring new areas into scope. Update the Current Attitude column after every important conversation. A register made at kickoff and never touched again is history, not a management tool.
Explore More Free PM Resources
Keep learning
- Free Feasibility Study Template: Word Download
- Free Project Kickoff Agenda Template: Word Download
- Free Risk Register Template: Excel, Sheets & PDF
- Free RACI Matrix Template: Excel & Google Sheets
- Free WBS Template: Work Breakdown Structure Word Download
- Free Gantt Chart Template: Excel Download