Post-Event Feedback Surveys That People Actually Answer

The post-event feedback survey is where good intentions go to die: twelve questions, sent a week later, answered by 15% of attendees, read by no one, and quietly ignored when planning the next one. The working version is almost embarrassingly small — and the smallness is the entire reason it works. Length is the tax you charge respondents, and most surveys overcharge.

The format: two questions, 48 hours

1. What was the best part?
2. What should we change next time?

Optionally, a single 1–5 rating so you have a trackable number across events. That’s the whole survey. Two open questions take a minute to answer and surface more than a Likert grid ever does, because people explain themselves in prose and flatten themselves into scales. And the timing matters as much as the length: sent within 48 hours, while the event is still vivid, you get specific memories; sent the following week, you get vague politeness from the few who bother.

Send it in the channel the event was organized in — Slack or Basecamp — not as an emailed link. Distance-to-the-ask governs response rates everywhere, and a survey is no exception. The combination of short, fast, and in-channel is what separates a healthy response rate from the 15% graveyard: Culture Amp puts a healthy staff-survey response in the 65–85% range (higher still for small teams), and a two-question in-channel pulse is built to land there rather than in the inbox where long, late surveys go to die.

Reading the answers

Tag each response with a theme as you read — food, schedule, venue, travel, content. Three or four themes will dominate, and the tagging takes ten minutes for an event’s worth of replies.

Beware the loud minority: one vividly-worded complaint occupies more mental space than ten quiet “it was great”s, and planners over-correct toward the loudest voice every time. The rating average and the theme counts are your anchor; individual anecdotes are color, not direction. If one person hated the hotel and twenty didn’t mention it, the hotel is fine.

The part everyone skips: closing the loop

Feedback systems die when answering feels pointless — people stop responding to surveys whose results they never see acted on, and the response rate decays event over event until it’s back in the graveyard. The antidote is public and specific: “You said the schedule was too packed — next offsite has free afternoons.” One visible change per event is enough to keep response rates healthy indefinitely, because it proves the survey is a lever and not a formality. Open the next planning cycle by reading out last time’s action list. The loop, not the questions, is what builds a feedback culture.

Make it automatic

The 48-hour window is exactly the moment the planner is most exhausted and most likely to skip the send — the event just ended, everything worked, and a survey feels like optional homework. That fragility is the strongest argument for automation: TeamRally sends the pulse the moment an event ends and attaches the results to the event record, so the loop closes even when you’re face-down recovering. The survey that actually goes out beats the better survey that you meant to send on Monday.

Part of the HR event logistics guide. Related: the complete events guide.

---

TeamRally sends post-event pulses automatically and rolls results into your event history. Join the waitlist.