Collect society event feedback that leads to one improvement

Choose the decision before writing questions

Identify one or two aspects you can realistically improve, such as whether the start time suited attendees, whether newcomers understood the activity or whether the room was easy to find. Write the decision in plain language: 'Should the next session begin earlier?' Then ask only for information that helps answer it. Avoid asking people to rate everything simply because a form makes it easy. If the event's purpose was to introduce a hobby, useful feedback might concern the clarity of the first activity rather than whether attendees liked the poster. Keep the evaluation proportionate to the event and the committee's capacity to act.

Ask about an experience people can describe

Use specific, neutral questions that do not tell respondents what answer you want. 'Which part of the arrival instructions was unclear?' is more useful than asking whether your excellent directions helped. Give room for someone to say a feature was not relevant or they did not use it. Keep optional written responses short and explain the purpose of the feedback. Where anonymity is offered, make sure the collection method actually supports that claim and follow the union's process. Do not request names or personal background information unless there is a clear, approved reason connected to the action you intend to take.

Combine comments with operational observations

Record factual details from the organising team: when the first activity began, whether a queue formed, which materials ran out and how many places were used. Distinguish an observation from an interpretation. 'Three people asked for the room number' is different from concluding that everyone found the publicity confusing. Ask helpers about the part of the event they actually saw rather than treating one person's impression as a complete account. A page in the event notebook can hold these notes. You do not need survey software or specialist equipment to notice a recurring practical problem and test a small change.

Review responses without overstating them

Read the feedback alongside attendance and the way it was collected. People who respond may have different experiences from those who leave without commenting, so avoid presenting a few answers as the view of every member. Group comments by the decision they inform and identify a feasible action. If someone reports a serious personal concern, use the union's appropriate support or reporting route rather than discussing it openly in a committee meeting. Keep the routine event review focused on operations. Where responses conflict, consider whether offering a choice or trialling a change would be more useful than claiming a single universal preference.

Close the loop with a concrete change

Choose an owner and date for one improvement, such as adding an entrance photograph to the next invitation or repeating instructions for late arrivals. Tell members what you learned and what will change without quoting identifiable feedback unless you have permission. Retain or dispose of raw responses according to the union's guidance. At the next event, check whether the change resolved the original issue before adding more questions. This creates a practical cycle of observation and adjustment. The evaluation is worthwhile when it changes an organising decision, not merely when it produces a large number of responses or a polished report.

Your next steps

• Choose the organising decision the feedback should inform.
• Ask a few specific and neutral questions.
• Separate direct observations from interpretations.
• Assign and review one concrete improvement.

Keep planning

• Publish useful access information for a society event
• Manage society event registration and a waiting list
• Communicate a society event change or cancellation clearly
• Sequence society event setup and clearance within the booking