How to Create a Volunteer Shift Handover Protocol

The end of one volunteer shift and the start of the next is where things get lost. The morning team knows the supply closet is getting low. The afternoon team doesn't. By the time anyone figures it out, a participant is waiting and there's nothing to give them.

Most organizations running multi-shift programs eventually figure out that a five-minute handover conversation, done consistently, is worth more than a thirty-minute debrief that only happens when something goes wrong. Here's how to build a handover protocol that becomes second nature.

What a Handover Is (and Isn't)

A shift handover isn't a full debrief. It's not the place to process difficult interactions, evaluate performance, or cover anything that requires more than a few minutes. It's a quick transfer of operational information: what happened, what's different from normal, what needs attention, and what the incoming shift should know before they start.

Think of it as answering four questions:

1. What's the current status of the things that matter?
2. What happened that was unusual or that I'd want to know if I were coming in next?
3. What's unfinished or needs to be followed up on?
4. Who needs to know about anything I just told you?

That's it. Most effective handovers cover those four questions in three to five minutes.

Who Should Be Involved

In an ideal world, there's overlap between the outgoing and incoming shift so they can do a brief in-person handover. Even ten minutes of overlap is enough. If that's not possible because of scheduling, a written note or a shared document is the next best option.

If you use a shift lead model, training your shift leads to own the handover responsibility is the most sustainable approach. The shift lead collects what they need to know from their team during the last fifteen minutes of a shift, then passes it to the incoming lead. Other volunteers don't need to be involved unless they have something specific to report.

The Three-Part Handover Format

Keep the format simple enough that volunteers will actually use it under time pressure.

The verbal check-in (if shift overlap exists): A brief conversation between outgoing and incoming leads covering anything that changed during the shift, any supply or resource issues, any participant situations that are ongoing, and anything that was flagged that didn't get resolved.

The written note (always, regardless of overlap): A short document or note that goes in a consistent, agreed-upon place. This might be a shared Google Doc, a whiteboard, a paper log, or a simple field in your scheduling tool. What matters is that the location is the same every time so the incoming team always knows where to look.

The resource check: A quick physical check of whatever needs to be restocked, reset, or handed off materially (keys, equipment, sign-in sheets, whatever your program uses). This is separate from the verbal and written portions because it's easy to remember to talk but forget to physically hand something over.

What to Include in the Written Note

A good shift handover note doesn't need to be long. A few lines covering:

• Date and shift time
• Names of who was present (or a quick head count if that's what matters)
• Anything that differed from the normal setup
• Supplies running low or things that need to be requested
• Any participant situations that are ongoing or that the next team should be aware of
• Any follow-up items that weren't resolved, and who owns them

This doesn't need to be typed. A printed half-sheet template that someone fills out by hand works just as well. The goal is consistency, not polish.

For programs that use a volunteer sign-in sheet, the attendance record can double as the start of the handover note, which reduces the paperwork overhead.

Building It Into the Schedule, Not Bolting It On

Handover only works if time is built in for it. If the shift ends at 2pm and volunteers are expected to be out the door by 2pm, the handover will get skipped whenever the shift runs long, which is often.

Add fifteen minutes to the end of the official shift for handover purposes. Make it part of the scheduled time, not "extra." Volunteers who know the shift genuinely runs from noon to 2:15 will plan for that. Volunteers who think it ends at 2pm and then get handed fifteen minutes of extra responsibility will resent it.

This also changes how you structure shift briefings at the start. If you know the previous team left notes, opening a shift with "let's take two minutes to check the handover log" becomes a natural habit rather than something you have to remind people to do.

Common Problems and How to Fix Them

Nobody writes the note. Add it to your volunteer task list as an explicit closing step, right before "turn off lights" and "lock up." If writing the note is step 7 of 8, people do it. If it's assumed, it gets forgotten.

Notes are inconsistent or hard to read. Use a template. A half-sheet with the four questions printed on it and space to fill in answers takes the cognitive load out of figuring out what to write. The incoming team can scan it in thirty seconds.

The incoming team doesn't check the notes. Make checking the log part of the shift opening checklist, the same way you'd expect someone to check their calendar at the start of a workday. This is a culture question more than a process question. It takes a few weeks of consistent modeling from the coordinator before it sticks.

Things get lost anyway. Review the handover notes at the end of each week as part of your own workflow. Anything that's been noted more than once is probably a recurring problem worth addressing at a higher level, not just flagging forward indefinitely.

Starting Simple

If you don't have any handover protocol right now, don't build an elaborate system from scratch. Start with a shared notebook in a consistent location. Ask your shift leads to write three things at the end of each shift: what went well, what was different, and what needs follow-up. Spend two weeks building that habit before adding anything else.

A simple protocol done consistently is better than a comprehensive protocol nobody uses. Once the habit is there, you can add structure as you figure out what information actually matters most for your specific program.