The Committee Handover Problem: Keeping Club Knowledge When Volunteers Move On

Somewhere in Britain this spring, a boat club will hold its AGM, present a bottle of something decent to a retiring honorary secretary, and lose ten years of operational memory before the chairs are stacked. Nobody plans it that way. The knowledge simply lived in one person's inbox and one person's head, and it walked out with them.

Anyone who has served on a committee will recognise the shape of the problem. The membership list is a spreadsheet on a laptop. The engine service history is a run of emails from the marine engineer, sent to a personal address. The reason the club insists on twenty-four hours' notice for cancellations is remembered by exactly one member, who is moving to Shropshire in May. Ask where anything lives and the honest answer is a person, not a place.

What actually has to survive a handover

The list is shorter than it feels. Four things matter, and most of the rest can be rebuilt in a season.

• Member records. Names, contact details, joining dates, qualifications, what has been paid and what is owed, and any consent members have given for how the club contacts them.
• Fleet history. What was serviced and when, which faults keep coming back, which boat drinks fuel, which engineer to call and which to avoid.
• The financial trail. Who was invoiced for what, which fuel sessions have been billed, and enough of a record to answer a query from eighteen months ago.
• The why behind the rules. Not just "members may hold two future bookings" but the argument that settled it, and the mess that prompted it.

That last one is the most commonly lost and the most expensive to lose. Rules without their reasons get relitigated. A new committee, faced with a rule it cannot explain, will either scrap it and repeat the original mistake or defend it badly and lose the argument at the next AGM.

Does the record belong to the role or the person?

Apply that question to everything the club keeps. A minute book in the commodore's loft belongs to the person. So does the spreadsheet on the treasurer's laptop, and so does every service quote sitting in a private mailbox.

Paper fails the test slowly: it survives the handover but not the house move, the loft clearance or the damp. Personal email fails it instantly. When the account holder stands down, the polite ones forward a few threads; the rest simply stop replying. Either way the club can no longer search its own history, and under data protection rules it should be uncomfortable that member details sit in a former officer's personal account at all.

Shared systems pass. A role-based address (secretary@ rather than someone's own email), a drive the committee controls, and club software where each officer signs in under their own role — these hold records that stay put when people move on. The person changes; the member list, the maintenance log and the audit trail do not.

The two-season rule

Here is a working standard for any committee that wants to know where it stands. Could a capable member, starting cold, run the club for two full seasons using only what is written down and stored where the committee can reach it? Not brilliantly — competently. If the answer is no, list what they would get stuck on. That list is your handover gap, and it is worth closing while the people who hold the answers are still around and still willing.

A practical handover pack covers six things:

1. The rules as actually applied, with a line of reasoning against each one and the date it was last reviewed.
2. The club year: lift-in and lift-out, insurance renewal, safety inspections, the AGM cycle.
3. An access register: every account the club holds, who can get in, and how access transfers. No account should have a single keyholder.
4. The fleet file: service history, known quirks, supplier contacts.
5. The money: what members are charged, how fuel is billed, where the records live.
6. A who's who: the engineer, the harbourmaster, the insurer, the neighbour who complains about the car park.

Most of this already exists in fragments. The work is not writing it; it is gathering it into something the committee owns rather than something scattered across five inboxes.

Succession is a retention problem

Clubs tend to treat handover as an administrative chore. It is closer to a recruitment issue. Members watch what committee roles cost the people who hold them, and a role that visibly runs on one exhausted volunteer's private systems looks like a life sentence. Nobody steps forward for that. Meanwhile the incumbent, unable to leave without the place wobbling, stays on past the point of enjoying it. That is how clubs end up run by tired people.

Documented rules and shared records reverse the picture. This is, quietly, one of the better arguments for keeping club administration in a shared system rather than a drawer of personal accounts. Software such as Nauticore holds member records, booking history, boat issues and fuel billing in one place the club owns, with separate roles for the secretary, treasurer and engineers — when an officer stands down, they stop signing in and the records stay exactly where they were. But the principle matters more than any product: records belong to the role.

The retiring secretary has earned the bottle and the round of applause. What they should not have to hand over is their inbox. Get the club's memory out of personal accounts while it is still a tidy job, and the next AGM changes nothing but the names.