Notes for the Next Pair of Boots: A Handover That Belongs to the Hosts

Most placements end in a mild flap: a last shift, a rushed goodbye, a suitcase that will not close, and a vague promise to ‘send some notes’. Then you get home, life resumes, and the next volunteer arrives to find a cupboard labelled ‘misc’ and a host team too polite to say they could have used a page of plain English.

A handover notebook can fix that. But only if it is written for the hosts first and the next volunteer second. This is not your legacy document. It is a working bridge, and like any bridge it should be built with the people whose land it crosses.

Start with the host, not the notebook

Before you write anything, ask the host organisation what would actually help. Who will receive the handover? Will the next volunteer read it, or will a staff member brief them? Are there topics they would rather cover themselves?

That conversation matters for a very practical reason: the host owns the relationships, the routines and the decisions. A UK volunteer who has been on site for three months may know where the spare batteries live, but that does not make them the author of the project’s future. Write with permission, not assumption.

If you are handing over to a named volunteer, check whether they are happy to receive your contact details. If you are passing on a staff member’s mobile number, confirm that staff member is happy for it to be shared. Consent is not a bureaucratic faff here; it is the difference between a useful note and a small breach of trust.

What earns its page

A good handover is short enough to be read on arrival and specific enough to answer the questions nobody thinks to ask until day two. The useful material tends to be:

• Agreed contacts. The host coordinator, the site supervisor, the person who handles expenses, and the out-of-hours number if one exists. Only include people who have agreed to be listed.
• The rhythm of a normal week. Market day, school hours, when the office is actually open, when the team eats together, and which meeting is not worth rearranging your day for.
• Practical logistics. Travel from the nearest station, the reliable taxi firm, where to buy a SIM card, which gate is locked after six, and the fact that the kettle takes an age to boil.
• Local norms you were taught. Not gossip, not a list of ‘quirks’, but the small things a host explained to you: how to greet elders, when to remove shoes, how to ask for help without causing offence, and who to check with before taking photos.
• Current work status. What is finished, what is half-finished, and what is deliberately parked. Name the decisions that are pending and who gets to make them.
• Safeguarding and emergency information. Only the approved version, in the place the host wants it. Do not improvise a parallel safety file.
• Questions you wish you had asked. This is often the most generous page. It gives the next person permission to ask early rather than guess.

The test is simple: does this help someone do the work well and treat people well? If it only helps them understand your personal story, it can probably go.

What should never go in

Some things are not handover material, however tempting they are to include.

Leave out health details, family circumstances, immigration status, financial information, relationship gossip and any personal data about volunteers, hosts or community members that is not necessary for the role. UK GDPR does not stop being relevant because the notebook is paper or the placement is overseas. Basic decency applies too.

Do not pass on passwords, bank details, unredacted case notes, photos of people who have not agreed to be photographed, or a list of ‘difficult’ individuals. Do not write down a safeguarding concern as a notebook anecdote. If something needs reporting, report it through the host’s proper channel and let the people responsible decide what happens next.

Also leave out the tempting character sketch: ‘X can be tricky’, ‘Y is the real power behind the throne’, ‘don’t mention Z’. Even when it feels true, it plants a judgement before the next person has met anyone. If a relationship needs careful handling, describe the behaviour or the process, not the person.

A notebook template that will not outlive its welcome

Keep it to a few pages. A template like this is enough:

Placement and dates
Your role, dates, and the name of the host organisation.

Agreed contacts
Name, role, contact method, and a note that consent to share has been given.

Normal week
Days, hours, meetings, meals, days off, and the reliable way to travel between them.

Practical notes
Local transport, shops, SIM cards, keys, lock-up routine, expenses process, and anything that saves an hour of confusion.

Local norms I was taught
Short observations, attributed to the person who explained them, with a note that the next volunteer should keep asking.

Work status
Finished, ongoing, paused, and not started. Include who decides priorities.

Open questions
Things I never got a clear answer to, and who might know.

Safeguarding and emergencies
Only the approved information, in the format the host uses.

Handover meeting
Date, attendees, and what was agreed.

Sharing and deletion
Who holds the master copy, where it lives, and when local copies should be deleted.

That last line matters. A handover should have an owner and an end point. It is not a document that follows you home in three different inboxes.

Hand the authority back, not just the keys

The kindest thing a departing volunteer can do is make themselves unnecessary. That means introducing the next person to the host, not positioning yourself as the gatekeeper. Let the host brief them on priorities. Let the host explain the boundaries. Let the host decide what gets shared.

If you are asked to stay in touch, be honest about what you can offer. A monthly email is lovely. A vague promise of ‘ongoing support’ that quietly expires is not. And resist the language of ownership: ‘my project’, ‘my kids’, ‘my team’. You were a guest in someone else’s work. That is not a smaller role; it is just a different one.

Take home lessons, not people’s data

When you leave, take home the things that are yours: the skills you practised, the questions you now ask better, the reference you have agreed with the host, and the friendships that survive without a spreadsheet. Return borrowed documents. Delete local copies of contact lists and case notes. Ask before using any story or photograph in a blog, CV or after-dinner anecdote.

A handover notebook is not a monument. It is a courtesy: a brief, honest, consent-led set of notes that helps the next pair of boots find the kettle, ask the right person, and get on with the work. Write it for the hosts, keep it short, and then let it go.