Reviewing what an event was worth to each stakeholder
Members, sponsors, speakers, the board and your own team each judged the event by something different, and one summary line will not serve them all.
The short answer
A stakeholder value review asks, for each group, what they wanted from the event, what evidence you hold about whether they got it, and what you can only say as an opinion. Keep the groups separate, and label each statement as observed, estimated or not measured.
Value is judged by the people who receive it. Your own view of success, or an overall satisfaction score, is not a stand-in for any one group's view.
List the groups and what each wanted
Name the groups from your records, not from memory: members or delegates, speakers, sponsors or partners, suppliers, the board or funder, the organising team. Add public agencies or regulators only if they took part.
For each, write what they said they wanted before the event, in their words where you have them. If you did not ask, write that, and avoid guessing.
A review table
| Group | What they wanted | Evidence held | Evidence status | What cannot be said |
|---|---|---|---|---|
| Delegates | Practical learning and contacts. | Session feedback, follow-up requests. | Observed and estimated | Whether practice changed. |
| Speakers | An audience and a fair process. | Speaker debrief notes. | Observed | Whether it helped their work. |
| Partners | Visibility and relevant contact. | Their own comments, enquiries logged. | Estimated | Business outcomes. |
| Board or funder | Delivery to scope and budget. | Delivery report, finance summary. | Observed | Long-term impact. |
A review sequence
- List the groups and their stated wants, using your objectives-to-evidence map for the objectives.
- Gather evidence per group from records you hold, such as feedback, enquiries, debriefs and finance reports.
- Ask each group a short follow-up question only where a gap matters. Do not ask partners to prove commercial results.
- Mark each statement as observed, estimated or not measured in the benefit evidence tracker.
- Write one paragraph per group and one list of what the evidence cannot show, then check that no statement leans on attendance or satisfaction alone.
Where groups disagree
- Record the disagreement instead of averaging it away.
- Note when one group's gain was another's cost, such as a long sponsor slot that cut breakout time.
- Say who decides the trade-off for the next edition.
Cautions for sponsor and partner value
Report what a partner told you or what you logged, such as enquiries received, and avoid claiming sales or leads that you cannot see. Do not promise or imply future results from sponsorship.
If a partner shares its own figures, quote them as theirs. See attribution limits.
Worked example · Fictional example
A stakeholder review after a regional professional forum
Fictional organisation and findings, written to show how the review reads.
Persatuan Fiktif Perunding Kejuruteraan Awam reviews its forum by group. For delegates, it holds session feedback and 14 follow-up requests, which it marks as observed. For speakers, it holds debrief notes saying the briefing came late.
The board's wish was delivery to budget and scope, which the finance summary supports. A partner says it was pleased with visibility, but the secretariat holds only that comment and an enquiry log, so it records value as estimated and writes that business results are not known. The report ends with a section on what the evidence cannot show.
| Group | Evidence held | Status | Limit |
|---|---|---|---|
| Delegates | Session feedback; 14 follow-up requests | Observed | Whether practice changed is not known |
| Speakers | Debrief notes | Observed | Briefing arrived late for three of them |
| Partner | One comment; enquiry log | Estimated | Business results not known |
Use this yourself
Stakeholder value review worksheet
Copy into a spreadsheet and add a row per group. Fill only from evidence you hold.
- Groups where you did not ask what they wanted:
- Disagreements between groups, and who decides:
- Statements that rely only on attendance or satisfaction, to revise:
- One paragraph per group for the report:
| Group | What they wanted | Evidence held and source | Observed / estimated / not measured | What cannot be said | Who follows up |
|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have few stakeholder groups and one person who talked to most of them.
- The review is for the committee's own learning.
- Evidence is already in feedback, debriefs and finance summaries.
Outside planning help earns its fee when
- Stakeholders have conflicting views of success and the board needs a balanced account.
- Several teams hold the evidence and none owns the whole picture.
- The review will inform renewal, funding or partnership decisions.
Want stakeholder reporting to repeat each edition?
If the same groups need reporting each time and the evidence sits with different people, recurring programme management can set the review calendar, evidence owners and debrief sequence once. A conference project lead can run the debrief and evidence collection for a single event. Judgements about value stay with your organisation and the groups themselves.
Questions organisers ask
Do we need to survey every stakeholder group?
No. Use evidence you already hold, and ask a short follow-up only where a gap matters to a decision. Over-surveying partners and speakers adds burden without clear benefit.
How do I report sponsor value without selling?
Report what the partner said and what you logged, mark it as estimated or observed, and avoid claims about sales or future results. Offer them a chance to supply their own figures as theirs.
What if the board and delegates want different things?
Record both and say so. A review that explains the difference is more useful than a single blended score.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.