Post-Event Surveys 101: Best Questions to Ask Attendees for Actionable Feedback

Your event has finished, the team is tired, and you need to decide what to change before selling the next one. Useful post-event survey questions ask whether the experience was worth the ticket price, where it disappointed people, and what would make them return. Start with a short core survey, then ask follow-up questions only about the parts each attendee experienced.

This guide gives you questions and answer scales you can adapt, a short survey template, and a way to turn the replies into production and budget decisions. You'll also see how to handle incomplete responses, compare different ticket groups, and avoid mistaking a positive rating for a promise to buy again.

Why post-event surveys matter

Post-event surveys connect what you planned with what people actually experienced. Sales tell you that someone bought a ticket. Check-in tells you that they arrived. Feedback can explain why a paying attendee left early, enjoyed the show but disliked the VIP package, or would only return if a specific problem changed.

Use the answers to make decisions such as these:

• Improve the next edition. Keep the formats people valued and investigate problems with sound, navigation, or session pacing.

• Measure the experience consistently. Track satisfaction and the parts of the event that matter to your audience, using the same questions across comparable editions.

• Compare attendee groups. Check whether first-time buyers, returning attendees, and different ticket groups describe the event differently.

• Spend the improvement budget carefully. Investigate whether a check-in problem needs more staff, better instructions, or a different entrance layout before buying equipment.

For more follow-up ideas, See research-backed strategies to extend engagement. PCMA's article is vendor-sponsored, so use the ideas as things to test with your own audience.

Start with the decision after the survey

Suppose you're deciding whether to renew a premium lounge at a paid show. An overall satisfaction score won't answer that. You need to hear from people who bought access, find out which promised benefits they used, and understand whether those benefits justified the extra price. You also need the lounge's cost and sales figures. A popular perk can still cost more to deliver than buyers will pay.

Write the decision down before choosing questions. For that lounge, you might ask which benefits people used, how they rated the upgrade's value, and what they would change. People who never had access should skip this section. Otherwise, their neutral responses could make the package appear less valuable even though they couldn't judge it.

Separate that question from the overall event experience. Someone can love the headline act and feel disappointed by their upgrade. If you only ask whether they enjoyed the show, you'll miss the problem until the next premium ticket release sells slowly.

Use the same approach for a workshop lunch, a festival shuttle, or a conference recording package. Start with something you can keep, remove, change, or price differently. A survey cannot make the decision for you, but it can explain the experience behind the sales numbers.

The first thing you want to do is agree who will read the answers. If nobody owns the lounge decision until next season, collecting detailed lounge feedback now may create an expectation you aren't ready to meet. Put the decision on the production calendar while the people who delivered it still remember what happened.

Designing your post-event survey

Start with the decisions you need to make, then choose the smallest set of questions that can inform them. These are useful starting rules:

• Keep it brief. Start with roughly eight core questions and test the actual completion time. A long question with several ratings can take more effort than several simple questions.

• Match the answer to the question. Use a clearly labelled rating scale for satisfaction, choices for specific experiences, and optional free text when you need an explanation.

• Design for phones. Avoid wide rating grids, keep instructions visible, and check that people can select answers without zooming.

• Explain privacy accurately. Say whether replies are anonymous or linked to an attendee, who will read them, and whether contact details are optional.

• Test the whole experience. Have someone outside the planning team complete the survey, including its skip questions and final submit step.

You need a survey tool that supports the questions and privacy settings you chose. Loopyah handles the attendee communication side: its email tools let you organize contacts into lists or purchase-based segments, personalize a message, and send a test. Build and collect survey responses in your survey tool. Confirm how completed responses can be excluded before arranging a reminder.

Ask one thing at a time

"How satisfied were you with the venue and catering?" sounds efficient until someone liked the venue and couldn't eat the food. You won't know what their middle rating means. Ask separately about the part you need to assess, or let them identify the problem before showing a follow-up.

Pew Research Center's question-writing guidance explains why wording, answer choices, and question order affect replies. Ask about a concrete experience in neutral language. "How easy was it to find the entrance?" is clearer than "Did our excellent signage help you arrive smoothly?"

Keep answer scales in a consistent direction and label their points. Include "Did not use" when someone may not have experienced a service. That answer is different from a neutral opinion. Don't mix them in your average.

Try the draft with people who resemble your audience. Ask them what they thought a question meant before showing them your explanation. If several people interpret "registration" as buying a ticket while you meant entry at the door, change the question. More replies won't fix that ambiguity.

Be clear about identity and follow-up

An anonymous survey means you cannot identify the person from the response. A form with a name field, attendee reference, or identifying link may be confidential without being anonymous. Check the actual collection settings before writing the invitation.

You might want to contact someone about a problem. Offer a separate, optional way to request a reply, and explain who will see it. Keep that request distinct from the main feedback if you intend the main survey to remain anonymous. Avoid asking for ticket numbers in the same form while promising that you cannot connect replies to individuals.

For sensitive complaints, provide a contact route your team monitors. Someone reporting an access problem or harassment should not have to wait for the next survey analysis meeting. Explain that the survey is for feedback, and point them to the right support contact for an issue needing a response. You can still learn from the report while handling the person with care.

Essential post-event survey questions

Treat the questions below as a question bank. Choose the ones your event needs; sending every question would make the survey unnecessarily long. Keep the overall questions consistent, and adapt the experience questions to what you actually sold.

Satisfaction and enjoyment

Find out how people judged the experience, whether it matched the promise, and whether they would recommend it.

• Overall, how satisfied were you with the event? Use Very dissatisfied / Dissatisfied / Neither satisfied nor dissatisfied / Satisfied / Very satisfied.

• How did the event compare with what you expected? Use Much worse / Somewhat worse / About as expected / Somewhat better / Much better / Not sure.

• How likely are you to recommend this event to a friend or colleague? Use a scale from 0, Not at all likely, to 10, Extremely likely.

Net Promoter Score, or NPS, uses the recommendation question above. Responses of 9 or 10 are promoters, 7 or 8 are passives, and 0 through 6 are detractors. Subtract the percentage of detractors from the percentage of promoters. The result is a score, not a percentage of attendees who will return.

Bain's explanation of the NPS calculation is the primary reference for the scoring method. For a hypothetical set of 100 answers, 50 promoters and 20 detractors produce an NPS of 30. The remaining 30 passive responses still belong in the denominator.

Decide whether this measure helps your event before including it. A recommendation question may suit a recurring public show. A specialist course may benefit more from asking whether attendees learned what they came to learn. A sold-out event can have a poor experience, and a highly recommended event can still lose money.

If you use NPS, report the number of people who answered it and keep the question consistent. Don't compare a small VIP-only survey with last year's whole audience and describe the difference as an event-wide improvement. The people responding changed along with the score.

Ask about ticket value and returning

Paid events need a question about value. "Considering what you paid, how would you rate the value of the event?" separates the buying decision from general enjoyment. Offer "I did not pay for my ticket" because guests, companions, and people whose employer paid may not know the price. Their experience still matters; their value judgment may answer a different question.

Then ask, "How likely are you to attend another edition?" Follow a low rating with an optional "What would most influence that decision?" Someone may be happy with the event but unable to return because of travel or timing. Someone else may be waiting for a different lineup. Those are different problems from poor sound or disappointing content.

Return intention isn't a future booking. Use it to understand reasons and plan a test, then check actual repeat purchases when the next event goes on sale. Don't forecast revenue by multiplying your satisfied respondents by the next ticket price. You haven't measured everyone's willingness or ability to buy.

For pricing decisions, avoid asking only whether people want a cheaper ticket. A more useful question might ask which part of the paid package mattered most, followed by what felt missing. Combine that with the cost of delivering each benefit before changing the offer.

Content and speakers

For a conference, workshop, or other programme-led event, find out whether the material delivered what buyers came to learn.

• How useful was the session you attended? Use Not at all useful / Slightly useful / Moderately useful / Very useful / Extremely useful / Did not attend.

• How relevant was the content to your interests or work? Use Not at all / Slightly / Moderately / Very / Extremely / Not applicable.

• How clearly did the speaker explain the material? Use Not at all clearly / Slightly clearly / Moderately clearly / Very clearly / Extremely clearly / Did not attend.

If you need session-level feedback, show only the sessions a person attended or let them select those sessions first. Ask about preferred formats only if you can act on the result. For future topics, an optional prompt is "Which topic would you most like us to cover next time?" Separate suggestions about adding a topic from complaints about a session that failed to deliver.

For a hypothetical paid workshop, high speaker ratings and weak usefulness ratings can coexist. The trainer may be clear and engaging while the material is too basic for the buyers. Before replacing the trainer, compare the session promise with the actual level of the content. Ask whether attendees could do the task the workshop advertised, then discuss the replies with the instructor.

Use questions the attendee can answer at that point. Immediately after a session, they can describe whether the explanation made sense and whether they had enough practice time. They cannot yet tell you whether it improved their work over the next month. If that later outcome matters, plan a separate follow-up and explain why you are asking again.

For a concert, replace learning questions with the parts of the performance you can assess. Ask about the view or sound in the area they used, and separate disappointment about a schedule change from dissatisfaction with the artist. For a food event, ask whether people could access the tastings included in their ticket. The survey should reflect the promise buyers paid for.

Networking and engagement

Use these questions when meeting people was part of the offer. A music audience should not have to rate a business networking programme it never bought.

• How useful were the organized networking activities you joined? Use Not at all useful / Slightly useful / Moderately useful / Very useful / Extremely useful / Did not join.

• Did you have enough time to meet the people you wanted to meet? Use Yes / No / Not sure / Meeting people was not a reason I attended.

• Did you make a connection you intend to follow up with? Use Yes / No / Not sure / Not applicable.

If you offered several formats, ask which activity they joined before asking what worked. A useful optional question is "What made it difficult to meet the people you wanted to meet?" Replies may point to timing, introductions, room layout, or the mix of attendees.

For a paid industry event, distinguish access to people from useful conversations. A full room tells you how many people arrived. It doesn't tell you whether a first-time attendee understood how to join a discussion or whether a buyer met the suppliers they came to assess. Ask what they tried to do before asking how well it worked.

You could use a question such as "Did you take part in an organized networking activity?" People who say no can skip the rating, with an optional question about why they didn't take part. They may have chosen to spend the time in a session. Others may have wanted to join but couldn't find the room. Neither group should be forced to rate the activity itself.

For people who participated, ask whether the activity helped them meet someone relevant to their reason for attending. If it didn't, the optional explanation can identify whether introductions, time, noise, or the attendee mix was the issue. Keep the wording about their experience; don't ask them to prescribe a new networking product.

Use later follow-up sparingly. If the event promise involved commercial introductions, a conversation at the event may take weeks to turn into a useful meeting. You can ask willing participants about that later, while keeping the immediate survey focused on what they can already judge. Avoid claiming that every exchange of contact details created a business opportunity.

Logistics and organization

Ask about separate parts of the visit so you can identify what the production team needs to investigate.

• How easy was it to find your way around the venue? Use Very difficult / Difficult / Neither easy nor difficult / Easy / Very easy.

• How satisfied were you with the sound in the area you used? Use Very dissatisfied / Dissatisfied / Neither satisfied nor dissatisfied / Satisfied / Very satisfied / Not applicable.

• How easy was it to enter the event after arriving at the entrance? Use Very difficult / Difficult / Neither easy nor difficult / Easy / Very easy.

For entry problems, ask where and roughly when the delay occurred, then compare the replies with your team's records. Our guide to the best event check-in apps explains how to assess check-in tools. Check the actual cause before assuming new software will fix a queue.

Choose logistics questions with evidence, then check your event

Loopyah's 2025 attendee survey asked 500 respondents what frustrates them most at events, with up to three choices allowed. The answers below can help you spot areas worth investigating. They do not describe your event or tell you which problem caused a low rating.

Source: Loopyah Event Attendee Insights Report, Q16, 500 US respondents, fielded November 11, 2025. These are raw shares of respondents. Multiple choices were allowed, so the bars do not total 100%.

Notice how different the possible fixes are. A queue could involve the entrance, a bar, a cloakroom, or a toilet block. Ask which one before deciding to add scanners. A sound complaint might come from one seating area while the rest of the audience heard clearly. Ask for the area rather than treating the overall average as a verdict on the entire system.

Keep safety and access questions separate from popularity. A problem affecting a small group can still need urgent action. Offer a clear way to describe the location and experience, and let people avoid disclosing personal information they do not want to share. The production team should review credible concerns even if most respondents selected a positive rating.

Don't ask attendees to diagnose technical faults. They can tell you that they couldn't hear the speaker in the back rows or that a route felt blocked. Your team needs to inspect the cause, compare staff records, and decide how to change the next event.

Open-ended feedback

Leave room for something you did not anticipate. Use one or two of these prompts, with answers optional.

• What was your favorite part of the event? Why?

• What could we have done to make the event better?

• Is there anything else you'd like to share with us?

Read free-text answers before selecting testimonials. They were submitted to help you understand the event; publishing an identifiable comment for marketing is a separate use. Ask permission and agree attribution before turning one into an ad or a quote on your ticket page.

Ask sponsors and no-shows different questions

An attendee survey won't explain whether a sponsor received the benefits you sold. Send sponsors a separate review focused on the package, delivery, audience fit, and what happened after the event. If an attendee rates a sponsor activation, make clear which activity you mean and let people who didn't visit it skip the question.

No-shows also need a different route. They can't rate the venue or programme. A short question about why they missed the event can help you understand travel disruption, timing, illness, or a change of plans. Don't combine those replies with attendee satisfaction scores.

Be careful with the records used to select that group. A missing scan can mean a missed check-in rather than an absent attendee. If the data is uncertain, start by asking whether they attended and show the relevant questions afterwards. That small check prevents a confusing email to someone who remembers being there all night.

Ticket buyers and attendees may be different people too. A buyer who bought four tickets cannot reliably answer for every companion. Decide whether your invitation reaches the purchaser or each attendee, describe that in the analysis, and avoid counting an order as several completed individual surveys.

Analyzing and acting on survey results

Read the overall results, then investigate differences that could change an operating decision. A good average can hide a poor experience in one room or ticket group. Your first analysis should end with a small number of actions the team can investigate and fund.

A simple analysis plan you can follow:

1. Review the responses. Record how you treated duplicates and incomplete replies. Keep valid answers from partial submissions where the question itself was answered.

2. Group the findings by the part of the event involved, such as entry, programme, facilities, and ticket value. Keep comments that mention several problems in each relevant group.

3. Choose what needs investigation. Repeated problems deserve attention, but a single credible safety or access report may need immediate follow-up.

4. Assign an owner and a decision date. Ask that person to check the cause and propose a fix before committing the budget.

5. Tell attendees what you can confirm. Explain the changes you have approved and be honest about suggestions you are still assessing.

These hypothetical examples show how an answer can lead to an investigation:

• At a paid conference, replies say introductory sessions repeated material buyers already knew. The programme lead could compare first-time and returning attendees' comments, review the session descriptions, and test demand for an advanced track before booking it.

• At a festival, attendees report a queue near one entrance. The operations lead could check arrival times, scanning records, transport drop-offs, and staff notes to distinguish slow scanning from a sudden surge or a blocked approach.

• At a professional forum, people say the room was busy but introductions were difficult. The team could ask a few willing respondents what stopped them, then test a hosted introduction format at a smaller event.

For the recap, send a relevant message to the appropriate attendee list in Loopyah. You can personalize the email and include resources you have permission to share. Keep research follow-up and promotional offers appropriate to the purpose of the message and the people receiving it.

Check who answered before comparing scores

Suppose, hypothetically, 200 of 1,000 attendees reply. That is a 20% response rate, but it doesn't tell you whether the respondents resemble the full audience. If most replies come from returning buyers while first-time attendees barely respond, you may miss problems that regulars have learned to work around.

AAPOR's survey research guidance explains that response rate alone does not establish survey quality. Record how people were invited, who could take part, and the number of responses. Treat an optional attendee survey as feedback from the people who chose to answer.

Compare respondents with the audience using information you can legitimately access, such as ticket group or first-time versus returning attendance. You don't need to publish a detailed breakdown of small groups. You need to notice when an important part of the audience is missing and avoid broad claims about it.

Check the number behind each question too. In the hypothetical survey, 200 people may answer overall satisfaction while only 35 used the shuttle. Report shuttle satisfaction among those 35 users, with the count visible. People who selected "Did not use" should not become neutral shuttle ratings.

For a very small group, read the individual experiences and investigate the issue. A percentage calculated from a handful of replies can make a minor numerical change look dramatic. Acknowledge the limited information and combine it with what staff observed.

Turn a complaint into a costed change

Imagine your paid event receives repeated comments about waiting for drinks. Before adding another bar, the operations lead checks when the queue formed, which drinks slowed service, and whether stock or payment issues caused stoppages. The survey identifies the experience; the investigation identifies the action.

Compare practical options. A shorter menu or clearer price board may cost less than a second bar. An extra payment point may help only if staff can keep up with orders. If you run several editions, test a change where the conditions are reasonably comparable and record both the cost and the result.

The improvement record can be simple. Write down the problem, the supporting evidence, the person responsible, the proposed change, and its cost. Add the measure you will check next time. For a queue, that might include observed wait times and a specific entry or service question, rather than hoping that the overall event rating rises.

Don't declare that a change caused higher satisfaction just because next year's average improves. The lineup, weather, audience, and ticket offer may also have changed. Describe what you changed and what you observed, and keep the explanation proportionate to the evidence.

Getting useful responses

Make the invitation relevant, remove unnecessary effort, and monitor which parts of your audience you are hearing from.

• Timing. Sending the next day is a reasonable starting plan for an experience survey. Leave time for people travelling home, and test the schedule with your audience.

• Incentives. Decide whether a reward is necessary and affordable. State the terms clearly, keep the reward independent of the rating, and check any applicable rules before offering a draw.

• Communication. Explain what the feedback will inform, provide an honest time estimate, and describe how you will use the replies.

• Follow-up. Plan one reminder a few days later. Exclude completed responses when your survey and mailing setup can reliably identify them.

Sample schedule:

1. At event close, mention the survey and show a readable QR code or short link where appropriate.

2. The next day, email the invitation at a time that suits your audience. Use the completion time measured in testing.

3. A few days later, send one short reminder with the closing date. Check the recipient selection before sending.

4. After the stated closing date, export the results, record the response totals, and assign the first investigations.

Use a clear subject line such as "How was Saturday's show?" and put the survey link near the start of the email. Explain a reward only if you are offering one. Our Event Email Marketing Strategy guide has more advice on the message and sending schedule.

Keep the survey easy to use. Avoid unnecessary logins and compulsory comment boxes. Show progress accurately if your tool supports it, and test what happens when someone goes back to change an answer.

A high response rate does not automatically make the answers representative. Check who replied and who is missing. Treat the findings as feedback from respondents, and keep that qualification when sharing results with the team or a sponsor.

Make the form work for people using it

The W3C accessible forms tutorial recommends clear labels, instructions, and feedback about errors. For your survey, test whether someone can identify each answer choice using a keyboard and a screen reader, and whether tap areas work comfortably on a phone. Attractive layout alone doesn't establish accessibility.

Check required fields carefully. Someone who cannot remember the exact session title should still be able to describe a problem. Explain validation errors in words and preserve answers when a submission fails. If your audience uses several languages, review the translations with someone who understands the event and check that the scales still mean the same thing.

Try the survey on a weak connection as well as office Wi-Fi. An invitation that opens quickly but loses a long comment at submission is frustrating. A shorter form with optional text may be a better choice than a complex questionnaire your team hasn't tested.

If you offer an incentive, budget its full cost before sending. In a hypothetical invitation to 500 people with a guaranteed $5 reward for every eligible completion, the maximum reward cost is $2,500 before administration. Don't quietly cap the reward later because more people replied than expected. State any eligibility and availability conditions at the start.

Keep the invitation neutral. A next-event discount can attract people already interested in returning, so consider that when interpreting the replies. Whatever the reward, a negative answer should be just as eligible as a positive one. You are asking for useful criticism, and the invitation needs to make that believable.

Share a fair account of the findings

When you prepare a team or sponsor report, include the question and the number who answered it alongside the result. "Respondents rated the event highly" tells the reader less than a statement explaining which rating, how many replies it received, and which audience was invited. Keep the full response distribution available so a good average doesn't conceal a group of unhappy attendees.

Use the same care with quotes. A vivid negative comment can help the team understand an experience, but it doesn't establish how common that problem was. A glowing comment can be useful encouragement without representing the whole audience. Read comments for explanation, then check the relevant ratings and operating records before describing a widespread issue.

If you make a chart from your own results, label the question, scale, response count, and any excluded choices. A bar chart can show the share selecting each answer. A list of comments should remain a list of comments; turning them into percentages requires a consistent way of grouping every relevant reply. Explain that method if you use it.

Keep a simple record of what happened after the review. Perhaps the team approved new signs, deferred a shuttle because the cost was too high, and asked the venue to investigate a sound problem. That record makes the next survey useful: you can check the experiences you meant to improve rather than producing another report nobody compares with the last one.

For recurring events, agree which details matter before changing the survey each time. Keep the core questions stable, record the invitation dates and audience, and note major differences in the event. You can then discuss whether the experience appears to be improving without hiding changes in who attended or who replied.

A short post-event survey template

For a general paid event, this eight-question starting template covers the core experience. Keep both text responses optional and offer Not applicable where appropriate:

1. Overall, how satisfied were you with the event? Use the five-point satisfaction scale above.

2. How did the event compare with what you expected? Use the five comparison choices above, plus Not sure.

3. Considering what you paid, how would you rate the value of the event? Use Very poor / Poor / Fair / Good / Very good / I did not pay for my ticket / Not sure.

4. How easy was it to enter the event? Use the five-point ease scale.

5. How satisfied were you with the main part of the programme you attended? Use the satisfaction scale, plus Did not attend.

6. How likely are you to attend another edition of this event? Use Very unlikely / Unlikely / Neither likely nor unlikely / Likely / Very likely / Not sure.

7. What should we keep for the next edition? Optional text answer.

8. What is the main thing you would change? Optional text answer.

Build it in your preferred tool and distribute via your email platform. If you're using Loopyah, set up a segmented send with the Email Event Attendees feature.

The template leaves out NPS to keep the core short. Add it if you already track recommendation consistently or have a clear use for the result. Replace the main programme question with a more relevant one if you run a concert, tasting, or exhibition. Don't append every section of this article to the form.

Use a short introduction in your own words. For example, "We are planning the next edition and would like to hear how this one was for you. The survey takes about four minutes, based on our test. Your answers will be read by the event team. Contact details are optional." Change the timing and privacy statement to match your tested form and settings.

Once the responses arrive, read a handful of complete submissions before looking only at averages. You may discover that a question confused people or that one experience needs an explanation you didn't ask for. Note that limitation rather than editing completed answers to make the results cleaner.

Save the final question wording and answer choices with the results. When you prepare the next edition, you can decide which questions to repeat and which need changing. If you do change one, record why, so a later comparison doesn't imply you measured exactly the same experience in exactly the same way.

Decide what you need to learn first

Before building the form, choose the next production or budget decision the replies should inform. Then test the short survey with someone who did not write it. If they cannot tell you what a question means, or the answer would not change anything you do, revise it before asking your attendees to spend time on it.

Loopyah can help you reach the attendee lists you already manage and send a clear follow-up. Use the survey results to decide what to investigate, and share confirmed changes when you invite people back.