How to Create a Volunteer Offboarding Checklist

When a new volunteer joins your program, there's a whole process. An orientation. An onboarding checklist. A welcome email. Maybe a buddy. You've probably thought carefully about that first impression.

When a long-term volunteer leaves, most organizations do almost none of that. They send a thank-you card, maybe. The volunteer walks out with access to your shared Google Drive still active, their name still on the shift schedule, and years of institutional knowledge inside their head that's now effectively gone.

Offboarding is the part of volunteer management that nobody builds a process for until something goes wrong. Here's how to do it right before that happens.

Why offboarding matters more than it seems

For most general volunteers (someone who signs up for occasional shifts and then stops coming), offboarding is simple. You remove them from the active list, send a kind note, and move on.

For long-term or high-involvement volunteers, the stakes are higher. These are the people who:

• Have login access to systems, databases, or platforms
• Hold institutional knowledge about how your program actually runs
• Have relationships with clients, donors, or community partners that nobody else knows about
• Are working in roles where a gap creates a real operational problem

Leaving these situations unmanaged creates real, if usually undramatic, risk. Forgotten access credentials, lost knowledge, and lingering roster confusion are all genuinely disruptive at a small organization where everyone is already stretched.

Offboarding is also the last impression your organization makes on someone who gave you real time and energy. Making it a good impression matters, both for the relationship and for what they say about you afterward.

The two reasons volunteers leave

Before you build the checklist, it helps to know which kind of departure you're dealing with.

Planned departures are the easier ones. The volunteer tells you they're moving, graduating, returning to work, or just ready for a change. You have a conversation, you have some lead time, and you can plan a transition.

Unplanned departures are trickier. A volunteer stops responding, stops showing up, or tells you on a Tuesday that they're done by Friday. These happen, and you can't always predict them. But you can have a checklist ready so you know what to do when they do.

The checklist covers both situations. Some steps only apply when you have advance notice. Others are things you'd run regardless.

The checklist

Access and security

• Revoke any login credentials (email accounts, scheduling systems, shared drives)
• Remove from shared Slack, WhatsApp, or other communication channels
• Collect any keys, keycards, or physical access items
• Update any shared passwords they had access to

Knowledge transfer

• Schedule a handoff conversation if their role carries specific institutional knowledge
• Ask them to document any processes or contacts that only they know about
• Check whether they're the sole contact for any external relationship (vendor, partner, donor)
• Confirm who will take over their responsibilities and whether that person has been briefed

Communication and relationships

• Let relevant clients, staff, or other volunteers know they're leaving, where appropriate
• Introduce their replacement or point of contact if one exists
• Make sure they're removed from any external-facing materials (website, program flyers)

Administrative cleanup

• Mark them as inactive in your volunteer database
• Remove from shift schedules or waitlists
• Archive their contact record with departure date and role history
• Return any equipment or supplies they were using

Closing the relationship

• Send a genuine thank-you that isn't a form letter
• Offer a letter of recommendation or reference if appropriate
• Ask if they'd like to stay connected as a program alum
• Log the departure reason if they've shared it, as part of your volunteer feedback process

The knowledge transfer conversation is the one most coordinators skip

Everything else on the checklist is administrative. The knowledge transfer conversation is the one that actually protects your program.

A volunteer who has been with you for three years knows things you don't realize you don't know. How to reach the community partner who never answers email. The workaround for the quirk in your scheduling system. Which client prefers which communication channel. The unofficial approach to a recurring task that actually works better than the documented one.

Spend 30 to 60 minutes with a departing long-term volunteer specifically asking: what do I need to know that I might not know to ask? What would trip up whoever takes this over? Who should I call if something goes wrong in the next six months?

This conversation needs to happen before their last day, not during the send-off.

Pair offboarding with your onboarding checklist

If you've built a thorough volunteer onboarding checklist, your offboarding checklist is, in many ways, its mirror. Access is granted at the start and revoked at the end. Institutional context is shared at the beginning and documented at the close. The relationship is welcomed in and acknowledged on the way out.

Building both processes together makes them easier to maintain and easier to train someone else to run.

Don't let offboarding get cold when departures are messy

Sometimes volunteers leave under circumstances that aren't entirely positive. They've had a frustrating experience, they're burned out, or there's some unresolved tension. It's tempting to let the process get perfunctory when that's the case.

Don't. Run the same checklist regardless of how the departure is going. Revoke access, document knowledge, send a sincere thank-you. If there's something to learn from why they're leaving, your volunteer exit conversation is the right place to explore that, separate from the administrative cleanup.

A volunteer who leaves feeling respected sometimes comes back later, or refers someone else. One who leaves feeling dismissed doesn't.

How this connects to organizational resilience

If you're finding that offboarding a single volunteer feels genuinely destabilizing, that's worth paying attention to. Over-dependence on any one person is a risk. The guide on what to do when you're over-reliant on one volunteer has strategies for distributing knowledge and responsibility before you're in a crisis.

Every time you document a role well and transfer knowledge cleanly, you build a little more organizational resilience. After a few cycles, you have systems instead of scrambling.

Volunteer Shift Manager makes the administrative side of this easier. Deactivating a volunteer from the system, removing them from shift assignments, and archiving their record are quick actions in the dashboard rather than a multi-step manual process. That's one piece of the checklist you can handle in a few minutes rather than a few hours.