The Club Runs on More Than Goodwill: Building a Handover File That Survives the Seasons
Photo: IDF Spokesperson's Unit photographer, CC BY-SA 3.0, via Wikimedia Commons
Every community club has one. The volunteer who knows where the fixture cards live, which login opens the league portal, the mobile number for the safeguarding lead at the county football association and the fact that the away team's changing rooms are locked until 10:15. When that person steps down — or simply goes on holiday — the club discovers how much of its season was held together by memory and goodwill.
In business continuity circles this is called the 'bus factor': the number of people who would need to be unavailable before a project stalls. At a grassroots sports club, the bus factor is often one. One secretary. One treasurer. One person who knows the padlock code for the equipment container. That is not a criticism of those volunteers. It is a warning about how much we ask them to carry in their heads.
Why memory is not a plan
A club can survive a wet winter, a difficult fixture list and a shortage of referees. It struggles when the person who holds the keys, the passwords and the supplier history moves house or steps back. The fixtures get renegotiated by people who do not know the league's deadlines. The bank mandate takes weeks to update. The safeguarding contact list is out of date before anyone notices. None of this is dramatic. It is just the slow unravelling of a season.
Succession planning is not about forcing anyone out. It is about making sure that when a volunteer does move on, the club says thank you and keeps running. The tool for the job is refreshingly ordinary: a handover file.
What goes in the handover file
The file should be a single, shared document — or a small set of linked documents — stored somewhere the committee can access, not on one person's laptop. Keep it practical and short enough to be read. A good handover file covers six areas.
Governance and people. The club constitution, committee roles, meeting dates, the annual general meeting timetable, affiliation numbers and insurance details. Add a simple who-does-what list with names, roles and contact details.
Fixtures and facilities. League and cup contacts, fixture-card deadlines, pitch bookings, keyholders, alarm codes and risk-assessment paperwork. Include the small stuff: where the goal nets are stored, who opens the pavilion and which local supplier delivers the line-marking paint.
Safeguarding. The safeguarding officer's contact details, the county governing body's reporting route, training dates and the process for checking volunteers. Personal data and DBS details belong in a secure, access-controlled system, not in a shared spreadsheet. Record where those records live and who can access them, not the records themselves.
Finance. Bank signatories, the process for online banking, grant deadlines, subscription dates and a short supplier history. Do not store passwords in the handover file. Record which password manager the club uses and who holds the keys.
Communications. Access to the mailing list, website and social accounts, plus templates for the weekly digest, matchday notices and welcome emails. Note who owns each channel and who can post.
The calendar. A list of recurring tasks with months attached: affiliation in spring, kit order in summer, insurance renewal, grant applications, end-of-season awards. A calendar turns invisible knowledge into a plan.
Shadowing that transfers more than a folder
A handover file on its own is a filing cabinet. What makes it work is people learning alongside people. Build shadowing into the season rather than leaving it to the week someone resigns.
Name a deputy for each key role — not to undermine the current volunteer, but to give them cover and a break. Use a simple rhythm: watch one, do one, teach one. The deputy watches the secretary register a team, then does it with support, then explains it to someone else. Book a six-week overlap when a role changes hands. Add a short decision log to the handover file so that future volunteers know why the club chose a particular league, supplier or format. And review the file at the start of each season, when the fixtures are fresh and the committee is already thinking about the year ahead.
Lower the bus factor without creating a bureaucracy
You do not need a 40-page manual. You need a few habits. Use a two-person rule for critical systems: two committee members can access the bank, the website and the fixture portal. Choose a password manager and stop sharing logins by text. Write one-page role descriptions so that new volunteers know what they are taking on. Have a succession conversation at the annual general meeting, not in a crisis. And thank outgoing volunteers properly — a handover is much easier when people leave feeling valued rather than guilty.
A 30-minute start
This week, create one shared document and list the five systems that would cause the most disruption if only one person knew them. Name a deputy for each. Book one shadowing session before the next fixture. Set a review date for the end of the month. That is enough to start lowering the bus factor from one to two.
Clubs run on goodwill, but they should not run on memory alone. A simple handover file is how a community club says: the season matters, the volunteers matter, and the next person through the door will be able to find the padlock code.
