Event survey questions: a practical guide and question bank

You’ll find a practical question bank you can copy and adapt for both pre-event and post-event surveys, tips on why and how to craft your event surveys, and some notes on how to build the whole thing into your workflow without adding a mountain of admin.

There’s also a template example at the end for company offsites: you can check it out if that it the kind of event you are planning for, or just to have a real-world example of event surveys in action.

If you want to go deeper into survey design best practices, including discussions on question bias, anonymity, inclusion, feedback fatigue, check out this post on pre- and post-training survey questions, which covers all of that in detail. Here we’ll focus on what’s specific to events.

What is an event survey?

An event survey is a short questionnaire sent to participants before or after a gathering, such as a company offsite, a team day, a conference, a leadership retreat, a community event. Its job is to help the organizer understand who is coming and what they need (pre-event), and to capture what participants experienced and what could be improved (post-event).

A pre-event survey is sent in the days or weeks before the gathering. It collects logistics information, helps you anticipate needs, and, when done well, contributes to building a sense of connection and intentionality before anyone has arrived.

A post-event survey is sent anytime from right at the end of the event to a few days later. It captures immediate reactions, identifies what worked and what didn’t, and begins to document the impact of the event on participants.

Together, they give you a before-and-after picture that’s genuinely useful: for improving future events, for reporting back to stakeholders, and for making participants feel their experience was seen and valued.

Why event surveys matter (and why they get skipped)

I often work as an independent freelance facilitator for established organizations, which gives me a front-row seat to how differently companies approach this. When it comes to event surveys, I must honestly admit that I’ve mostly encountered two types: the organization where a survey is mandatory after every event (and that is the only rationale for running it: it’s mandatory), and the one where the matter is more or less completely ignored. The good news is: that’s a lot of room for improvement.

A story from the first camp. I was once told, as an external facilitator, that I couldn’t contribute to the survey design: the organization had a copy-paste template it sent after every event, and that was that. Fair enough, in principle. But when I was eventually sent a summary of the responses, I discovered there was no useful information in there for me, as the main facilitator, at all.

All 250 attendees had been sent a quick questionnaire. One question was asking for a general approval of the event, “give us 5 stars” mode. Another was about the food. None were about the facilitation, or what participants were taking away. From my point of view, it was a missed opportunity: the event had happened, people had opinions, and we had no way to capture any of it in a useful form.

When surveys are treated as a formality rather than a tool, they are run, some information gets collected, and they give everyone the reassuring sense that feedback was gathered, without actually telling you much.

The reasons event surveys get neglected are familiar. Time pressure is the obvious one: when you’re deep in logistics, survey design feels like a nice-to-have. Unclear ownership is another, especially for larger events where multiple people are involved in planning. And let’s admit that a main reason surveys are badly designed, or not sent out at all, is fear of what the results might reveal. But without that feedback, good or bad, how can we become learning organizations?

Events are often significant investments of time, money, and people’s attention. A two-day company offsite might involve travel, accommodation, and a day or more of work time for everyone present. Sending a five-question survey at the end is one of the cheapest and most direct ways to start learning whether the investment was worth it, and what to change next.

It also signals something to participants: that their experience matters beyond the event itself. As long, that is, as someone will actually read their answers and do something with them.

What’s different about event surveys (compared to training surveys)

If you’ve worked with training surveys before, most of what you know applies here. But there are a few differences worth naming.

Events are often more logistically complex. A pre-event survey for a two-day offsite needs to cover dietary requirements, travel constraints, accessibility needs, and sometimes accommodation preferences. A pre-training survey rarely has to go that far.

The goals of an event are often less measurable. A training program usually has defined learning objectives. An offsite might be aiming for “better alignment,” “renewed motivation,” or “stronger relationships across teams.” These are things that are real and important but harder to pin down. This means post-event survey questions need to be more open-ended and exploratory, rather than measuring a specific shift.

Participants come with different roles and expectations. At a company event, you might have senior leaders, new joiners, and long-tenured team members all in the same room. A pre-event survey helps you understand that range before you’re standing in front of it.

The post-event window is short. People return from an event and immediately re-enter their regular work patterns. Response rates drop fast. Sending your post-event survey within 24 hours or, better, building a few minutes at the end of the event to complete it together, makes a real difference.

How to create an event survey

Building a good event survey doesn’t require a lot of time, but it does require a little intention. Here’s a simple process to follow, whether you’re starting from scratch or adapting a template.

Start with what you actually need to know

Before you open a form builder, sit with one question: what decisions will this survey inform? For a pre-event survey, the answer might be logistical (who has dietary requirements, who needs accessibility support) or design-related (what do people need from this time together). For a post-event survey, it might be about quality (what worked, what didn’t) or impact (did anything shift for participants).

Write down two or three things you genuinely need to know, and let those drive your question choices. If a question doesn’t connect to one of them, it probably doesn’t belong in the survey.

Choose your questions carefully

Once you know what you’re after, pick questions that will actually get you there. A few principles:

• Ask one thing at a time. “Was the event useful and well-organized?” is two questions. Split them, or you won’t know which one people are answering.
• Match the format to the information you need. Rating scales are fast to complete and easy to compare across responses. Open questions take more effort but give you texture: the why behind the numbers. A good survey usually has both.
• Keep some questions optional. If you are worried that people will click away if they see open questions (and that’s a fair concern), make most questions optional.
• Include at least one open question. No matter how well you anticipate what people might want to say, someone will have something useful that your closed questions didn’t capture. An “anything else you’d like to share?” at the end costs nothing and occasionally surfaces something important.
• Let the event’s personality come through. A survey for a strategy offsite and a survey for a team away day can ask similar things in very different ways. “Please rate the overall quality of the event,” and “How was the week for you?” are after the same information, but one fits a formal leadership retreat and the other fits a team that uses first names and eats lunch together. Match the language and tone to the event itself, and people will engage with it more naturally.
• Be specific enough to be useful. “How was the event?” will get you vague answers. “What would you change about the program structure?” will get you something you can act on.

Keep it short

Survey length is one of the biggest predictors of response rate. For most events, five to eight questions is enough. If you’re struggling to cut, ask yourself: is this question genuinely useful, or just nice to have? Nice-to-have questions can wait for a future event.

For a 30-day follow-up, three to five questions is plenty. People are further from the experience and have less reason to spend time on a long form: respect that.

Think about tone

The survey is part of the participant experience. A form that feels cold or bureaucratic sends a signal about how the organization relates to its people. One that feels warm, clear, and considerate sends a different one. Read your questions out loud before you send them. If they sound like they were written by a compliance team, rewrite them.

For internal team events especially, a conversational tone tends to get more honest responses than formal language. People answer differently when they feel like they’re talking to a colleague rather than filling in a report.

A note on inclusion and privacy

A few things are worth pausing on before you hit send. If your survey asks about medical needs, accessibility requirements, or anything that touches on personal identity or circumstance, make sure sensitive questions are clearly optional and that you explain briefly why you’re asking. People are more willing to share when they understand the purpose.

For events with a mixed or international audience, watch for language that assumes a shared cultural reference, a particular kind of working environment, or a specific organizational hierarchy. A question like “will your manager support you in applying what you learned?” doesn’t translate well to flat organizations, matrix structures, or events where participants aren’t employees at all.

On anonymity: for post-event surveys in particular, especially where you’re asking for candid feedback on facilitation or leadership, consider whether named responses will actually get you honest answers. For a deeper look at all of this—bias, anonymity, inclusive question design—check out this post on pre- and post-training survey questions, which covers it in full.

Decide when and how to share your survey

Timing matters more than most people realize.

For pre-event surveys, send one to two weeks before the event. Early enough that you can actually do something with the responses, like adjust the program, flag a logistics issue, brief a co-facilitator, but not so far out that people forget they filled it in.

For post-event surveys, the closer to the event the better. Within 24 hours is the target. Response rates drop significantly after that, and the quality of open-ended answers tends to drop too, as the experience fades. One of the most reliable ways to get a near-complete response rate is to build five minutes into the closing of the event itself to fill it out together, before people have left the room.

Think about the channel too. Email works, but if your team lives in Slack or another messaging tool, sending the link there might get faster uptake. And always check that your survey works well on mobile: a significant proportion of people will open it on their phone.

I hope you now feel equipped to prepare your next event survey. If you’d like some inspiration on what to ask, or if you are here to copy-paste some questions to begin with, here is a question bank:

Pre-event survey question bank

Pre-event surveys have two distinct jobs: collecting the practical information you need to run a smooth event, and helping participants arrive feeling prepared and engaged. Here are questions for both.

Questions for logistics

These are the non-negotiables. They help you anticipate needs and avoid surprises on the day.

• What is your dietary preference? (e.g. vegetarian, vegan, omnivore)
• Do you have any food allergies or intolerances we should know about?
• Do you have any accessibility needs we should take into account when planning the event?
• Are there any scheduling constraints on your side we should be aware of? (e.g. need to leave by a certain time, can’t attend a specific session)
• What is your current role and team?
• How long have you been with the organization?
• Will you need accommodation? If so, do you have any preferences or requirements?
• How will you be traveling to the event? (Useful for coordinating arrivals and shared transport)
• Is there anything else you’d like us to know before the event?

That last question is always worth including. In my experience, most people leave it blank, but the ones who write something in have genuinely useful things to say, from a logistical need you hadn’t thought of to a heads-up about something going on in their team.

Questions to help participants prepare

These questions do something slightly different: they prime people for the event. A good pre-event survey signals, in tone, style, and content, the beginning of the experience itself. When you ask people what they’re hoping to get out of a day together, you’ve already started the conversation.

• What are you most looking forward to about this event?
• What would make this event feel like a good use of your time?
• Is there a topic or question you’d really like the group to address during our time together?
• What’s one thing you’d like to leave the event having figured out, decided, or reconnected with?
• Is there anything you’re coming in with that might affect your participation? (e.g. a current project deadline, a team situation, an open question)

A couple of years ago, I was the lead facilitator for a two-day offsite for a large cooperative working in the humanitarian space. My client’s brief had been mostly about skill sharing and training, so although there was spaciousness in the program, it was packed: activities, sessions, plenty of opportunities for the thirty-or-so participants to learn together.

It was reading the pre-event survey responses that made me realize the client had somewhat underestimated (or chosen to gloss over?) how tired most staff members were. Working in the humanitarian sector every day is genuinely hard, and the risk of burnout is high. Response after response came in saying the same thing: people were looking forward to the offsite to relax, decompress, and connect with colleagues on a deeper level. As I read through them, I could almost see pieces of my agenda drifting away.

We still got a lot done. But I built in longer buffers, a journaling section, walk-and-talk moments, and time in nature. Would I have adjusted on the fly if I’d arrived without that information? Probably. But having it in advance meant I could make deliberate choices rather than reactive ones, serving the group’s actual needs rather than the brief I’d been handed and, maybe most importantly, I had data to back up my choices should the boss complain (incidentally, he didn’t).

Post-event survey question bank

Post-event surveys need to move quickly: send within 24 hours, keep it short, and make it easy to fill in from a phone. The goal is honest, useful feedback while the experience is still fresh, not a comprehensive evaluation that takes twenty minutes to complete.

Questions to help improve future events

These are your quality check. They tell you whether the event worked as designed, and where to focus your energy next time. Keep this section short and action-oriented: you want answers you can actually do something with.

• How would you rate the overall event? (Scale: 1–5)
• Was the event well-paced? (Too slow / About right / Too fast)
• What worked particularly well?
• What would you change or improve for next time?
• How would you describe the event in three words?

That last question is one of my favorites. It captures mood and atmosphere in a way that longer questions don’t, and the results make for a good wordcloud visual to share with the organizing team or leadership.

Questions on impact

These are the questions most event surveys skip, but I recommend asking at least one of them. Logistics and quality feedback tell you how the event ran. Impact questions start to tell you whether it mattered or, in other words, whether anything shifted in how people think, feel, or relate to each other and the organization. They tend to produce more open, reflective answers, so give people room to write.

• Did the event achieve what you hoped it would?
• What’s one thing you’re taking away from this event?
• Has anything shifted for you, in terms of relationships, thinking, or priorities, as a result of this event?
• Is there something you intend to do differently after this event?
• How connected do you feel to the team/organization after this event, compared to before? (Scale: much less connected – much more connected)

Checking in 30 days later

For events with a specific intention behind them, such as a strategy offsite, a team reset, a leadership retreat, a short follow-up survey a month later can tell you something a post-event survey can’t: whether anything actually changed.

This doesn’t need to be long. Three to five questions sent 30 days out, while people still remember the event, is enough to get a meaningful signal.

• Has anything changed in how you work or think as a result of the event?
• Have you had the opportunity to act on anything that came out of the event? If yes, how did it go? If no, what got in the way?
• How connected do you feel to the team/organization now, compared to right after the event?
• Is there anything you’d want to do differently at the next event?

Set a calendar reminder the moment the event ends, or this won’t happen.

A ready-to-use template for company offsites

If you’re planning a company offsite and want a ready-made starting point, SessionLab has an offsite template you can open, copy, and adapt directly. It includes a suggested agenda structure as well as pre- and post-event survey forms you can customize to your context.

In it you will find:

• Detailed agenda plans for every day of the offsite;
• A checklist to help you prepare workshops and logistics;
• A pre-event survey example;
• A post-event survey, ready to copy and send out;
• A quick 30-day pulse check for impact assessment.

How SessionLab takes the stress out of event surveys

The practical barrier to running event surveys is often the friction of doing it when you’re already juggling everything else. That’s what SessionLab’s Forms are designed to address.

When you’re building your event in SessionLab, you can add a Form directly to the same session, pulling from a set of ready-made templates. A few that are particularly useful for events:

• Participant questionnaire. Covers logistics needs and key information about participants: a solid starting point for any pre-event survey.
• Workshop feedback. A post-session form covering overall experience, what worked, and key takeaways. Easily adapted for events.
• Meeting retrospective. Useful for team events where you want structured reflection on how the time together went.

What makes this different from using a standalone survey tool is integration. Your event agenda, your pre-event form, your post-event feedback, and any follow-up notes all live in the same place. You’re not switching between tools or hunting for which folder the results ended up in.

If you’re running the same kind of event regularly, such as quarterly offsites, annual retreats, or recurring team days, you can save your customized survey as a reusable template and pull it into future sessions with one click. Over time, you also start to build comparable data across events, which makes it much easier to spot patterns and show the value of what you’re doing.

For a full walkthrough of how Forms works in SessionLab, the help center has everything you need.

How event surveys help us with our team retreats

You should now have all you need to feel confident about creating your next event survey. In closing, I’ll share a story of how the process of diligently creating, populating, and analysing post-event surveys helps us here at SessionLab.

We are a fully remote team of thirteen people spread across Europe. Every six months we gather for a week-long team retreat: you can see an offsite template based on how we organize our days together here. In the week after each retreat, we all take time to fill out a survey covering everything from food and accommodation to the individual parts of the program.

That data is interesting to read in the moment, but its real value shows up a few months later, when it’s time to start planning the next retreat.

Reading through responses, event after event, has let us build the kind of offsite that actually works for this team. We learned early on that there wasn’t enough room in the program for people to unwind, call their families, or just have some personal time, so we added it.

We also found that while some people thrive with open space and a flexible agenda, others prefer to arrive knowing exactly what’s expected of them, so we now offer both, encouraging people to prepare a session in advance if that helps, or to show up and improvise if they’d rather. None of this came from guesswork. It came from asking, listening, and taking the answers seriously. I hope this article helps you do the same! If you’ve got more questions, or survey stories to share, consider joining our friendly community and getting peer-to-peer feedback there.

Deborah Rim Moiso Facilitation Content Writer

Deborah Rim Moiso is an Endorsed Facilitator with the IAF – International Association of Facilitators and former co-chair of the Italian IAF Chapter.

She is the author of a manual and deck of cards on facilitation available in Italian (Facilitiamoci!). Deborah has been working with groups since 2009 in the fields of innovation in education, citizen participation, and environmental conflicts.