How to work with volunteers (6 principles)

Working with volunteers is one of those things that looks straightforward and turns out to be subtle. Most new coordinators arrive expecting it to feel like managing staff, or like working with customers, or like cultivating donors. It’s none of those things, and the moments where the difference matters tend to come up unexpectedly.

This guide is for the coordinator, staff member, or executive director at a nonprofit, community group, or grassroots organisation who works with volunteers regularly. Whether you’ve just been handed the role or you’ve been doing it for years and want to think about it more clearly, the six principles below are the ones that actually matter.

Take what’s useful. Argue with the rest.

1. Understand what relationship you’re actually in

Most of the confusion about working with volunteers comes from the wrong mental model. New coordinators tend to default to one of three frames, and each one gets the work subtly wrong.

Volunteers as free staff. The most common mistake. You’d never ask a staff member to give up a weekend with no notice, accept work without clear scope, or take instructions from someone they don’t know. Treating volunteers this way produces short-term compliance and long-term turnover. Volunteers always have the option to leave, and the ones worth keeping will exercise it.

Volunteers as customers. The opposite mistake. Treating volunteers as people to be pleased and accommodated to the point of giving them whatever they want erodes the program. Volunteers came because they wanted to contribute to something meaningful, not because they wanted to be served. Over-accommodation actually decreases satisfaction over time.

Volunteers as donors who give time. Better than the first two, but incomplete. There’s truth in this. Volunteers do give a form of resource, and the relationship requires similar stewardship. But the donor frame can make the relationship feel transactional, which loses what’s special about volunteer communities.

The most useful frame: volunteers are community members who happen to be doing work. They’re there for specific reasons that matter to them: connection to the mission, a problem they want to help solve, a community they want to be part of, skills they want to use or develop, a debt to someone or something the organisation supports. These motivations are why they came, and they’re what keep them coming back.

The relationship is reciprocal but not transactional. They give time and effort. You give clarity, purpose, recognition, and useful experience. The reciprocity has to be active and visible, but it’s not a contract. It’s an ongoing exchange between people who share a common cause.

This matters because it shapes how you respond when things get hard. When a long-tenured volunteer is underperforming, the staff frame says have a performance conversation. The customer frame says keep them happy at all costs. The community-member frame says have an honest conversation, person to person, about what’s going on. The third one is the right answer almost every time.

2. Design the work so volunteers can succeed without you

The single biggest avoidable problem in volunteer management is creating roles that require the coordinator’s involvement to function. When a volunteer can’t complete a task without your specific input, the program’s capacity is permanently capped by your availability, and you become the bottleneck for everything.

Good roles are designed for autonomous execution. A volunteer should be able to look at the role description, understand what to do, do it, and know whether they’ve done it well, all without needing to ask. This isn’t always possible, but most roles get closer to it than coordinators realise.

A useful test: write the role description as if you’ll never speak to the volunteer again. What information would they need? What decisions would they need to make on their own? What should they do when something unexpected comes up? Designing for this clarity from the start is much easier than trying to retrofit it later.

A “Saturday morning shop assistant” role description, written this way, might read: “Open the shop at 9 am using the keys in the lockbox (code in your welcome pack). Set up the till using the provided checklist. Greet customers and process sales. At 1 pm, count the till, complete the closing sheet, lock up. If a customer asks for something not on the shelf, take their details and tell them we’ll be in touch by Wednesday. If something else comes up, text the number on your welcome card.” That’s a role someone can run without you. Specific times, specific tools, a fallback for the most common unexpected situation, a clear escalation path.

If you’re starting a new program from scratch, spend more time on role design than on recruitment. A specific, well-designed role attracts the right people without you having to find them. A vague role attracts confused inquiries and no-shows even after extensive recruitment effort.

3. Spend most of your effort on a volunteer’s first few hours

The first hour a volunteer spends actually doing the work shapes the entire relationship. Programs that handle this carefully see retention curves that look completely different from programs that don’t, often with no other changes to recruitment or training.

What the first hour needs to deliver: a real welcome from a named person, a clear sense of what they’ll be doing and why it matters, someone to ask when they don’t know what’s happening, enough success that they leave feeling capable, and a specific invitation to come back.

Most failures in this hour are operational rather than relational. The volunteer arrives and the coordinator is dealing with a different crisis. The buddy who was supposed to show them around called in sick. The task isn’t quite ready. The closing instructions aren’t where they were supposed to be. Each of these is a small thing on its own. Each one tells the new volunteer the organisation isn’t quite ready for them, which is the opposite of the message you want to send in their first hour.

The fix isn’t more training documentation. It’s protected time and protected attention. The coordinator’s first hour with any new volunteer should be on the calendar in advance, treated as undivided, and structured around the new person rather than fitted into whatever else is happening that day. This is one of the few moments where being slightly over-prepared pays for itself for years.

There’s also a smaller version of this principle that applies every time a volunteer starts a new role or returns from a break. The first hour back is where you can reset the relationship, recommit to what they need, and avoid the slow drift that ends most volunteer tenures. Treat it accordingly.

4. Communicate at the cadence of the work, not your anxiety

The single most overcommunicated channel in volunteer management is the “we miss you, please come back” message to lapsed volunteers. The single most undercommunicated is “here’s exactly what’s happening on your shift this week.”

Both errors come from the same source: coordinators communicate based on their own emotional state about the program rather than based on what volunteers need to know to do the work. The fix is calibration.

Volunteers actively engaged in roles need shift reminders, clear logistics for upcoming work, schedule changes, and operational updates. Frequency depends on activity. A weekly volunteer needs less general communication than an event volunteer in the lead-up to an event.

Volunteers between shifts or roles need occasional updates that they’re still part of the community, news about the organisation’s work, and invitations to relevant opportunities. Monthly is usually enough.

Volunteers who’ve drifted away need an honest, single check-in. Not a campaign. Not a “we miss you” series. One message asking whether they want to stay on the list or leave it, with a graceful exit if they choose. Programs that respect the second answer get the first one more often than they expect.

What to avoid: organisation-wide newsletters that mix fundraising appeals with operational updates, mass messages addressed to “Dear Volunteer,” and any communication where the implicit message is “we want something from you” rather than “here’s what you need to know.”

5. Recognise specifically, redirect honestly

Most discussions of volunteer recognition cover the same ground: thank people genuinely, celebrate milestones, share credit publicly. All true. The harder, less-covered side is the redirect: knowing when to have a difficult conversation, and how.

Three situations come up regularly.

Volunteers in roles that don’t fit them. Sometimes the person is keen but the work isn’t right. Most coordinators avoid this conversation for months, hoping it’ll self-resolve, while the volunteer continues to underperform and lose confidence. A direct, kind conversation about whether there’s a better-fit role does more good than another month of hoping.

Volunteers whose behaviour affects others. Someone who consistently arrives late, talks over others, or doesn’t follow basic policies. The cost of not addressing this is the volunteers who quietly leave because of it. The fix is a specific, factual conversation about the behaviour and what you need to be different, with a clear next step if it doesn’t change.

Volunteers who’ve outgrown their role. A volunteer who’s been doing the same task competently for two years is usually being underused. The recognition they need isn’t another thank-you. It’s an invitation to do more, lead, mentor, or shape the program. Not offering this is its own kind of failure to recognise.

The principle that holds across all three: honest conversations, conducted person to person and respectfully, are part of recognition. They communicate that you take the volunteer seriously enough to engage with them as an adult who can handle direct information. The discomfort of having the conversation is much smaller than the cost of avoiding it.

6. Let the volunteer relationship change over time

Volunteer programs that last are programs where the relationship between the organisation and its volunteers evolves. A volunteer who joined two years ago shouldn’t be in exactly the same role today, communicated with in the same way, and recognised through the same channels. Their relationship to the organisation has grown. Volunteer engagement should grow with it.

The strongest indicator that you’re doing this well: your most committed volunteers eventually take on responsibilities you would have done yourself. They train new volunteers, lead shifts, propose changes, sit in on planning. Programs that hoard this kind of authority lose their best people. Programs that share it find that the program becomes more durable than the coordinator.

Volunteer fire departments are a useful pattern to study here. Many have functioned for decades with the same structure: members start by helping at events, move into responding to calls, train for technical roles, eventually lead crews, and finally mentor the next generation. The progression isn’t formal. It’s a natural arc of growing responsibility that the organisation makes space for. Nonprofits could borrow more from this model than they typically do.

This also applies to volunteers leaving. Most volunteers won’t stay forever, and that’s fine. The way you handle the end of an active period shapes whether they come back later, refer others, or speak well of the organisation in their communities. Ask why they’re leaving. Tell them they’re welcome to return. Keep them on a low-touch list for future opportunities. A graceful exit is often the start of an alumni relationship that pays off in unexpected ways.

When the right time comes, ask volunteers what they’d change about the program if they were running it. The answers will surprise you, and they’ll point to the next set of changes the program needs.

Frequently asked questions

How is working with volunteers different from working with paid staff?

Volunteers have fundamentally different motivations and constraints. They’ve chosen to be there, which means they can also choose to leave at any time without consequence. They give time as a form of contribution to a cause they care about, not as labour for compensation. The implications are practical: clarity about roles matters more, recognition matters more, the cost of a bad experience is higher, and authority works through reciprocity rather than employment.

What’s the most important skill for working with volunteers?

Listening, calibrated by context. The volunteer in front of you may be a first-time helper, a long-tenured regular, a frustrated supporter, or someone testing whether they want to commit further. Each of these calls for a different kind of attention. Coordinators who treat all volunteers the same lose the ones whose situation needs something specific from them.

How do you set boundaries with volunteers?

Define your hours, your response time, and your scope upfront. Something like “I respond to volunteer messages between 9 and 5 on weekdays. Urgent issues can go to [named contact]. Outside that, I’ll get back to you the next working day.” Clear, written boundaries are easier to maintain than informal ones, and volunteers respect them when they understand them. The coordinators who burn out are usually the ones who tried to be available all the time to seem helpful.

How do you handle difficult volunteers?

Have the conversation early, name the specific behaviour or pattern, explain what needs to be different, and follow up. Most coordinators avoid the conversation for too long, hoping the problem resolves itself, which it rarely does. The cost of the conversation is one uncomfortable hour. The cost of not having it is the other volunteers who quietly leave because of the unaddressed behaviour.

How do you keep volunteers engaged long-term?

Let the role evolve. A volunteer doing exactly the same task for years is either uniquely happy with the work or being underused. Most are being underused. Offering more responsibility, leadership opportunities, mentoring roles, or input into how things run is the strongest retention tool you have. People who feel their commitment is being recognised through growth, not just through thanks, stay.

How do you say no to a volunteer offer?

Directly and respectfully. “Thank you for offering. I don’t think we have a role right now that fits what you’re describing, but I’ll keep your information and reach out if something changes” is much better than vague follow-ups that never lead to a placement. Adults can handle a clear no. They can’t handle months of unclear maybe.

What’s the best software for working with volunteers?

The right tool lets you post tasks, accept signups, communicate operationally with active volunteers, and track participation in one place. Look for software that doesn’t charge per volunteer (so you’re not paying more as you grow) and that handles posting, signup, and messaging together. Zelos is built for exactly this, with unlimited volunteers on every plan and built-in messaging. For very small programs, a Google Form and group chat will get you started. You’ll outgrow it when administrative time crosses a couple of hours a week.

Ready to work with volunteers without the chaos?

Zelos gives coordinators a place to post tasks, organise shifts, track participation, and message volunteers through built-in channels. The systems do the operational work, so your time with volunteers can focus on the relationship rather than the logistics. Unlimited volunteers on every plan, no per-person fees, set up in an hour.

Listen, design, recognise, evolve. That’s the work.