What to Do When You're Too Dependent on One Volunteer

Every small nonprofit has one. The volunteer who's been there since the beginning, who knows where everything is, who fills in without being asked, who the other volunteers call when something goes wrong.

They're a blessing. They're also a risk.

If that person moved away, got sick, or simply burned out and stopped showing up, how quickly would things fall apart? If the honest answer is "pretty fast," you have a dependency problem worth addressing now, before it becomes an emergency.

Why This Happens (And Why It's Nobody's Fault)

Key volunteer dependency tends to develop quietly, through a series of reasonable decisions. Someone steps up, proves reliable, and gets handed more responsibility. Over time, they become the informal expert on a piece of the program. Coordinators, stretched thin, gratefully lean on them. The volunteer enjoys being useful. Everyone benefits, until something changes.

The problem isn't that this person became valuable. The problem is that the knowledge and the relationships stayed concentrated in one place instead of spreading through the program.

This is sometimes called the "bus factor" (the number of people who would need to be hit by a bus before a project collapsed). For many small nonprofits, the volunteer bus factor is one. That's a fragile place to be, and it often goes unnoticed until the moment it matters most.

Warning Signs to Watch For

A few indicators that your program has a dependency problem worth addressing:

Only one person knows how to do a critical task. Whether it's operating a piece of equipment, managing a specific relationship with a partner organization, or knowing the unofficial rules for recurring situations, single-source knowledge is a risk.

Other volunteers defer to them, not to you or your systems. When volunteers have questions, who do they call? If it's mostly one peer rather than following a documented process, that's a signal.

You'd struggle to cover their absence on short notice. Test this mentally: if they texted tonight saying they couldn't make the next shift, what would you do? If the answer is "I have no idea," there's a gap.

They've become an informal gatekeeper. Sometimes key volunteers accumulate roles where things don't move forward unless they're involved. This often starts from good intentions, but it concentrates both authority and risk in one person.

What to Do About It

The goal isn't to reduce their role or signal that they're doing something wrong. It's to build the program's resilience so it can survive the changes that inevitably happen when life gets complicated for anyone.

Document the informal knowledge. Sit down with your key volunteer and ask them to walk you through what they know that isn't written down anywhere. Turn that into a simple reference document. This isn't about replacing them; it's about making their knowledge available to the whole team. Building a volunteer skills inventory is a useful companion to this process, since it surfaces the full picture of who knows what.

Cross-train at least one other person. Pick the tasks your key volunteer currently owns and start training others to handle them too. You don't need everyone to know everything; you need at least two people who can cover each critical function. Think of it as building redundancy into the program the same way you'd want it in any other system that can't afford to break.

Name a backup for every role. When assigning shift leads or program responsibilities, name a backup explicitly. This normalizes the idea that multiple people can handle important roles, and it removes the pressure from any one volunteer.

Build a leadership pipeline deliberately. If your key volunteer has been carrying informal leadership, it's worth thinking about who might grow into more formal responsibility over time. A volunteer leadership pipeline takes time to develop, but it's one of the highest-leverage investments you can make in the program's long-term stability.

Talk to them directly. If your key volunteer has been carrying more than their share, they may already be feeling it. A direct conversation about sharing the load, framed honestly and appreciatively, is better than waiting for the burnout to arrive. Sometimes the volunteer who does everything is quietly hoping someone will give them permission to do less.

The Harder Conversation: When There's Resistance

Sometimes key volunteers are resistant to sharing knowledge or stepping back from ownership. This can happen for a few reasons: they genuinely love being essential, they're worried others won't maintain standards, or the role has become part of their identity after years of being the person everyone turns to.

It's worth being curious before being concerned. Ask what they'd need to feel confident delegating. Ask what their specific worries are. Sometimes there are legitimate concerns (the task genuinely requires expertise) and sometimes there's just attachment.

If the resistance is persistent and the dependency is creating real risk, that's a harder conversation about what's best for the program. You can appreciate someone's contribution enormously while also being honest that the current arrangement isn't sustainable as the program grows.

If They Leave Before You're Ready

If your key volunteer exits before you've built resilience, you're in triage mode. A useful short-term checklist:

1. Identify the gaps immediately: which tasks, relationships, and knowledge are now at risk.
2. Talk to other experienced volunteers first: they'll often know more than you think.
3. Check whether any documentation exists, even informal notes or old emails.
4. Prioritize what's time-sensitive over what's merely uncomfortable.
5. Communicate clearly with the rest of the team: they'll notice the change, and honest communication keeps morale higher than silence.

Handing off a volunteer program is a related read, since many of the same principles apply when a key volunteer exits as when a coordinator role fully transitions.

Why It's Worth Doing Before a Crisis

The time to solve a dependency problem is when things are stable. It's much easier to cross-train a volunteer when there's no urgency than to scramble after an unexpected departure.

It's also fairer to the volunteer carrying the weight. When people hold too much informal responsibility for too long, the load can turn into resentment even when it started as enthusiasm. Deliberately sharing the work protects them as much as it protects the program.

If you've been grateful for one reliable volunteer who carries a disproportionate amount, the best way to honor that contribution is to make sure the program can eventually thrive without depending on any single person. That's not disloyal. That's how you build something that lasts.

What to do when a reliable volunteer stops showing up is worth reading alongside this one, since the early signs of someone pulling back are often visible before the full exit.