Additional course links
This lesson is for membership, network and partner teams planning collection and engagement. You will produce a stakeholder-and-collection map. The map describes how to listen and work together; it is not a ranking of people’s worth or a requirement to identify every individual.
- Name the decision and its scope.
- List affected groups, contributors, delivery roles and decision owners.
- Separate groups, organizations, representatives and people.
- Choose engagement based on impact, knowledge, responsibility and access.
- Assign collection routes, owners and a useful return.
- Review missing voices and maintain the map as relationships change.
Which decision are you mapping?
Start with a concrete decision, such as revising a network’s annual support plan. A map for that task may differ from a map for evaluating an event or coordinating supplier evidence. Avoid building a master list of everyone the organization knows before deciding what it is for.
Ask who experiences the consequences, who knows about delivery, who supplies data, who can act and who may be overlooked. A current contact database is a starting source, not a complete account of relevant voices. People who have not joined, left recently or cannot access existing channels may matter to the decision.
How do you distinguish the entities?
A member organization, its representative and the people attending its activities are different. Record the relationships rather than mixing them in one undifferentiated stakeholder list. A representative’s survey response may describe organizational activity, but it does not automatically represent every member’s personal experience.
| Entity | Fictional network example | Collection implication |
|---|---|---|
| Member organization | Cedar Association | Annual activity return belongs to the organization and period. |
| Representative | Current nominated contact | Record who submitted the return and when their role applies. |
| Participant group | People attending a regional event | Experience feedback needs an appropriate participant route. |
| Organizer | Local host team | Operational report may arrive as a file with its own source and period. |
Use stable identifiers for continuing entities where identification serves the purpose. A group-level planning entry need not contain a list of named individuals. Review potential duplicate identities before merging; a shared name or email is not conclusive evidence.
How should you choose who needs attention?
Use several questions rather than a power score alone: how affected is the group, what relevant knowledge does it hold, what decision responsibility does it carry, and what barriers could prevent participation? Record the reason for the engagement choice.
A low-response member group may need an accessible collection route, not less attention because its apparent interest is low. A highly influential sponsor may need a formal review meeting, while participants need a suitable way to describe their experience. Those are different engagement tasks, not necessarily competing ranks.
If a priority tier helps manage staff time, define what it changes: urgency of contact, level of involvement or frequency of review. Do not make a tier an automatic reason to exclude affected people from evidence collection.
What should the collection map contain?
For each group, record the decision question, evidence needed, route, timing, owner and planned return. Allow local formats while agreeing the few core fields required for shared questions. Registration can supply stable profile context; recurring surveys and files capture changes and events.
| Group | Question | Route | Return |
|---|---|---|---|
| Member organizations | Which activities and support needs changed? | Annual return with a small common core and local detail. | Reviewed organization summary and appropriate network findings. |
| Event participants | What was useful or difficult? | Accessible post-event feedback under a clear privacy promise. | What the organizer will change and how to respond. |
| Local organizers | What happened operationally? | Existing report and supporting documents. | Specific clarifications and a useful review of delivery. |
This fictional map is a starting example, not a universal survey schedule. Add an ad hoc consultation or study where a separate question requires it. Do not make each new question another annual field by default.
How do you find missing voices?
Compare the map with the population affected by the decision. Ask local representatives who is absent and why, but do not assume one representative can answer for everyone. Review access, language, timing and previous response patterns.
Keep “not contacted,” “invited but no response,” and “represented through another source” distinct. None proves lack of interest. If some voices cannot be included in the current round, disclose the limitation and plan the next opportunity.
How does the map stay current?
Assign an owner and review it when roles, activities or decisions change. Preserve relevant relationship dates so a new representative does not inherit an earlier person’s statements. Update current profile fields while retaining history needed for comparison.
A diagram is one view of the underlying records. It does not maintain itself because identifiers exist. Decide which updates are automatic in the configured workflow and which require a person to review the relationship or engagement plan.
Where does Sopact fit?
You can begin with a table and source list. Sopact’s connected approach can keep recurring responses, organizational context and documents available together, using shared definitions for analysis. That helps the team revisit the map without rebuilding all the evidence from separate exports.
AI can suggest groups or questions from authorized material, but it cannot discover every missing voice from your existing contact list. People confirm the map, identity matches, access and engagement decisions. Test whether local context remains visible when summaries are prepared.
Practice: add the voice your list missed
Map one network decision using the example fields. Include a group affected by the decision that is absent from the current contact list. Write a suitable route to learn from it, who will arrange that route and what the group will receive in return. Explain why influence alone would have produced a weaker plan.
Frequently asked questions
Should high-power stakeholders always get most attention?
Not automatically. Consider affectedness, relevant knowledge, responsibility and barriers to participation as well as influence. Choose the engagement needed for the decision and document the reason.
Does every stakeholder need a personal record?
No. Some planning and feedback can remain at group or organization level. Use identified records only where they serve a justified purpose and appropriate access rules. Do not collect names merely to complete a map.
Can we merge duplicate-looking contacts automatically?
A possible duplicate needs a matching rule and review appropriate to the consequences. Shared names or inboxes may refer to different people. Preserve source identifiers and a correction path.
How does this connect to data collection?
The map determines whose evidence is needed, for which question, through which route and at what time. It also names the owner and useful return. That makes it an input to the collection plan rather than a diagram with no operational use.