How to choose meeting feedback questions

Choose meeting feedback questions that test whether participants understood the purpose, could contribute, and know what happens next. Start with the five-question template below, then add a question only when its answer could change an agenda, a production document, or an assigned action. For event-company operations, connect each issue to an owner and a review point before sending the survey.

Key takeaways

• Use a short core survey and add questions only for a specific decision.
• Separate feedback about the meeting experience from confirmation of production decisions.
• Give each actionable response an owner, a destination, and a review point.
• Review unresolved production concerns individually, even when overall ratings are positive.

Choose questions by the decision you need to make

Before drafting the form, write down what you are prepared to change. For a production review, that could be the preparation pack, the approval sequence, or who needs to attend. For a leadership meeting, choose a decision such as retaining the format or moving routine updates into a written brief.

Meeting evaluation can cover preparation, participation, and accountability, as reflected in BoardSource’s assessment framework. Use those categories to assign questions to the people who can act on them. Ask the meeting owner to approve that assignment before distributing the form.

Apply a simple deletion rule: remove any question whose possible answers would leave your next action unchanged. If you ask whether the agenda was available early enough, be ready to change its release point. If the schedule is fixed, ask which preparation material was missing and name who will supply it.

Define the meeting’s purpose before evaluating whether it achieved that purpose. Use the event purpose statement guide as a planning reference, then write a meeting-level objective such as “confirm the show-flow version authorized for rehearsal.” Put that objective at the top of the survey.

Use this five-question meeting feedback template

Use these questions as a starting set for a production review, planning meeting, or internal debrief. Keep the response labels visible and include an optional comment field beside the closed questions. Treat the answers as input for review, with the production record remaining subject to its normal approval process.

1. How fully did this meeting achieve its stated purpose?

Offer “fully,” “partly,” “not achieved,” and “I could not assess this.” Repeat the stated purpose immediately above the question. When someone selects “partly” or “not achieved,” ask what remains unresolved.

Route this answer to the meeting owner. Ask that person to record whether the next step is another decision session, a written clarification, or closure of the item. Avoid automatically scheduling another meeting.

2. What information did you need earlier to contribute?

Use an optional open-text response. Ask respondents to name the missing document or detail without including confidential content. For a production review, prompt for a file title, version, or approval status where appropriate.

Assign the preparation-pack owner to review these answers. If no information was missing, allow the respondent to skip the question without entering a placeholder.

3. Were you able to raise the concerns relevant to your role?

Offer “yes,” “partly,” “no,” and “no concerns to raise.” Add an optional field asking what prevented participation. Do not require respondents to name another participant.

Send participation issues to the facilitator for review. Route any unresolved production concern separately to the person responsible for that operation, so a facilitation issue does not hold up an operational check.

4. How clear is your next responsibility after this meeting?

Offer “clear and assigned,” “clear but unassigned,” “unclear,” and “no action expected from me.” Ask for the affected task or decision reference when clarification is needed. Avoid asking respondents to reconstruct the whole action list.

Survicate’s meeting survey examples include a question about clarity of post-meeting action points. For this template, distinguish an unclear task from an unassigned task and send each answer to the action-register owner.

5. What single change should we test at the next meeting?

Use an open-text answer and make it optional. Ask for one change to the meeting process, such as circulating the decision brief before the call. Keep requests about live production issues in the clarification route described above.

Slido recommends combining rating questions with open-text feedback. Keep that combination here, and choose the next change based on relevance to the meeting’s purpose and the authority available to implement it.

Adapt the survey for event feedback and hybrid participation

For an attendee-facing event feedback survey, replace internal responsibility questions with questions about the experience promised to attendees. Ask what they came to do, whether they could do it, and what got in their way. Keep the production-team debrief separate from that attendee form.

The University at Buffalo’s post-event question list covers reasons for attending, content satisfaction, location, and event length. Select only the topics that match your event purpose and the decisions still open to you. For a survey for event feedback after a learning session, for example, prioritize content relevance over an unrelated logistics question.

Use these optional replacements as parallel choices, selecting the ones that fit the event:

• “How well did the session address the topic you attended for?” Use a labeled scale and a “did not attend” option.
• “What prevented you from taking part in the activity you selected?” Use optional text and route access-related concerns for individual review.
• “Which part should receive more time at the next event?” Use the actual agenda items as choices.
• “What should we change about arrival or joining instructions?” Use optional text and assign a logistics owner.

For hybrid meetings and events, ask how the respondent participated: in person, remotely, or through a recording. Review the relevant answers within each participation mode before preparing an overall summary. Avoid asking recording viewers to rate their opportunity to contribute live.

SmartSurvey’s meeting template includes technology and participation questions. Split those topics in your own form: ask whether participants could hear the discussion, then ask whether they could contribute when needed. Assign an audio issue to technical review and a turn-taking issue to facilitation review.

Assign meeting follow ups through a response-to-action record

Before sending the survey, create a response-to-action record in your existing task register or spreadsheet. Give the meeting owner responsibility for reviewing new responses at a stated point. Choose that point according to the next operational deadline, and publish it in the invitation.

For each issue selected for action, record the following fields:

• The source response reference and meeting date.
• The affected artifact, including its version where relevant.
• The action owner and required approver.
• The proposed action and due date.
• The closure evidence and next review point.

Keep access to the original response separate from access to the action record where needed. Share only the detail required to resolve the issue. Before promising anonymity, check the form settings and explain who will see raw responses.

A worked production-review pattern

Use this generic production-review pattern to test the process. Set the meeting objective to confirm a rehearsal-ready show flow, then review two sample answer types: positive purpose ratings and a comment that the cue document has no confirmed version. Keep the version concern open until the designated document owner checks it.

Assign that owner to identify the authorized file and ask the designated production approver to confirm its status. Record the clarification in the action register, then issue the approved reference through the established communication route. Do not treat a survey response as authorization to change the cue document.

At the next review, check whether the authorized version was issued and acknowledged through the required process. Close the action against that evidence. Separately decide whether to add a version check to the next meeting’s preparation pack.

For the broader document and approval boundaries, use the event production management guide alongside this record. Keep the survey’s scope limited to collecting feedback and initiating review.

Handle dissent before choosing automation

Use separate review rules for overall experience and unresolved operational concerns. Review experience ratings together to choose process improvements. Review a concern about an unconfirmed approval, an access barrier, or an unclear responsibility individually, regardless of how many respondents raised it.

Set the response action to “verify” until the authorized owner has checked the underlying record. Give the reviewer room to conclude that the issue is already resolved, requires correction, or needs more information. Record that conclusion without turning the survey into a second approval channel.

For recurring meeting feedback, keep the core wording and answer labels stable while testing one process change. If you change a question, record the change and review its answers separately. Keep nonresponses visible in your review notes and leave their meaning unassigned.

Decide whether AI belongs in the process

Start with manual review when the meeting owner can read the responses and maintain the action record reliably. Before adding AI, define a bounded task to test, such as proposing themes with references to the underlying responses. Require a reviewer to check each proposed action before it enters the operational register.

For an AI-assisted design, test whether the system preserves a minority concern, distinguishes a suggestion from an approved action, and restricts access to sensitive comments. Include a failure case in which a response lacks enough context to classify. Require that case to remain unresolved for human review.

Compsia’s operating standard requires system-specific definitions of data, actions, owners, controls, acceptance tests, and operating limits. That standard applies to Compsia’s custom AI production systems, not only to event-industry applications. Event Compsia applies the broader Compsia model to event-company operations; see its production trust and claims boundary. Apply that discipline before authorizing writes to production records. Keep sending messages and changing assigned work outside the initial test unless their approval paths are explicitly defined.

Frequently asked questions

What are some good feedback questions to ask?

Ask how fully the meeting achieved its purpose, what information was missing, and what change to test next. Add a participation question when you need to review whether people could raise relevant concerns. For a production meeting, also ask whether each respondent understands their next responsibility.

What are 5 good survey questions examples?

Use the five questions in this template: purpose achieved, information needed earlier, ability to raise concerns, clarity of next responsibility, and one change to test. Keep the answer options attached to each question. Replace internal responsibility wording when surveying event attendees.

What are the 5 P's of meetings?

For this workflow, use purpose, preparation, participation, process, and progress as a planning checklist. Treat these as this article’s working labels, without assuming every meeting framework uses the same terms. Assign a review question to each label only when you are prepared to act on its answer.

What are the four questions to lead a meeting?

Use these four prompts: What must we decide? What evidence do we need? Who has authority to decide? Who will do what afterward? Put the answers in the meeting brief and update the decision and action records before closing.

Choose the next meeting to test

Select one recurring production or planning meeting with an accountable owner. Publish the five-question form, name the review point, and prepare the response-to-action record before collecting answers. At the review, choose one process change and verify any unresolved production concerns separately.

Compsia designs, builds, launches, and operates custom AI production systems; its scope is not limited to the event industry. Event Compsia is the AI partner for the event industry, applying that broader Compsia model to event-company operations. If your event-company feedback workflow requires a custom AI production system, map an event-company production perimeter before choosing components. Start by identifying the exact result, the authorized actions, and the person who will accept the system.