Free Stakeholder Analysis Template (Fillable + Example)

What should a stakeholder analysis template actually contain?

Most templates in circulation are a five-column list: name, role, interest, influence, strategy. That is a starting point, not a working tool, because it records a position without recording a direction. You cannot tell from it whether the person is a supporter you are neglecting or a blocker you are flattering.

The eight columns below are the minimum for a map you will actually use. Each one answers a question that a project manager gets asked in a steering meeting.

The engagement scale is the one many teams are missing. PMI’s guide to project management popularised a five-level version — unaware, resistant, neutral, supportive, leading — assessed twice, once for the current state and once for the desired state. It sounds bureaucratic until you use it: “the CFO is neutral and needs to be supportive by the funding gate” is a plan. “The CFO is high power, low interest” is a description.

The fillable template

Copy the grid into a spreadsheet and fill it left to right. Leave the strategy column empty until the scores are done, or you will write strategies that flatter your existing habits.

Two rules make the grid behave. First, score power by decision, not by seniority: a facilities coordinator who controls building access has more power over a move than a vice president who controls none. Second, score interest by consequence, not by friendliness. Someone who is quietly hostile and unaffected by the outcome is a low-interest stakeholder, and treating them as high-interest wastes the scarcest resource you have, which is calendar time.

How do you fill it in without a two-day workshop?

Forty-five minutes, one projector, and no more than four people. Groups larger than that produce politics rather than analysis.

Minutes 0–10: name everyone. Brainstorm without judging. Include the people who can say no (security, legal, finance, works council), the people who do the work, and the people who will be blamed if it fails. The test for inclusion is simple: would this person’s opinion change a decision, or would they be materially affected by one?

Minutes 10–20: score power and interest. Go around the table once. Disagreement is useful here — if one person scores the operations director as high power and another as medium, the conversation that follows is the actual value of the exercise.

Minutes 20–30: score current engagement. Be pessimistic. A stakeholder who has never been briefed is unaware, not neutral. A stakeholder who raised an objection two months ago and received no answer is resistant until proven otherwise.

Minutes 30–40: set targets and pick owners. Target levels should be tied to the next gate, not to the end of the project. Every row needs an owner who is not the project manager, or the map quietly becomes one person’s private anxiety.

Minutes 40–45: agree the review date. Put it in the project calendar before anyone leaves the room. A map without a review date is a photograph.

Worked example: a warehouse relocation and WMS go-live

Northline Distribution is moving 22 staff and 4,100 pallet locations to a new facility while replacing its warehouse management system. Nine months, $480,000, and a go-live date fixed by a lease expiry. Fourteen people appear in the first brainstorm; eight survive the scoring.

Two rows carry the lesson. Sam, the security lead, is high power and low interest — the exact profile that gets a line in the template and no calendar invite. Dana is high power, high interest, and resistant: the person whose cooperation decides whether go-live stays go-live, and the only stakeholder with a weekly floor walk rather than a meeting.

Notice what the map does not do. It does not resolve Dana’s objection; it allocates the time in which the objection can be resolved. Templates are scheduling devices with a theory attached.

What do the four quadrants actually require from you?

The grid comes from Mendelow’s stakeholder mapping work, cited in the standard management literature as a 1981 conference paper, and its four quadrants have survived because the default actions are obvious once you see them.

The bottom-left quadrant deserves a warning. People move. A low-power, low-interest stakeholder becomes high-power the moment they are promoted, seconded to an audit, or asked to sign something. That is why the review date matters more than the initial score.

Which engagement level should you be aiming for?

Not everyone needs to be a champion. A project where twelve people are “leading” is a project with twelve owners and no decisions. The target should be the lowest level that removes the risk.

Two practical notes. Resistance that is never written down becomes folklore, so log objections and the answer given. And “leading” is a finite resource: a sponsor who spends political capital on your project has less for the next one, which is an argument for asking for it once, at the right moment.

How do you turn the map into an engagement budget?

Multiply the cadence by the people. In the Northline example, the eight mapped stakeholders imply 80.5 hours of engagement across the nine months.

Two Manage Closely stakeholders at 30 minutes a week for 40 weeks is 40 hours. Three Keep Satisfied stakeholders at 20 minutes a month for nine months is 9 hours. Six Keep Informed stakeholders at 15 minutes a fortnight across 20 fortnights is 30 hours, and three Monitor stakeholders at 10 minutes a quarter is 1.5 hours. The total is 80.5 hours, or roughly two hours a week.

That figure is the real output of the exercise, because it is a number you can defend. When a project manager says they have no time for stakeholders, the honest reply is that they have about two hours a week and are spending it in unplanned interruptions instead. Scheduled engagement is usually cheaper than the same conversations held in a corridor after something has gone wrong.

How do you know the map is working?

Score the gap and weight it by power. Power high counts 3, medium 2, low 1. Engagement runs 1 for unaware to 5 for leading. Multiply each stakeholder’s gap by their power weight and divide by the total weight.

In the Northline map, the weighted gaps are 3 for the CFO, 3 for the operations director, 6 for the supervisor, 9 for the security lead, 0 for the vendor, 2 for the union steward, and 0 for both low-power stakeholders. The total is 23 across a total weight of 18, which is an average gap of 1.28 levels on a four-level scale.

The useful part is not the average. It is that 15 of the 23 points — about 65% — sit with two people, and one of them is the stakeholder the original template would have listed last. That is the whole argument for scoring rather than listing: it tells you where the next two hours go.

What does one missed stakeholder cost?

Return to the security lead. Had the encryption gap surfaced at the design gate, remediation would have cost days. Surfacing at week 30, it costs three weeks: 21 days of delay against a lease expiry, which at $8,400 a month of double rent is about $5,880, plus 60 hours of weekend overtime at $45, or $2,700. The total is $8,580.

The two gate reviews that would have surfaced it cost 1.5 hours of three people’s time at $85 an hour, or roughly $382.50. The ratio is about 22 to 1 — and that comparison is generous to the project, because it ignores the credibility lost with the steering group when the go-live date moved.

This is the arithmetic that justifies the template’s most annoying column. Nobody needs a map to remember the sponsor. The map exists to force a scheduled conversation with the person who can stop you and has no reason to think about you.

Is power and interest enough?

No, and the gap is worth knowing. The salience model from Mitchell, Agle, and Wood adds legitimacy and urgency to power, producing seven stakeholder types and a useful warning: stakeholders with urgency but no power are noisy; stakeholders with power but no urgency are the ones that surprise you.

For most projects the two-axis grid is sufficient, because it is fast and it produces a calendar. Add urgency as a flag — a simple yes or no column — when deadlines are externally imposed, and add legitimacy when the project touches regulated or contractual obligations. Beyond three axes the template stops being fillable in forty-five minutes, and a template nobody fills in has no value at all.

What are the limits and trade-offs of a stakeholder template?

It is a political document, so keep it private. A stakeholder map that circulates becomes a statement about people’s loyalty, and the scores get managed rather than the relationships. Store it with the risk register, share it with the project leadership team, and never paste it into a channel.

It also rots fast. Influence shifts with reorganisations, budget cycles, and one bad quarter. A map that is six months old is a historical artefact, and using it confidently is worse than using nothing.

And it flatters the person who made it. Scores are judgements, not measurements, and they tend to encode whatever the project manager already believes. That is the strongest argument for filling it in with two or three other people and for writing the evidence next to each score.

What are the most common mistakes?

Listing organisations instead of people. “Procurement” cannot take a call.

Scoring by job title. Grades predict budgets, not behaviour.

Recording only supporters and blockers. The neutral majority is where go-live decisions actually get made.

Writing strategies that are really just status reports. A strategy changes what someone knows, decides, or does.

Skipping the review. The map is only accurate on the day it is drawn.

Which version do you need?

A three-month internal project with six people needs the eight-column grid and nothing else. A regulated, multi-site programme needs the full grid plus a salience flag, an objections log, and a gate-by-gate review.

The middle case, which is most projects, needs the grid plus one extra discipline: every row owned by someone other than the project manager. That single constraint converts an analysis into a set of commitments.

How does Doitify fit into this?

Doitify is our product, so treat this as disclosure. It holds projects, tasks, sub-tasks, checklists, owners, and due dates alongside Kanban boards, Gantt charts, roadmaps, calendars, workload views, work and performance reports, automations, import and export, and project documents, with Doitify Copilot and AI Coach helping turn a goal into a plan.

The part that matters for stakeholder work is the follow-through. A briefing cadence is a recurring task with an owner and a date; an objection is a task with a written answer attached; a gate review is a milestone, not a good intention. Doitify does not do the analysis for you, and a template is still a judgement call, but it does make the commitments visible enough to be kept.

Conclusion

A stakeholder analysis template earns its keep in three columns that most versions leave out: the decision a person controls, the level they are engaged at now, and the level you need by the next gate. Everything else — quadrants, colours, RACI codes — is a way of organising those three.

Fill it in with other people, score pessimistically, attach an owner to every row, and diarise the review. Then spend the two hours a week the map just told you the project requires, starting with the powerful person who has no reason to think about you yet.

If this post on stakeholder analysis template was helpful, you might also enjoy Project Management Software With Automation and Project Management Software for Research Teams: 2026 Guide.