What is an event feedback survey?
An event feedback survey collects participants' assessments of an event so organizers can decide what to keep, change or investigate. It can cover relevance, delivery, access, logistics and the participant's next steps. A useful survey connects each question to a decision; it is more than a request for a satisfaction score.
For an association, the decision may concern the next annual conference. For a business network, it may be whether a meeting helped members make useful connections. For a training program, it may be which parts participants can apply at work. Choose the questions that fit that purpose rather than sending every audience the same form.
The practical sequence is simple: choose the decision, ask the relevant people, review the results with their limitations, assign improvements and tell participants what changed. This guide provides questions and a worked example you can adapt.
A short post-event survey you can adapt
Start with a small set of questions. The following is a draft for a professional event, not a validated scale or a questionnaire that every event should use. Replace the event name and test it with a few people before sending.
- What was your main reason for attending [event]? Offer options that reflect the event's purpose, such as learning about a topic, meeting peers, finding partners or sharing expertise, plus another reason. Ask for one main reason if you need a primary-goal breakdown.
- How well did [event] meet that goal? Use a clearly labelled scale, such as not at all, slightly, moderately, very well and extremely well. Keep the scale unchanged if you plan to compare events.
- Which part of [event] was most useful to you? Use a short text field. This can reveal something the organizer did not anticipate.
- What, if anything, made it difficult for you to participate? Allow people to describe an obstacle. If you provide a checklist, include an other option and distinguish “no difficulty” from missing answers.
- What is the one change you would most like us to make? A focused open question helps the team identify an actionable suggestion.
- What do you expect to do next because of the event? Offer relevant actions and “nothing planned” or “not sure.” Treat these as intentions, not completed outcomes.
Add a separate overall satisfaction question if it serves a reporting decision. For example: “Overall, how satisfied or dissatisfied were you with [event]?” Use a balanced set of response options from very dissatisfied to very satisfied. An overall score helps track a consistent measure, while the specific questions help interpret it.
Avoid combining several topics into one rating, such as “How good were the speakers, venue and networking?” A participant may have different answers to each. Pew Research Center's question-writing guidance explains why wording and response options deserve careful testing.
Ask different questions when the role is different
An attendee, exhibitor, speaker and volunteer may all attend the same event but experience different parts of it. Give each the questions they can answer. Keep a few shared measures only when their meaning is genuinely comparable across groups.
Scroll horizontally to see all columns →
| Audience or topic | Example question | Decision it supports |
|---|---|---|
| Session attendee | How relevant was this session to the work you do? | Which topics or audience descriptions need revision? |
| Session attendee | What is one idea from this session you would like to try? | What practical follow-up could help? |
| Networking participant | Were you able to meet the kinds of people you hoped to meet? | Should introductions, group sizes or meeting formats change? |
| Remote participant | Which parts of the event, if any, were difficult to access online? | What technical or participation barriers need investigation? |
| Speaker | What information or support would have helped you prepare? | How should speaker onboarding improve? |
| Exhibitor or partner | How well did the opportunities provided match the goals agreed before the event? | Should the partner offer or delivery change? |
| Volunteer | Were your responsibilities clear before your shift began? | Where do briefings or handoffs need attention? |
| Non-attending registrant | What prevented you from attending? | Which registration or attendance barriers should be reviewed? |
Do not ask non-attendees to rate the event itself. Do not ask someone to rate a session they did not attend. Use routing or an explicit not-applicable option. If one person holds several roles, decide whether they need one combined survey or separate short sections, and keep that choice visible in the analysis.
When should you send the survey?
Choose timing based on what you want people to remember or demonstrate. A brief session question can capture an immediate experience. An event-level follow-up soon afterward gives people space to reflect. A later check-in is needed if you want to know whether someone applied an idea or continued a new relationship.
There is no single timing rule that proves every event's value. Write down the schedule and keep it consistent enough for the comparisons you intend to make. Record the event date and response date so late responses are not silently treated as immediate reactions.
Explain why you are asking, how the response will be used and whether it will be linked to registration. Give an honest completion-time estimate based on a test. If you send a reminder, avoid repeatedly contacting people who have already responded where your collection setup can identify completion without undermining promised anonymity.
A QR code at the venue can be convenient, but it may miss people who leave early or cannot access it. An email may miss people whose registration address is shared or rarely checked. Use channels that suit the audience and document coverage rather than assuming one distribution method reaches everyone.
Keep the event, person and response distinguishable
For a recurring event series, use a stable event identifier and a clear reporting period. Session responses should also identify the session. If you are allowed to link a participant's responses over time, retain an appropriate participant identifier rather than matching names by guesswork.
Keep the units separate. One person can submit feedback on three sessions and one overall event. That is four response records, not four people attending. A staff member may submit an organizer report on behalf of an event; it should not enter the attendee satisfaction denominator.
Anonymous feedback has a different purpose from a named follow-up record. Do not promise anonymity and then use hidden registration details to identify the respondent. If people want contact, explain that separately and make the choice clear. Design the feedback and follow-up processes together before distributing the form.
Across chapters or locations, agree a small shared core: event type, period, audience, attendance definition and any common rating. Local organizers can add questions. A data dictionary should state the wording, scale, unit and eligible respondents for each shared measure. Similar-looking questions with different meanings should not be averaged together.
How to analyze event feedback without losing context
Begin with coverage, not the average. Record how many eligible people were invited, how many responded and how many answered each question. Compare the respondent mix with what you know about the attendee mix. A survey dominated by one role may leave another role's experience largely unseen.
Then examine the structured responses. Show the distribution as well as any summary measure: a middle average can hide a split between satisfied and dissatisfied groups. Keep not-applicable and unanswered responses distinguishable. Use the same definition when comparing events, and label changes to wording or scales.
Read comments using a small set of clear themes. Keep examples for each theme, allow multiple themes when needed and retain the source passage. Review unclear comments and examples that do not fit the dominant interpretation. If AI assists with coding or summaries, check its output against the original responses before sharing findings.
Finally, connect the themes to the decision. “Networking” is a topic, not an action. “First-time attendees described difficulty joining established groups” suggests a design question about introductions. A specific reported issue provides a stronger starting point than a general positive or negative label.
Worked example: from responses to a planning decision
This fictional example illustrates reporting, not a customer result. A professional network has 200 eligible attendees and receives 120 event-survey responses. Of those, 100 answer the overall satisfaction question and 70 provide a comment.
- The overall survey response rate is 120 out of 200, or 60%.
- If 80 of the 100 satisfaction answers are satisfied or very satisfied, report 80% of those answering that question—not 80% of all attendees.
- If 21 of the 70 commenters mention difficulty meeting new people, report 21 commenters, or 30% of commenters. This does not show that 30% of all attendees had that difficulty.
Suppose the comments suggest that first-time attendees found introductions difficult. Check the number of first-time attendees responding and inspect what they actually said. Do not turn a few vivid comments into a claim about every newcomer. If the group is small, use it as a reason to investigate rather than publishing an unstable percentage.
The planning team might test facilitated introductions at the next event. Record the change, the owner and how it will be reviewed. Ask a comparable question next time, while checking whether the audience or event format changed. An improved result would be useful evidence for continued review, but it would not alone prove the intervention caused the improvement.
Turn findings into a small, owned improvement list
Rank findings using more than mention counts. Consider the seriousness of the experience, which groups are affected, the strength of the evidence and whether the team can act. A less frequent access problem can deserve attention even when it is not the largest theme.
Scroll horizontally to see all columns →
| Finding | Next action | Owner and review |
|---|---|---|
| Some newcomers could not find an easy way to join conversations. | Test an optional facilitated introduction at the next event. | Event lead; review participation and the relevant feedback question. |
| Remote participants describe difficulty hearing audience questions. | Check the recording and technical setup; agree a microphone procedure. | Production lead; test before the next session and ask remote attendees afterward. |
| Several people request deeper coverage of a topic. | Check demand and propose a focused follow-up session. | Program lead; review interest before committing resources. |
These are example actions, not automatic conclusions. Keep each approved action connected to the finding and its sources. Record a decision not to act as well: the reason may be useful when the same suggestion appears next time.
Tell participants what happened next
Close the feedback process with a short account of what the team heard, what it will change and what still needs investigation. Avoid exposing personal details through quotes or small-group breakdowns. Ask for permission where necessary before using an identifiable comment publicly.
A useful update might say: “Respondents asked for easier introductions. At the next meeting we will test a hosted welcome session. We also heard interest in a specialist workshop and are checking demand.” It should not promise that every suggestion will be adopted.
Keep the approved summary with the event record. Future organizers should be able to see the question, result, limitation and decision together, rather than rediscovering them in a slide deck or an old inbox.
What should your collection and analysis workflow support?
Test practical requirements: audience routing, clear question versions, permitted links to registration, separate session and event records, reusable definitions, source-based comment review and an export your team can understand. Verify the relevant permissions and integration details in the actual setup.
For an association or network running recurring events, Sopact can be evaluated as part of a broader collection, analysis and governance workflow. The useful question is whether the team can bring its evidence together and maintain the process between events. A summary generated by AI is only one step; reviewed findings and follow-through still need owners.
Plan a recurring network evidence workflow in the Academy →
Build the wider member satisfaction survey →
Frequently asked questions
How many questions should an event survey have?
Use the smallest set that supports your decisions. Start with a short core, then add relevant role or session questions. Test the completion time and remove questions whose answers will not change anything.
Should an event feedback survey be anonymous?
That depends on the purpose and the promise made to participants. Anonymous feedback can support event improvement. Individual follow-up or linked history requires a clearly explained approach to identity and access. Do not describe identified responses as anonymous.
Can I compare feedback from different chapters?
Yes, where the measures, eligible respondents, periods and scales are comparable. Agree a shared core and document local differences. Keep results separate when the definitions do not support an aggregate.
Does positive feedback demonstrate event impact?
It demonstrates respondents' reported experience on the questions asked. Learning applied later, relationships sustained or other outcomes need appropriate follow-up evidence. Immediate satisfaction alone does not establish those outcomes.
How do I use AI to analyze comments responsibly?
Define the themes and reporting units, preserve source passages, review ambiguous and contradictory examples, and check summaries before using them. Keep permissions and the limits of the respondent sample visible.
