Event feedback form: questions to ask after your event
Create an event feedback form with useful rating questions, room for comments, and a clear review plan. Adapt the examples for workshops, meetups, or webinars.
An event feedback form should help you decide what to repeat and what to change. Start with the decisions the next event needs: whether to keep a session, adjust its length, or change how people find the venue. Ask attendees about experiences they can describe from that event.
For a workshop, you might need to know whether the exercises were useful. For a webinar, the joining instructions may matter more. A generic satisfaction score alone will not tell the organizer which part needs attention.
A question set you can adapt
Use these as a question bank. Choose the ones that match the event and remove questions whose answers nobody plans to review.
- How satisfied were you with the event overall? Use choices from Very dissatisfied to Very satisfied, with a neutral option.
- Which sessions did you attend? Include the actual session names and allow more than one choice when the schedule permits it.
- How useful was the session you attended for your work or interests? For an event with several sessions, ask about a named session or invite people to name the one they are reviewing.
- How did the event length feel? Offer Too short, About right, and Too long. Someone answering Too long may still have liked the content.
- How easy was it to join or find the venue? Use wording that matches an online or in-person event, and include Not applicable if needed.
- What should we keep for the next event?
- What would you change?
- What topic would you like us to cover next?
For a small meetup, the overall rating and two comment questions may be enough. A training workshop could replace the future-topic question with "Which exercise would you like more time to practice?" Keep written explanations optional so attendees can submit a brief response.
Separate content from event logistics
"Were the speakers and venue good?" combines two things the organizer might need to fix separately. Ask about the session content and the venue in separate questions if both decisions are in scope. Pew Research Center's question-writing guidance discusses the problems with questions that ask about multiple concepts at once.
For a webinar, a participant could find the presentation useful but miss the first ten minutes because the joining link was hard to find. A single low score leaves you guessing whether to change the speaker or the invitation. A separate joining question gives the organizer a place to investigate.
Keep registration details out of the feedback form
An RSVP form collects information before an event. A feedback form asks what happened afterward. Reusing the registration questions can leave irrelevant fields such as dietary requirements in a survey about sessions. Create a separate form and give it the event's name so the purpose is clear when somebody opens the link later.
If you do not need individual replies, leave out contact questions. If you ask for contact details, explain what they will be used for. Use the anonymous feedback form guide before making an anonymity promise on the invitation.
Build and test the survey
Start with the Customer Feedback template or a blank form in Thunder Forms. Replace the customer-service labels with event questions. Remove the recommendation question or slider if it does not support your review. Preview each question and make a test submission through the public link on a phone.
Check the saved answers as well as the screen. If you use a slider, test what happens when somebody leaves it untouched. The template's default-value explanation shows why a midpoint answer may need care during analysis.
Share the link where attendees can use it
Choose a collection window that matches the experience. You could share the link at the end of a session and include it in the follow-up email. For feedback about applying a training skill, send a later question once attendees have had a chance to use it.
For a room or reception desk, a QR code linking to the feedback form can make the link easier to open. Provide a readable URL too. Keep the survey available for the period stated in the invitation.
Turn comments into the next event's checklist
Group comments by the decision they affect, such as session length or arrival instructions. Record how many people answered before quoting percentages. If five attendees reply out of a room of sixty, describe those answers as feedback from the respondents, not a verdict from every attendee.
Assign an owner to each change you accept. A note such as "Include a venue map in the reminder email" is usable when preparing the next event. Keep raw comments restricted to the people reviewing them and share a summary when updating attendees.
Match the questions to the event format
| Event | Ask about | Leave out unless needed |
|---|---|---|
| Small meetup | Topic, pace, and what attendees want next | Ratings for sessions that did not happen |
| Training workshop | Practice time, instructions, and confidence using the skill | Broad speaker ratings with no session context |
| Webinar | Joining process, audio, captions, and question handling | Venue and travel questions |
Use the table as a filter, then edit it for the event you ran. If attendees chose between parallel sessions, only ask them to rate a session they attended. Add "I did not attend" where a required choice would otherwise force an inaccurate answer. Keep comments optional so a person can share a rating without writing a paragraph.
For question banks by goal, from product testing to employee pulses, see the survey questions guide.
Frequently asked questions
Short answers to the questions every reader asks next.