Stakeholder Engagement Plan: The 6 Steps, a Template, and a Full Example

Quick answer: A stakeholder engagement plan is a document that lists everyone affected by your project, how much power and interest each person has, how supportive they are today, how supportive you need them to be, and exactly how often you will talk to them. It turns “keep people informed” into a real schedule.

Most projects don’t fail because the work was bad. They fail because somebody important was surprised.

The finance director hears about the budget change in a meeting. The team that has to use the new system finds out two weeks before launch. By then, fixing the relationship costs more than fixing the project.

A stakeholder engagement plan stops that. It is a simple document that says who matters, what they care about, and when you will speak to them.

This guide gives you the full process, a copy-and-paste template, and a completed example you can copy the shape of.

What Is Stakeholder Engagement Plan?

A stakeholder engagement plan is a written plan for how you will communicate with everyone your project affects.

For each person or group it answers five questions:

1. Who are they, and what do they care about?
2. How much power do they have over the project?
3. How supportive are they right now?
4. How supportive do we need them to be?
5. What will we do about the gap, and how often?

That last question is the one that matters. A plan without a contact schedule is just a list of names.

A simple way to think about it

Imagine you are planning a surprise party for a friend.

Some people need to know everything: the friend’s partner, who has to get them to the right place. Some just need the address and time. One person must absolutely not find out, because they cannot keep a secret.

You already do stakeholder planning in your head for a party. A project just has too many people to hold in your head, so you write it down.

Why bother writing it down?

• You stop forgetting people. The ones you forget are the ones who object late.
• You spend your time in the right place. Not everyone deserves a weekly meeting.
• You can hand the project over. A new project manager can see who to call.
• You can prove you consulted people. This matters in regulated and public sector work.

Stakeholder Engagement Plan vs Stakeholder Register vs Communication Plan

These three documents overlap, and people mix them up constantly. Here is the difference.

Document	What it holds	The question it answers
Stakeholder register	The list: names, roles, contact details, interests, influence	Who is involved?
Stakeholder analysis	The assessment: power, interest, attitude, priority	Who matters most?
Stakeholder engagement plan	The actions: target engagement level, approach, owner, frequency	What will we do about them?
Communication plan	The mechanics: every meeting, report and email, with dates and formats	What gets sent, when, and how?
Stakeholder management plan	Often another name for the engagement plan, used more in formal settings	How do we manage all of this?

The order runs left to right. You build the register, analyse it, plan the engagement, then schedule the communication.

On a small project you can combine all of them into one table. On a large one, keep them separate, or the document becomes unusable.

Who Counts as a Stakeholder?

A stakeholder is anyone who affects your project, or is affected by it. That is wider than most people assume.

Group	Examples	Often forgotten?
Decision makers	Sponsor, steering group, budget holder	No
Delivery team	Project team, technical leads, contractors	No
End users	The people who will actually use the thing	Yes
Support functions	IT, HR, finance, legal, procurement	Yes
Suppliers	Vendors, agencies, consultants	Sometimes
Oversight	Auditors, regulators, compliance, health and safety	Yes
Affected outsiders	Customers, neighbours, other departments, unions	Yes

Three questions that find the stakeholders you missed

1. Who has to change how they work because of this project? They are stakeholders even if nobody invited them.
2. Who can say no? Anyone with a veto belongs on the list, however junior their title sounds.
3. Who will be blamed if this goes wrong? They will get involved eventually. Better early.

Ask your team these three questions in a 20-minute session. You will usually find three or four people nobody had listed.

How Do You Write a Stakeholder Engagement Plan?

Six steps. On a normal project this takes half a day, plus an hour a month to keep it current.

Step 1: List everyone

Get the team in a room and brainstorm names and groups. Don’t filter yet. A long messy list is the right starting point.

Write down the person’s name, their role, and one line on what they care about. “Cares about” is more useful than job title. The finance director cares about the budget forecast, not about your Gantt chart.

Use your project charter as a starting point — the sponsor and main groups are usually already named there.

Step 2: Rate power and interest

Give each stakeholder two scores, high or low.

• Power: can they change the project’s direction, budget, or whether it happens at all?
• Interest: how much do they personally care about the outcome?

Keep it to high and low. A five-point scale sounds more precise but starts arguments that waste an afternoon.

Step 3: Assess their current attitude

This is the step most teams skip, and it is the most useful one.

For each stakeholder, ask: how supportive are they today? Use these five levels:

Level	What it looks like
Unaware	Doesn’t know the project exists
Resistant	Knows about it, and is against it
Neutral	Knows about it, doesn’t care either way
Supportive	Wants it to succeed, will help if asked
Leading	Actively drives it forward without being asked

Be honest here. Writing “supportive” for someone who is actually resistant does not make them supportive. It just means your plan is wrong.

Step 4: Decide the level you need

Now ask a different question: what level do we actually need from this person?

Not everyone needs to be “leading.” For many stakeholders, “neutral” is a perfectly good target. You need them not to block you, and that is all.

The gap between current and needed is your whole plan. If someone is already where you need them, you only have to keep them there.

Step 5: Choose the approach and the owner

For each gap, decide what you will do and who will do it.

Match the messenger to the person. A resistant finance director will respond better to the sponsor than to a project coordinator. Peer to peer works; junior to senior often doesn’t.

Write the owner’s name. “The team will engage with them” means nobody will.

Step 6: Set the frequency and write it in

Give each stakeholder a contact rhythm and a format. Weekly email, monthly meeting, quarterly steering group.

Then put those into your actual calendar and your project schedule. A plan that lives only in a document gets forgotten by week three.

What Is the Power Interest Grid, and What Do You Do With It?

The power interest grid sorts stakeholders into four boxes, based on their two scores. It is the most widely used tool in stakeholder analysis.

Most guides show you the grid and stop there. The grid is not the plan. Each box gives you a different stakeholder engagement strategy, and those strategies are the plan.

Box	Power / Interest	Strategy	What that means in practice
Top right	High power, high interest	Manage closely	Involve them in decisions. Meet regularly. Ask their opinion before you need their approval.
Top left	High power, low interest	Keep satisfied	Short, clear updates. Never surprise them. Escalate only what needs their decision.
Bottom right	Low power, high interest	Keep informed	Regular updates, and a real route for feedback. These people become your advocates.
Bottom left	Low power, low interest	Monitor	Light touch. Include in general announcements. Re-check occasionally in case their interest rises.

Two rules people get wrong

“Monitor” does not mean ignore. People move between boxes. A quiet department becomes a high-interest stakeholder the moment your project touches their work. Re-do the grid at every project phase.

“Keep satisfied” does not mean keep quiet. High-power, low-interest people are the ones who cause the biggest problems when surprised. They pay little attention, then object loudly and late. Short regular updates are cheap insurance.

When the grid is not enough

On complex projects, two boxes are not enough detail. The salience model adds a third factor:

• Power — can they make things happen?
• Legitimacy — do they have a proper right to be involved?
• Urgency — do they need an answer now?

Someone with all three is your top priority. Someone with only urgency is loud but can wait. It is more work than the grid, so use it only when the grid genuinely isn’t separating people well.

What Is the Engagement Assessment Matrix?

The engagement assessment matrix is a simple table showing where each stakeholder is now, and where you need them to be. It is the part that turns analysis into action.

Mark the current level with a C and the desired level with a D.

Stakeholder	Unaware	Resistant	Neutral	Supportive	Leading
HR Director (sponsor)				C	D
Finance Director			C	D
IT Manager				C, D
Line managers		C	D
Union representative		C	D
Staff (end users)	C			D

Read it in one glance. Where C and D sit in the same box, you are fine — just maintain. Where they are apart, you have work to do, and the distance tells you how much.

This one table does more than pages of notes. It is also the easiest thing to show a sponsor, because it makes your engagement effort visible.

How Often Should You Contact Each Stakeholder?

Frequency is where most plans go vague. “Regular updates” means nothing. Put a real rhythm against each group.

Grid position	Typical rhythm	Format
High power, high interest	Weekly, plus a monthly formal review	Meeting or call, plus a written summary
High power, low interest	Monthly	One-page written update, half a page if possible
Low power, high interest	Every two weeks	Email update, plus an open channel for questions
Low power, low interest	At milestones only	General announcement
Anyone who is resistant	Weekly, until they move	Face to face, one to one

Three adjustments worth making:

• Increase frequency near a change. Before a go-live, everyone moves up one level.
• Decrease it when things are steady. Weekly meetings with nothing to say teach people to stop attending.
• Resistant people need face-to-face time. You cannot email someone out of an objection. You need to hear what is actually bothering them.

The Stakeholder Engagement Plan Template

Copy this and fill it in. On a small project the table alone is enough.

STAKEHOLDER ENGAGEMENT PLAN

Project:
Project manager:                 Sponsor:
Date:                            Version:          Next review:

SECTION 1 — STAKEHOLDER TABLE

| Name / group | Role | What they care about | Power | Interest |
|              |      |                      | H/L   | H/L      |

SECTION 2 — ENGAGEMENT LEVELS

| Name / group | Current level | Needed level | Gap? |
|              | unaware / resistant / neutral / supportive / leading |

SECTION 3 — ENGAGEMENT ACTIONS

| Name / group | Approach | Owner | Frequency | Format |
|              |          |       |           |        |

SECTION 4 — KEY MESSAGES

| Audience | Main message | What to avoid saying |
|          |              |                      |

SECTION 5 — ESCALATION

Who to escalate to, and when:
Decision maker for stakeholder conflicts:
Response time expected:

SECTION 6 — REVIEW

Plan reviewed: monthly / at each phase gate
Reviewed by:
Trigger for an early review:
(e.g. a new senior stakeholder joins, or a major scope change)

Approved by:                     Date:

What Does a Completed Stakeholder Engagement Plan Look Like?

Here is a filled example. The project is a new HR and payroll system for a services company with 400 staff, running over 9 months.

Section 1 — stakeholder table

Name / group	Role	What they care about	Power	Interest
Sana R.	HR Director, sponsor	Getting the system live before the next pay year	High	High
Daniel K.	Finance Director	Cost control and accurate payroll output	High	Low
Priya M.	IT Manager	Security, and not inheriting an unsupported system	High	High
Line managers (32)	Approve leave and timesheets	Not having more admin work	Low	High
Staff (400)	End users	Getting paid correctly and on time	Low	High
Tomas B.	Union representative	Fair treatment, no job losses, staff consulted	Low	High
Vendor team	Supplier	A clean delivery and a reference customer	Low	High
Payroll team (4)	Run payroll each month	Not breaking payroll during the switch	Low	High

Section 2 — engagement levels

Name / group	Current	Needed	Gap?
Sana R.	Supportive	Leading	Yes — needs to champion it publicly
Daniel K.	Neutral	Supportive	Yes — needs to defend the budget
Priya M.	Supportive	Supportive	No — maintain
Line managers	Resistant	Neutral	Yes — they expect more admin
Staff	Unaware	Supportive	Yes — biggest gap on the project
Tomas B.	Resistant	Neutral	Yes — worried about job losses
Vendor team	Supportive	Supportive	No — maintain
Payroll team	Neutral	Supportive	Yes — they carry the risk at switchover

Section 3 — engagement actions

Name / group	Approach	Owner	Frequency	Format
Sana R.	Give her the launch announcement to deliver herself	PM	Weekly	30-min call
Daniel K.	One-page cost and benefit summary, no jargon	PM	Monthly	Written
Priya M.	Include in all technical decisions	Tech lead	Weekly	Stand-up
Line managers	Show the time it saves, not the features. Run a hands-on demo.	HR lead	Fortnightly	Demo and Q&A
Staff	Early, honest announcement. Explain what changes for them.	Comms lead	Monthly, then weekly near go-live	Email and team meetings
Tomas B.	Meet before any announcement. Answer the job question directly.	Sana R.	Weekly	Face to face
Vendor team	Clear requirements, fast decisions	PM	Weekly	Call
Payroll team	Parallel run, full training, named support contact	HR lead	Weekly	Working session

Section 4 — key messages

Audience	Main message	What to avoid
Staff	You will be paid the same way, on the same date. Requesting leave gets easier.	“Efficiency savings” — it sounds like job cuts
Line managers	Approvals move from paper to two clicks on your phone	Listing features they didn’t ask for
Finance	Costs are fixed; payroll errors should fall	Vague benefit claims with no number behind them

What happened

The union representative was the turning point. Sana met him before the company-wide announcement, not after, and answered the job security question in plain terms.

He moved from resistant to neutral within three weeks. Because he did, the staff announcement landed calmly instead of setting off a rumour cycle.

The line managers were harder. The first demo focused on features and went badly. The second one showed a manager approving leave on a phone in eight seconds, and the mood changed in the room.

The lesson recorded: the order of conversations mattered more than the content. Telling the union rep first cost one meeting. Telling him second would have cost months.

How Do You Handle Difficult Stakeholders?

Four situations come up on nearly every project. Here is what works.

The blocker who won’t approve

Someone with authority keeps delaying a decision.

Usually this is not stubbornness. It is unclear risk, no time, or a worry they haven’t said out loud. Ask directly: “what would you need to see to be comfortable approving this?” Then give them exactly that, in writing, with a deadline and a named consequence of no decision.

If it continues, escalate to your sponsor with facts and dates, not frustration.

The silent stakeholder

They ignore your emails for months, then object loudly at launch.

Change the channel. Someone who doesn’t read emails may answer a five-minute call. Get their sign-off in writing at each phase, so silence stops counting as agreement. Write into your plan: “no response within 5 working days is treated as approval, and this was agreed on [date].”

Two stakeholders who want opposite things

Finance wants it cheaper. The users want it richer. Both are senior.

Do not try to please both quietly — you will fail both. Put the conflict in front of your sponsor with three options and a clear recommendation, showing the cost and impact of each. A decision made openly is one you can build on. A compromise made privately gets reopened.

The one who changes their mind

Every month they want something different.

Move them to a formal change process. Every new request goes in writing, gets costed, and needs approval. This is not bureaucracy for its own sake — it makes the cost of changing direction visible to the person asking.

How Do You Keep the Plan Alive?

Most stakeholder plans are written once and never opened again. Four habits stop that.

• Review it monthly, or at each phase gate. People change roles. New senior people appear. Attitudes shift.
• Re-check engagement levels after any major event. A missed deadline can turn a supportive stakeholder resistant in a week.
• Track what you actually did. Log meetings and updates. When someone says “nobody told us,” you will have dates.
• Set an early review trigger. Write down what forces an unscheduled review — a new sponsor, a scope change, a reorganisation.

When the project ends, the plan feeds your closure report: who was engaged, what worked, and which relationships the next project inherits.

How Does Stakeholder Engagement Change by Project Type?

The process is the same. The hard stakeholders are different.

Project type	The tricky stakeholders	What usually works
Internal software rollout	End users, line managers, IT support	Early hands-on demos; show time saved, not features
Construction	Neighbours, councils, regulators, site teams	Public consultation early; a single named contact
Organisational change	Staff, unions, middle managers	Talk to representatives before announcements
Marketing campaigns	Brand, legal, sales, external agency	Agree approval routes and turnaround times upfront
Product launches	Support, sales, early customers	Give support teams the information first
Public sector	Residents, elected members, oversight bodies	Document every consultation; assume it will be reviewed

One pattern runs through all of them: the people who have to change how they work are the most important stakeholders, and the most often ignored.

What Are the 8 Most Common Stakeholder Engagement Mistakes?

1. Only listing senior people. The people who use the thing daily decide whether it succeeds.
2. Writing the grid and stopping. Analysis is not engagement. The actions are the plan.
3. Recording a flattering attitude instead of the real one. A plan built on wishful thinking fails quietly.
4. Treating everyone the same. Equal effort for everyone means too much for some, too little for those who matter.
5. Announcing before consulting. Once people hear news secondhand, you are repairing rather than building.
6. No named owner per stakeholder. Shared responsibility means nobody makes the call.
7. Vague frequency. “Regular updates” is not a commitment anyone can keep or check.
8. Never updating it. A six-month-old plan describes a project that no longer exists.

What Software Tools Help You Manage Stakeholder Engagement?

Four jobs need doing. Different tools suit each.

Job	What to look for	Type of tool
Holding the register and analysis	Custom fields for power, interest, current and desired level; filtering	Spreadsheets, or a project platform with custom fields
Scheduling the contact rhythm	Recurring tasks, calendar integration, reminders per owner	Project management or calendar tools
Writing the plan and the updates	Templates, version history, shared editing	Document and wiki tools, plus AI writing assistants
Logging what actually happened	A simple dated record of meetings and updates sent	Any shared document, or your project tool’s comments

Two practical points. Keep it where the team already works — a perfect plan in an unopened folder does nothing. And keep the register in something sortable, because a table you can filter by “resistant” is worth far more than a pretty diagram.

How Does Writegenic AI Fit In?

Stakeholder engagement generates a steady stream of writing: the plan itself, monthly updates for people who won’t read more than a page, announcement emails, and the careful message you send a stakeholder who is unhappy.

The Writegenic AI stakeholder engagement plan generator drafts the plan structure from your project details, so you start from a filled outline rather than a blank page.

You can also use Writegenic AI to:

• Draft the plan from your stakeholder list and project brief
• Write the one-page update for a high-power, low-interest stakeholder
• Rewrite a technical update in plain language for end users
• Draft a difficult message to a resistant stakeholder, then soften or sharpen the tone
• Turn meeting notes into a dated engagement log

Explore AI for project management, browse the project management tools, or use the prompt generator to write sharper instructions for your drafts.

Draft with the tool, keep the judgement. AI can build the structure and write a clear update in seconds. It cannot know that your finance director hates long emails, that the union rep must be told first, or that one manager is quietly against the whole thing. Those judgements are yours, and they are the part that decides whether the project lands.

Try Writegenic AI free

Frequently Asked Questions

Related reading:

• Project Charter Templates With Real Examples
• Project Planning and Scheduling: Steps + Example
• Contingency Plan in Project Management: Template + Example
• Risk Assessment Plan: How to Write One + Template
• Project Closure: Checklist + Closure Report Template