Volunteer Care
How to Know How Your Volunteers Are Actually Doing
You find out how your volunteers are really doing by asking one short question right after they serve, while the morning is still fresh, then reading those answers across every team over time. A single recurring prompt tells you more than a quarterly survey, because it catches the feeling before it fades and shows you when someone goes from energized to flat before they stop signing up.
I learned this the slow way. We used to send a volunteer survey twice a year, a tidy form with rating scales and an open comment box, and almost no one filled it out. The handful who did were our happiest people, the ones who'd have told me they were fine over coffee anyway. The folks I most needed to hear from stayed silent, and by the time their silence registered, a couple of them were already gone.
Why don't volunteer surveys work?
Long surveys fail because they arrive after the moment has passed and ask people to grade their own commitment, which most volunteers are too gracious to do honestly. The response rate stays low, and the people most worn down are the least likely to answer. A short post-serve check-in catches the real feeling while it's fresh, from the people you'd otherwise never hear from.
Think about when a survey lands. It shows up weeks after the Sunday that frustrated someone, framed as a formal request for feedback, and it competes with everything else in a busy person's inbox. By then the specific moment, the check-in line that backed up or the kid who needed extra hands, has blurred into a general sense that things were a little hard. General feelings are easy to wave off. The person tells themselves it was just a rough week and clicks delete.
There's a second problem. Surveys ask people to evaluate, and most of your volunteers don't want to seem like they're complaining about a church they love. So they round up. "How satisfied are you?" gets a 4 out of 5 from someone who's actually running on fumes, because saying otherwise feels disloyal. You get back a page of polite numbers that hide exactly the thing you were trying to find.
What should I ask volunteers after they serve?
Ask one open question they can answer in a single sentence: how did serving go today, and is there anything you need? The open wording matters. It lets a volunteer name what actually happened, a station that felt short-staffed or a moment that meant something, in their own words instead of a rating you then have to interpret.
The instinct is to ask more, because you have more you want to know. Resist it. Every extra field lowers the odds anyone answers at all, and the open box is where the real information lives. A number tells you a 3 became a 2. A sentence tells you "loved it, but we were one person short at the door all morning," which is something you can fix this week.
A few prompts I'd trust, depending on your teams:
- How did this morning go for you? The simplest version, and often the most honest. People will tell you more than you'd expect when the question is plain.
- Anything you need from me before next time? This invites a request without making them feel needy for having one.
- What's one thing that would make serving here better? Use this sparingly. It's great quarterly, too much every week.
The wording is yours. The discipline is keeping it to one question, asking it close to when they served, and reading what comes back as words instead of data to be scored.
How is a post-serve check-in different from a survey?
A post-serve check-in is one question asked in the moment, where a survey is a long form asked after the fact. The check-in rides along with serving itself, so it doesn't feel like homework, and it gives you a running read on each person instead of a snapshot taken twice a year when the moment has long since passed.
The two are easy to confuse because both are technically "asking for feedback." But they behave nothing alike in practice, and the difference shows up in who answers and what they say.
| The twice-a-year survey | The post-serve check-in |
|---|---|
| Arrives weeks after the moment | Lands the same day they served |
| Five to ten questions, rating scales | One open question, one sentence |
| Mostly your happiest people reply | Catches the worn-down people too |
| A snapshot, frozen in time | A trend you can watch move |
| Easy to ignore in a full inbox | Part of serving, not extra work |
| Numbers you have to interpret | Words you can act on |
The right column is the one that tells you something before it's too late to use it. When the same person answers a short prompt every few weeks, you stop reading single replies and start reading the line they draw over time.
How can I tell if a volunteer is about to quit?
Watch their words and their behavior together, and look for the trend rather than any single moment. Answers that shrink from a full sentence to one word, replies that come slower than they used to, sign-up slots they once grabbed early now sitting open. A volunteer almost never announces they're done. They get quieter first, and quieter is something you can notice if you're set up to see it.
This is where reading across teams earns its keep. Your kids director might notice that Marcus has gone a little flat, but she doesn't know he's also on the parking team and the setup crew, where he's pulled back too. Each leader sees a small dip and assumes it's nothing. The full picture, three small dips on the same person in the same month, only exists if someone holds all three rosters side by side. That's the pattern that should pull a name onto your list for a real conversation.
I want to be honest about the limits here. None of this reads someone's heart. You can see that an answer got shorter; you can't see exactly why, and you shouldn't pretend to. What the trend gives you is a reason to reach out, a specific one, before the person steps off the team. If you'd like a deeper take on rising load specifically, I wrote about that in how to spot volunteer burnout, which pairs closely with this.
How do I read volunteer sentiment across teams without it becoming a project?
Keep one running place where every volunteer's recent check-in answers sit together, regardless of which team they served on, and glance at it the same day each week. The work isn't analysis. It's refusing to let a person's feedback stay trapped inside one team's silo. When the answers live in one view, the trend reads itself.
Here's a version you can run with a shared spreadsheet, no software required:
- Make a row per volunteer, not per team. The person is the unit. Someone on three teams still gets one row.
- After each serving date, drop in their one-line answer. A new dated cell each time. Keep the old ones, because the history is the point.
- Skim the rows weekly. You're looking for a line that's changing, sentences getting shorter or flatter, instead of grading any single Sunday.
- Flag anyone whose trend turned down. Two or three replies heading the wrong way is your watch list.
- Pick two or three real conversations. Not a program, just the people the trend pointed you to, reached this week while it still matters.
The reason this stays small is that you're not adding a meeting or a campaign. You're capturing what people already feel, in the moment they feel it, and putting it somewhere a downward line can't hide. For the broader version of catching people before they slip away, keeping people from slipping through the cracks covers the same instinct applied to the whole congregation.
This is the one place I'll mention what I'm building. I made Scout because I wanted that running view to keep itself. Team Pulse asks a volunteer one short prompt after they serve and shows you their answer in their own words, gathered across every team onto one profile, so the trend is already drawn for you instead of waiting in a file you have to remember to open. The manual version above works on its own. Scout is the version that doesn't depend on your memory.
Frequently asked questions
How do I know how my volunteers are actually feeling? Ask one short question right after they serve, while the morning is fresh, instead of sending a quarterly survey. Then read the answers across teams over time, so a person going from energized to flat shows up before they stop signing up. A small, recurring prompt beats a long form nobody opens.
Why don't volunteer surveys work? Long surveys arrive when the moment has passed and ask people to grade their own commitment, which most are too polite to do honestly. Response rates stay low and the people most worn down are the least likely to reply. A one-question post-serve check-in catches the real feeling while it's still fresh.
What should I ask volunteers after they serve? Keep it to one open question they can answer in a sentence: How did serving go today? Anything you need? The open wording lets them name a child who needed extra help, a station that felt short-staffed, or that they loved it, in their own words rather than a number you have to interpret.
How can I tell if a volunteer is about to quit? Watch the trend in their own words and their behavior together. Answers that shrink from a full sentence to one word, replies that arrive later, slots they used to grab early now sitting open. A volunteer rarely announces they're done; they get quieter first, and quieter is something you can notice.
How often should I check in with volunteers? Make the check-in part of serving itself rather than a separate event. A short prompt after each time someone serves gives you a running read without adding a meeting. Reserve longer, sit-down conversations for the people whose answers or patterns tell you something has changed.
Nic Moore is a pastor and the founder of Scout. He built most of Team Pulse after one too many volunteers answered "fine" right up until the Sunday they didn't come back.