Post-event survey questions
Most post-event surveys are written in the last hour before send, stretch to thirty questions because every department added three, and earn a 4% response rate that represents nobody. The question bank below is organized the way the data gets used — event-level for the executive recap, session-level for next year's program committee, speaker-facing for faculty you want back. Ask less, ask faster, and read every open answer.
QUICK ANSWER
Good post-event surveys are short, specific, and sent within 24 hours. Ask overall value as NPS or 5-point scale, what drove attendance, which sessions delivered, and one open question you will actually read. Session-level feedback belongs in its own two-question pulse tied to each session, not a 40-item year-end form. Speaker surveys close the loop for next year's program.
SECTION 1
Event-level survey — 8 questions max
Send within 24 hours while the lanyard is still on the desk. One scale question set, two open answers.
- How likely are you to recommend this event to a colleague? (0–10 — your NPS baseline year over year)
- Overall, how valuable was the event for you? (1–5, anchored: 1 = not worth the time, 5 = clearly worth it)
- What was the main reason you attended? (choice: program topics / specific speakers / networking / CE credits / exhibits)
- Did the program deliver on that reason? (1–5)
- Which single session or moment was the most valuable? (open — this line writes next year's marketing)
- What should we change or drop next year? (open — read every answer)
- How was the venue and logistics experience — registration, rooms, food? (1–5, one combined question, not five)
- May we contact you about next year's program committee, speaking, or early registration? (opt-in checkboxes)
SECTION 2
Session-level pulse — 2 questions per session
Attach to each session in the app or follow-up, not a year-end omnibus. Response rates triple when the ask is tiny and immediate.
- Rate this session (1–5 stars — one tap, no login wall)
- One thing you'll use from this session? (open, optional — doubles as testimonial pipeline and speaker feedback)
- For CE/CME sessions add the required knowledge-check and disclosure confirmation to the same flow, not a separate portal
- Route results per session to the program committee — aggregate scores decide repeat topics; open answers decide repeat speakers
SECTION 3
Speaker & faculty survey — retention questions
Faculty who feel taken care of come back and recruit peers. Five questions, sent within a week.
- How was your experience as a speaker, from acceptance to stage? (1–5)
- Did you have what you needed before your session — AV, room setup, timing, audience info? (1–5 + open)
- How was the submission and review process? (1–5 — this measures your CFP tooling, read it honestly)
- Would you speak again, and what topics are you developing for next year? (open — this seeds next year's program)
- Anyone in your network we should invite to submit? (open — cheapest speaker sourcing that exists)
SECTION 4
Mistakes that kill response rates
- Sending a week later — every day after the event halves your response rate; send within 24 hours
- Thirty questions because every stakeholder added three — cap event-level at 8, cut anything nobody will act on
- Unanchored scales — label what 1 and 5 mean or the averages mean nothing
- Asking session feedback in the year-end survey — nobody remembers Tuesday's 2pm panel; pulse per session instead
- No follow-through signal — tell attendees one change last year's feedback caused; response rates compound when people see effects
- Survey data in a silo — scores that never reach the program committee or speaker records change nothing next cycle
Frequently asked questions
What questions should a post-event survey ask?
An NPS or recommendation question, overall value on an anchored 1–5 scale, why they attended and whether the program delivered on it, the most valuable session, one open change question, one combined logistics rating, and a contact opt-in. Eight questions maximum at event level.
When should the post-event survey be sent?
Within 24 hours of the event closing — sooner for session-level pulses, which work best in the event app while the session is fresh. Every day of delay costs response rate.
What is a good response rate for event surveys?
Event-level surveys typically see 10–30% depending on audience relationship and brevity; in-app session pulses can run far higher because the ask is two taps. A short survey answered by a third of attendees beats a long one answered by 4%.
Should session feedback be separate from the event survey?
Yes. Session feedback should be a two-question pulse attached to each session, sent or prompted immediately. A year-end omnibus asking about individual sessions gets guesses, not feedback.
Should speakers get their session feedback?
Share aggregate scores and constructive open answers with each speaker — it's the cheapest faculty-retention tool you have, and it makes the ask to return next year concrete instead of flattering.
How should survey results feed next year's event?
Scores should attach to session and speaker records, not live in a spreadsheet. On Sessionboard, feedback lands on the same program record as the session and its faculty, so the next cycle's committee starts with last year's evidence.