Committees know this and mostly deal with it by hoping. It is worth dealing with it in the six months before it becomes urgent rather than the six weeks after.
The indispensable volunteer is a risk, not an asset
This is the reframe that makes the rest of it possible, and it needs handling carefully, because the person in question has usually given the club a decade of their life and does not deserve to hear that they are a liability.
They are not. The arrangement is. A club where one person is the only route to something important is a club with a hole in it, and that is true no matter how good or how willing that person is. It also tends to be quietly unfair to them: the indispensable volunteer is usually the one who cannot take a season off, cannot get ill at a bad time, and feels obliged long after they stopped enjoying it.
The test, and it is worth actually running: pick a role. If that person were unreachable for three months starting tomorrow, what specifically stops? Not "it would be difficult" — what actually stops. Most committees find one or two answers that are genuinely alarming and several that turn out to be fine.
What actually gets lost
Very little of what disappears is a skill. Almost all of it is one of four things, and all four are writable down.
Access
Logins, keys, bank signatories, who the account is actually in the name of, the padlock combination, the email address the insurance renewal goes to. This is the most recoverable category and the most immediately painful.
Relationships
The farmer whose field you retrieve from. The engineer who does your annual and fits you in. The council contact. These are held by a person, not by the club, and they do not transfer automatically — but they transfer easily if somebody is introduced before the handover rather than after.
Undocumented arrangements
The member on a payment plan agreed three treasurers ago. The historic agreement about the trailer. The arrangement about winter storage that has never been written down because everyone involved knows about it. These surface at the worst possible moment, usually as somebody being chased for money a previous committee agreed to waive.
The reasons
The most valuable and the most often lost: why things are done the way they are. Why the launch point is at that end. Why that field is not used for retrieves. Why the club stopped running a particular event.
A new committee that does not know the reasons will eventually re-litigate every one of them, and will occasionally rediscover the reason the hard way. A single sheet headed "things we tried that did not work, and why" is worth more than most policy documents.
Succession, in decreasing order of effect
- Name a deputy for every critical role. Not a successor, which sounds like a threat — a deputy, who covers when the main person is away. The covering is the training. It also means someone can take a holiday.
- Write the role down. Half a page: what the job is, what happens when, who to contact, where things are. Written by the person doing it, which is also the moment they discover how much of it was never written anywhere.
- Rotate the shadowing. Somebody else does the invoicing run once a quarter, with the treasurer watching. Twenty minutes of awkwardness buys a club a working fallback.
- Put the artefacts somewhere the club owns. Not a personal laptop, not a personal email account, not a phone. This is the least popular item on the list and the one that most reliably causes trouble later.
- Talk about terms. Not enforced limits necessarily, but a norm that a role is reviewed every few years gives a tired volunteer permission to stop without it being a resignation or a crisis.
Doing the handover itself
A handover done in an evening is a handover of the things that are easy to say. The ones worth having take a season.
- Overlap deliberately. The incoming person does the job with the outgoing one available for a few months. Nothing else surfaces the undocumented parts, because neither of you knows what they are until one of them comes up.
- Hand over during the quiet season. Taking over the treasury in April is materially harder than taking it over in November.
- Write the list, including the awkward parts. The treasurer's chapter has a worked version; every role has an equivalent.
- Introduce the relationships in person. One phone call each, before the handover, saying "this is who you'll be dealing with now".
When the person is not leaving well
Sometimes the handover is not amicable. Somebody has been asked to step back, or has fallen out with the committee, or is leaving with a grievance. This is common enough in volunteer organisations to be worth planning for and it is rarely written about.
Two things hold up in that situation. First, the artefacts should already live somewhere the club controls, which is not something you can arrange retrospectively in a bad week. Second, whatever the disagreement, the handover conversation is not the venue for it — separate them explicitly, even if that means a third person sits in.
And it is worth saying plainly: a decade of unpaid work deserves to be acknowledged properly even when the ending is difficult. Clubs are small and long-memoried, and how someone is treated on their way out is watched closely by everyone who might volunteer next.
The roles that genuinely cannot be split
Some cannot, and pretending otherwise wastes effort. A club with one instructor qualified to do something has a qualification problem, not a documentation problem, and the answer is to train somebody, which takes years and has to start early.
The useful move is to be honest about which category each role is in. Documentation fixes the knowledge roles. Only recruitment and training fix the qualification ones, and those are the ones committees leave until the person is already halfway out the door.
Where the record-keeping comes in. Roles held inside a system that the club controls, rather than in one person's habits, means a handover is a permission change and not an archaeology project — which is a large part of why GliderOps assigns roles rather than accounts. But the harder half of this chapter is not software. It is the sheet headed "why we do it this way", and nobody can write that for you.