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.

First, what this isn’t

This is not an engagement survey. It doesn’t produce an eNPS, a sentiment score, or a number you present to the board. Nobody gets rated, ranked, or benchmarked against last quarter.

It’s worth being blunt about the difference, because the two get filed under the same word and they do opposite things. An engagement survey asks people to summarise how they feel about working somewhere, in the abstract, on a scale. A post-event question asks how a specific afternoon went, while they still remember it, so the next one is better. The first tends to accumulate — dashboards, trend lines, quarterly reviews of the trend lines. The second gets used within a fortnight and then it’s done.

If you’re currently running both, notice which one has ever actually changed anything. (If you do want the periodic instrument as well, there’s an honest guide to measuring employee happiness without fooling yourself — and a longer argument about what the score is actually downstream of.)

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 something comparable across events. That’s the whole thing. 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.

Timing matters as much as length. Sent within 48 hours, while the event is still vivid, you get specific memories — the bus, the second afternoon, the food on Thursday. Sent the following week, you get vague politeness from the few who bother.

Send it in the channel the event was organised in — Slack or Basecamp — rather than as an emailed link. Response rates track distance-to-the-ask, and this is no exception. Short, fast, and in-channel is what separates a healthy response rate from the 15% graveyard. Even the engagement-survey vendors put a healthy response in the 65–85% range, higher for small teams — and a two-question message lands there far more easily than a long form does from an inbox.

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. Theme counts are your anchor; individual anecdotes are colour, not direction. If one person hated the hotel and twenty didn’t mention it, the hotel is fine.

The part everyone skips: saying what you did

Asking stops working when answering feels pointless. People go quiet on questions whose answers 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 people answering indefinitely, because it proves the question was real. Open the next planning cycle by reading out last time’s list.

That loop is the whole thing. Not the questions, and definitely not the number.

Ask while you still can

The 48-hour window is exactly when the organiser is most wrecked and most likely to skip it — the event just ended, everything worked, and asking feels like optional homework. That’s the honest argument for letting something else handle the send.

In TeamRally it’s called How’d it go? — the question goes out when the event wraps and the answers land against that event, so you still have them when you’re planning the next one. A question that actually gets asked beats the better one you meant to send on Monday.

Related: planning a company offsite, the complete events guide, and engagement ideas for remote teams.

---

TeamRally is where teams celebrate birthdays, milestones and farewells — and run the offsites in between. No engagement scores. Start free.