When a Key Volunteer Leaves: A Continuity Plan for Clubs

The most dangerous sentence in a committee meeting is not “we have lost money.” It is “only Jamie knows how that works.”

Jamie may be the secretary who controls the club email, the treasurer who understands every payment reference, or the competition organiser whose personal laptop contains the only complete results archive. Nothing has failed yet. That is why the risk is easy to ignore.

A committee-proof club is not a club without valuable volunteers. It is a club where no volunteer has to be irreplaceable.

Separate the role from the person

Start by listing the functions that would stop if a key volunteer disappeared tomorrow. Include administration access, banking, membership records, competition setup, website control, venue access and communication channels.

For each function, record:

1. The role responsible.
2. A named backup.
3. The club-controlled account or storage location.
4. The last date both people proved they could use it.
5. The handover action required when an officer changes.

The phrase “club-controlled” matters. A secretary’s personal email address is not a club asset. Neither is a spreadsheet in a private cloud drive or a password known only to the chair.

Use addresses such as secretary@yourclub.org for durable roles, with access controlled by the committee. Keep recovery methods current. Appoint the replacement before removing the departing officer, especially after a contested election or an abrupt resignation.

ServeLeague supports multiple club administrators, so the practical rule should be at least two current administrators. That does not eliminate every recovery problem, but it removes the simplest single point of failure. The broader data ownership principles are useful when deciding which records the club itself should hold.

Make the handover a routine, not an emergency

Most handovers fail because they begin after the knowledgeable person has already left. Build them into the calendar instead.

At every AGM, ask each office holder to complete a short operational handover while they still hold the role. The incoming person should perform one real task, not merely receive a document. The new treasurer can reconcile a sample payment. The new league organiser can open a test session. The new administrator can sign in and find Club Settings.

The handover should explain decisions as well as buttons. Why are membership categories configured that way? Which bank reference format does the treasurer expect? Who has authority to finalize results? A screen recording can help with a complicated process, but it should supplement a written checklist, not replace one.

Keep the checklist short enough to repeat. A perfect 40-page manual that nobody updates is less useful than a two-page runbook tested every year. ServeLeague’s help centre can document product steps, while your club document records local policy, ownership and escalation contacts.

Continuity also depends on a portable copy of the club’s records.

Access continuity is only half the job. The committee also needs its own usable copy of the club’s data.

In Club Settings, an administrator can open Club Settings, choose Club data pack, then Download data pack. The download includes a readable club record, spreadsheet-friendly files, guidance about the format, and checksums that help reveal whether a file later changed.

The pack is designed to be portable and inspectable. It is not a promise that another system will import everything automatically. It is also not useful if nobody downloads it before access is lost. The platform and the administrator’s browser must still be available when the pack is created.

Set a standing instruction: download a pack after the final session of each competition and at least once per season. Store it in committee-controlled storage. Because it can contain personal, payment and competition data, restrict access and apply your retention policy. The club becomes responsible for every exported copy.

Then test one. Open the archive, inspect a player file, read the included guidance and find a recent result in the readable club record. A backup that has never been opened is an assumption.

For the broader ownership question, read Who Owns Your Club’s Data?. the published privacy information is also relevant when deciding where exports may be stored.

Run a ten-minute continuity check

Put this checklist on the AGM agenda:

• At least two current administrators can sign in.
• Durable roles use club-controlled email addresses.
• Departed officers no longer have access.
• Banking, website, venue and communication accounts each have a backup owner.
• A recent club data pack exists in approved storage.
• One committee member has opened and spot-checked that pack this year.
• Local runbooks name current people and current processes.
• The committee knows who acts first after an unexpected departure.

Do not wait for a volunteer to become “key” before doing this. The point is not distrust. It is kindness. Good continuity lets a tired volunteer step away without guilt, and lets the next person begin without archaeology.

A resilient club remembers the contribution of its volunteers without making its future depend on any one of them.