Collecting Useful Feedback After a Community Event
Community event feedback is most useful when it helps answer a decision. A large pile of general comments can be difficult to act on, while a few well-chosen questions may reveal where information, access or coordination needs attention. Decide what you need to learn before designing a form.
For a country show, different people experience different parts of the event. A visitor, an exhibitor and a volunteer may all describe the day accurately while referring to very different processes. Keep those perspectives visible rather than combining them into one unexplained satisfaction score.
Choose a small set of learning questions
Begin with the decisions likely to matter next time. You might need to know whether exhibitors understood delivery directions, whether volunteers received a useful handover or whether visitors could find a particular information point.
Ask about an experience the person actually had. "How clear were the exhibit collection instructions?" is more focused than "Was everything well organised?" Include a way to say that the question does not apply, so people are not forced to rate a process they did not use.
Avoid asking for praise in the question
Keep the wording neutral. A question that describes an activity as excellent before requesting a rating already suggests the expected answer. Give people room to identify both helpful features and problems without feeling that criticism is unwelcome.
Make responding manageable
Use a short format with clear instructions and an optional open comment. Offer an appropriate alternative for people who cannot or do not wish to use an online form. A QR code can help some visitors, but it should not be the only possible route where another method is practical.
Explain the purpose of the feedback and how it will be used. Collect only the personal information necessary for that purpose. If someone requests a response to a specific concern, provide an approved contact route rather than publishing their details in a shared comment sheet.
Separate observations from interpretations
When reviewing comments, preserve what the person reported. "I could not find the receiving table" is an observation about their experience. "The whole pavilion layout failed" is a much broader interpretation that needs more evidence.
Sort feedback into a few useful categories:
- Information that was unclear or missing.
- Physical access or movement difficulties.
- Role, timing or handover problems.
- Features people found helpful and worth retaining.
Keep urgent safety or safeguarding concerns in the appropriate reporting process. Do not leave them waiting for a general end-of-season review because they arrived through a feedback form.
Look for repeated issues without dismissing single reports
Several similar comments may point to a recurring problem. A single comment may still reveal an important barrier or incident. Frequency helps describe the evidence, but it is not the only measure of importance.
Be honest about who responded
Record the number and broad type of responses where appropriate. Do not claim that a voluntary survey represents every attendee. People who choose to respond may have different experiences or motivations from those who do not.
Use careful language in summaries. "Several responding exhibitors found the map unclear" is more defensible than "everyone disliked the map". Keep exact counts when available and do not turn a small, informal set of comments into a precise-looking percentage without useful context.
Create a short action record
For each priority issue, name a proposed response, a responsible role and a point at which progress will be checked. Some actions may require approval, funding or a discussion with the venue. Record those dependencies instead of writing a promise that no one has agreed to deliver.
For example, unclear delivery directions might lead to testing a revised instruction sheet with new exhibitors. That is a specific action. "Improve communication" is an intention, but it does not tell anyone what to do next.
Keep the successful parts too
Record what should remain unchanged. If a simple sign or a calm receiving process helped people, include it in the next planning brief. Feedback is not only a list of failures; it can preserve good practices that might otherwise be lost during a redesign.
Close the loop respectfully
Share an appropriate summary with the people involved, avoiding identifiable comments without permission. Explain which changes are planned, which need further work and which cannot be made at present. Acknowledge the contribution without implying that every suggestion will be adopted.
Useful feedback creates a connection between an experience and a decision. Clear questions, careful interpretation and a manageable action list make that connection visible. The goal is not to produce the longest report, but to make the next event easier to understand and participate in.