# Post-Event Survey Questions: A Practical Guide for Attendee Feedback Use post-event survey questions to collect attendee feedback, examine differences, and plan a more useful next event. - Canonical URL: https://www.harmate.com/en/blog/post-event-survey-questions-a-practical-guide-for-attendee-feedback - Author: Harmate Team - Published: 2026-10-20 - Updated: 2026-10-20T03:48:56.037939+00:00 - Language: en ## Content # Post-Event Survey Questions: A Practical Guide for Attendee Feedback Start a post-event survey with the decision the answers can still inform: a format to keep, a confusing step to fix, or a need to check. Ask people about an experience they actually had, then give them room to explain. A rating records a stated assessment; it does not explain what produced it. Use the questions below as a draft, not as a validated scale. Remove any question that has no possible follow-up, and test the remaining wording with a few people similar to the attendees you plan to invite. ## A short question set to adapt 1. **How easy was it to find the venue or join the event online?** Single choice: very easy / somewhat easy / neither easy nor difficult / somewhat difficult / very difficult / not applicable. Each person selects one option; keep “not applicable” if some attendees did not need to find a venue or join link. 2. **Which part of the event, if any, was useful to you?** Open response. Optional follow-up in a separate field: “What did you take away from it?” 3. **Did you have any difficulty following the event?** Open response. Optional follow-up: “If so, can you describe a specific moment?” 4. **What, if anything, should we keep for a future edition?** Open response. Optional follow-up: “What made it useful to you?” 5. **What change, if any, would you suggest first?** Open response. Optional follow-up: “In what situation would that change help?” 6. **Which sessions did you attend?** Use multi-select if several answers can be true: [list sessions actually offered] / none / other. This records exposure to multiple sessions; it is not a single-choice question. Selecting “none” must rule out selecting a session at the same time. 7. **Is there an important part of your experience we have not asked about?** Optional open response. Do not automatically send all seven questions. For a short event, questions 2, 3, and 5 may be enough if you know how the answers could inform a decision. Add the others only when they serve a clear purpose. At a multi-session event, asking which sessions someone attended helps put their account in context; do not ask them to rate a session they did not attend. ## Decide what the survey can change Write the intended decision in one sentence: “After reviewing the responses, we can decide whether to…”. It might concern keeping a format, revising an instruction, adjusting the pace, or checking an accessibility need. If no decision can change, consider whether a survey is useful at all, or whether observation or a few focused conversations would answer the question better. Define who you are inviting and which experience you want to understand: in-person attendees, remote participants, people who attended a particular session, or a recurring event’s audience. Those groups may have experienced different things. State the period and response channel too. A prompt immediately after an event and one sent several days later do not call on the same memories. Keep pre-event expectations separate from post-event experience. The [pre-event survey guide](/en/blog/pre-event-survey-choose-topics-for-your-event-programme) helps organizers choose topics or formats that are still open to a decision. A follow-up survey asks a different question: what did attendees experience, and what may be worth changing? ## Write questions that do not lead the answer Ask one thing at a time, using words attendees know. “How did you find the welcome and the workshops?” combines two experiences; split it if you need information about both. Avoid wording that assumes the event was successful, useful, or inclusive. “What helped you take part?” leaves room for a real account; “What did you like about our excellent event?” signals the answer you expect. For a single-choice closed question, check that options do not overlap and cover reasonable answers. State explicitly when an option may not apply. A checkbox list serves a different purpose: use it when several answers may be true at once, such as sessions attended. Do not turn that multi-select question into a ranking or a single-choice item. Open questions let attendees describe situations and aspects the organizer may not have anticipated. They take more effort to answer, and analysis should preserve the context. A closed question may support a descriptive comparison, but it cannot explain why people answered as they did. Neither format alone makes answers representative or free of bias. [AAPOR recommends specific, simple questions that address one concept at a time, and recommends pretesting with people similar to the intended respondents](https://aapor.org/standards-and-ethics/best-practices/). Ask a few people to read each question before sending it: find out what they think it means and whether the answer choices let them respond. This qualitative check can uncover comprehension problems; it does not validate a scale. ## Review the responses before changing the event Start by describing who responded and how they received the survey. Unless you know the invitation coverage and nonresponse, do not present the replies as the view of every attendee. A missing response does not tell you why someone did not reply. An individual assessment is worth examining, not generalizing. For each theme, retain the original response, relevant context, your interpretation, and the decision being considered. Look for recurring accounts and for experiences that differ. If some attendees describe difficulty joining remotely while others do not, preserve that difference. Check whether they used different links, devices, or participation formats before drawing a conclusion. Fictional example: several responses say a session was hard to follow online. This is an account from respondents, not proof that the platform caused the problem or that every attendee experienced it. The organizer could check the format, instructions, and connection conditions, then test an adjustment in a future session. Record what you will observe to see whether the change addresses the issue. A [project lessons-learned review](/en/blog/project-lessons-learned-method-questions-and-an-adaptable-template) can complement attendee feedback when the team and partners need to examine roles, handoffs, and operational learning. Keep their observations separate from attendee responses: they offer another perspective and do not replace participant accounts. ## Explain how responses will be used Before sending the survey, explain who will see the responses, how they will be used, whether quotations may be reused, and who will receive the findings. Do not promise anonymity without checking what is collected, who has access, group size, and whether a comment could identify its author. A quotation without a name may still be recognizable from its context. Do not ask for personal details that do not serve the decision. After reviewing the feedback, share what you decided, what remains uncertain, and what will not change, with a clear reason. If you collect open comments, Harmate can help [collect open-ended responses, organize themes, and return to source comments](/en/product/open-questions); it does not choose the interpretation or make the decision for the organizer. The method remains the same: start from described experiences, consider possible explanations, and check whether the next action improves the situation.