A stakeholder engagement plan template you can use
A stakeholder engagement plan template records whom you need to involve, the decision their input will inform, how they can contribute, who owns the work and how you will report back. It should help a team run the engagement, review what it learns and follow through on commitments.
Start with one decision and a manageable set of groups. You can maintain the plan in a spreadsheet when the scope is small. Add software when repeated collection, permissions or the volume of evidence makes it useful; automation is not a prerequisite for a sound plan.
Download the editable plan template (CSV). Open it in Excel, Google Sheets or another spreadsheet application. It includes a clearly marked fictional example and a blank row to copy. No sign-up is required.
What to put in the template
The columns below cover both planning and follow-through. Leave findings and responses blank until there is evidence to enter. A planned consultation is not the same as an activity completed or a concern resolved.
Scroll horizontally to see all columns →
| Field | What to enter |
|---|---|
| Stakeholder group | The people or roles you need to hear from, including relevant locations or access needs. |
| Decision and purpose | The question their input will help answer and what can still change. |
| Input needed | The experience, evidence or choice you need them to contribute. |
| Method and access | The collection route, language, accessibility and confidentiality arrangements. |
| Timing and owner | When the work will happen and the person responsible for running it. |
| Evidence and coverage | Where the findings are stored, who contributed and whose perspective remains missing. |
| Decision or action | What was agreed, by whom and by when. |
| Report back and review | How contributors will hear the result and when follow-through will be checked. |
The downloadable version separates some fields into individual columns so you can filter by owner, date or status. Adapt the structure to your work. A group may need several rows when it contributes to different decisions or participates through different routes.
Before filling it in: three decisions to make
What is open for discussion?
Explain the boundary. If a reporting requirement is fixed, contributors may still help choose the collection process or the examples used to explain it. Do not present an information session as shared decision-making.
Who needs a practical opportunity to contribute?
Use your stakeholder analysis to identify affected people, not just existing contacts. Consider smaller sites, people with limited time, nonrespondents and those whose views may differ from a formal representative.
Who will review and act on the findings?
Name the review owner before collecting feedback. The person sending an invitation may not have authority to change the process. Agree how issues will reach the person who can decide and what response contributors can reasonably expect.
Filled example: changing a network's quarterly return
This fictional example concerns a business network with local offices. The central team needs comparable operating information; local teams want to avoid duplicate data entry. The decision is how to collect the shared core while allowing useful local detail.
Scroll horizontally to see all columns →
| Group | Purpose and input | Method, owner and timing | Review and report back |
|---|---|---|---|
| Local reporting coordinators | Identify duplicate fields and test whether instructions are clear. | A draft return plus an optional short call; reporting lead; before the pilot closes. | Compare issues by office size, revise the draft and send a change summary. |
| Site operations teams | Check whether source records support the requested measures. | A sample-record review through the site manager; operations owner; during the pilot. | Resolve unit and period differences before aggregating the returns. |
| Central decision owners | Confirm which questions the combined report must answer. | A review of the proposed measures; program sponsor; before collection. | Approve the shared core and explain why each field is needed. |
| Smaller offices not yet represented | Understand timing and access barriers. | Another invitation route and an alternative meeting time; engagement owner; before finalizing. | Record remaining coverage gaps and avoid claiming network-wide agreement. |
The plan leads to different activities for different groups. It does not force everyone to complete the same questionnaire. Only the information needed for common analysis requires shared definitions.
How to complete and use the template
- Add the decision and groups. Keep the first version limited to a real piece of work. Use separate rows when groups need different methods or response commitments.
- Write the input you need. “Feedback” is too vague. “Which source records can supply a quarterly count of completed cases?” gives contributors a clear task.
- Choose the least burdensome suitable method. Reuse recent evidence where appropriate. A short interview, form or document review may each serve a different need.
- Assign an owner and dates. Include time for interpretation and responding, not only for collection.
- Record findings and gaps. Link to the authorized source record and note who was not represented. Avoid putting sensitive raw comments in a widely shared spreadsheet.
- Record the decision and return it. State what changed, what did not and why. Check that promised actions were completed.
Review the plan at useful points in the work. The ONS recommends using stakeholder mapping to inform who should be contacted, when and how, then revisiting the assessment as the context changes. Source: ONS stakeholder mapping guidance.
Keep evidence and response status separate
A useful plan distinguishes what happened from what is intended. Choose status labels your team understands and define them in a note next to the sheet. For example:
- Planned: the activity has an owner and a proposed date.
- Collecting: people have been invited and input is arriving.
- Reviewing: the team is checking findings and gaps.
- Action agreed: a decision and responsible owner are recorded.
- Reported back: contributors have received the response.
- Follow-up checked: the team has reviewed whether the agreed action happened.
These labels describe different parts of the work. An action can be completed while a participant remains dissatisfied. A summary can be sent while a technical fix is still pending. Keep separate fields when a single status would hide those distinctions.
Consider a pilot with 20 offices invited and 12 returns received. Eight mention duplicate entry. The finding is eight of 12 responding offices, with eight offices still missing. If the team removes two duplicate fields, records the decision and sends a summary, it has acted and reported back. It should still test whether the revised process reduced work; a completed action is not proof of an improved experience.
Use a shared core without imposing identical forms
When local teams collect different information, define the small set needed for comparison: group or organization reference, reporting period, eligible activity and agreed measures. Keep stable registration information separate from recurring questions and update it when appropriate.
A data dictionary should explain each shared field's meaning, unit, source, missing-data rule and owner. If one office counts visits and another counts unique people, the plan should name the difference before a report combines them. Local questions can remain local when no shared comparison is needed.
For role-specific wording, see the stakeholder survey question examples. Use only the questions needed for the decision. The template is a coordination tool, not a reason to expand every survey.
Common template mistakes
Listing activities without decisions. A row saying “quarterly webinar” does not explain what you need to learn or what participants can influence. Add the purpose and response commitment.
Making one contact stand for a whole group. Check whether that person knows the relevant experience and whether additional perspectives are needed. Record the coverage limit rather than silently generalizing.
Treating all comments as public. Separate restricted evidence from a shareable summary. Explain access before collecting input, and do not promise anonymity where a small group or detailed comment may identify someone.
Filling the action column with “noted.” Record a decision, an owner or a reason no action will be taken. Acknowledgment alone does not tell contributors what happens next.
Adding complexity nobody maintains. Keep fields that support a decision or responsibility. A small manual plan can work well; a large automated one can still contain outdated assumptions.
When to connect the plan to a data workflow
A spreadsheet is useful for coordinating a small engagement. As evidence grows across sites and periods, a collection and analysis workflow can help keep sources, definitions and review decisions connected. Evaluate the work that is becoming difficult before choosing a tool.
Sopact's relevant role is recurring collection, analysis and governance. A pilot should show how partner or member context is retained, how comments and documents can be reviewed, and how the team maintains its own definitions and permissions. Confirm whether task tracking and notifications are native or require another system.
AI can help draft a summary, but an owner must review the interpretation and decide the response. Do not promise that adding a template will automatically keep every finding current or resolve every concern. Use the Membership & Networks course to plan the recurring workflow, and the feedback guide for reviewing what contributors say.
Frequently asked questions
What format is the downloadable template?
It is a CSV spreadsheet with column headings, a fictional example and a blank row. You can open it in Excel or Google Sheets and adapt the fields to your project.
Does every stakeholder need a separate row?
No. Group people who share a relevant role and participation need. Split rows when the decision, method, access needs or response commitments differ.
How long should the plan be?
Long enough to assign the work and explain the response, but short enough to maintain. A focused project may need only a few rows; a wider program may need linked plans by site or decision.
Can a communications plan replace this template?
A communications plan can cover messages, channels and timing. Add the input needed, review responsibility and response process when people are being asked to contribute to a decision.
How do we know a concern is resolved?
Define the expected result and review the evidence after action. Marking a task complete or sending a response does not necessarily mean the underlying concern has been resolved.
Choose your next step
ASME
See how stakeholder feedback supports a membership organization’s work.
Read the customer story →