Event stakeholder register: who matters and who owns what
Different people expect different things from your event, and some of them will only speak up when something changes.
The short answer
A stakeholder register lists every person or group with a stake in the event, what they need, how much say they have, and who in your team owns the relationship. It is a working table, reviewed at each committee meeting.
Its main use is to expose gaps: an approver nobody has spoken to, a funder with a reporting expectation, a venue contact who changed, or a group affected but never consulted.
Who belongs in the register
- Decision-makers: sponsor, chair, treasurer, council or board, funder.
- Delivery parties: committee members, volunteers, venue, suppliers, speakers, co-hosts.
- Audience and influencers: member categories, employers who approve attendance, partner associations.
- Affected groups: venue neighbours, other departments, staff who cover for attendees.
- Authorities and specialist parties whose answers you need, such as licensing, accreditation or data protection contacts. Note the question owed, not the answer.
A decision sequence to build it
- Brainstorm names and groups with two or three committee members, using the charter and scope as prompts.
- For each, write what they need from the event and what they could stop or change if unhappy.
- Rate influence and interest as high, medium or low, and group them: manage closely, keep satisfied, keep informed, monitor.
- Name an owner for each relationship, by role, and the next contact date.
- Link to roles in the responsibility matrix so each stakeholder question has a person to answer it.
How the groups are handled
| Group | Influence and interest | How to handle |
|---|---|---|
| Manage closely | High and high | Regular contact, involve in decisions, record agreements. |
| Keep satisfied | High influence, lower interest | Brief updates at key points, no surprises. |
| Keep informed | Lower influence, high interest | Clear communication, a route to ask questions. |
| Monitor | Low and low | Check at review meetings. |
Keeping it alive
Review the register at each committee meeting for new names, changed roles and promises made. Record agreements and open requests in the decision log.
Keep personal details to what the team needs, restrict who can see it, and ask the person responsible for data protection if you are unsure what is appropriate.
Worked example · Fictional example
A fictional register for a co-hosted forum
Fictional organisation and figures, illustrative only.
Two fictional associations co-host a one-day forum. The register has fourteen rows. The funder is high influence and moderate interest, owned by the treasurer, with a progress note due before the venue deposit.
While building it, the secretariat finds that nobody owns the relationship with the partner association's president, who can approve the use of its logo. The vice-chair is named owner, with a call booked within the week.
Use this yourself
Stakeholder register
Copy this table into a shared spreadsheet. Add a row per person or group, and name roles rather than only people.
| Stakeholder | Role in the event | What they need | Influence | Interest | Relationship owner (role) | Next contact and date |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- The committee is small and knows most of the stakeholders.
- There is one clear sponsor and a short approval chain.
- Someone will update the register after each meeting.
Outside planning help earns its fee when
- Co-hosts, funders and councils each have a different expectation and none has agreed who speaks to whom.
- Stakeholder relationships depend on one person who is leaving.
- A project lead is needed to hold the contact rhythm and flag conflicts early.
Want stakeholder contact managed, not just listed?
A scoped conference project lead can build the register with your committee, assign a relationship owner to each stakeholder, and run the contact rhythm, flagging decisions that need an approver. Where the workstream is yours, the lead coordinates and reports; your approvers keep the decisions.
Questions organisers ask
How many stakeholders should the register hold?
Ten to twenty for a professional event is typical. If it is longer, group minor ones.
Who should own the register?
The day-to-day lead, with each row assigned to a relationship owner. Review it at each committee meeting.
Is a stakeholder register the same as a RACI?
No. The register records who matters and what they need. The responsibility matrix records who does, approves, advises and is told about each task.
Should speakers and sponsors be in it?
Yes, as delivery parties or funders, with the person who owns the contact. The register records the relationship, not any commercial terms.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.