Most event feedback surveys collect data nobody acts on. The form goes out, responses come in, someone glances at the average satisfaction score, nods, and the file gets archived. The reason isn't that organizers don't care — it's that the survey was built without a decision in mind. A survey designed to fill a slot in the post-event checklist produces a number; a survey designed to answer a specific question produces a to-do list. This post covers the three parts that turn feedback into a better next event: what to ask, when to send it, and — the part almost everyone skips — what to actually do with the responses.
Before You Write a Single Question: Decide What Decision This Survey Supports
The question to answer before writing any question is: what will I do differently based on the answers? Every question on the form should trace back to a real decision. There are four kinds you're likely making.
Content decisions. Was the topic, speaker, or format right for this audience? These questions tell you what to put on the agenda next time and who to put on stage.
Logistics decisions. Did the venue, timing, tech, and organization work? These tell you what to fix operationally — the room that was too cold, the registration line, the audio that cut out.
Audience fit decisions. Did you reach the right people? These tell you whether your promotion and targeting pulled in the attendees who got value, or a mismatched crowd.
Return decisions. Will they come back, and will they bring others? These predict the health of the event as a recurring property and tell you whether word of mouth is working for or against you.
Map each question to one of these four decisions. If a question doesn't connect to a decision you'll actually make, cut it — it's costing you completion rate and buying you nothing. This decision-first discipline isn't unique to events; it's the same logic behind any well-built set of market research survey questions.
Here's the test in practice. "Did you enjoy the keynote?" feels reasonable, but enjoyment alone doesn't map to a decision — you can't act on it. Rewrite it as "How relevant was the keynote to your work?" and now it feeds a content decision: if relevance is low, you change the speaker brief or the audience targeting next time. Same topic, but one version produces a vanity number and the other produces a choice. Run every draft question through that filter before it goes on the form.
Core Questions for Any Event (Include These Every Time)
Five questions belong on every event survey you send, regardless of format. They're your benchmark set — keep them identical across events so you can compare this conference to the last one and watch the trend move.
"Overall, how satisfied were you with [Event Name]?" (1–7 scale)
"Would you attend another [Event Name] event?" (Yes / No / Maybe)
"How likely are you to recommend [Event Name] to a colleague?" (0–10)
"What was the single most valuable part of today?" (open-ended)
"What would make the next event better?" (open-ended)
The two open-ends do the heavy lifting: the first tells you what to protect, the second tells you what to change. The three scaled questions give you the comparable numbers. Change everything else based on what you're trying to learn for a given event, but never touch these five — the moment you reword them, you lose the trend line. A reusable event feedback survey template makes it easy to keep this core constant and swap only the event-specific questions.
Questions by Event Type
The five core questions stay. These are the format-specific questions you add on top, chosen to match how attendees actually experienced the event.
Conference or Multi-Session Event
"How would you rate the quality of the sessions you attended?" (1–7)
"How effective were the speakers at delivering useful content?" (1–7)
"How relevant was the content to your role or work?" (1–7)
"How valuable was the networking and connection time?" (1–7)
"How was the pacing and schedule?" (too packed / about right / too sparse)
"How would you rate the venue and on-site logistics?" (1–7)
"Which format would you prefer for the next event?" (in-person / hybrid / virtual)
"What topic would you most want covered next time?" (open-ended)
Conferences live or die on session quality and the feeling of a day well spent, so the session, speaker, and relevance ratings are the ones to watch most closely. The format-preference question matters more than it looks — it tells you whether to keep investing in a physical venue or shift budget toward hybrid reach.
Webinar or Online Event
"How was your technical experience — audio and video quality?" (1–7)
"How was the depth of the content?" (too basic / just right / too advanced)
"How was the session length?" (too short / just right / too long)
"How effective was the Q&A portion?" (1–7)
"Do you plan to watch the recording?" (Yes / No / Already did live)
"What format would you prefer for future webinars?" (live / on-demand / hybrid)
"How easy was the registration process?" (1–7)
"What follow-up content would be most useful to you?" (open-ended)
Webinars fail most often on two axes: tech and content depth. The "too basic / too advanced" question is the single most useful diagnostic here, because a webinar that's pitched at the wrong level reads as boring or confusing without the attendee being able to say why. If you're running the event on a platform that allows it, SegmentOS's embeddable survey link can be shared in the chat at event close for immediate in-session collection — which captures responses before attendees close the tab and the sentiment fades.
Workshop or Training Session
"Were the learning objectives met?" (yes / partially / no)
"How confident are you to apply what you learned?" (1–5)
"Which exercise or activity was most valuable?" (open-ended)
"What did you wish had been covered that wasn't?" (open-ended)
"How effective was the facilitator?" (1–7)
"How would you rate the quality of the materials?" (1–7)
"What kind of follow-up would help most?" (resources / coaching / community)
"How likely are you to apply this within 30 days?" (1–7)
Workshops are judged on transfer — did people leave able to do something they couldn't before. The confidence-to-apply and likelihood-to-apply-within-30-days questions are your real success metrics, far more telling than a satisfaction score. A workshop everyone enjoyed but nobody applied didn't work. If you can, send a short follow-up 30 days out asking whether they actually applied it — comparing predicted application against real application tells you whether your sessions build genuine capability or just temporary enthusiasm, and it's the one measurement that separates a good workshop from a memorable one.
When to Send Your Event Feedback Survey
Send within 24 hours of the event ending — and ideally within 2 to 4 hours. Not "24 to 48 hours as best practice." Not "a few days later once things have settled." The research on event memory is unambiguous: sentiment regression starts immediately. The event you'd rate a 7 four hours later you'd have rated an 8 right after. Every hour that passes pulls the average down, even when the event was genuinely good, because the specific highs fade faster than the general impression.
For virtual events, send while attendees are still on the platform, or within 30 minutes of the close — the in-session moment is the highest-response window you'll ever get, often two to three times the response rate of a next-day email. For in-person events, send via email within 2 hours, or collect on-site with a QR code before people leave the room. The QR-on-exit approach consistently outperforms email because it catches people while they're still in the event headspace, before the commute home resets their mood and a full inbox buries your link. If you can only invest in one delivery method per format, make it the in-session link for virtual and the exit QR for in-person — those are where the responses actually are.
Do not send three days later "once they've had time to process." There's nothing to process — you want the gut reaction, not a considered review, and both response rate and quality drop with every day of delay. The one exception: for multi-day conferences, send a short daily pulse each evening (the five core questions, nothing more) plus a comprehensive survey after the final day. The daily pulse catches day-one problems while you can still fix them for day two.
Build a study, reach verified respondents in your market, and get answers back in days.
Everything a research team does. Without the research team.
With SegmentOS you can build the study, reach a verified audience, and get data you can actually trust. End to end, no research background required.
Data quality
Every study runs through device fingerprinting, speeding detection, attention checks, and screener disqualification.
What to Do With the Results (The Part Nobody Writes About)
Collecting the data is the easy half. Here's the three-step framework that turns responses into a better event.
1. Triage within 48 hours. While the event is still fresh for your team too, scan for anything below 5 out of 7 on the core questions, and any open-ended comment that names the same problem twice. Two people flagging the same broken thing is a pattern, not noise. This pass takes an hour and tells you where the real issues are.
2. Write a one-page "What We Heard" summary and share it with the organizing team. This is the step that closes the loop internally. One page: the core scores, the top three positives, the top three problems, and the standout quotes. Without this, the feedback lives in one person's inbox and the team never aligns on what actually happened.
3. Build a "Next Event" improvement list. Pull three specific changes from the open-ended feedback, and give each one an owner and a deadline. Not "improve catering" — "switch caterers, owned by Sam, decided by March 1." Limit it to three on purpose: a list of fifteen changes gets you zero, while three with owners and dates actually ship. Prioritize by how many attendees raised each issue and how cheap it is to fix — the items that are both frequently mentioned and easy to change are your first three every time. Build this list into a reusable post event feedback survey template and process so every event starts from the last one's lessons instead of from scratch.
Satisfaction scores without action items are vanity metrics. The survey exists to produce a to-do list — if it doesn't, you ran it for decoration.
SegmentOS's Event Feedback template covers attendee satisfaction, content quality, speaker ratings, logistics, and return intent — 9 questions, about 4 minutes, ready to deploy. Access a targeted consumer panel or send directly to your attendee list. See the template →
Frequently Asked Questions (FAQ)
When should you send a post event feedback survey?
Within 24 hours, ideally 2–4 hours after the event ends. Sentiment drops measurably with every hour that passes, so a fast send captures the most accurate and highest-volume response. For virtual events, share the survey in-session at close; for in-person, use a QR code on exit or email within two hours.
What questions should I ask in an event feedback survey?
Always include five core questions: overall satisfaction (1–7), would you attend again, likelihood to recommend (0–10), the single most valuable part, and what would make the next event better. Then add 6–8 format-specific questions for a conference, webinar, or workshop. Keep the core five identical across events so you can track trends.
How many questions should an event feedback survey have?
Aim for 9–13 questions, around 3–5 minutes. That's five core questions plus six to eight tailored to your event type. For multi-day conferences, send a short five-question daily pulse each evening and a fuller survey after the final day. Past roughly 13 questions, completion rates fall and answer quality drops.
What's different about a virtual event feedback survey?
A virtual event feedback survey should ask about technical experience (audio and video quality), content depth, and whether attendees plan to watch the recording — issues that don't exist in person. Timing matters even more: collect responses in-session at close, while attendees are still on the platform, since online audiences disperse and disengage faster than a room.
What should you do with event feedback survey results?
Triage within 48 hours for low scores and repeated complaints, write a one-page "What We Heard" summary for your team, then build a "Next Event" list of three specific changes, each with an owner and a deadline. Scores without action items are vanity metrics — the survey's job is to produce a concrete to-do list.
