The Common Table Notes
Group Work

Volunteer Handover Checklist: Transfer Work Clearly

The Common Table Notes · Updated 2026-09-07 · 7 min read
Volunteer Handover Checklist: Transfer Work Clearly
In briefA volunteer handover checklist should name ongoing tasks, next actions and deadlines, approved record locations, decision authority, receiving owners, and transfer status. Confirm the recipient has accepted the work and can access what they need; sending notes is not enough. Use authorized administrators for access changes, protect sensitive records, and follow safeguarding and retention procedures. Required checks, training, permissions, and qualified advice still apply.
Contents

What belongs in a volunteer handover?

A volunteer handover should identify ongoing work, the next deadline, where approved records live, who has authority, and who has agreed to take each responsibility. Confirm the recipient can use the information before marking work transferred. Arrange equipment return and access changes through authorized people, protect sensitive records, and follow the organization's safeguarding and retention procedures. A handover note does not replace required training, checks, permissions, or qualified advice.

The Common Table Notes' checklist below is an editorial tool for small groups, not a prescribed legal form. It works best for ordinary coordination: a club newsletter, a community meeting calendar, or volunteer administration. Higher-risk roles need the responsible organization's formal process.

The aim is a fair ending and a usable beginning. The departing volunteer should not have to remain permanently available because nobody has decided who receives the next email.

Start with the role that actually exists

Ask the departing volunteer what they currently do, including quiet recurring work that never appears on the meeting agenda. Compare this with the agreed role description. Do not automatically pass every extra task to the next person.

NCVO recommends role descriptions that explain tasks, boundaries, relevant policies, expenses, and whom to ask about changes. It also recognizes that volunteers may need information in different formats. NCVO: writing volunteer role descriptions

For a handover, mark each responsibility as:

These are proposed working labels, not NCVO categories. Their purpose is to stop a handover from quietly becoming a larger job description.

If the project is still being defined, revisit the volunteer project kickoff first. A new person cannot meaningfully accept a responsibility that the group itself has not settled.

Make one row for each piece of ongoing work

Use this original checklist as a cover sheet. Link approved source records rather than copying everything into it.

Field What the next person needs
Work item A specific recurring task or unfinished commitment
Current position Completed steps, pending response, or unresolved question
Next action and date The next observable step and its actual deadline
Working record Approved location and access route
Authority and limits Who approves changes and what the role may decide
Receiving owner A named person who has agreed to consider or accept it
Transfer status Prepared, sent, reviewed, accepted, or blocked

Write "room request submitted; confirmation not received" instead of "venue sorted." Write "draft awaiting approval" instead of "newsletter ready." A useful handover preserves uncertainty where it exists.

Distinguish the document owner from the decision-maker. Someone maintaining the calendar may have no authority to sign a venue agreement. Refer to the group's decision log for the reason and approval behind an existing commitment, without turning this cover sheet into another decision register.

What does a completed row look like?

Here is a hypothetical example for a small reading group. It is invented to demonstrate the checklist, not a report about a real organization.

The row is deliberately not marked accepted merely because it was emailed. Its reader needs both enough context and the means to proceed.

For multiple versions of a file, identify one current copy and label obsolete working drafts according to policy. Do not delete records merely to make the folder look simpler. Record retention and disposal require their own authorized decision.

Check capacity before transferring the whole role

Ask what time the receiving volunteer can realistically offer and what support they need. Acceptance of one task is not acceptance of every unfinished item in the departing person's inbox.

Consider an illustrative weekly workload: 20 minutes preparing the meeting notice, 15 minutes updating the calendar, and 25 minutes answering routine group queries. That totals 60 minutes. If the incoming volunteer has offered 40 minutes, the gap is 20 minutes, not a reason to describe the role as "only a small commitment."

The group could keep the first two tasks together, totaling 35 minutes, and assign the 25-minute query task to another consenting person. Alternatively, it could reduce the service or pause it. These figures are planning assumptions, not measured averages or promises about how long the work will take.

Add unusual peaks separately: an annual event or a backlog may not fit an ordinary week. Leave room for the receiving person to question the estimate after trying the work.

How do you check that the handover is usable?

Arrange a short review if both people can participate. Our suggested 30-minute outline is five minutes for scope, ten for the next live task, five for questions and blockers, five for access status, and five for acceptance and follow-up. The total is 30 minutes; complicated roles need more preparation, not a rushed sign-off.

Ask the recipient to explain, using the handover materials:

  1. What is the next action?
  2. What information is still missing?
  3. Who can approve a change?
  4. Where is the approved working record?
  5. What must happen before work can begin?

This is a document check, not a test of the volunteer's intelligence. If the answer requires unwritten knowledge, add that context.

Use a harmless draft or a verbal walkthrough. Do not send real messages, make purchases, change permissions, or carry out safety-critical tasks just to demonstrate that a handover works.

Transfer access through the authorized administrator

Keep passwords, recovery codes, and sensitive participant information out of the handover sheet. Ask the authorized administrator to arrange the receiving person's appropriate access through the organization's approved system. Do not share another person's login or move organizational records into a personal account as a workaround.

Record a status such as "administrator confirmed access on 18 September," not the credential itself. The recipient should check that the required approved records are accessible through their own authorized access.

NCVO's safeguarding guidance calls for returning organizational property, removing former volunteers' access, changing relevant passwords or codes, and making clear that the person no longer holds the role's privileges. Treat these as administrator-led offboarding tasks, not instructions for volunteers to alter systems on their own. NCVO: ending the volunteering relationship

A missing replacement is not a reason to leave unnecessary access active indefinitely. Escalate the continuity problem to the responsible coordinator. Follow immediate security or safeguarding restrictions where required.

What should stay out of general handover notes?

Exclude unnecessary personal details, medical information, confidential allegations, and private explanations of why someone is leaving. A broadly shared checklist can identify the responsible restricted-record owner without reproducing the record.

The UK Information Commissioner's Office explains data minimisation as holding enough relevant personal information for the purpose, but no more than necessary. This is UK guidance; legal requirements elsewhere must be checked locally. ICO: data minimisation

Do not interpret minimisation as permission to destroy required records. The ICO's storage-limitation guidance says retention depends on purpose rather than one universal period for every kind of personal data. Ask the organization's responsible data lead about retention, restricted transfer, and approved disposal, including any applicable preservation requirement. ICO: storage limitation

Both ICO pages were marked under review when checked on 7 September 2026. This checklist does not determine legal compliance or a retention schedule. Seek qualified privacy or legal advice where needed.

What if the volunteer leaves suddenly?

Start from approved organizational records and appoint a temporary coordinator within the group's authority. Mark assumptions as unconfirmed. Identify the nearest commitments, then decide what can continue, what needs approval, and what must pause.

NCVO advises giving absent volunteers the benefit of the doubt and deciding when to stop repeated attempts at contact. If there is concern that someone may be at risk, follow the organization's safeguarding process. NCVO: ending volunteering well

Do not search private accounts, impersonate the former volunteer, or pressure their personal contacts for project access. A safeguarding concern belongs with the designated lead, not in a general group discussion. Follow applicable emergency procedures for immediate danger. A routine handover is not an investigation or a substitute for required checks.

Close the handover without leaving an open-ended obligation

Read back what was accepted, what remains blocked, and who owns each unresolved item. If the departing person freely offers a follow-up conversation, agree its scope and endpoint. Do not assume continuing availability.

Thank them and invite feedback through an appropriate route. NCVO includes recognition, feedback, planned handover, and checking whether someone wants future contact in its ending-volunteering guidance. That last choice matters: finishing a role need not mean joining a permanent advice service.

Keep the final cover sheet in the agreed location with its review date. More small-team structures are in Group Work. The handover is complete when the remaining work has an accountable destination—or an explicit pause—not when the last attachment leaves the outbox.

Sources

FAQ

How much detail should volunteer handover notes include?

Include enough for the next person to identify the next action, deadline, approved record, and decision-maker without relying on private knowledge. Link supporting material instead of copying an entire archive. Keep sensitive records restricted and describe unresolved questions honestly. A short usable cover sheet is more helpful than an unexplained folder.

When can I mark a task handed over?

Mark it accepted only when the receiving person has agreed to the responsibility, understands the next action, and has the necessary authorized access and approvals. Until then, use a status such as sent, reviewed, or blocked. Training or safeguarding checks may still prevent work from starting even after documents are received.

Should I put passwords in a volunteer handover document?

No. Ask the authorized administrator to provide appropriate access through approved systems and manage the departing person's access under organizational policy. Record whether access is confirmed, not passwords or recovery codes. Never share someone else's login, copy sensitive records into personal accounts, or bypass restrictions because a deadline is approaching.

What happens if no replacement volunteer is available?

The responsible coordinator should identify urgent commitments and decide whether to delegate, reduce, or pause the work within their authority. Record unassigned items explicitly. Do not presume the departing volunteer remains responsible indefinitely or leave unnecessary access active. Safety-critical work still requires the appropriate trained, checked, and authorized people.

Should the departing volunteer delete all project records?

No. First follow the organization's authorized transfer and retention process. Required records must not be destroyed as a general cleanup step, and unnecessary personal copies should be handled through approved disposal procedures. Ask the responsible data lead about sensitive information and preservation requirements; seek qualified privacy or legal advice where needed.