How to Create a Volunteer Coordinator Handover Document

Most volunteer coordinators leave their role with months or years of institutional knowledge that exists nowhere except their own heads. The spreadsheets they know how to read. The volunteers who need a specific reminder format to actually show up. The shortcut for the supply closet key. The contact at the city parks department who actually returns calls. When that coordinator walks out the door, all of it goes with them.

A handover document doesn't fix that completely, but it gets you close. If you're leaving a coordinator role, or if you want to build one proactively while you still have the context to do it well, here's what to put in it.

Why "Just Show Them Around" Doesn't Work

A verbal walkthrough feels efficient. You spend an afternoon with your successor, explain how everything works, answer their questions, and call it done. The problem is that the questions they have in that moment are not the questions they'll have three weeks later, when they're sitting alone trying to figure out why volunteers in a particular program get a different reminder email or what to do when a shift lead doesn't show.

A document is searchable. It's there at 9 PM on a Thursday when you're no longer reachable. It can be updated as things change. And it signals to your successor that you took the transition seriously enough to write things down, which sets a good tone for the relationship going forward.

What to Include

Active Volunteer Roster

Not just a list of names, but a working roster with relevant context. For each active volunteer (or at minimum, your most reliable ones), capture:

• Contact information
• Which programs they're active in
• Typical availability and any quirks about their schedule
• Communication preferences (some people respond to texts, some to emails, some only to direct phone calls)
• Anything the next coordinator needs to know to work with them effectively

This is especially important for your core volunteer team, the people your program runs on. A successor who knows upfront who the keystones are can prioritize those relationships.

Program and Shift Structure

A clear description of each program: what it is, when it runs, how many volunteers it needs, and what those volunteers actually do. Include the things that aren't obvious from the schedule alone.

For example: "The Tuesday food pantry typically has 8 volunteers, but 3 of them are always the same people and the other 5 are from the drop-in pool. If fewer than 2 drop-ins sign up by Sunday, send a reminder to the backup list. The backup list is in this folder."

That context is worth more than a calendar.

Platform Logins and Tools

Every tool your program uses: the scheduling software, the communication platform, the spreadsheet you use for tracking, the folder where onboarding materials live. For each one, include:

• What it's used for
• Where the login is (or who holds it, if you're not able to share it directly)
• Any gotchas or non-obvious settings the new coordinator should know about

If you're using Volunteer Shift Manager, note which programs are set up, how the reminder cadence is configured, and whether there are any volunteers with special settings or notes.

Recurring Tasks and Calendar

A list of everything that happens on a recurring basis and when. This catches the things that aren't on anyone's radar until they're suddenly urgent.

Examples:

• Volunteer newsletter: sent the first Tuesday of each month
• Annual volunteer appreciation event: typically scheduled in April, booking starts in January
• Grant reporting deadline: quarterly, due the 15th of the following month
• Background check renewal reminders: 90 days before expiration

If there's a task that happens every year and the person currently doing it has just done it once, it's almost certainly not in any system. Ask yourself: "What would fall through the cracks if someone started this job tomorrow?" and make sure those things are written down.

Vendor and Partner Contacts

The people outside your organization who keep your program running. This might include:

• The background check provider and your account contact
• The venue or site contacts for each program location
• The email service you use for volunteer communications
• Corporate partners who send volunteer groups
• Community organizations you partner with for referrals

For each contact, include what they help with and any relationship context that matters ("Sandra at the food bank is extremely responsive; Marco at the parks department prefers to be contacted by phone, not email").

What's Currently in Progress or Unresolved

This section is often the most valuable and the most overlooked. What problems are you in the middle of solving? What conversations have you started with volunteers that aren't finished? What changes were you planning to make but haven't implemented yet?

Your successor shouldn't have to figure out mid-stream what was already in motion. A simple list of "here's what I was working on and where things stood" can prevent a lot of dropped balls.

This is also a good place to flag anything politically sensitive: a volunteer relationship that's been strained, a program partner that's been difficult to work with, a conflict that was resolved but bears watching.

What You Wish You'd Known

This is the informal section that turns a functional handover document into a genuinely useful one. What did you learn the hard way? What mistakes did you make that your successor could avoid? What took you months to figure out that you could just tell someone?

This isn't about complaining. It's about being honest with someone who's about to walk the same road. "The volunteer signup link for the Saturday shifts breaks every time we change the shift name, so don't change the shift name unless you're ready to re-share the link" is extremely useful. Write things like that down.

When to Write It

The right time to write a handover document is while you still have context, which means starting it well before you know you're leaving. A lot of coordinators intend to write one when they have more time, and then they're in their last week and overwhelmed and produce something rushed that misses half of what matters.

If you're in a coordinator role and you don't have a handover document, consider writing one now. Not because you're planning to leave, but because the process of writing it forces you to document your own program processes in a way that makes you more organized while you're still there.

It also turns out to be useful for continuity during vacations, medical leave, or any situation where someone else needs to cover your role for a period. A handover document isn't just for permanent transitions.

The Leadership Transition Context

If you're leaving due to a broader organizational leadership change, the handover document becomes even more critical. In those situations, institutional knowledge often gets lost not just from one person leaving, but from the disruption of the transition itself. Getting it into writing before the transition rather than after is the difference between a program that continues smoothly and one that effectively has to be rebuilt.

Your volunteers will notice the difference. The ones who've been around a while know when a coordinator really prepared for the handoff and when they were left to figure things out on their own. Giving your successor the best possible start is also one of the most concrete ways to honor the volunteers who built the program with you.