Event survey questions that lead to useful decisions
Choose post-event survey questions around decisions you can make. Includes a sample survey, response-rate calculation, and analysis checklist.
Write the decision before the survey question. If you need to choose next year's workshop topics, ask about topics. If you need to fix access problems, ask where people had trouble. A general satisfaction score alone cannot answer either question.
Start with a short survey you can explain
The following questions are a sample to adapt, not a validated research instrument. Keep only questions whose answers will inform a decision, and tell respondents how their feedback will be used.
Scroll sideways to see all columns.
| Sample question | Answer format | Decision it supports |
|---|---|---|
| How did you attend? | In person / remotely / both / did not attend | Separate experiences that may differ |
| How useful was the programme for your reason for attending? | Five labeled points from not useful to very useful; plus not applicable | Assess programme relevance |
| Which session was most useful, and why? | Optional short answer | Identify content worth developing |
| Did anything make it difficult to participate? | Optional short answer | Find barriers and support problems |
| Which topic would you most like covered next time? | Optional short answer | Inform future programme choices |
| What is one thing we should change? | Optional short answer | Create a manageable improvement list |
Avoid questions that combine different issues
“Were the speakers and venue excellent?” combines two judgments and suggests a desired answer. Ask about each separately when both matter. Use consistent response labels, offer “not applicable” where appropriate, and avoid requiring an answer about a session the person did not attend.
Test the form on a phone and have a colleague complete it without explanation. Remove ambiguous wording. Ask only for personal details you need, and make the intended use of responses clear.
Send it when people can still recall the event
Choose a delivery time that fits your audience and communications plan. A session-specific question may be useful immediately afterward; a whole-event question needs the event to have happened. If sending a reminder, exclude people who have already replied when your tools permit it.
Do not assume a particular response rate makes a survey representative. People who respond may have different experiences from those who do not. Incentives can also affect who responds, so record whether they were offered.
Calculate and report the response rate
Illustrative example: 60 valid responses from 240 invited attendees produce a 25% response rate. Record who was invited, the collection dates, and how duplicate responses were handled. This number is arithmetic, not a target or an industry benchmark.
Read comments without overclaiming
Group comments into topics such as access, programme, venue, and networking. Keep examples of what people actually said, removing identifying details where necessary. Distinguish a repeated issue from a single suggestion, while still investigating a serious issue reported by one person.
A complaint about audio is evidence of that respondent's experience. It does not establish how many others experienced the same problem. Check the support log and production notes before estimating the scale.
Close the loop with an action
For each selected change, name an owner, a deadline, and the evidence used. You might revise joining instructions, give a workshop more time, or change the room assignment. Those are possible actions, not claims of measured improvements at a past event.
Combine survey findings with the post-event reporting worksheet. Explain what the combined evidence supports and what still needs investigation.