Outcomes and post-event reporting
Event participation quality report
The headcount looks fine, but the committee wants to know whether the right people took part in the right way.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A participation quality report describes who was in the room, how they took part, and how that compares with the audience the event was meant for. It uses counts you can check and labels judgements as judgements.
It sits beside the attendance reconciliation. Reconciliation settles how many; this report asks who and how.
Define the intended participant first
Write down who the event was designed for: roles, sectors, seniority, membership status. Without that, quality can only mean more, which is not quality.
Agree which participation behaviours matter for your objectives, such as attending a whole day, joining a discussion, or meeting a named group.
Indicators you can collect
| Dimension | Indicator | Source | Watch out for |
|---|---|---|---|
| Fit | Share of attendees in the intended groups | Registration fields | Self-declared roles may be loose |
| Presence | Attendance by session, not only day totals | Session counts or check-ins | Counting method must be the same for every session |
| Active part | Questions, poll responses, workshop contributions | Facilitator and platform counts | Few outspoken people can inflate totals |
| Mix | Spread across sectors, regions or member types | Registration data | Small groups should not be identifiable |
| Return | Repeat attendance from last edition | Registration records | Needs consistent identifiers and a privacy check |
Report the pattern, then the cause you can support
Say plainly what the data shows: for example, senior roles were well represented on day one and thinner on day two. Offer possible reasons as possibilities and say what would test them.
Do not rank sessions by popularity alone. A smaller room can be the right room.
Keep people unidentifiable
- Report groups of a size that cannot point to one person.
- Hold registration data under the same rules as the registration purpose; ask the privacy owner before combining datasets.
- Keep names out of the report and use ranges where counts are small.
Worked example · Fictional example
A two-day forum aimed at mid-career managers
Fictional organisation and figures, illustrative only.
A fictional association designed its forum for managers in their third to tenth year in the profession. Registration showed 58 percent in that band, 27 percent more senior and 15 percent junior, as declared by registrants.
Session counts showed the Day 2 workshops held about half of Day 1's audience. The report records this as observed, suggests the schedule may be a reason, and flags that no exit feedback exists to confirm it.
Use this yourself
Participation quality report template
Copy and complete using your registration and session records.
- Intended participants and why:
- Fit: share of attendees in the intended groups (basis and source):
- Presence by session (method of counting):
- Active participation indicators and their limits:
- Mix and any groups too small to report:
- Pattern observed, in one or two sentences:
- Possible reasons, labelled as possibilities:
- Evidence missing and how to collect it next time:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Registration captured the fields you need and one person can read them.
- The question is simple, such as whether members or non-members attended.
- No cross-checking between datasets is required.
Outside planning help earns its fee when
- Data sits with several parties, for example host, ticketing platform and partner.
- Funders or a board expect a defined participation measure.
- Privacy rules on combining datasets are unclear.
Want participation measured the same way each edition?
A recurring programme manager can define the participant profile, the counting method and the evidence fields once, then carry them across editions so reports are comparable. For one event, a conference project lead can coordinate the data sources and check the privacy questions with the right owner.
Questions organisers ask
Is a high attendance rate the same as good participation?
No. It shows people turned up. Quality looks at fit with the intended audience and how people took part.
Can we publish the breakdown by company?
Only if the privacy owner confirms it, and only at group sizes that cannot identify individuals.
Do we need special tools?
Not at first. Registration fields and session counts in a spreadsheet are enough to start.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.