How to make a great volunteer survey (7-step guide)

Volunteer surveys are one of the easiest things to do badly. Send too few and you find out about problems after the people experiencing them have already left. Send too many or ask the wrong questions, and you train your volunteers to ignore you, or worse, to give you the answers they think you want to hear.

This guide is for the coordinator who wants a survey that actually tells them something. Not a vanity satisfaction score for the annual report. Real signal about what’s working, what’s broken, and what the people doing the work would change if they were running things.

Seven steps, opinions about each one, and sample questions you can adapt to your own program. The questions matter, but the thinking behind them matters more. Most volunteer surveys fail at the design stage, not the distribution stage.

1. Start with what you actually want to learn

Before you write a single question, answer two of your own.

What specifically do you want to know that you don’t already know? “Are our volunteers happy” is a vibe, not a question. “Are our Tuesday volunteers staying long enough to recoup the training time we put into them” is a question.

What will you do with the answer? If the answer is “nothing, really, we’d just like to know”, don’t run the survey. Asking volunteers for feedback you can’t or won’t act on is one of the fastest ways to make them stop trusting you. Surveys are an implicit promise. If you can’t keep it, don’t make it.

A useful framing: before you write the questions, write the headline of the action you’d take based on different possible results. If you can’t imagine the action, the question isn’t worth asking.

Most surveys try to do everything at once: satisfaction, recruitment feedback, role fit, training quality, communication, retention signals. The result is usually a 25-question form that fewer people finish, and where the data on each topic is too thin to act on. Pick one or two themes per survey. Run more surveys, each shorter, instead of one giant annual exercise that produces a binder nobody opens.

2. Time the survey to the work, not to the calendar

The most common mistake in volunteer surveys is sending them once a year, in January, to everyone in the database.

By January, the people who were unhappy in May are gone. The people who joined in October don’t have enough context. The events you’re asking about happened three months ago, which is plenty of time for memory to soften the rough edges. You’ll get a polite response from people who still feel warmly enough toward your organisation to fill in a form, and you’ll learn very little.

Better moments to survey: the week after a big event, when the experience is fresh and the rough edges still sting. After someone’s first three shifts, when there’s still time to fix onboarding problems for the next cohort. When someone hasn’t shown up in three months, which is the exit interview you’d otherwise never do. And twice a year for the whole base, in a quieter format, on a topic specific enough to be actionable.

A single annual satisfaction survey is theatre. Multiple short, well-timed surveys is listening.

3. Keep it short. Three good questions beat thirty average ones

Survey length is the single biggest predictor of response rate, and response rate is the single biggest predictor of whether the data is worth anything.

A volunteer survey that takes more than five minutes to complete will lose people. A survey that takes more than ten minutes is essentially asking your volunteers to do free labour to help with your internal reporting.

Three to seven questions is usually the right range. If you can’t fit your survey into that, the goal isn’t focused enough. You’re trying to do two surveys at once, and you should split them.

A short survey doesn’t mean a shallow one. A single open-ended question, well-asked, can produce more useful data than fifteen Likert scales. Length is about discipline, not depth.

4. Write questions that surface honest answers

Most volunteer surveys produce sanitised, polite, useless data because the questions are designed to be answered, not to be honest.

A few principles worth holding to.

Don’t ask leading questions. “How great was our event?” predicts the answer. “How did the event compare to what you were expecting?” doesn’t.

Don’t double-barrel. “Was the training useful and well-organised?” forces volunteers to average two different judgments into one rating. Ask them separately or pick one.

Ask about behaviour, not feelings, where you can. “Are you planning to volunteer with us again in the next three months?” is a stronger retention signal than “How satisfied are you with our program?” People tend to overstate satisfaction and accurately predict their own behaviour.

Give people a real “no” option. Multiple-choice questions that don’t include “neither of these”, “I don’t know”, or “other (please specify)” force volunteers to pick an answer they don’t believe.

Be careful with anonymity. Anonymous surveys get more honest answers on sensitive topics, and worse data overall. You can’t follow up to understand what someone meant, can’t segment by tenure or role, and can’t show that you took action on a specific person’s concern. For small programs (under 30 volunteers), where you mostly know who said what anyway, named surveys with strong confidentiality norms often work better than fully anonymous ones. For sensitive topics (harassment, exit feedback, complaints about specific people), anonymous is the right call.

The goal isn’t a beautiful dataset. It’s an honest conversation, in writing, at scale.

5. The questions worth asking

A short list of question types that consistently produce useful answers, grouped by what stage of the experience you’re surveying.

For new volunteers, after their first few shifts:

How did your first few shifts compare to what you expected when you signed up?
Was there anything in the onboarding that you wish had been clearer?
Who has been your most helpful point of contact so far?
Is there anything you’re not sure how to do that’s affecting your work?

For active volunteers, twice a year:

Are you planning to keep volunteering with us over the next three months?
What would you change about the program if you were running it?
What’s the most useful thing we do? What’s the least useful?
On a scale of 1 to 10, how likely would you be to recommend volunteering with us to a friend? (Volunteer NPS: the single most useful metric for a program’s health)

For volunteers who’ve drifted away:

Was there a specific reason you stopped, or did it just happen?
Is there anything we could have done that would have kept you involved?
Would you consider coming back if circumstances changed?

For volunteers after a specific event or campaign:

What worked best about how this was organised?
What didn’t work?
If we ran this again, what would you change first?

A few of these in any single survey is plenty. Pick three or four that align with what you decided in step one.

The question most coordinators forget to ask, and the one that produces the most actionable feedback, is some version of: “What would you change about this program if you were running it?” It invites volunteers to think like owners rather than rate things as consumers. The answers are nearly always specific and nearly always usable.

6. Distribute, follow up, and respect the people you’re surveying

A survey isn’t done when you send it. Response rate is everything, and the difference between a 15% and a 60% response rate is mostly about how the survey is introduced and followed up on.

What consistently helps: send from a real person, not a generic info@ inbox. Tell volunteers up front why you’re asking, what you’ll do with the answers, and how long it takes. Give a clear deadline (one to two weeks is plenty, more drags it out). Send one reminder, no more. For longer-tenure volunteers, a personal message (“I’d really value your perspective on this”) consistently beats a mass send.

What to avoid: don’t use survey invitations as recruitment marketing or fundraising. Mixing fundraising into a feedback request makes it look like the survey is for you, not them. Don’t offer incentives that distort the response pool. A small thank-you like a coffee voucher or an entry in a draw is fine. A meaningful financial incentive will get you responses from people who want the incentive, not people who care about the program. And don’t send mass surveys to people who’ve only volunteered once or are still onboarding. You’ll get noise. Wait until you’ve got something to ask about.

7. Act on what you heard, then tell volunteers what changed

This is the step where most volunteer survey efforts fall apart. You collect the data, you put it in a slide deck, you mention it in a board meeting, and then nothing visible happens. Volunteers see the next survey land in their inbox a year later and think, with some justification, that the last one was a waste of their time.

The fix is simple in concept and uncomfortable in practice: pick a small number of things to change, change them, and tell volunteers about it.

A useful pattern. Read the responses within a week of the survey closing, while it’s still fresh and you still care. Pick one to three changes you’ll actually make, ideally things you can implement in the next month. Communicate back to volunteers within two or three weeks: here’s what we heard, here’s what we’re going to do about it, here’s what we’re not going to change and why. Six months later, report on whether the changes worked.

The “what we’re not going to change and why” is as important as the change itself. Volunteers don’t expect you to do everything they suggest. They do expect you to take their input seriously enough to engage with it honestly. A short explanation of why a popular suggestion isn’t being adopted is far more respectful than silence.

When volunteers see their feedback turning into visible action, they participate in future surveys at much higher rates and they refer others to your program. The survey stops being an obligation and starts being a sign that the organisation actually listens.

Frequently asked questions

How often should you survey volunteers?

More often than once a year, in shorter forms. Annual mega-surveys produce thin data and ask people to remember experiences from months ago. Better to run a short post-event survey after big activities, a check-in survey for new volunteers after their first three shifts, and a twice-yearly retention pulse for active volunteers. Each one short, each one focused.

What’s the ideal length for a volunteer survey?

Three to seven questions. Anything longer loses people. If you can’t fit your goals into that range, you’re trying to do two surveys at once and should split them. Length is about discipline, not lack of depth. A single well-asked open-ended question can produce more useful insight than fifteen Likert scales.

Should volunteer surveys be anonymous?

It depends on the topic and the size of your program. Sensitive topics (harassment, exit feedback, complaints) should be anonymous. General feedback in small programs (under 30 volunteers) often produces better data when named, because you can follow up for context and show action on specific concerns. Whatever you choose, be explicit about it on the form. Surprise anonymity, in either direction, erodes trust.

What questions should I ask in a volunteer satisfaction survey?

The single most useful question is the volunteer NPS: “On a scale of 1 to 10, how likely would you be to recommend volunteering with us to a friend?” It correlates with retention and produces a number you can track over time. Beyond that, ask about specific behaviours (are you planning to keep volunteering), specific moments (how was your first shift), and one open-ended question on what they’d change if they ran the program.

How do I get more volunteers to respond to surveys?

Send from a real person, tell them why you’re asking and what you’ll do with the answers, keep the survey short, give a clear deadline, and send one reminder. The bigger lever, though, is what happened with previous surveys. If volunteers saw real changes come from the last one, they’ll respond to the next one. If nothing happened, they won’t.

What’s the best tool for sending a volunteer survey?

Any free form tool (Google Forms, Microsoft Forms, Typeform’s free tier) does the job for small programs. The right answer is whichever one lets you send a clean survey, see results clearly, and import or reference responses in the tool where you actually manage your volunteers. If you’re using a volunteer management app, keep the responses connected to volunteer profiles so you can act on them in context rather than spreadsheet exile.

How long does it take to design a good volunteer survey?

Less time than you’d think, if you’ve done the thinking up front. Once you’re clear on what you want to learn and what you’ll do with the answers, writing three to seven good questions takes an hour. The real work isn’t the survey design. It’s deciding which conversation you actually want to have with your volunteers, and committing to acting on what they tell you.

Ready to act on what your volunteers are telling you?

Volunteer surveys are only the start. The real work is everything that happens after: adjusting roles, fixing onboarding, restructuring communication, showing people their input mattered.

Zelos is built for the day-to-day of running a program that actually responds to feedback. Post tasks, organise shifts, message your team through built-in channels, and keep volunteer information in one place so you can act on what you hear. Unlimited volunteers on every plan, no per-person fees, set up in an hour.

Listen, adjust, build. That’s the work.