A useful post-event survey asks attendees for information that could change what you do at the next event. Start with a decision, such as whether to change the session mix or arrival process, then choose only questions that help you make it.
The sample questions below are a practical synthesis, not a validated universal survey. Adapt them to your event, leave out information you already have, and treat answers as evidence to consider rather than a verdict on every attendee’s experience.
Decide what feedback could change
Before drafting questions, write down what you might do differently after reading the answers. You might move a workshop to a larger room, add time for discussion, alter the start time, or provide a clearer route from registration to the venue. If an answer cannot affect a decision, it probably does not belong in the survey.
This is more than an editing shortcut. The University of Wisconsin–Madison’s event evaluation guidance cautions against collecting feedback merely for its own sake and advises organisers to seek information they can use. Put that test into practice: for every proposed item, finish the sentence, “If attendees answer this, we could decide to…” If no plausible ending follows, remove the item.
For example, if you already know attendees’ job titles from registration, asking them to repeat that information adds work without helping a future choice. If you need to decide whether to keep a beginner session, ask whether its content was relevant and useful, not for a broad profile that does not answer the question.
The relevant decision depends on the event. A devotional gathering might be considering whether to make more time for a particular programme segment; a product demonstration may need to know whether the explanation answered likely customer questions. For a continuing online programme, questions about usefulness and programme fit may be more informative than asking how attendees felt about venue catering. See how a continuous stream of recorded Sunday school lessons differs from an in-person event before borrowing its feedback categories.
Keep the audience in view as well. Attendees can describe their experience, but they may not know whether sponsors met their objectives or whether staff found a check-in process workable. Ask those groups separately if their answers will inform separate decisions. Cvent, for instance, organises its examples into distinct attendee, sponsor and speaker question sets in its event survey question guide.
Keep the survey focused
For a general event, a short core questionnaire can cover satisfaction, expectations, value, improvement and future interest. Use those as starting points, not a checklist that every organiser must follow. Add a question only if you can name the decision it informs; remove one if another question already covers the same ground.
A practical sequence might be:
- Overall, how satisfied were you with the event?
- Did the event meet your expectations or the goal you had for attending?
- Which part of the event was most valuable to you?
- What is one thing we could improve for next time?
- How likely are you to attend a future event or recommend this one to a colleague?
This set brings together common topics in university and vendor question banks. It is not a validated instrument with a universal scoring method. The University at Buffalo’s post-event question bank, for example, also includes topics such as the reason for attending, content, logistics, event length and cost. Those are options when they fit your decisions, not a reason to ask about everything.
Choose a response format that matches the information you need. A rating or multiple-choice item is quick to answer and easier to compare; a written prompt can reveal a problem you had not anticipated, but takes more effort to review. SurveyMonkey recommends combining closed questions with a few open-ended ones in its post-event survey advice. Treat any suggested question count or completion time from a vendor as guidance, not a universal rule or a guarantee of responses.
Keep each item to one subject, use ordinary language and offer balanced response choices. If you want to compare answers across events, keep the wording and scale consistent enough for a fair comparison. Make written responses optional if your survey platform allows it; that leaves room for detail without requiring every attendee to compose a comment.
Ask about overall satisfaction
A broad satisfaction question gives you a useful first reading of the event as a whole, but it does not explain what went well or badly. Ask: “Overall, how satisfied were you with the event?” Then choose a consistent, balanced scale with options ranging from dissatisfied to satisfied, including a middle response.
Do not assume a rating identifies the cause. An attendee may give a low overall score because a session started late, the content missed their needs, or access arrangements did not work. The score tells you to investigate the experience; a targeted follow-up or a comment can help explain it.
Avoid putting several dimensions into one item. “How satisfied were you with the speakers, venue and refreshments?” creates an unclear answer if the attendee liked the speakers but disliked the venue. If each area could lead to a different change, ask a separate question about the area that matters. If no decision depends on a dimension, leave it out.
The scale is a tool for organising impressions, not an objective measurement of event quality. Do not present a mean score as proof that every group had the same experience. When comparing events, check whether the audience, event format, question wording and response options were sufficiently similar. A score from a small, unusually engaged group may not represent people who did not respond.
Ask whether expectations were met
Overall satisfaction says how attendees felt; an expectations question gives them a different reference point. Ask: “Did the event meet your expectations or the goal you had for attending?” You can offer clear choices such as “yes”, “partly” and “no”, with an optional comment asking what shaped the answer.
This question is especially useful when attendees come for different reasons. Someone might attend a local business event to find suppliers, while another comes for a particular talk. If the event met one person’s aim but not another’s, the distinction can guide programme descriptions, session choices or the way you explain who an event is for.
Expectations are not always reasonable or clearly set. A “no” answer may reflect a mismatch between the event and its promotion rather than a failure of delivery. Read comments alongside the event description and registration information before deciding what to change. If you cannot make a future choice from this information, omit the item rather than asking it by habit.
For a recurring series, the question can help you see whether the experience promised in advance matches what attendees receive. A programme built around recorded talks has different expectations from an interactive gathering: compare formats before adapting questions from a continuous stream of recorded Sunday sermons. Keep the question focused on the attendee’s goal, not on whether they approve of every individual detail.
Ask what was most valuable
“What was most valuable to you?” helps identify what attendees would want retained, expanded or made easier to find. It is broad enough to suit different event formats, but it works best when people can answer in their own terms. You could add a short list of likely options, such as a talk, demonstration, networking, practical advice or a performance, followed by “something else”.
Use the answers to decide what deserves attention in planning. If several attendees point to a particular session, you might keep it or make time for a related topic. A single detailed comment can still prompt a useful check, but it is not proof that the same feature mattered to most people. Look for patterns and preserve context rather than counting comments as if they were representative votes.
When the event contains distinct parts, ask about the parts that could change. A conference organiser may want to know which session was most useful; a business running a product demonstration may want to know whether attendees valued the demonstration, the questions or the supporting material. The product-demo video schedule guide shows why the format and sequence of demonstrations can matter, but a survey should ask only about elements your team can actually adjust.
Be careful not to confuse popularity with quality or learning. A lively segment may be memorable without meeting the event’s purpose. If you need to decide whether content was useful, ask that directly; “most valuable” answers a related but different question. Select the distinction that will help you choose what to retain or change.
Ask what to improve next time
An open prompt such as “What is one thing we could improve for next time?” gives attendees space to mention an issue you did not anticipate. Limiting it to one improvement helps focus the response. Keep it optional where possible, and do not require a comment from someone who has nothing to add.
Open text is useful for concrete examples, but it costs time to read and group. Review comments for recurring themes, specific incidents and possible actions. Record the context: “the room was hard to find” may suggest better signs, while “the opening was confusing” may point to a programme or welcome change. Avoid taking the strongest wording as the most common experience.
Decide how you will handle sensitive or personal comments before sending the survey. Tell attendees how their feedback will be used, avoid asking for personal information that is not needed, and route reports about access barriers or safety concerns to someone able to review them. A survey is not a substitute for a direct support channel when a person needs a response.
Accessibility questions deserve particular care. If you can make changes to participation, ask whether attendees were able to access and take part in the event, and whether anything hindered them. Do not imply that a post-event form replaces asking about accommodation needs during planning or registration. It can reveal barriers to address in future events, not retroactively resolve someone’s experience.
Choose a future-attendance or recommendation question
Future attendance and recommendation are related, but they ask about different intentions. “How likely are you to attend a future event?” can inform scheduling or programme planning. “How likely are you to recommend this event to a colleague?” asks whether attendees would encourage another person to take part. Choose one, or both only when each answer will inform a distinct decision.
Use a clear response scale and avoid treating stated intention as a promise. People may say they would return and later be unavailable; others may recommend an event without attending again themselves. These answers are signals to weigh with attendance records, comments and the event’s purpose, not forecasts of turnout or growth.
If you need to compare answers over time, retain the same wording and response options, and note what changed about the event or audience. Do not compare a recommendation question from one year with a future-attendance question from another as though they measured the same thing. Keep sponsor outcomes and staff process review separate from attendee feedback: those groups see different parts of the event.
Timing and follow-up affect the quality of feedback. Send the form soon enough that people can recall details; Cvent recommends sending it as soon as possible, while SurveyMonkey suggests within one to two business days. These are practical recommendations rather than proof of one universally best time. A QR code at the close can collect immediate reactions, while an email link reaches people after they leave. Avoid repeated reminders that make a small questionnaire feel like a demand.
Close the loop when you can. Thank attendees, explain how you will use the feedback, and share something relevant, such as slides or details of the next event. Do not promise changes that you cannot make. If your event is part of an ongoing online programme, the operating format may affect what attendees can experience; a Sikh kirtan radio station stream guide is one example of a format with different decisions from a one-day gathering.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How many questions should a post-event survey have?
Use as few as you can while still answering the decisions you identified. A short core set might cover satisfaction, expectations, value, improvement and future interest, but some events need fewer and others need a focused extra module. SurveyMonkey’s suggested limits are vendor guidance, not a universal standard.
When should I send the survey?
Send it soon after the event while details are still easy to recall. Cvent advises sending it as soon as possible, and SurveyMonkey suggests within one to two business days; neither recommendation establishes an optimal time for every audience. An immediate QR code and a later email can serve different purposes.
Should every attendee receive the same questions?
Keep a shared core if you need to compare experiences, then add only questions relevant to particular formats or decisions. Avoid asking attendees to repeat details already available from registration or attendance records. If you compare groups or events, check that the question wording and response options are comparable.
Is this a validated survey questionnaire?
No. These questions are a practical synthesis of university and vendor examples, not a validated universal instrument. Adapt the wording to your event, explain how responses will inform decisions, and avoid collecting feedback without an actionable purpose.