How to Find and Keep Event Volunteers

It is 4:30am the morning of the fish fry. The event chair's phone buzzes twice, back to back. First text: one volunteer's kid has a fever, she's out. Second text: nothing — the other person just never responds. Setup starts in 90 minutes. There are now six people doing eight people's jobs, and the person who knows where the extra extension cords are stored is 71 years old and already on his way.

This happens every year. Not because the volunteers don't care. Because nobody ever wrote down what the jobs are.

Why the Same 6 People Do Everything

This is not a personal problem. It is a structural one.

When a club runs on institutional memory instead of written systems, the people who hold that memory become irreplaceable. The event chair knows the setup sequence, knows who to call when the deep fryer doesn't light, knows which parking lot gate stays locked until 7am. Nobody else does, because nobody else was ever told.

That creates a ceiling.

New volunteers show up, don't know what to do, and either stand around feeling useless or get handed the most boring task available. Neither experience brings them back next year. The regulars do everything, get exhausted, and complain that nobody helps — while simultaneously holding all the information that would let someone else help.

The fix is not finding more volunteers. The fix is making the information available so that more people can actually do the work.

Writing Down What You Actually Need: Shift Slots, Not Vague Asks

"We need help at the fish fry" is not a job posting. It is a vague social obligation that people can quietly ignore.

A shift slot is different. A shift slot has:

A specific time: Saturday, 4:00pm–7:00pm
A specific task: "ticket table — collect money, hand out wristbands, manage the line"
A headcount: "we need two people for this slot"
What you need from them: cash box, comfortable shoes, no experience required

When someone sees that, they can picture themselves doing it. They can say yes or no to a real thing, not a vague "help."

Build a simple shift grid for every event. List every job. Break each job into two-to-three hour blocks. Count the bodies you need. That grid is your recruiting target — specific, countable, actionable.

How to Recruit Volunteers Who Aren't Already Members

Your current members are tapped out. You already know that.

The people who will help at your community food drive, your suburban chili cook-off, your annual dinner — they exist. They are in the same community. They just have not been asked in a way that made it easy to say yes.

Family members of existing members are the lowest-hanging fruit. A member's adult kid, spouse, or neighbor who has heard about the fish fry for ten years might actually show up if someone personally asked them to work the ticket table for three hours on a Saturday.

Local high school groups often need service hours. Contact the principal's office or the National Honor Society chapter directly. Have a specific task ready — "we need four students to help with setup on Saturday from 2–5pm" — not just "we'd love student volunteers."

Church and civic groups are already organized and already volunteer. A quick ask to the pastor or group coordinator — "could three or four of your people help us staff the 50/50 raffle table this year?" — works better than any Facebook post.

Neighborhood and community apps like Nextdoor let you post directly to your ZIP code. Short, specific, time-bound asks get responses. "Looking for two people to help with setup at the Riverside Community Center Saturday morning from 9 to noon — coffee provided, no experience needed" will get replies.

The common thread: every ask names a task, a day, and a time. Nothing vague makes the list.

Making the Ask Specific

"Can you help with our fish fry?" almost never results in a commitment.

"Can you work the ticket table this Saturday from 4 to 7pm?" is a question someone can actually answer.

The difference is that the second version removes the mental work required to say yes. The person does not have to figure out what "helping" means, whether they're qualified, or what they're getting into. They know exactly what they're agreeing to.

Write the ask before you make it. Know the specific slot, the specific time, the specific task. If you are asking by text or email, put all three in the message. If you are asking in person, have the same information ready.

When someone hesitates, offer a shorter version. "If Saturday is too long, we also need someone from 4 to 6pm." Giving people a way to do less is better than letting them walk away from a commitment they almost made.

Confirmation and Reminders the Week Before

A volunteer who said yes three weeks ago may or may not still remember.

Life happens. Send a reminder. It does not have to be elaborate. A text the Tuesday before the event — "Hey, just confirming you're still good for the ticket table this Saturday, 4–7pm. Let me know if anything changed." — does two things: it confirms the commitment, and it gives someone a graceful way to tell you early if they cannot make it.

Do the same thing the morning of. Not a guilt trip. A brief check-in: "Morning — we're all set for tonight, setup starts at 3. See you at 4."

This is not nagging. This is event management.

The volunteers who go silent and no-show without warning are usually the ones nobody followed up with. The reminder gives them a natural moment to bow out early, which is far better than finding out at 4:30am.

Day-Of Volunteer Management: Tell People Exactly What to Do

The single most important thing you can do when a volunteer arrives is tell them specifically what their job is.

Not "just help out wherever." Not "float around and see where you're needed." A specific task, a specific location, the name of one person they report to if they have a question.

Write a one-page volunteer sheet for every event. List every job, every slot, every name. Print copies. Hand them out at the start of the shift. Walk new volunteers to their station and introduce them to whoever they're working with.

When someone knows exactly what they're doing and who they're working next to, the event runs. When someone is "floating," they are quietly irrelevant, and irrelevant volunteers do not come back.

Have one person designated as the day-of contact for volunteer questions. Not the event chair — the event chair is managing fifteen other things. A dedicated volunteer coordinator handles questions, fills in for no-shows, and keeps the floor running.

How to Follow Up Afterward

A thank-you that means something is specific.

"Thanks for all your help" means nothing. "Thanks for running the ticket table — we had 200 people through in the first hour and the line never backed up. You made that work" means something. The person now knows what they contributed. That memory sticks.

Send the follow-up within 48 hours. The further out you get, the less it lands.

Text is fine for most volunteers. Email works if you have a larger group. A handwritten card for someone who put in significant time is worth the two minutes it takes.

Do not send a form letter with a merged first name at the top. Those go straight in the trash. Write it like a person wrote it.

If the event raised money toward a goal, tell the volunteers what the outcome was. "We raised $3,400 for the scholarship fund — the most we've ever raised at the fish fry." That closes the loop and gives people a reason to care about whether the next one goes well.

Building a Volunteer List You Actually Own

A Facebook RSVP is not a commitment and it is not your data.

Facebook owns those names. When the algorithm changes, when people stop using Facebook, when your page gets restricted — the list disappears. You cannot email those people. You cannot text them. You have no record they ever said yes to anything.

A signup form on your own website — with a name and email — is yours. You control it. You can export it. You can build a real volunteer contact list that survives platform changes.

Potluck builds that website for your org in 5 minutes. Free to start.

Every event you run should have a simple sign-in sheet or a digital form where volunteers put their name, email, and phone number. After the event, those names go into a spreadsheet or contact list that lives somewhere you control. That list is the asset. The Facebook RSVP is a convenience that expires the moment someone closes the tab.

Treat every event as a list-building opportunity. The volunteer who staffed the 50/50 raffle table at your car show is the most likely person to come back next year — if you can reach them.

Why Some Volunteers Don't Come Back

It is usually one of five things.

They did not know what to do. Nobody told them their job and they spent three hours feeling in the way.
The event was disorganized and stressful. They showed up and nothing was ready, nobody was in charge, and the whole thing felt like chaos.
Nobody thanked them. They gave up a Saturday and the only acknowledgment was a general "thanks everyone" at the end of the night.
They felt like an outsider. The regulars knew each other, had their own rhythms, and the new person was never pulled in.
They were not asked back. This is the most common one. Nobody followed up. The next event came and went with no direct ask.

Before next year, look at who showed up once and did not come back. If you have their contact information, a simple message — "Hey, thanks again for helping at the fish fry last spring. We're doing it again in October — would you be up for working the ticket table again?" — has a high response rate, because they already know what they're agreeing to.

The volunteers who left are not gone forever. Most of them just were not asked again.

The fish fry runs on volunteers. The volunteers come back when they felt useful, knew what they were doing, and someone thanked them. Potluck helps your org look like it has its act together — free →

Looking for more ideas? See the full list: Fundraising Ideas for Small Nonprofits and Community Clubs.