Attendee feedback survey templates

Most post-event surveys land in inboxes with 18 questions and a 9% completion rate. The organizer then makes decisions about next year's agenda using data from the 8% most motivated attendees — which is exactly the sample that tells you the least about your median attendee.

The fix is not a better subject line. The fix is asking less, more often, at the right time. Three short surveys will produce more usable data than one long one. This guide gives you the three surveys we recommend for every B2B event, with the exact questions and the completion rates you should expect.

1. Three surveys, three jobs

Do not send one big survey. Send three small ones:

Post-session micro-survey (2 questions)

Sent immediately after each session via the event app or a QR code on the screen:

1. "How would you rate this session?" (1-5 stars)
2. "What's one thing you'll do differently after this?" (optional text)

Expected response rate: 30-50%. Drives session-level data for next year's agenda. The second question — "what will you do differently" — is far more useful than "what did you like," because it forces the attendee to commit to an action, which is the real signal of a session that landed.

End-of-day pulse (3 questions)

Sent via push notification at the end of each day:

1. "How was today overall?" (1-10 slider)
2. "What's the best thing that happened today?" (text)
3. "What's one thing we should fix for tomorrow?" (text)

Expected response rate: 15-25%. This lets you adjust day 2 based on day 1 feedback — if 40% of day-1 attendees complain about lunch, you still have time to fix day 2's lunch. Most organizers skip the end-of-day pulse because it feels like a lot of work to respond. Read the responses and act on the top three themes anyway. The attendees who gave you feedback will notice.

Post-event NPS (5 questions)

Sent at T+24 hours:

1. "How likely are you to recommend {Event} to a colleague?" (0-10)
2. "What's the main reason for your score?" (text)
3. "What's the single best session?" (multi-choice, pulled from actual agenda)
4. "What's one thing we should change for next year?" (text)
5. "Will you attend next year?" (yes / no / maybe)

Expected response rate: 20-35%. The post-event survey of record. Send within 24 hours — response rate drops sharply after 72 hours and rarely recovers.

2. What to cut from your survey

Most survey problems come from including questions that should not be there.

• Likert-scale matrix questions ("rate each of these 12 attributes from 1-5"). Completion collapses. Pick the two you actually act on.
• Demographic questions. You already have role, company, industry from registration. Do not ask again.
• "How did you hear about us?" Track via UTM attribution, not a survey self-report, which is wildly inaccurate.
• Open-ended questions beyond 1-2 per survey. Response rate collapses past the second text field.
• Sponsor-related questions inside the attendee survey. Attendees are not there to rate your sponsors. If sponsors need feedback, ask them directly.
• Anything you will not act on. If the answer would not change a decision, the question is noise.

3. Timing and channel

The channel for each survey matters as much as the copy:

| Survey | Timing | Channel | Expected response | |---|---|---|---| | Post-session | 5 min after session ends | In-app push or QR on slide | 30-50% | | End-of-day pulse | 6pm local | In-app push + SMS | 15-25% | | Post-event NPS | T+24 hours | Email + in-app | 20-35% |

The single largest lever for completion rate is channel: an in-app push notification outperforms an email by 2-3x. A purpose-built conference app that already has the attendee's attention has a structural advantage over any external survey tool.

4. Acting on the data — or why bother

Surveys without action erode trust. If attendees fill out your NPS survey this year and nothing visibly changes, your response rate next year drops 10-15 points. Within 14 days of the event:

1. Publish a "you said, we're changing" summary — a short post or email listing the top 3-5 themes and what you will do about each. Transparency about what you will not change matters too.
2. Reach out individually to detractors (NPS 0-6) with a personal note from the organizer. Not a templated apology — a real message asking what would have made the difference. Detractors who receive a personal response convert to next-year registrants at 2-3x the rate of those who don't.
3. Share session ratings with speakers. With context, not raw scores. Speakers who get feedback ship better second-year talks.
4. Feed the data into next year's planning. Session themes that scored above 4.5/5 should get more time; themes that scored below 3.5/5 should be replaced.

5. Segment the NPS, not just the average

Aggregate NPS hides important sub-segment problems. Always break it down by:

• First-timer vs returner. First-timer NPS below returner NPS is normal and expected. If first-timer NPS is above returner NPS, you have a retention problem.
• Ticket tier. VIP/premium attendees should score highest. If they score lowest, your VIP experience is under-delivering.
• Primary track. A single underperforming track can drag aggregate NPS down.
• Acquisition channel. If attendees from one paid channel score dramatically lower, the targeting is wrong.

A single aggregate NPS number is a vanity metric. Segmented NPS is management information.

Survey question quality checklist

Before you send any event survey:

• [ ] Every question has a clear decision it informs
• [ ] Total questions ≤ 5 (≤ 2 for micro-surveys)
• [ ] Only one text field (two max for post-event)
• [ ] No demographic questions you already have
• [ ] Mobile-responsive format
• [ ] Estimated completion time ≤ 90 seconds
• [ ] Pilot-tested with 5 colleagues first

FAQ

Should I incentivize survey completion? Small incentives (entry to a prize draw, a $25 gift card at random) lift completion 5-15%. Large incentives skew the data because you attract attendees who want the incentive, not attendees who want to tell you something useful. Keep it small.

How do I segment NPS data usefully? By first-timer vs returner, by ticket tier, by primary track, and by acquisition channel. Aggregate NPS hides sub-segment problems.

What's a good NPS for a B2B conference? Above 50 is strong. 30-50 is solid. Below 30 signals a program problem, not a survey problem. Top-tier conferences like AWS re:Invent and Dreamforce consistently publish NPS in the 60+ range.

Should I publish my NPS publicly? If it is above 50, yes — it is marketing. Below 50, publish it internally and to sponsors who ask. Transparency is a long-term trust builder.

How long should I let the survey stay open? Close it at T+7 days. Responses after day 7 are rare and the data staleness starts to bias the analysis of immediate post-event feeling.

Related guides

• Post-event follow-up best practices
• Measuring event ROI
• Event analytics 101

Ready to run your next event? Create your event on WebMobi →