Post-Event Survey Design — 9 Questions That Actually Predict NPS + Pipeline (2026)
Most post-event surveys are too long, too vague, and capture data nobody uses. The 9-question survey that captures NPS, predicts pipeline, identifies session improvements, and finishes in 90 seconds — with 60%+ completion rates.
The average corporate post-event survey gets 22% completion rate. The 9-question template below consistently hits 55-70%. The difference: short, specific questions that respect the attendee's time and only ask what you'll actually use.
The 9 questions
1. NPS (the only required question)
"On a scale of 0-10, how likely are you to recommend [Event Name] to a colleague?"
Single-question NPS. The score divides into: - 0-6: Detractors - 7-8: Passives - 9-10: Promoters
NPS = (% Promoters) − (% Detractors). Industry benchmarks for corporate events: 30-50 good, 50+ excellent.
This question alone justifies the survey. Everything below is optional context.
2. Why that score (open text)
"What's the main reason for your score?"
Open-text. Aggregates beautifully into: - Top 3 things attendees loved (high-promoter themes) - Top 3 things attendees hated (detractor themes) - New content ideas (passive-themed suggestions)
Send aggregated themes to event team within 5 days post-event.
3. Session-level feedback (1 question, multi-select)
"Which session was most valuable to you?" [list all sessions]
Easier than per-session 1-5 ratings, captures the same signal. Top-voted sessions go in next event lineup; bottom-voted get replaced.
For events with parallel tracks, ask which track they attended first to avoid bias.
4. What was missing (open text)
"What topic, speaker, or session format would you most like at our next event?"
The single best question for content roadmap. Aggregates into next-event programming priorities.
Common patterns: 80% of "missing" requests cluster into 3-5 themes. Use those for next event.
5. Networking quality (1-5 scale)
"How well did the event support your networking goals?" (1 = not at all, 5 = excellent)
This is where most corporate events under-perform. If avg <3.5, redesign networking (longer breaks, structured introductions, networking app, designated networking zones).
6. Next-step intent (multi-select)
"What's your most likely next step after today?" - [ ] Start a free trial / pilot - [ ] Book a demo or consultation - [ ] Share with my team - [ ] Buy related content (book, course) - [ ] Attend a follow-on event - [ ] Wait and see
The single best Tier-2 ROI predictor available within 7 days. Cross-reference next-step intent with actual pipeline 30+ days later.
7. Recommended improvements (open text, optional)
"What single thing would make this event 10x better?"
Open text. Filter for actionable suggestions (not "the AV had a glitch"). Combine with question 4 for next-event prioritisation.
8. Permission for follow-up (consent question)
"May we contact you about: (1) Future events in this series, (2) Related content + resources, (3) Product demos relevant to topics discussed today?"
Separate opt-ins per category. GDPR-compliant + segments the follow-up email lists.
9. Email + role confirmation (carryover from registration)
"Confirm: [Email pre-filled] [Role pre-filled]. Anything to update?"
Keeps your CRM clean + gives attendees a chance to update if registration data was outdated.
Survey delivery best practices
Timing
Send within 24 hours post-event. After 72 hours, response rates drop by 50%. Best window: T+1 day at 10am attendee local time.
Format
- Single-page web form (not multi-page wizard)
- Mobile-responsive (50%+ of completions are mobile)
- Estimated completion time stated at top ("90 seconds")
- Progress indicator (questions 3 of 9)
Subject line
"Quick favour: 90 seconds on [Event Name]?"
Or: "[Event Name] feedback — 90 seconds, your input shapes next event"
Incentive (optional)
- Free report / content download for completion (+10-15% completion)
- Charity donation per completion (+5-10%)
- Prize draw (€100 voucher) — works but biases the sample
Follow-up sequence
- T+1 day: initial survey email
- T+5 days: 1 reminder to non-completers ("Last chance")
- After T+5: stop. Further reminders hurt brand trust.
What NOT to ask
Skip these common questions:
- "What did you think of [each speaker]?" — too long. Replace with "most valuable session" (question 3).
- "How did you hear about us?" — Should be in registration, not post-event.
- Demographics already captured at registration — wastes time, signals you didn't read the registration.
- "Would you attend again next year?" — vague + low signal. NPS captures this better.
- "Rate the venue / food / coffee" — captures what attendees can already tell you in open text on question 2.
If a question can be answered better another way OR doesn't drive a decision, cut it.
How to use the results
Within 5 days
- Calculate NPS + share with event team
- Aggregate open-text themes (questions 2, 4, 7)
- Identify session winners + losers (question 3)
- Send top-feedback summary to leadership
Within 30 days
- Action plan for next event based on aggregated insights
- Follow up with detractors personally (1:1 calls or emails — saves brand)
- Promote next event to opt-in respondents (question 8)
Within 90-180 days
- Cross-reference next-step intent (question 6) with actual CRM activity
- Validate Tier-2 ROI predictions
- Refine survey for next event based on what you actually used
Frequently Asked Questions
Will 9 questions get 60% completion? In our analysis, yes — if survey is mobile-responsive, sent T+1 day, with clear time estimate. We've seen 65-75% completion at well-run corporate events of 100-500 attendees. Events >2,000 attendees typically see 40-55% — still much better than the 22% average.
Should I make NPS mandatory? Yes (single required question). Others optional. Required-everything = 30% completion. Optional-everything = 60-70%.
Can I A/B test survey versions? Yes — try short (5 questions) vs full (9 questions) on a single event. Usually 5-question wins on completion but loses on actionable depth. Iterate based on what your team actually uses.
Should questions be in event's primary language only? If 30%+ of attendees are non-native, offer 2-language version. Spanish + English is most common in EU events.
How do I handle anonymous vs identified survey responses? Default to identified (pre-filled email) for B2B events. Add explicit "Submit anonymously" option only if you must.