Survey Questions to Ask After an Event
For an event organizer writing the feedback survey that goes out to attendees after a conference, workshop, fundraiser, company offsite or webinar. The questions run in the order of a good form: overall satisfaction first, then content and speakers, registration and the lead-up, the venue and the day itself, value for money and time, and whether people would come again. Each has a note on the answer type to use (a rating, a yes or no, a choice or an open box) and on what a good or a worrying result lets you change, and the guide shows how to cut the list down to a form people will finish.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Overall
Overall, how satisfied were you with the event?
Why ask it
Make it the first thing on the form, as a five-point rating from very dissatisfied to very satisfied, so the lunch and the parking have not been brought to mind yet. This is the one number you will set beside last year's, which only works if the wording never changes. A pile-up in the middle is more worrying than a few low marks: it usually describes an event nobody will remember, and no single fix cures that.
How likely are you to recommend this event to a friend or colleague?
Why ask it
Recommending puts a person's own name behind the event, which makes it a harder test than satisfaction. Use a 0 to 10 scale with both ends labeled; for the net promoter figure, subtract the share who answered 0 to 6 from the share who answered 9 or 10. For a company offsite that nobody chose to attend, ask instead whether they would want another one.
What is the biggest reason for the score you just gave?
Why ask it
An open text box, placed straight after whichever rating you lead with so the two are read together. Sort the replies by score: the reasons from people who gave a middling number are the ones you can most plausibly fix. If the form has room for only one open question, make it this one.
What was the most valuable part of the event for you?
Why ask it
One line of open text is enough. The answers show what to protect when the budget is cut, and what to quote, with permission, when you promote the next one. If most people name the breaks and the conversations in the hallway, give those more of the schedule.
What is one thing we should change before the next event?
Why ask it
Asking for one thing makes people rank their complaints, so what comes back is the complaint that mattered most. Leave it as an open box and tally the replies by theme. The same problem raised unprompted by several people outweighs a slightly low mark on a rating grid.
How did the event compare with what you expected when you signed up?
Why ask it
Give three choices: fell short, about what I expected, better than expected. 'Fell short' beside decent ratings elsewhere points at the invitation or the listing, which promised a different event from the one you ran. That gets fixed in the copy, not the program.
What were you mainly hoping to get from the event?
Why ask it
Ask it as a single-choice list written for your own event: to learn something, to meet people, to support the cause, to see one speaker, because work sent me, something else. The tally matters less than what it lets you do with the other answers, since every rating can then be read separately for those who came to learn and those who came to mingle. If 'because work sent me' leads, the employer is your real customer and the invitation should be written for them.
Did you get what you came for?
Why ask it
Yes, partly or no. Set each reply beside what that person said they came for, because an event can score well overall and still fail the group that came for one specific thing. If 'partly' is the most common answer, add an optional box asking what was missing.
Content and speakers
How would you rate the quality of the sessions as a whole?
Why ask it
This is the headline figure for the program, on a five-point scale from poor to excellent. Keep it even if you also rate sessions one by one, since not everybody finishes a long grid. Good logistics scores beside a weak number here describe a well-run event with a thin program.
Which session or speaker did you get the most out of?
Why ask it
Offer a pick list of the sessions so nobody has to remember a title, and let people choose one. Count the votes against how many were in each room. A small session that half its audience names is a stronger result than a keynote everyone saw and a few picked.
Which session was least useful to you, and why?
Why ask it
Include 'none of them' in the pick list so people are not pushed into naming one, and make the comment optional. Look at the reason before dropping anyone: a good speaker in the slot after lunch, or with a failing microphone, is your problem to fix and not theirs. Speakers often ask to see their feedback, so decide before the form goes out what you will pass on.
How relevant were the topics to your work or interests?
Why ask it
Low relevance with high speaker scores means good talks for the wrong audience, so check who the invitations went to before you change the program. Rate it from not at all relevant to very relevant. If registration collected a job role or membership type, split the result by it.
Was the content too basic, about right, or too advanced for you?
Why ask it
A three-way choice beats a rating here, because a middling score on a scale would not say which direction to move. A split between 'too basic' and 'too advanced' is the usual sign of a mixed room. The answer to that is tracks or labeled levels, not a compromise that suits nobody.
How would you rate each speaker you saw?
Why ask it
Build a grid with one row per speaker and a 'did not attend' column, so people rate only what they saw. At a single-speaker workshop or webinar, use two rows instead: how well the speaker knew the subject and how clearly they explained it. Those two can come apart, and they call for different fixes.
Was there enough time for questions and discussion?
Why ask it
Yes or no is all this needs. A majority of 'no' is among the easiest results on the form to act on: shorten the talks by a few minutes and hold speakers to time. After a webinar, ask in the same place whether the person's own question got answered.
What is one thing you learned that you expect to use?
Why ask it
Specific answers, such as a tool someone plans to try on Monday, show the content landed, and they are the lines that sponsors and employers who paid for tickets want to see. Blank boxes and 'lots of things' suggest a pleasant day from which little stuck. Open text, and optional.
How useful were the workshops, breakouts or hands-on activities?
Why ask it
Add a 'did not take part' option to the rating, so that people who only went to the talks are not counted. When the talks outscore the hands-on parts, the usual causes are groups that were too large or instructions that were rushed, and a follow-up box will say which. When it runs the other way, cut a talk and lengthen the exercise.
Were you able to get the slides, recordings or handouts you wanted afterwards?
Why ask it
Yes, no, or 'I did not look for any'. A run of 'no' is usually a delivery problem and not a content one: the link went out late, sat behind a login, or a speaker never sent the file. Ask speakers for permission to share before the event, so you are not promising attendees something you cannot send.
Before the event
How easy was it to register?
Why ask it
Everyone answering this made it through. The people the sign-up defeated are not on your mailing list, so read even a handful of 'difficult' ratings as the visible part of a larger problem and go through the process yourself on a phone. A five-point scale from very difficult to very easy, with a box for what went wrong.
Before you arrived, did you have all the information you needed?
Why ask it
Yes or no, and on 'no' show a box asking what was missing. The replies are usually concrete: parking, the dress code, which entrance, when the link to join would arrive. Each one is a line to add to the confirmation email, which costs nothing to change.
Were the emails we sent before the event too few, about right, or too many?
Why ask it
'Too many' matters most when the same list will be invited to the next event, since people who felt pestered may stop opening. If 'too few' wins, go back to what people said was missing from the information they had and put those details in a reminder the day before. Three choices, no comment box needed.
Did you hear about the event early enough to plan for it?
Why ask it
The answers set the date of your next announcement, and a yes or no is enough. People who need a budget approved, travel booked or child care arranged want far more warning than locals do, so look at who is saying 'no'. If it is mostly those who traveled, send a save-the-date early and fill in the program later.
How did you first hear about the event?
Why ask it
This tells you where to spend promotion effort next time and nothing about the event itself, so cut it if your registration form already asked. Multiple choice: an email from us, a colleague or friend, social media, a search, a partner organization, other. A large share for 'a colleague or friend' is good news twice over: it cost nothing, and it means an earlier event was worth mentioning.
On the day
How well organized was the event on the day?
Why ask it
Treat this as the headline rating for logistics. People tend to answer it on two things: whether sessions started when the schedule said, and whether they knew where to be. A low mark beside good venue and food ratings points at the running order and the timekeeping, not the building, and an optional box asking when it felt disorganized will name the moment.
How smooth was check-in when you arrived?
Why ask it
Check-in is the first thing people experience on the day, and a bad one follows them into the opening session. Keep it on the same rating scale as the rest of the form, and for an online event ask instead how easy it was to get in with the link. Low marks usually come from the busiest stretch just before the start, so extra hands at that peak often do more than a new system.
How would you rate the venue on each of these: location, comfort, sound and view of the stage?
Why ask it
A single venue score cannot tell you whether to change the building or only the microphones, which is why this is a grid with one row for each. Sound and sightlines can often be fixed in the same room. Poor marks for location and comfort usually mean looking for a different one.
How easy was it to find your way around the venue?
Why ask it
Pair the rating with a comment box, since the useful part is where people got lost: the registration desk, the breakout rooms, the restrooms. Most of that is fixed with signs and a person standing at the turns, without changing venue. Trouble reaching the building is a separate matter of transport, parking and the directions you sent, so keep it out of this question.
How would you rate the food and drink?
Why ask it
Catering tends to draw strong comments, so read the score and resist rebuilding the menu around three loud replies. What to act on is narrower: running out, long lines, and nothing for people who could not eat the main option. A five-point rating with 'did not have any' as a choice.
If you had a dietary or access need, was it met?
Why ask it
Offer yes, no and 'I did not have any', with a box on 'no' asking which need it was. Even one 'no' deserves a personal reply, because that person was shut out of part of the event. Compare the answers with what your registration form asked: a need you never asked about is a need nobody planned for.
How did the pace of the day feel: rushed, about right, or too slow?
Why ask it
'Rushed' is what people say when sessions run back to back with no slack for a room change. 'Too slow' points to long gaps, or a late finish that people sat through out of politeness. For an evening event or a webinar, turn the three choices into a question about total length: too short, about right, too long.
Was there enough break time during the day?
Why ask it
People who came to meet others want longer breaks than people who came for the content, so read this beside the reason each person gave for attending. Yes or no, with a box for what they would change. Online, the same question is whether there was a break at all.
How helpful were the staff and volunteers?
Why ask it
Leave room to name someone, and pass the praise on: for volunteers it is most of what they are paid in. The rating runs from not at all helpful to very helpful. Low marks tend to trace back to briefing, people who were willing and did not know the answer, more than to attitude.
Did you have enough chances to meet and talk with other attendees?
Why ask it
Yes, no, or 'that is not why I came'. A 'no' from people who listed meeting others as their goal is a real failure, and structure fixes it better than a longer coffee break: badges with a topic on them, seated lunches, a short round of introductions. Skip it after a webinar unless you ran breakout rooms.
If you joined online, how well did the sound, video and platform work for you?
Why ask it
Show it only to online attendees, as a rating plus a box for what failed. Sound is the one to watch, since people will sit through a frozen slide and tend to leave when they cannot hear. After a hybrid event, compare this group's overall score with the room's to see whether they got a lesser version of the day.
Value
For what you paid, how would you rate the value of the event?
Why ask it
Only ticket buyers should see this one, on a scale from poor value to excellent value. Poor value beside high satisfaction says the event is fine and the price is ahead of it, or that what the ticket covered was not clear at booking. Split it by ticket type before concluding anything about the price.
Was the event a good use of your time?
Why ask it
This is the value question for anything free or compulsory, such as a webinar, a staff offsite or a volunteer day, where time is the whole price. Yes, somewhat or no. After an offsite, expect some of the 'no' answers to be about the work that piled up while people were away, which is a scheduling finding and not a verdict on the content.
After the event, how clearly do you understand what the money raised will pay for?
Why ask it
For fundraisers, rated from not at all clearly to very clearly. Guests who leave unsure where the money goes may still have given on the night, out of goodwill toward whoever invited them, and that is hard to draw on twice. A low score is fixed in the program: one story and one figure, early in the evening.
After the offsite, how clear are you on what the team is trying to do next?
Why ask it
It tests the purpose of a company offsite or kickoff, where a satisfaction score would mostly test the hotel. Use a scale from less clear than before to much clearer. If the result is flat, the sessions were talk without decisions, so ask in a box what is still unclear and answer it in writing.
Did you meet anyone you expect to stay in touch with?
Why ask it
A blunt yes or no on whether the networking promised in the invitation happened, and far easier to answer than a rating of 'networking opportunities'. A high share of yes is worth quoting in the next round of promotion, as long as you report the real figure.
How useful were the sponsors and exhibitors to you?
Why ask it
Sponsors will ask for this at renewal, so it pays to have it. Rate it from not useful to very useful with 'did not visit' as a choice, and watch that last share: it tells you whether the booths were on the route people walked. Leave the question off if there were none.
How does this event compare with similar ones you have been to?
Why ask it
Better, about the same, worse, or 'I have not been to any'. It gives you a yardstick your own ratings cannot, since some audiences mark everything high. Add an optional box asking which event they had in mind, then go and see what that one does.
Next time
Would you come to this event again?
Why ask it
Treat it as a mood reading and not a forecast, because people are generous about a future that costs them nothing today. Offer five choices from definitely to definitely not. The 'not sure' group is the one to study: look at what they said was missing.
What would make you more likely to attend next time?
Why ask it
Open text, shown to everyone who did not answer 'definitely'. Replies about the event itself, the speakers, the length, the price, are yours to act on. Replies about distance, dates and budgets at work describe limits you can only plan around.
Which speakers or topics would you most like on the program next time?
Why ask it
An open box, or a pick list if you already have a shortlist to test. Names and subjects that several people raise go to whoever books the program, while a single request for a famous name is a wish and not demand. Read the replies from people who rated the content low with extra care: what they ask for is what this program lacked.
Would you prefer the next one in person, online, or with both options?
Why ask it
Read it by how each person attended this time, because people tend to vote for the format they just had. A clear lean among those who came the other way is the only strong reason to change. It is a single-choice question, and an added online option is a real cost, so do not act on a narrow margin.
Which days of the week and times of day would suit you best?
Why ask it
Allow several answers and look for the slot the most people can make, which is often nobody's favorite. Three or four broad choices, such as weekday daytime, weekday evening and weekend, get answered, where a full grid of days and hours gets skipped. Everyone replying managed your date this time, so if you can, put the same question to those who registered and did not come.
Would you be interested in speaking, volunteering or sponsoring next time?
Why ask it
Checkboxes, with a space for an email address if the survey is otherwise anonymous. Checking a box in the glow of a good event is easy, so follow up within a couple of weeks, before the interest cools. Even a few names shorten next year's recruiting.
Was this your first time at this event?
Why ask it
It changes nothing by itself and earns its place as the split for everything else. First-timers judge the welcome and the signs; returners judge whether it was as good as last year. Yes or no, and a high share of first-timers who would not come again is the pattern to worry about.
May we use your comments, with or without your name, when we promote future events?
Why ask it
Ask on the form and you will not have to chase people for permission later. Give three choices: yes with my name, yes without it, no. Rules on using people's words and names in marketing differ by place and by employer, so find out what applies where you are before publishing anything.
Is there anything about the event we did not ask that you want us to know?
Why ask it
The last question, open and optional. It catches what the form had no place for: a safety worry, a kindness from a volunteer, a problem with one particular session. Read every reply, even when you only count the rest.
How to build and use a post-event survey
Practical guidance for the conversation itself
Before you write the form
Start from what you can change
List the decisions that are still open for the next event: the venue, the length, the ticket price, which speakers to invite back, whether to offer an online option. Every question on the form should feed one of them. A question whose answer could not change anything, such as a rating of the weather or of a venue you are already committed to, takes up space the useful ones need.
Pick ten or so, not all of them
This page is a menu. A form people can finish in three or four minutes usually means the first two Overall ratings, one open question, a handful from the sections that fit your event and one from Next time. A fundraiser has no use for the session ratings and a webinar has none for the venue grid. If you cannot decide between two, keep the one whose answer you would act on first.
Send it while the day is fresh
A day or two after the event is the usual window: people are home, and they still remember which session was which. For a webinar, a link at the close of the session or in the email that carries the recording works well. One reminder a few days later is reasonable. More than that starts to cost you goodwill with the same list you will invite next time.
Do not ask what registration already told you
Ticket type, organization, whether someone came in person or online, and which sessions they booked are often in your records already. If your form tool can carry those details in with the link, use that. Tools differ, so check how yours handles it. Every profile question you avoid leaves room for one about the event.
Decide whether it is anonymous, and say so
Anonymous forms tend to get blunter answers, which matters most after a staff offsite, where people are rating something their employer organized. Named forms let you reply to a problem and match answers to ticket types. Either is fine as long as the first line of the survey says which it is and the statement is true. What you may collect and how long you may keep it depends on where you and your attendees are and on your organization's own policy, so ask whoever handles that before you send.
Building the form
Follow the order on this page
Overall first, while the impression is whole, then the program, the lead-up, the day, value, and what happens next. Profile and permission questions go last. If someone drops out halfway, you still have the answers that matter most.
Match the answer type to the job
Ratings give you a number to compare across events and between groups. A yes or no, or a three-way choice such as too short, about right, too long, tells you which direction to move, which a rating cannot. Open boxes tell you why. Two or three open boxes are plenty for most forms: they take the longest to answer and the longest to read.
Keep one scale all the way down
Pick five points, label every point or at least both ends, and keep the good end on the same side throughout. Someone working down a form on a phone may stop reading the labels after the first grid, and a scale that flips halfway then produces answers that mean the opposite of what was intended. The 0 to 10 recommendation question is the one accepted exception.
Let people skip what did not apply
Add 'did not attend', 'did not use' or 'does not apply' wherever a rating might not fit, and show the online questions only to online attendees if your tool allows conditional questions. Without a way out, people who skipped lunch rate the food in the middle and blur the result.
One thing per question
'How were the venue and the catering?' cannot be answered by someone who liked one and not the other. Split it, or use a grid with a row for each. The same goes for 'informative and engaging' when rating a speaker.
Make almost nothing required
Require the first rating and leave the rest optional. A required open box gets a period typed into it, and a required grid makes some people close the tab.
Reading the results
Remember who answered
Replies come from the people who cared enough to open the email, which tends to mean the very pleased and the very annoyed. Report how many of your attendees responded alongside every figure, and be careful with conclusions drawn from a small share of the room.
Split before you average
An overall score hides the groups inside it. Compare first-timers with returners, in-person with online, and people who came to learn with people who came to meet others. A result that looks fine in total can turn out to be two groups, one delighted and one let down.
Sort the comments into themes
Read every open answer once, then go back and tag each with a theme such as sound, parking, pace or a speaker's name. A count of themes turns a pile of remarks into a ranked list, and it stops the most vividly written complaint from standing in for the most common one.
Ask the same questions next time
A satisfaction score of four out of five means little alone. The same question, worded the same way after the next event, tells you whether the changes worked. Keep the Overall ratings and the wording of any question tied to something you changed.
Tell attendees what you changed
A short note to attendees, or a line in the next invitation, saying what you heard and what will be different is the best argument for filling in the next survey. It also works as promotion: 'you asked for longer breaks and a later start' is a reason to come back.
Mistakes to avoid
Sending every question
A form built from all six sections takes far longer than most attendees will give, and the people who abandon it are lost for the questions that mattered. Cut until it fits in a few minutes, then cut one more.
Leading the answer
'How much did you enjoy our inspiring keynote?' has told people what to say. Write the plain version, 'How would you rate the opening keynote?', and let the scale carry both good and bad.
Rewarding praise
A prize drawing for everyone who completes the survey rewards the effort. Anything that rewards a high score, or a line asking for 'five stars if you had a great time', leaves you with numbers that say nothing. Rules on prize drawings and giveaways vary from place to place, so check what applies to you before offering one.
Surveying only the people who came
No-shows and people who left at lunch have the most to tell you about the date, the price and the program, and they are missing from an attendee survey. One short question sent to them separately, asking what kept them away, fills the gap.
Collecting it and filing it
Results that reach nobody change nothing. Before the form goes out, decide who gets the venue comments, who gets the speaker scores, and when the planning group will sit down with the whole set. Share speaker feedback with care: a summary and the constructive comments, not every raw remark.