Event Feedback Form Template
Capture attendee verdicts while the lanyards are still on — overall rating, the highlight, logistics smoothness, and whether they will come back next time.
You were there — tell us what the event was actually like so the next one is better.
Event feedback has a brutal half-life: response quality drops by the hour after doors close, and by Monday attendees remember a vibe, not specifics. This template is tuned for that reality — short enough to finish while walking to the car, with the one question that matters most for your business asked point-blank: are you coming back?
Why these fields. The overall rating gives you the single number to compare editions against each other. The highlight question is open text on purpose — patterns in what people volunteer as the highlight tell you what the event is actually for, which often differs from what the agenda says it is for. The most-value question forces a choice between talks, workshops, networking, and exhibitors, and that forced trade-off is the input your program committee argues about all year; a multi-select here would let everyone pick everything and teach you nothing. Logistics gets its own scale because operational pain — queues, signage, wifi, food lines — systematically drags down content scores when you do not separate the two. And the return-intent question is the event world's honest metric: someone who says "probably not" gets one respectful follow-up about what would win them back, which is the cheapest attendee-recovery program you will ever run.
What we left out. Per-session rating grids (they belong in a separate per-talk form with its own QR code at the room door), demographic batteries (your registration form already knows), and contact fields (feedback candor drops when identity is attached, and your registration list already gives you reach).
Who uses this. Conference organizers push it through the event app minutes after the closing keynote, meetup hosts drop the link in the follow-up thread, and corporate event teams print the QR code on exit banners.
Make it yours. Rename the value options to your actual format — a hackathon might use "mentors" and "demo night". Set a close date a week out in Settings so late responses do not dribble into next year's numbers, and export the CSV before the retro meeting. Focus mode is the right call here: one question per screen feels effortless on a phone in a hallway.
The one-slide readout. Two numbers belong on the retro slide: the average overall rating and the share answering "count me in" on return intent. Everything else is diagnosis. Cross the most-value answers against return intent and you will usually find your event's real engine — if networking-first attendees return at twice the rate of talk-first ones, next year's schedule should protect hallway time as fiercely as it protects keynotes.
Frequently asked questions
When should we send this to attendees?
Within an hour of the event ending — response rate and specificity fall fast. A QR code on exit signage catches people even earlier, while impressions are freshest.
Why is there no per-talk rating?
Session-level grids belong in a per-session form so each speaker gets clean numbers. Keeping this one about the event as a whole keeps ratings comparable across editions.
Can we stop collecting after a week?
Yes — set a close date in Settings and the form stops accepting responses automatically, showing a custom closed message to late clickers.
Who sees the "probably not" answers?
Only you and whoever you share exports with. The win-back question those respondents see is the most valuable free consulting your event will get — read every one.