Post-Event Survey: The Questions to Ask and When to Send It
The event is over, and now you need to know whether it worked: what to repeat, what to fix, and what to tell the people who funded it. A post-event survey is the simplest way to collect event feedback while the event is still fresh, in the attendees' own words rather than your guesses.
Most surveys fail in three ordinary ways. They are too long, so people quit halfway. They go out a week late, when the event is a blur. And the answers get read once and never acted on. This guide covers when to send the survey, how many questions to ask, the questions themselves, and what to do with the responses so the next event is better.
Send it fast, and keep it short
Two decisions shape your response rate before anyone reads a single question.
Send it within a day or two, while the event is still fresh. The longer you wait, the fewer people reply, because the detail fades and your email gets buried. Have the survey written before the event so you can send it the next morning.
Keep it to five to ten questions, two or three minutes to finish. Every extra question costs you responses. Use rating scales or multiple choice for most of it so people can answer in a tap, and keep the open text boxes to one or two, since those are the questions people skip.
Send it to everyone who registered, not only the people who showed up. A one-question survey to the no-shows, asking what got in the way, tells you whether the problem was the event or the timing. Then queue one reminder a few days later to everyone who has not answered, which is the cheapest way to lift the response rate.
Questions to add for specific events
Tailor the last few questions to the kind of event you ran.
- Virtual or hybrid. Ask about the platform and the tech: "How was the audio and video quality?" and "How easy was it to join and take part?" A strong talk over a broken stream still scores badly, and you want to know which one you are looking at.
- Sponsored events. Ask attendees whether they visited sponsor booths or sessions, and survey sponsors separately about the leads they got, so you have real numbers when you renew them.
- First-time versus returning. One early question, "Is this your first time at this event?", lets you read every other answer by newcomer or regular. The two groups often want opposite things, and the average hides it.
Write questions that get honest answers
The wording decides whether the answers are usable.
Ask one thing per question. "How were the venue and the food?" forces one answer to two questions, so split them. Keep your rating questions on one consistent scale, the same 1 to 5 across them, so you can compare across questions and across years; the overall 0 to 10 recommend question is the deliberate exception. Keep the wording neutral rather than fishing for praise: "How would you rate the sessions?" not "How great were the sessions?" And put the open-ended question last, so people answer the quick ratings first instead of stalling on a blank box.
What to do with the responses
A survey nobody acts on is just a chore you imposed on your attendees. The value is in what happens next.
Read the open-ended answers in full, since the patterns there are where the real problems and the best ideas live. Write a short summary, the overall number, what worked, and the two or three things to fix, and share it with your team and the people who funded the event. Pick the changes you will actually make next time, and where you can, tell attendees what you changed because of their feedback. That single follow-up does more for next year's response rate than any incentive.
Then keep the overall number. Tracked across events, "would you recommend this" turns a pile of opinions into a trend you can manage.
If you remember one thing
Send the survey fast, keep it short, and act on what comes back. The exact questions matter less than the habit of asking the same overall one each time and doing something with the answers.
