Handing over a role so it does not die with you

Ask most volunteer organisations where their institutional knowledge lives and the honest answer is: in three people's heads, and one of them is thinking about stepping back. The treasurer knows which members pay from their spouse's account. The events person knows which venue will hold a booking without a deposit and which one will not. The secretary knows why that clause about proxy votes was added in 2021. None of it is written anywhere.

So every handover in a volunteer organisation is a small extinction event, and the successor spends their first year rediscovering things that were already known. The good news is that the fix is not documentation in the corporate sense - nobody is going to write a manual. It is a handful of habits that make a role transferable while you are still doing it.

Write down only what is not obvious

The instinct when handing over is to document the process, which produces a long file describing things anyone could work out, while omitting the actual value.

What matters is the stuff that is not deducible. Not "send the renewal reminders" but "send them in the first week of the month, because people are paid at the end of the previous one". Not "book the hall" but "ask for Pak Yusuf, and if he says the hall is booked, ask about the small room, which is not on the online calendar". Not "chase unpaid members" but "Ibu Sri always pays late and always pays, so leave her alone until March".

That kind of knowledge is a page, not a manual, and it is worth more than any process document. A useful exercise: over one month, every time you do something in the role that required knowing something, write the one line that would have saved a newcomer the trouble. At the end of the month you have the handover document, and it took no dedicated effort at all.

Share the access now, not at the handover

The most common handover failure is not knowledge, it is access. Passwords, the bank login, the domain, the email account, the file where the member list lives, the admin rights on the group chat. A great deal of it sits with one person, sometimes attached to their personal email, occasionally on a phone that is about to be replaced.

Fix this while nothing is going wrong. Every important account should be reachable by at least two people, and it should be in the organisation's name rather than an individual's. That means an organisation email address rather than someone's Gmail, and a shared record of where things live. It takes an afternoon and it prevents the specific disaster where a committee member leaves on bad terms, or falls ill, and the organisation cannot get into its own accounts.

Systems built for organisations help here, because access is a role you grant rather than a password you share - which means removing someone is a click rather than a change-every-password scramble. Our piece on moving off the spreadsheet covers that shift.

Let them do it while you are still there

A handover meeting where you explain the role for two hours transfers almost nothing. People learn a role by doing it badly once with someone to ask.

So overlap deliberately. Have the successor do the next cycle - the next renewal run, the next event - while you are still around and available, rather than explaining it and then leaving. You will be tempted to step in when they do it differently. Do not, unless it is going to cause real harm. A role performed slightly differently by someone who owns it is far more durable than one performed exactly your way by someone following instructions.

One cycle is usually enough. Two is generous. Six months of shadowing is not generosity, it is a failure to actually leave.

Hand over one role, not everything you accumulated

Long-serving volunteers accumulate. You joined to do the accounts and now you also run the website, hold the storeroom key, and answer the general email address, because at some point each of those things needed doing and you were there.

That accumulation is precisely why nobody wants your job. Before handing over, separate what you do into the actual role and the things that simply stuck to you, and hand those out to different people. A treasurer's role that is genuinely about the money will find a taker. A treasurer's role that includes the website and the keys will not, and the vacancy will sit open while you carry on doing it, slightly resentfully, for another year.

Leave properly

The last part is the hardest for people who care about the organisation. Once you have handed over, actually go. Stay available for questions, and stop having opinions in public about how the role is being done.

A predecessor who lingers - who answers questions that were addressed to the successor, who comments on decisions, who is still the person members instinctively ask - prevents the new person from ever fully holding the role. Members keep going to the old contact, the new one never quite establishes themselves, and when they get frustrated and leave you are back where you started, having never really left.

Tell the membership plainly who does this now, redirect anyone who comes to you, and let them do it their way. Our guide on managing volunteers covers the wider question of building an organisation where roles change hands routinely rather than as a crisis.

The version that works

An organisation where handover is easy is not one with better documentation. It is one where more than one person can get into every account, where the odd non-obvious knowledge is written down as it comes up, where roles are small enough to be attractive, and where the person leaving actually leaves. None of that takes a project. All of it has to be done before you need it, which is why most organisations only learn it the hard way.