Coordinating Volunteers Without Burning Out

In short: What wears coordinators down is usually the administrative grind. Catching every cancellation individually, filling every gap via group chat. No-show rates of 20 to 50 percent are normal when volunteers have no employment contract. Three things help: volunteers can regulate themselves. Dropouts get planned for rather than fought — through waitlists and automatic backfilling. And the role becomes shareable, because the planning state no longer lives in one person’s head.

Three people had confirmed for Saturday. Friday evening, one cancels. Another hasn’t responded since Thursday. The third simply doesn’t show up on Saturday. The coordinator posts in the WhatsApp group: “Urgent. Today, 2 to 6 pm, who can step in?” Half an hour later, she’s found someone. The shift is covered. Phew, a lot of stress.

This only works because one person does it by hand every single time. Anyone who’s coordinated before knows this routine. Not as an exception, but as the normal state of things.

What volunteer coordination actually does

Coordinators often play a very central role in the volunteer structure. Everyone talks to this person. She knows the people. She knows who’s reliable and who only commits when asked three times. She catches conflicts early and keeps the organization running.

A large part of this work is relationship maintenance. No tool can replace that. When someone posts in the WhatsApp group “Who can cover Saturday?”, people respond because they know the person asking. That’s fine, as long as everyone’s still okay with it.

But the work is often deeply draining. Manual follow-ups, hunting down phone numbers. The fact that every cancellation and every shift swap has to go through a single person. Administrative busywork and constant firefighting drain energy. Little time is left for the human side of the job.

What makes volunteer coordination unnecessarily hard

Four patterns show up in nearly every volunteer structure. None of them is a personal failure, but all four are structural problems.

Flake rate is normal. Manually catching every gap is not.

Anyone who coordinates volunteers knows: a significant share of people who commit don’t show up. Depending on context, that’s 20 to 50 percent. This isn’t a failure of the organization — it’s part of the volunteer context. People have no employment relationship, no contract, no legal consequences. That some cancel spontaneously or simply don’t come is to be expected.

What doesn’t have to be part of it: every single gap being filled manually. When the coordinator individually reaches out, follows up, and replans for every open shift, a normal occurrence multiplies into a constant workload.

Accountability comes from processes, not people

Part of the problem is a lack of accountability. When there’s no defined process for what happens after a cancellation, every case becomes a dilemma. For the coordinator: Do I say something? Do I let it slide? For the volunteers: Do I need to cancel, or is it fine to just not show up?

Fixed processes help both sides because they’re predictable. When it’s clear what happens after a cancellation, nobody needs to feel guilty and nobody needs to chase people down. At the same time: too much pressure tips into (self-)exploitation. That turns the organization into a ticking time bomb. The process has to work without being overbearing.

If you’re interested in this principle, there’s a good parallel in the article about roommate cleaning schedules. What applies to four roommates applies to volunteer groups just the same: it’s not the model that determines whether it works, but whether everyone knows and supports the process.

Single point of contact

Everything runs through one person. Every question, every swap, every cancellation. That’s a classic bottleneck. When that person is unavailable for a weekend, others feel like things are falling apart. The coordinator isn’t actually irreplaceable — but in the moment, it feels that way.

No path to self-organization

In many groups, self-organization already works. Just informally. The coordinator posts in the group, someone steps in. That’s better than an empty shift nobody sees. But it depends on one person giving the nudge. Without the message, nothing happens.

The question is: what if volunteers could see open shifts and sign up themselves, without someone having to prompt it every time? Or what if volunteers could commit to regular shifts on a set rhythm, but vacations and last-minute obligations didn’t become a stress test?

The pattern is often similar. Coordinators quit after one to two years. The role stays vacant for months afterward and the community loses significant momentum.

What makes the difference

The WhatsApp group already shows that the mechanism works: an open shift, a message, someone steps in. The next step is to make this flow sustainable. When volunteers can see open shifts and sign up or swap among themselves, most of the manual matchmaking disappears. The coordinator sets the framework, not every individual assignment.

Plan for the flake rate instead of fighting it

No-shows and last-minute cancellations are normal in a volunteer context. Instead of trying to push them to zero, it’s more effective to expect them: waitlists, automatic backfilling, overstaffing for critical shifts. Coordination gets lighter when dropouts no longer require firefighting.

The role has to be shareable

Not every organization needs a paid position. But coordination should always be understood and executable by more than one person.

shiftfold

I’m building shiftfold because I want to solve exactly this problem. Volunteers sign up for shifts themselves, see open slots, and swap among each other. Coordinators keep the overview without having to manage every assignment by hand.

shiftfold is currently in early access. Sign up here.