Post-Event Survey Questions: 25 to Copy and What a Survey Misses

Good post-event survey questions ask about things only the attendee knows: whether the event was worth their time, what they took away, who they met, and whether they will come back.

Below are 25 questions grouped by purpose, a 5-question short version, and a short pre-event survey. Leave out anything your registration and check-in records already answer.

Download post-event-survey-questions.csv (plain CSV, no sign-up): all 25 questions with their answer formats, the 5-question short version, and the 6 pre-event questions. Copy the rows into Google Forms, Typeform, or SurveyMonkey.

What questions should you ask in a post-event survey?

Pick the groups that fit the event. A customer conference needs the networking and intent questions, and a training day leans on the content ones. Keep the whole survey under 5 minutes. Scales run from 1 (poor) to 5 (excellent) unless noted.

Overall value

1. How likely are you to recommend this event to a colleague? (0 to 10)
2. Overall, how would you rate the event? (1 to 5)
3. Did the event meet the goal you had when you registered? (Yes / Partly / No)
4. Was the event worth the time and cost of attending? (Yes / Partly / No, with a comment box)

Sessions and content

5. What was the single most useful thing you took away? (open text)
6. How relevant were the sessions to your work? (1 to 5)
7. Was the content pitched at the right level for you? (Too basic / About right / Too advanced)
8. Which topic did you expect to see that was missing? (open text)
9. How would you rate the speakers overall? (1 to 5)

Networking

10. How many new professional contacts did you make? (0 / 1 to 2 / 3 to 5 / 6 or more)
11. Did you meet at least one person you plan to follow up with? (Yes / No)
12. How easy was it to find the people you wanted to meet? (1 to 5)
13. Which format helped you connect most? (Receptions / Roundtables / Event app messages / Breaks between sessions / Other)

Logistics

14. How easy was it to register? (1 to 5)
15. How would you rate the venue, or the virtual platform if you joined online? (1 to 5)
16. How was the pace of the schedule? (Too packed / About right / Too loose)
17. How useful was the information you received before the event? (1 to 5)
18. Did anything get in the way of your experience? (open text)

Intent to return

19. How likely are you to attend next year? (Definitely / Probably / Not sure / No)
20. If you are not sure, what would decide it? (Budget approval / Dates / Location / Program / Other)
21. Would you tell your manager this event is worth the budget? (Yes / No / Not sure)
22. Which format would you choose next time? (In person / Virtual / Either)

Open-ended

23. What is one thing we should change for next year?
24. What is one thing we should keep exactly as it was?
25. Is there anything else you want the organizers to know?

Questions 20 and 21 matter most for a B2B audience, where the person who attends is often not the person who approves the trip. A "Probably" held up by budget approval tells you something different from a "Probably" held up by the program.

What are good event feedback questions?

Good feedback questions are specific, ask about one thing at a time, and lead to a decision you can make. "How was the event?" fails on all three counts. "Was the content pitched at the right level for you?" passes: if a third of respondents say "Too basic", you know which track to rework.

A few rules keep a feedback form useful:

• Do not ask what you already know. Session attendance, check-in, and which booths people visited sit in your event platform when it records them. Asking again costs response rate and gives you a less reliable copy of data you hold.
• Pair every rating with a reason. A 3 out of 5 with no comment cannot be acted on.
• Ask about next year as well as this one. Intent to return and the reason behind it tell the budget owner more than a satisfaction score does.

If you only get 5 questions, use these:

1. How likely are you to recommend this event to a colleague? (0 to 10)
2. What was the single most useful thing you took away? (open text)
3. How likely are you to attend next year? (Definitely / Probably / Not sure / No)
4. If you are not sure, what would decide it? (Budget approval / Dates / Location / Program / Other)
5. What is one thing we should change for next year? (open text)

Pre-event survey questions

A pre-event survey is shorter and has a different job: it sets the baseline the post-event survey is measured against. Question 3 in the post-event list only works if you asked about the goal in the first place. Send these with the registration confirmation or a week before the event.

1. What is the main thing you want to get from this event?
2. Which topics do you most want covered? (choose up to 3)
3. Who do you hope to meet? (role, industry, or company type)
4. How familiar are you with the main topic? (New to it / Some experience / Advanced)
5. Do you need any accessibility, dietary, or travel arrangements?
6. How did you hear about the event?

When should you send a post-event survey?

Send it while the event is still fresh: at the end of the last session for a virtual event (a link on the closing screen), and the same evening or the next morning for an in-person one. Send one reminder a few days later and close the survey within about 2 weeks, so the results can go into the post-event report while people still remember the event.

A multi-day conference can add a one-question pulse at the end of each day. Keep that to a single rating plus a comment box, or the final survey will get fewer answers.

Some questions cannot be answered the next morning. Michael Faulkner of ITA Group told Skift Meetings that when you bring people together, you want "retention and recall of information three, six, nine months down the line". If the event was meant to change how people work, send a 3-question follow-up a few months later asking what they applied.

In MPI's Meetings Outlook Q2 2026 report, 80% of planners use post-attendee surveys to measure the human impact of events, and 47% name low survey response rates as a challenge in that measurement. If yours is low, try a shorter survey sent sooner before changing anything else.

Why didn't members attend the conference?

A post-event survey only reaches people who came. For an association, the members who did not come can be the larger group, and the reasons they stayed away do not show up in any attendee survey. Split them before you ask, because each group has a different cause:

Skift Meetings reports no-show rates of 40 to 60% for free events and 10 to 20% for paid ones. The same article lists the outside pressures on attendance: delayed budget approvals, travel costs, geopolitical uncertainty, and visa concerns. Your own rate, by registration type, comes from the method in event attendance rate.

In ASAE research reported by Skift Meetings in April 2025, about half of associations reported decreased attendance. Skift puts the figure for professional associations at "an approximate 56% decline" and for trade associations at 35.5%, without saying whether those are shares of associations or the size of the drop. In the 32nd Convene Meetings Market Survey, 34% of planners saw attendance decline, up from 20%.

Freeman data reported by Trade Show Executive shows that only 40% of attendees report a peak moment, against blended year-over-year attendee retention barely above 30%, while Ken Holsinger told the SISO CEO Summit that "85% of event attendees reported they are more likely to return" after a peak moment. Question 5 ("the single most useful thing you took away") is the closest a survey gets to asking about that moment, so keep it even in the short version.

A non-attendee survey should be 3 questions at most: the one from the table, a multiple choice on the main barrier (budget, travel, dates, program, other), and "What would bring you back?" Send it from a named person on the team.

What can't a survey tell you?

A survey records what people say they did, which often differs from what they did. The attendee who rates a track "most valuable" may have spent the afternoon in another room. The sample is also narrow: it covers only the people who chose to answer.

At ASAE Annual 2026, Reggie Henry and Jeff Horne ran a session titled "Knowing Without Asking" on this idea: build from the member data you already hold instead of asking members to repeat it. For events, that means checking the survey against the records your systems keep.

To check a survey against those records:

1. Match every record to one person. Use one ID across systems where you can, or the email address where you cannot. Count the records that did not match, and report that count next to your results.
2. Put stated and observed side by side for one track: the survey rating in one column, unique attendees and time in session in the next. Where they disagree, look into it before you change the program.
3. Cut every survey question the records answer. Keep the ones about why people chose what they did, how satisfied they felt, and what they intend to do next.
4. Check intent against behavior a year later. Compare "Definitely" and "Probably" answers to question 19 with who registered again, the return cohort that attendee retention builds. That tells you how much to trust next year's answers.

Use only data attendees agreed to share, say in the registration terms what you record, and aggregate wherever a decision does not need a name. Where outreach does need one, restrict access to the staff who already handle those contacts and log who opened the data. This is not legal advice; review your terms with counsel.

The survey and the records are both inputs to the post-event report template, which puts attendance, engagement, costs, and outcomes on one page. For the engagement metrics worth tracking across events, see event marketing analytics; for booth and sponsor results, see event sponsorship ROI.

Where EventIQ fits

EventIQ replaces nothing. It connects on top of the platforms you already run: registration and ticketing (Cvent, Zoom, Swapcard, StubHub), CRM (Salesforce, HubSpot, GoHighLevel), and marketing (Google Ads, Meta Ads, LinkedIn Ads, Mailchimp, Google Analytics). Platforms with an API outside that list are connected on request.

Registrations and attendance stay separate records. Survey answers reach EventIQ from Swapcard only, together with session views, questions, and booth visits, as records per participant. If you run your survey in another tool, the answers stay in that tool. Contacts are matched by exact email, and every record keeps its result: matched, unmatched, or no email. Salesforce deals, stages, and close dates link to an event through a campaign relationship you confirm. Records sync on a schedule: Swapcard every 15 minutes, Cvent every 30, Zoom every 2 hours, Salesforce every 4. The Event Dashboard and the Portfolio Dashboard show them in one view.

Ask any vendor, including us, which of these it holds in the product rather than on a slide: the full cost of the event, the ROI figure itself, one person counted once across sources, and a total in a single currency. The method in this article is the one you run on top of those records.