Months of Planning, a Two-Day Feedback Window
Single-day events run on cruel arithmetic: a year of preparation compresses into eight hours, and most organizers then spend three days writing the follow-up email — by which point attendees remember the food and nothing else. The honest feedback window for a one-day event is the car ride home. Everything about this debrief is designed to be completed inside it.
The Exit Capture
The survey link travels as a short, permanent URL rendered as a QR code on exit signage, table tents, the closing slide, and — for badge events — the lanyard map. Attendees scan while queueing for coats and rideshare; completion rates from exit capture routinely beat next-day email by a factor of several. The email still goes out the following morning as a second net for everyone who walked past the sign, but it is the backup, not the plan.
Ask About Moments, Not Abstractions
‘Rate the event overall’ produces a number and no program intelligence. One-day debriefs work when they interrogate the day’s actual moments:
- The moment of the day. A picture choice question — thumbnails of the keynote, the workshop tables, the food station, the photo corner — lets attendees point at what they’ll be retelling. Pointing beats describing, and the winning thumbnail is next year’s program headline.
- The logistics scorecard. Venue, food, check-in, and sound each get a quick rating — the four pillars where single-day events are publicly won or lost.
- The schedule test. One yes/no: was there a stretch where you wished you were somewhere else? Agenda dead zones are invisible from the run-of-show document and obvious from the floor.
- Come again? Would they attend the next edition — the truest loyalty signal a one-day event can collect.
- One suggestion. An optional open field, because the best program idea for next year is usually sitting in an attendee’s head unsolicited.
Five minutes, thumb-native, done before the parking lot.
Ask the Crew Too
Attendees see the show; volunteers, staff, and vendors see the machinery — and the machinery is where one-day events actually fail. A three-question crew version, spun off by duplicating the form and trimming it, catches the check-in bottleneck, the speaker who arrived late, the AV scare that nearly happened. Crew answers explain attendee answers: the low venue score and the ‘restrooms unlocked twenty minutes late’ crew note belong in the same debrief document.
More formats for the whole event lifecycle — before, during, and after — sit in the event forms collection and the plan-events category, with the planning side covered in the event-planning use case.
Frequently Asked Questions
Paper cards or QR — which should we run?
QR on volume and legibility; paper where phones aren’t welcome or hands are full. Events with older or international crowds run both — the paper cards get keyed in by volunteers, which is a cost, not a compromise.
When should the day-after email go out?
Before noon the next day. Open rates hold through the morning; by the following week both opens and memory have sagged together.
How do we hear from people who left early?
They rarely fill exit surveys — that’s what the day-after net is for. The crew version matters most here: staff at the door usually know exactly why people left, and asking them is faster than surveying the departed.
Can we compare this year's edition against last year's?
Yes, provided the core questions stay identical year over year. Fixed logistics scores and the come-again question form a trend line; the moment question can change freely since the program itself changes.