A volunteer project handover: deliverables, owners and open questions

Published 2026-10-25 · Practical guide
By the Nakhweh independent editorial desk

A volunteer project handover needs more than a folder full of files. The next volunteer also needs to know which version to use, what remains unresolved and who can make the next decision. A short handover can make those boundaries visible without turning a departing volunteer into permanent support.

This guide is for transferring a small, non-sensitive community project. If you are still defining the work, start with the volunteer-project brief. Bring its agreed deliverable into the handover so the recipient can compare what was requested with what is actually ready.

Download the plain-text handover template or copy the fields below. The seed-library example is fictional; it demonstrates the template and is not a report of work performed by this site.

Separate the result from the remaining work

Begin with the project's name, the version of this note and an “information current as of” date. Write one sentence describing the agreed outcome. Then give each deliverable one of three plain labels: ready for review, accepted, or unfinished. “Accepted” means that the recipient has explicitly agreed to take it over; sending an email or uploading a file does not establish that agreement.

Record where the deliverable is stored, what it contains and any known limits. Link to the maintained copy rather than attaching another version to every message. If a document needs restricted access, identify the person or role that can grant it through the organizer's approved process. Do not paste passwords, private participant lists or sensitive case notes into a general handover.

Give every open item an owner or an honest gap

An open item needs a concrete next action, an agreed owner and a review date. “Someone should follow up” leaves all three missing. If nobody has accepted responsibility, write “unassigned—organizer decision needed.” Do not fill the gap with a volunteer's name without their agreement.

Keep a decision separate from a task. For example, “organizer decides whether to print labels” is a decision; “prepare the approved label file” is a task that depends on it. State that dependency so the next person does not mistake an unresolved choice for permission to proceed.

Worked example: a seed-library catalogue

Imagine that two volunteers agreed to catalogue donated seed packets, but not to make planting or food-safety recommendations. These invented roles and filenames show how a short handover could read:

Outcome: a catalogue of the packets present at the session, with readable packet labels transcribed and uncertain entries marked for review.
Deliverable: catalogue.csv, version 1, ready for review. The file index identifies its approved shared-folder location; it contains no donor or recipient details.
Limit: the catalogue records the packet labels. It does not verify the contents, germination rate or suitability for a particular use.
Open item: three labels are unreadable. The organizer role agrees to decide whether those entries remain excluded from the public list before the next catalogue release.
Dependency: printing shelf labels is paused until that decision is recorded. No printing volunteer has been assigned yet.
Transfer check: the receiving catalogue volunteer opens the file from their own approved account, identifies the uncertain entries and explains where the organizer's decision will be recorded.
Acceptance: pending until the recipient records the version received and any exceptions. A successful file download alone does not close the open items.

The important distinction is between accepting custody of the catalogue and declaring every catalogue entry complete. The recipient can take over the maintained file while keeping the unreadable-label decision visibly open.

Use a short recipient walkthrough

Ask the receiving person to locate the maintained file, open it with their own authorized access and describe the next unresolved action in their own words. Check the link together. If it fails, record the access issue and its owner instead of sharing an account or marking the handover complete.

Then record the recipient's acceptance, exceptions and review date. Agree whether there will be a limited clarification period, such as one scheduled check-in, and what the organizer will handle after it ends. The arrangement should fit the volunteer's actual availability; the template does not impose an obligation to remain available.

Copy these fields

Project; note version; information current as of.
Agreed outcome; scope exclusions.
Deliverable; maintained location; version; status; known limits.
Open item; next action or decision; dependency; agreed owner or unassigned; review date.
Access issue, if any; approved access manager; resolution owner.
Recipient walkthrough outcome; acceptance or exceptions; date.
Clarification boundary; next review; organizer responsible after closure.

Only include information the recipient needs and is authorized to receive. Follow the organizer's records, privacy and safeguarding procedures for the activity. This lightweight template is not a substitute for those procedures or for requirements in the relevant jurisdiction.

Why this structure, and what it cannot prove

Volunteering Australia's National Standards for Volunteer Involvement emphasize documented responsibilities and roles, appropriate volunteer records and information handling, support, and review. Those principles informed this guide. The template, its three status labels and the walkthrough are editorial suggestions; the Standards do not prescribe this particular handover form, and using it does not establish compliance or certification.

A filled form also cannot prove that a project succeeded or that a recipient understands every task. Use the walkthrough to expose missing information, then revise the handover. Ask the recipient at the next review what was difficult to find; that is a specific improvement to make before the next transfer.

Independent editorial guide, separate from the historical Nakhweh organization. Sources checked 24 October 2026. No current volunteer placements, organizational affiliation or first-hand project experience are claimed. See the editorial desk's source and correction methods.