Pre-Event Survey: Choose Topics for Your Event Programme
A pre-event survey can help you decide which topics and formats deserve space in the programme. To make the answers useful, first define what you can still change, ask registrants what they hope to work on, and keep those expectations separate from availability and practical needs. Responses inform the decision; they do not make it for the organizer, and they do not automatically represent every attendee.
Define the programme decision first
Before writing a question, complete this sentence: “The answers may still help us choose…” The decision might concern topics, depth, session format, or the balance between talks and workshops. Do not ask registrants to rank choices that have already been fixed.
Set out the programme’s constraints too. Which slots are still open? Which topics are essential? Which formats can you actually deliver? This prevents you from collecting expectations you cannot address.
A study presented around the 2014 CHI conference illustrates one way to bring attendee preferences into scheduling. Participants could review accepted papers and mark preferences before sessions and the schedule were announced. The authors describe those responses as complementary to author input and as providing additional scheduling alternatives in that particular case. It was a recommendation tool built around that conference’s accepted papers, not evidence that a generic survey improves every event. Read the study on community-informed CHI 2014 scheduling.
Separate topic interest from availability
Someone may want to attend a session but be unavailable at the proposed time. Another person may be free without being interested in the topic. If these answers are mixed together, you may mistake a scheduling problem for a lack of content interest.
Use two clearly separate sections, or two separate surveys:
- Programme: Which topics, questions, or formats would be useful?
- Practical arrangements: Which times work, what access arrangements are needed, or what information should be shared?
The practical section helps you organise the event. It does not measure interest in a topic. If timing affects the programme, keep that constraint in a separate column when you make the decision. The articles on constraints versus preferences and the World Café method cover related situations, but the first concerns exceptions in group composition and the second a specific facilitation format. This article is about topics for the whole programme.
Ask about expectations without closing off answers
A list of topics lets you compare options, but it can reveal only what the organizer thought to include. A free-text response may surface a missing question or a different expectation. It does not, by itself, guarantee a complete, valid, or representative answer.
Start with an open question that does not suggest a preferred answer: “What question would you like to be better able to address after this event?” Then, if you already have a list of possible topics, ask which would be useful and include “another topic”, “none of these”, or “no preference”. Do not force everyone to select a theme.
You might also ask which format would make the topic usable: a short talk, case study, practical workshop, guided discussion, or no preferred format. Do not present all of these as equivalent if you can deliver only some of them. In that case, list only the formats you can realistically offer.
Write each question to support one specific decision. “What do you need?” can mix content, timing, accessibility, and networking expectations. It is clearer to ask separately: “What situation would you like to work through?” and then “Which format would help you address it?” For more on question wording, see the guide to open-ended questions and common survey-bias traps.
A fictional pre-event survey example
The following example is entirely fictional. An association is preparing a day about local collaboration. The team can still change the topics of two workshops, but the venue, date, and times are fixed.
Open question: “What situation involving collaboration would you like to handle better after this event?”
Comparison question: “Which of these proposed topics would be useful to you?” The list includes only topics the team can deliver, plus “another topic”, “none”, and “no preference”.
Format question: “Which format would suit this topic best?” The options distinguish a talk, case study, small-group exercise, and guided discussion.
Follow-up: “Is there a question or point of view missing from this list?”
Separate availability section: “If a session is offered in the morning or afternoon, when will you be able to attend?” This answer helps set the timetable; it does not rank interest in the topics.
In this fictional scenario, several free-text answers ask for examples of collaboration between associations, while others focus on how roles are divided. The team does not automatically turn these into two workshops. It checks which requests fit the available topics, notes the different needs, and decides whether one workshop can address both or whether one point should be set aside. These responses say nothing about the people who did not reply.
Read the responses before deciding the programme
Before counting selections, record who was invited, when the survey was open, and who actually replied. If you do not have a complete response frame, describe the results as “expectations expressed by respondents”, not as the view of all registrants. No response is not a refusal, and silence does not prove a lack of interest.
A small grid helps keep each step visible:
| Topic or proposal | Responses that mention it | Different needs or limits | Organizer’s decision |
|---|---|---|---|
| Examples of local collaboration | Free-text responses asking for a concrete case | Some requests are more about roles | Use a case in a workshop; keep roles as a discussion question |
| Division of roles | Responses asking for clearer responsibilities | The situations described are not all comparable | Add a short segment if the programme allows |
This grid is fictional too. In a real analysis, keep the original wording behind your groupings. Record what recurs, what differs, and what you cannot interpret separately. Do not squeeze an unexpected response into the nearest category just to complete a table. If there are many free-text answers, reviewing themes alongside source excerpts can help the team keep the nuance visible; it does not choose the topics or the programme.
Explain the decision and its limits
After making the decision, briefly explain what you selected, what you set aside, and why. Link each choice to evidence you actually observed and to the programme constraints. If an expectation was not selected, do not imply that it was rare or absent unless you can establish that.
A pre-event survey is one input among others. Responses reflect the people who replied, the wording of the questions, the list of suggested topics, and the timing of collection. They do not predict post-event satisfaction or actual attendance at each session. Evaluating the experience requires a separate post-event feedback process. The post-event survey questions guide offers an adaptable attendee-feedback template.
To plan the next edition using feedback on each talk, the conference session evaluation links responses to content actually attended and an explicit response base.
For a seminar, preview the participant expectations and goals questionnaire. Adapt the topics, formats, and constraints to your event. Responses inform the programme; they do not predict registrations or session attendance.
So the useful question is not only “which topic received the most selections?” It is “what expectations did we observe, what limits remain visible, and which decision can we explain?”
