How to Hand Off a Volunteer Program When You're Leaving

Coordinator turnover is one of the more underappreciated risks in volunteer program management. The coordinator often carries an enormous amount of knowledge in their head: who the reliable regulars are, why the Thursday shift runs differently from the Saturday one, which volunteer needs a gentle heads-up before a stressful event, which partner organization needs two weeks of lead time. When that person leaves without a good handoff, the program doesn't fail. But it limps. And the volunteers notice.

If you're the person leaving, a clean handoff is one of the most useful things you can do for the people who showed up for you every week. If you're the person inheriting the role, the quality of that handoff will shape your first six months more than almost anything else.

Start the Documentation Early

The mistake is waiting until the last two weeks to write anything down. By then, you're wrapping up, scheduling going-away events, and mentally halfway out the door. The documentation gets rushed, the important nuances don't make it in, and the new coordinator gets a skeleton outline of the job instead of the real thing.

The right time to start is the moment you know you're leaving, which is usually weeks or months out. Treat it like a project with a deadline, not a last-minute task.

What needs to be written down:

The operational fundamentals. How shifts are structured, how volunteers sign up, how reminders go out, where the physical supplies are stored, who the venue contacts are. If your program runs on volunteer scheduling software, document which features you use and how.

The relationships. A brief note for each regular volunteer: how long they've been coming, any relevant context (health considerations, scheduling constraints, preferred communication style). This is the kind of thing you'd never write in a formal HR document, but it matters enormously when someone is trying to build a relationship from scratch.

The recurring calendar. What happens in June that doesn't happen in March? Which events have partner organizations involved? Which programs have annual cycles? Write out the full calendar cycle at least once.

The soft stuff. What's worked well in recruiting volunteers. What's been tried and hasn't. What the organization is sensitive about. What the friction points are with other departments.

Who Needs to Know, and When

Telling volunteers before the transition is usually the right call, unless organizational politics prevent it. Volunteers often have a personal relationship with the coordinator, and finding out after the fact that their point of contact changed feels disorienting.

A simple, honest note works fine: "I've loved working with you all, I'm moving on to a new opportunity, and I'm excited to introduce you to [successor] who will be taking over in [month]." It doesn't need to be long. It acknowledges the relationship, gives them context, and points them toward the next person.

If you can do an in-person or video introduction between the outgoing and incoming coordinator and your key volunteers, that's worth the time. For long-term regulars who've been volunteering for years, a direct personal message (not just a group email) is appropriate. How you communicate this change matters almost as much as the content.

The Transition Overlap

A period where both the outgoing and incoming coordinator overlap is not always possible, but when it is, use it intentionally. This isn't just about shadowing. It's about the incoming person being introduced as the point of contact while the outgoing person is still available to answer questions.

A week or two of overlap is usually enough for smaller programs. Larger programs with more complexity might need a month.

If there's no overlap, the documentation becomes even more critical, and a written FAQ for the first 30 days is worth creating. Not a comprehensive manual, but a document that answers the ten most likely questions the new coordinator will have in the first month.

Handing Off Digital Access and Tools

This is easy to forget and harder to fix after the fact. Before you leave:

• Transfer admin access to any scheduling or communication tools the program uses.
• Make sure any shared accounts don't require your personal email to reset passwords.
• Export or share any volunteer contact lists from personal email threads or spreadsheets you've been maintaining outside the main system. Keeping volunteer data secure during a transition matters: you don't want contact lists floating around in personal email accounts.
• Hand off any shared folders, shared inboxes, or file storage living in your personal workspace.

Check whether access to your tools is tied to your personal account or to the organization. If it's personal, transfer the account before you close it.

Staying Available (Within Reason)

Most coordinators feel some pull to stay reachable after they leave, in case the new person has questions. That's generous, and setting a light version of this up is fine: "I'm happy to answer emails for the first few weeks if something comes up."

But there's a version of this that goes wrong, where the outgoing coordinator becomes the de facto backup system because the handoff documentation wasn't thorough enough. That's not fair to you, and it delays the new coordinator from building confidence and relationships on their own terms.

A clean handoff, thoroughly documented, is more generous in the long run than being indefinitely reachable.

If You're the New Coordinator

If you're inheriting the program, push for documentation early, even if the previous coordinator hasn't offered it. Ask specific questions: who are the five most reliable volunteers, what are the three things most likely to go wrong in the first month, what does the fall surge look like?

A good entry point is running your first few shifts alongside someone who knows the ropes, even if that person is a long-term volunteer rather than the outgoing coordinator. The volunteer coordinator's first 90 days are about relationship-building as much as operational competence. You need both.

The volunteers will give you grace if you're new. What they need to see is that you care about the program and about them. The rest can be learned along the way.