Stakeholder Analysis: How to Map Your Stakeholders (Template + Example)

November 14, 2026

GanttMaster

Plan Smarter. Execute Faster.

Interactive Project Management Tool, real-time collaboration.

⭐ 4.8 Rating • Trusted by modern teams worldwide

Most projects that go sideways do not fail because the schedule was wrong. They struggle because someone important was surprised: a facilities manager who learned about the renovation the week it started, a department head who was never asked about clinic hours, a neighbor who complained about early deliveries, or an owner who expected a weekly update and never got one.

A stakeholder analysis is how you avoid those surprises. It is a short, structured look at everyone who can affect your project or is affected by it, what they care about, and how you will work with each of them. This guide explains what a stakeholder analysis is, the power/interest grid, a step-by-step process, a template you can copy, and an illustrative example. It is written for project managers, construction and field teams, healthcare operations, and small business owners.

What is a stakeholder analysis?

A stakeholder is any person, group, or organization that can influence your project or will feel its results. That includes the obvious people (the client, the sponsor, the project team) and the less obvious ones (end users, inspectors, suppliers, neighbors, other departments that share a space or a budget).

A stakeholder analysis answers four questions:

  • Who has a stake in this project?
  • What does each of them want, need, or worry about?
  • How much influence and interest does each one have?
  • How will we involve and inform each one?

The result is usually a stakeholder register (a table with one row per stakeholder) plus a simple grid that shows where each one sits. It is not a one-time document. You create it at the start, ideally around the project charter and kickoff, and revisit it whenever the project changes phase.

Why it is worth an hour of your time

  • Fewer late surprises. Requirements and objections surface early, when they are cheap to handle, instead of during handover.
  • Better decisions about communication. You stop sending everything to everyone, and you stop forgetting the people who actually need to know.
  • Clearer approvals. You know who signs off on what before you need the signature.
  • Earlier risk warnings. An influential stakeholder who is unhappy is a project risk, and the analysis helps you spot one before it grows.

The power/interest grid

The most common tool for stakeholder analysis is the power/interest grid (also called the influence/interest matrix). You rate each stakeholder on two scales, power (how much they can affect the project) and interest (how much they care about it), and place them in one of four boxes:

  • High power, high interest: manage closely. Sponsors, owners, key clients, and department heads whose teams are directly affected. Involve them in decisions and keep them informed in detail.
  • High power, low interest: keep satisfied. Senior executives, regulators, or landlords who rarely look at the project but can stop it. Give them short, focused updates and bring them in for the decisions that need them.
  • Low power, high interest: keep informed. End users, staff working near the site, and residents. They want to know what is happening and when. Regular, clear updates go a long way.
  • Low power, low interest: monitor. People and groups with a small stake. Check now and then whether their position has changed, but do not flood them with information.

Positions move. A neighbor with low interest becomes very interested the day the noisy work starts. An executive with low interest becomes highly involved when the budget runs over. That is why the grid needs a quick review at every phase.

How to do a stakeholder analysis: 6 steps

1. List every stakeholder

Brainstorm with your team and start broad. Go through the project from start to finish and ask who approves, who pays, who does the work, who uses the result, who supplies materials or services, who inspects, and who is disrupted while the work happens. Write down groups as well as individuals, and split a group when its members want different things (for example, "nursing staff on the day shift" and "nursing staff on the night shift").

2. Describe what each stakeholder wants

For each name, note their main interest, their expectations, and their likely concerns. Be concrete: "keep two exam rooms open during the work" is far more useful than "supportive." If you do not know, write that down and plan a short conversation to find out. Guessing is where most stakeholder analyses go wrong.

3. Rate power and interest

Use a simple scale such as high, medium, and low, or 1 to 3. Do it as a team, since one person's view of who holds power is often incomplete. Then place everyone on the power/interest grid.

4. Note the current and desired attitude

Some teams add one more column: how the stakeholder feels about the project today (supportive, neutral, or resistant) and where you need them to be. The gap between the two tells you where to spend effort. A resistant stakeholder with high power deserves a plan of their own.

5. Plan how you will engage each one

Decide, for each stakeholder or group, what they need to receive, how often, through which channel, and who on your team owns the relationship. This is where the analysis feeds directly into your project communication plan. Give every key stakeholder one named owner, so updates do not depend on whoever remembers.

6. Review and update

Put a short stakeholder review on the schedule at each phase change, such as design sign-off, start of work on site, and handover. Ask whether anyone new has appeared, whether anyone's power or interest has changed, and whether the engagement plan is working.

Stakeholder analysis template

Copy these columns into a spreadsheet or a shared document:

  • Stakeholder (name, role, or group)
  • Organization or department
  • Main interest or expectation
  • Key concerns
  • Power (high, medium, low)
  • Interest (high, medium, low)
  • Grid position (manage closely, keep satisfied, keep informed, monitor)
  • Current attitude and desired attitude
  • Engagement approach (what, how often, which channel)
  • Relationship owner on the project team
  • Next review date
  • Notes

Keep the register private to the project team. Notes about a stakeholder's concerns or attitude are working notes, not something to send around.

Example: renovating a clinic waiting area

Here is an illustrative example for a small project: renovating the waiting area and reception desk of an outpatient clinic while the clinic stays open.

  • Clinic director (sponsor): wants the work finished within budget with minimal disruption to patients. High power, high interest. Manage closely: weekly progress check, involved in every scope or budget decision.
  • Facilities manager: concerned about access routes, after-hours work, and building systems. High power, high interest. Manage closely: joins planning meetings and approves the work schedule.
  • Reception and nursing staff: need a working temporary reception and clear patient routes. Low power, high interest. Keep informed: short notice before each phase and a named contact for problems.
  • Patients and visitors: want to find their way and wait in reasonable comfort. Low power, high interest. Keep informed: signage and notices at the entrance before each change.
  • Building owner or landlord: cares about approvals and the condition of the building. High power, low interest. Keep satisfied: notified of the plan up front and of any change that affects the building.
  • Contractor and trades: need clear working hours, access, and decisions on time. Medium power, high interest. Manage closely through the site schedule and regular coordination.
  • Neighboring tenants: worried about noise and deliveries. Low power, low interest at first. Monitor, and move them to keep informed before noisy work starts.

Notice how the analysis shapes the plan itself: after-hours work for noisy tasks, a temporary reception set up before demolition, and a checkpoint task for the facilities manager's approval before work on building systems begins.

Tips for a useful stakeholder analysis

  • Talk to people, do not just rate them. A ten-minute conversation tells you more than an hour of guessing.
  • Look for the quiet stakeholders. Night shift staff, cleaning crews, and delivery drivers rarely attend meetings but are often affected the most.
  • Turn concerns into tasks or risks. If a stakeholder worries about noise, plan the noisy work at a better time, or log it as a risk with a mitigation and an owner.
  • Keep it short. A one-page register that the team actually reads beats a long one that nobody opens.
  • Connect it to your RACI. The stakeholder analysis tells you who matters and why. A RACI matrix tells you who is responsible, accountable, consulted, and informed for each piece of work.

Common mistakes

  • Doing the analysis once at the start and never looking at it again.
  • Listing only the people inside the project team.
  • Treating a whole group as one stakeholder when its members want different things.
  • Rating stakeholders without ever asking them what they need.
  • Leaving engagement to "everyone," so in practice nobody owns it.

Putting your stakeholder plan to work in GanttMaster

The analysis itself lives in a document or a spreadsheet. The follow-through (meetings, approvals, notices, and the work they lead to) belongs in your project plan, where your team will see it. GanttMaster is a project management app for iPhone and iPad that helps with that part:

  • Invite members and organize teams. Add the people who work on the project, group them into teams, and give them a role: Project Manager, Team Manager, or User.
  • Assign engagement tasks. Turn "weekly update to the clinic director" or "notice to staff before phase 2" into tasks with dates, assigned to a user, a team, or both.
GanttMaster task details screen on iPhone showing task information, start and end dates, assigned user and assigned team.
Example project: a task with dates, an assigned user, and an assigned team.
GanttMaster iPad onboarding screen explaining teams, roles, and assignments: projects can include multiple users and teams, each team can have a manager.
Teams, roles, and assignments in GanttMaster.
  • Checkpoint tasks with dependencies. Add a short task for each key approval and link the work that depends on it on the Gantt chart, using Finish-to-Start, Start-to-Start, or Finish-to-Finish dependencies.
  • Per-task conversations and file links. Keep the discussion about a specific task in its comments, and attach links to meeting notes or notices.
GanttMaster Comments tab on iPhone with a team comment on a task, a Reply button, and an Add Comment field.
Example project: a conversation on a single task.
  • Stakeholder risks in the risk register. Log a concern from an influential stakeholder as a project risk with a category, likelihood, impact, mitigation plan, owner, and due date.
  • Status at a glance. Project cards show progress, total and overdue tasks, and members, so you can share an honest status in seconds.
  • Today view, reminders, and notifications. See what is due today, set a reminder before a stakeholder meeting, and get notified about task updates, comments, and assignments.
GanttMaster Projects list on iPhone with project cards showing progress bars, total tasks, overdue tasks, and project members.
Example projects: progress, total and overdue tasks, and members on each card.

There is no per-user pricing, so you can bring the whole team in without counting seats. GanttMaster is free to download with a 1-week trial, then $5.99 a month or $34.99 a year.

A stakeholder analysis does not need to be complicated. List the people, understand what they need, decide how you will work with each of them, and check the picture again as the project moves. Most surprises are avoidable when you know who to talk to and talk to them early.

GanttMaster logo

Plan it on your iPhone or iPad

Full disclosure: we make GanttMaster, an iPhone and iPad app with FS/SS/FF dependencies, tasks and subtasks, checkpoint tasks, a Today view with reminders, team assignment, risk and budget tracking, and no per-user pricing. It is free to download with a 1-week trial, then $5.99/month or $34.99/year.

Download on the App Store