How to Create a Survey for Event Feedback: Questions and Steps

Before the crew finishes the wrap report, assign someone to manage the survey for event feedback and track the decisions made from its responses. Build the questionnaire around the event’s purpose, use clearly labeled response scales, and leave room for participants to explain what should change. Record who will send the questionnaire, review the responses, and approve any resulting changes to the next production plan.

Key takeaways

• Start with the decisions your team must make, then keep only questions that support those decisions.
• Use a short attendee questionnaire and separate follow-up questions for sponsors, speakers, crew, and suppliers.
• Assign a survey owner, a technical operator, and a decision owner before launch.
• Test the complete path from invitation to approved follow-up, including duplicate responses and failed transfers.
• Keep participant feedback separate from verified causes, supplier responsibility, and approved production changes.

1. Choose the decisions before writing the questions

Write a survey brief before opening a form builder. Name the event’s purpose, the audience whose experience you need to understand, and the choices you expect to make afterward. For each proposed question, complete this sentence: “The answer will help this person decide whether to change this part of the event.”

Keep those choices concrete. A production director might need to approve a different room layout, while a program lead might need to adjust discussion time. Avoid asking participants to evaluate something your team has no intention or authority to change.

The GCFA survey guide recommends asking only what you are willing to use and connecting questions to later planning decisions. For each question, record the decision its answers will inform, the person who will review them, and the deadline for that decision. Remove a question when nobody can name its reviewer or intended use.

Use your event purpose statement as the starting point for the brief. If the purpose is peer exchange, ask whether participants had useful conversations and what prevented them. Keep satisfaction as a separate measure rather than treating it as proof that the purpose was achieved.

2. Adapt this five-question attendee survey

For a first version, use the following five questions as an editorial starting point, not a mandatory standard. Replace the bracketed text with the actual event purpose or activity. Keep the same wording and answer options wherever you intend to compare responses across editions.

1. Overall, how satisfied were you with this event?
2. How well did the event help you [achieve the stated participant goal]?
3. Which part of the event was most useful to you?
4. What, if anything, made it harder for you to participate?
5. What one change should we prioritize for the next event?

For the first question, label every option: very dissatisfied, dissatisfied, neither satisfied nor dissatisfied, satisfied, and very satisfied. For the second, use not at all, slightly, moderately, very well, and extremely well. Add “not applicable” where a participant could reasonably have no basis for answering, and keep that response separate from the midpoint.

For the third question, list the actual program elements and include “none of these” and an optional explanation. Leave the fourth and fifth questions open-ended and optional. Do not require participants to write a comment before they can submit.

The University at Buffalo question bank includes overall satisfaction, expectations, reasons for attending, future attendance intent, and open-ended improvement questions. Select from those categories when they support your brief, rather than adding the entire bank to one form. If future attendance matters to your planning, substitute an intent question for a less relevant item.

Add targeted questions through branching

Use a follow-up question when a response needs operational detail. After a participation difficulty, offer relevant categories such as room access, audibility, timing, registration, or another issue. Then invite an optional description of where and when it happened.

Keep each rating focused on one subject. The GCFA guide advises separating combined questions, including questions that ask about the venue and food together. Apply the same rule to speaker knowledge and delivery, or room comfort and audibility: ask separately when the answers would lead to different actions.

3. Give each audience questions they can answer

Do not send a single questionnaire to everyone involved in the event. The GCFA guide recommends distinct feedback approaches for attendees, vendors or sponsors, speakers, and internal teams. Define the audience routes before preparing your invitation lists.

For sponsors, focus your questions on the agreed experience: preparation, placement, access to the promised activities, and follow-up information. For speakers, ask whether the briefing, technical preparation, and session timing supported their contribution. Keep questions about attendee experience with the attendees themselves.

For crew and suppliers, ask about the work they could observe directly. Use prompts such as “Which instruction was provided too late to act on?” and “Which handoff needed clarification?” Request the relevant schedule version or production document when the reviewer needs to investigate further.

Ask each audience to describe what they observed so your team can investigate who was responsible afterward. Do not ask a participant to identify which supplier caused an audio issue. Ask where they were, which session they attended, and what they experienced, then assign the investigation internally.

For smaller meetings, adapt the questionnaire to the discussion itself. Ask whether participants understood the intended outcome, had a useful opportunity to contribute, and left knowing their responsibilities. Use the meeting feedback questions guide when choosing between meeting-level and event-level prompts.

4. Build ownership into the launch checklist

Put the survey into the checklist for event management before the event opens. Name the people who will design, approve, send, monitor, and act on it. One person may hold several roles, but record each responsibility explicitly.

Start by assigning the following responsibilities to named people on your team:

• The operations lead approves the survey brief, audience routes, and decision deadlines.
• The program or experience lead checks whether the questions reflect the event’s purpose.
• The technical operator configures the form, invitation path, exports, permissions, and transfer checks.
• The feedback reviewer checks comments, requests clarification where permitted, and prepares proposed actions.
• The relevant decision owner approves, rejects, or defers each proposed change.
• The ongoing system operator maintains access, monitors failures, and controls later configuration changes.

Choose an initial sending window and document who can change it. The GCFA guide recommends an initial survey within 24 to 48 hours after the event and a reminder a few days later if needed. Treat that as a starting point, then set separate schedules where a sponsor or supplier follow-up requires different preparation.

Before launch, complete this checklist for event feedback:

• Confirm the audience list, exclusions, sender, and reply destination.
• Approve the questions, response labels, branching, and invitation text.
• Explain whether responses are anonymous or identifiable and who may review them.
• Test the form on a phone, including optional fields and submission confirmation.
• Check that exported answers retain the correct question labels and event identifier.
• Assign an escalation route for sensitive comments or immediate concerns.
• Schedule the review meeting and name the owner of its action record.

Add these checks to your broader events management checklist. Keep the survey launch and the feedback review as separate completion items. Require evidence that both have happened before marking the team's feedback work as complete.

5. Test the handoffs before buying more software

When evaluating software for event management, test the feedback process you intend to run rather than accepting a feature list. Trace a response through collection, export or transfer, review, assignment, and closure. At each handoff, specify the destination record, the person responsible, and the evidence that the transfer succeeded.

For an event organization platform, check the native survey function first. Use it if it meets the approved requirements for questions, audience routing, access, export, and follow-up. Add a separate tool only when you can name the requirement it must satisfy and the person who will maintain the connection.

Create a small acceptance test set before enabling recurring transfers. Include an incomplete response, a duplicate transfer, an unavailable destination, an unexpected answer value, and a response assigned to the wrong event. Require the operator to demonstrate how each case appears, who receives the exception, and how to recover without creating duplicate follow-up tasks.

Define the builder’s handoff to the operator

Ask the builder to deliver the configuration record, field mapping, access list, test results, operating instructions, and manual fallback. Ask the operator to accept those artifacts and demonstrate the recovery procedure. Do not close the build merely because the form accepts submissions.

Event Compsia designs, builds, launches, and operates custom AI production systems for a defined business result and operational perimeter. Our design-through-operation method is the relevant reference when evaluating who will build a cross-tool system and remain accountable after launch. For a proposed feedback system, require an explicit scope and acceptance plan rather than assuming any particular integration or action is available.

Keep the first implementation manual when the approved process is manageable that way. Consider a managed system when you can define recurring cross-tool work, authorized data access, acceptance tests, and an ongoing owner. Do not commission a custom build just to replace a form that already meets the need.

6. Separate the comment, the cause, and the approved change

Use this generic production pattern to work through the review. An attendee reports difficulty hearing a breakout session. Record that as a participant observation, with the session and location if provided, without assigning fault.

Have the production reviewer compare the observation with the room plan, technical notes, and relevant incident record. Ask the appropriate supplier or crew lead for clarification through the agreed production contact. Keep the raw comment restricted, and share only the information needed for that review.

Then prepare a proposed change with an owner and acceptance check. A revised room layout, for example, should include who approves it and how the team will check audibility before doors open. Close the action only when the named owner records the decision and its implementation status.

Choose anonymity or individual follow-up deliberately

If you promise anonymity, do not attach responses to identifiable registration records. If individual follow-up is necessary, explain that choice before submission and request permission to contact the respondent. Offer a separate contact route when you want an anonymous questionnaire and optional individual assistance.

When reviewing the results, report how many people answered each question and identify the audience those respondents represent. Treat a reported problem as a reason to investigate, not as an established root cause or an automatic instruction to replace a supplier.

For comment analysis, preserve access to the original responses. Qualtrics distinguishes rating questions, multiple-choice questions, and open-ended questions, with open text allowing participants to describe their views in their own words. If you introduce AI-assisted categorization, test it against human-reviewed comments and require a reviewer to check sensitive or ambiguous items before assigning actions.

Frequently asked questions

What are some good feedback questions for events?

Ask about overall satisfaction, achievement of the participant goal, the most useful element, barriers to participation, and the change to prioritize. Add operational detail only where someone owns the resulting decision. Keep questions about different subjects separate.

What are five good survey question examples?

Use the five-question template above: satisfaction, goal achievement, most useful element, participation difficulty, and one priority change. Label the rating options and make written explanations optional. Replace the goal wording with the actual promise made to participants.

What are some good survey questions to use for meeting feedback?

Ask whether the meeting achieved its stated purpose, whether participants could contribute, and whether the next actions were clear. Add “What discussion needed more time?” when agenda allocation is under review. Assign any proposed agenda change to the meeting owner.

How do you create a survey for feedback?

Write the decision brief, choose the audience, draft the questions, and configure the response options. Test the invitation, form, exports, access, and follow-up process before sending. Name the reviewer and schedule the decision meeting before launch.

Choose one feedback process to review before the next event

Bring the questionnaire, invitation list, export, wrap report, and follow-up record to one review. Decide whether the next change belongs in survey design, team ownership, the existing tool configuration, or a separately scoped system. Use how Event Compsia builds and operates the system to frame that conversation.

We look at how your team runs an event and show you what we would make more efficient.