How do you hand off a volunteer program when the only coordinator gives notice?

Inventory what actually lives in one person's head

The first week after notice should be spent listing, not training. Sit down with the departing coordinator and write out everything the program depends on: where the roster lives, which accounts and logins exist and who owns them, the recurring schedule and its exceptions, the volunteers who are fragile or need particular handling, the partner organizations and their contacts, the shift leads and what each is good at, and the informal rules nobody wrote down. Expect the list to be long and expect it to surprise the leadership.

Pay attention to the relationships. A program's health is often carried by a dozen loyal regulars who volunteer because of the coordinator personally. Those people need to hear about the transition directly, ideally from the departing coordinator with the successor present, before they hear it as a rumor. A short note that says who is leaving, who is coming, and that the program continues will hold most of them.

Keep reading: Why does coordinating volunteers through group texts fall apart as an organization grows?, How can a nonprofit fill last-minute volunteer shift gaps before an event begins?, What is the most effective way to reduce volunteer no-shows for scheduled shifts?. See how HelperRoster helps you volunteer shift scheduling and rosters.

Move everything into shared ownership immediately

Any account in the coordinator's personal name should be transferred to an organizational one this week: the scheduling tool, the email list, the shared drive, the social accounts, the phone number volunteers text. If the program runs on the coordinator's personal cell, get a number the organization controls and start telling volunteers about it now. The goal is that on the last day, the departing coordinator can hand over a login sheet and nothing breaks. Related: Why does coordinating volunteers through group texts fall apart as an organization grows?

The same applies to files. Waivers, hours logs, grant reports, and training materials should be in a shared, permissioned location with a simple folder structure. If they are on a laptop or in a personal inbox, copy them now, while the person who knows what each file is can still label it. Recovering context from an anonymous folder six months later is nearly impossible. Related: How should a nonprofit track volunteer hours accurately for grant reports and thank-yous?

Run a structured overlap

If there is any overlap between the outgoing and incoming coordinators, structure it around real shifts and real cycles. The successor should build one full week's schedule with the outgoing coordinator watching, send one round of reminders, handle one no-show, and run one shift lead check-in. Doing each thing once with a safety net is worth more than any document. If there is no overlap, ask the departing coordinator to record short walkthroughs of the weekly tasks and to be reachable for a few defined questions in the first month, if they are willing. Related: What is the most effective way to reduce volunteer no-shows for scheduled shifts?

Introduce the successor to the shift leads as a group during this period. Leads are the successor's most important allies, and they will keep the program running through the awkward first weeks if they trust that the new person listens. A coordinator who arrives and starts changing things before meeting the leads loses the room fast.

Make the next handoff easier than this one

Once the dust settles, the new coordinator should spend a little time each month keeping a living operations document current: how the schedule is built, what the reminder cadence is, who the leads are, what each partner expects, and where everything lives. The best version of this document is boring and short, and it is updated whenever something changes rather than rewritten in a panic.

The scheduling system itself carries part of this load if it is set up well. A tool where shift templates, role requirements, volunteer histories, and lead assignments are stored in the organization's account means the next coordinator inherits a working program rather than a blank page. That is the quiet argument for moving off personal spreadsheets long before anyone gives notice. Related: How can a nonprofit fill last-minute volunteer shift gaps before an event begins?