Running clubs depend on volunteers, and sooner or later every committee role changes hands.
A chair reaches the end of their term. A membership secretary needs more time for family commitments. A treasurer moves away. A communications volunteer decides they would rather return to simply enjoying their club runs.
None of this is unusual.
The problem comes when everything that person knows leaves with them.
Important dates live in somebody’s memory. Membership records sit on a personal laptop. Website access belongs to an old email address. Nobody else knows when the venue invoice is due or how the weekly update is produced.
A good committee handover protects the club from that disruption. It gives the incoming volunteer enough information, access and confidence to continue the role without having to rebuild everything from scratch.
It also allows the outgoing volunteer to step away properly rather than remaining the club’s unofficial help desk for the next two years.
Why Running Club Committee Handovers Often Go Wrong
Most poor handovers are not caused by people being unhelpful.
They happen because volunteers are busy.
Someone announces that they are stepping down, the AGM approaches quickly and everyone assumes there will be time to explain the role later. A few passwords are shared, a folder is passed across and the new volunteer is told to get in touch with any questions.
That may be enough for the first week.
Then renewal season begins.
A venue asks for updated information.
The club’s governing body sends an important deadline.
A member asks a question that only the previous volunteer knows how to answer.
The incoming committee member is left searching through old emails and trying to understand decisions made years earlier.
A proper handover should transfer more than documents. It should transfer understanding.
Start the Handover Before the Role Ends
The best handovers begin as soon as somebody confirms they will be stepping down.
Do not wait until their final committee meeting.
Ideally, the outgoing and incoming volunteers should have some overlap. Even a few weeks can make a significant difference because the new person can observe real tasks rather than only reading instructions.
For example, a membership secretary might show their replacement how they:
- Review new applications
- Update member statuses
- Check renewals
- Respond to common questions
- Prepare membership figures for meetings
- Handle former or inactive members
- Store relevant records
Watching one genuine renewal or enquiry being handled is often more useful than a page of abstract instructions.
Where overlap is impossible, arrange at least one dedicated handover meeting rather than trying to squeeze everything into the end of a normal committee session.
Begin With a Clear Responsibility Map
Before transferring accounts or files, clarify what the role actually includes.
Committee roles often grow gradually. A person who originally agreed to manage memberships may also have taken responsibility for welcome emails, guest runners, kit enquiries and website updates simply because nobody else was doing them.
The incoming volunteer needs to know which tasks officially belong to the role and which have been added informally.
Create a simple responsibility map covering:
| Area | Current responsibility | Future responsibility |
|---|---|---|
| Membership applications | Membership Secretary | Membership Secretary |
| Renewal reminders | Membership Secretary | Membership Secretary |
| New member welcome email | Membership Secretary | Communications Volunteer |
| Guest follow-up | Membership Secretary | Welcome Coordinator |
| Monthly figures | Membership Secretary | Membership Secretary |
| Website updates | Membership Secretary | Website Volunteer |
This exercise often reveals that one person has been carrying far more than the committee realised.
A handover is a good opportunity to redistribute work rather than automatically passing an overloaded role to somebody new.
Our guide on reducing running club committee workload explores how separating repetitive tasks and sharing responsibility can make volunteering more sustainable.
Document the Annual Club Cycle
Many committee jobs only happen once or twice each year, which makes them easy to miss during a handover.
Create a month-by-month overview of important tasks.
For example:
January
- Confirm annual race calendar
- Review member communication schedule
- Check venue arrangements
- Prepare affiliation information
March
- Begin membership renewal communication
- Review subscription fees
- Update website membership information
April
- Process renewals
- Confirm governing-body registrations
- Follow up outstanding member records
Summer
- Arrange club social events
- Review beginner or taster programmes
- Prepare race or event volunteers
Autumn
- Begin AGM preparation
- Request committee nominations
- Review policies and role descriptions
- Prepare annual reports
December
- Confirm holiday session arrangements
- Review emergency contacts
- Archive old records
- Plan the first committee meeting of the new year
Your club’s calendar will be different, but the principle remains the same.
The incoming volunteer should know not only what they need to do now, but what will arrive six months later.
List Every System, Account and Service
Running clubs often use more systems than they realise.
Create a complete list covering anything the role needs to access, such as:
- Club email account
- Website
- Domain registrar
- Hosting
- Membership platform
- Attendance system
- Payment provider
- Bank access
- Accounting software
- Governing-body portal
- Social media accounts
- Design tools
- Email marketing platform
- Cloud storage
- Online forms
- Venue booking portals
- Race-entry systems
- Shared calendars
- Messaging groups
For each system, record:
- What it is used for
- Who owns the account
- Which email address is attached
- Who currently has access
- Whether two-factor authentication is enabled
- Where recovery details are stored
- What level of access the incoming volunteer requires
Avoid passing around one shared password wherever individual user accounts are available.
Individual access makes it easier to understand who can see or change information, and it allows the club to remove an outgoing volunteer without changing access for everybody else.
Transfer Ownership, Not Just Passwords
Knowing a password does not always mean the club controls the account.
A website may be registered under a former volunteer’s personal email address. A social media page may have only one administrator. The recovery number for an important system may belong to somebody who left the committee three years ago.
Check ownership carefully.
Where possible:
- Use an official club email address
- Add more than one appropriate administrator
- Update recovery details
- Transfer ownership of files and folders
- Confirm billing contacts
- Remove obsolete personal details
- Store recovery information securely
This work may feel unimportant while everything is functioning.
It becomes urgent when the club is locked out of an account and the only recovery email belongs to somebody who is no longer involved.
Organise the Club’s Files
A handover should not involve sending the incoming volunteer a folder containing hundreds of unexplained documents.
Review the files first.
Create a clear structure such as:
- Committee meetings
- Membership
- Finance
- Policies
- Welfare
- Incidents
- Venues
- Events
- Communications
- Website and branding
- Governing-body information
- Previous annual reports
Archive material that must be retained but is no longer actively used.
Remove obvious duplicates.
Use file names that make sense to somebody other than the person who created them.
AGM-Minutes-2026.pdf is far more helpful than final-version-NEW-2.pdf.
The goal is not to make every historic document perfect. It is to help the next volunteer find current information without searching through years of clutter.
Write Down Recurring Processes
Every regular task should have a short explanation.
It does not need to become a complicated operations manual.
A useful process note might explain:
- When the task happens
- Why it matters
- Where the information comes from
- Which system is used
- Who needs to be informed
- What a completed task looks like
- What usually goes wrong
For example:
Sending the Weekly Club Update
When: Tuesday evening
Source information: Shared committee calendar and run-leader group
Platform: Club email system
Includes: Wednesday session, weekend runs, events, volunteer requests and member achievements
Approval: Urgent changes checked with the chair
Common issue: Late route changes received after the email has been scheduled
That is enough to help somebody understand the task without overwhelming them.
Clear processes also reduce the risk of one person becoming indispensable. Our article on preventing volunteer burnout explains why protecting volunteers from permanent, undocumented responsibilities matters.
Explain the Decisions Behind the Process
Instructions tell somebody what to do.
Context tells them why.
For example, your club may limit guest runners to a particular number of free sessions. The incoming volunteer should know whether that decision was based on insurance, club policy, venue capacity or simply committee preference.
A weekly email may go out on Tuesday because run leaders confirm their routes on Monday evening.
A membership field may exist because the club needs it for session planning.
Without that context, a new volunteer may remove or change something that appears unnecessary but serves an important purpose.
Include short notes explaining significant decisions, particularly where the reason is not obvious.
Record Important Relationships
Running clubs rely on relationships as well as systems.
The handover should identify useful contacts, including:
- Venue managers
- Governing-body contacts
- Local authority representatives
- Race organisers
- Coaches
- Welfare contacts
- Website or technical support
- Kit suppliers
- Photographers
- Local media
- Community partners
- Sponsors
- Accountants or bookkeepers
- Insurance contacts
Include the person’s role, contact information and the reason the club communicates with them.
Avoid vague notes such as:
Speak to Steve about the hall.
A better entry would be:
Steve Morgan, venue manager. Contact regarding Wednesday evening bookings, annual price review and access arrangements.
Handle Member Information Carefully
Committee handovers often involve personal member information.
Only transfer what the incoming volunteer genuinely needs for their role.
Do not copy entire membership databases onto personal devices simply because that is how the outgoing volunteer worked.
Check:
- Where member information is currently stored
- Who should have access
- Whether old exports still exist
- Whether personal copies need deleting
- Whether former administrators still have access
- Whether sensitive information is separated appropriately
- Whether the club’s agreed retention and data procedures are being followed
Welfare and safeguarding information needs particular care. It should not be included in a general handover folder or discussed with people who do not need access.
The incoming welfare officer may require a separate, confidential handover from the outgoing welfare officer.
Give Financial Roles Extra Structure
Treasurer handovers need careful planning because they involve club funds, payment access and formal records.
A financial handover should normally cover:
- Current balances
- Outstanding income
- Unpaid invoices
- Regular subscriptions
- Direct debits
- Payment-provider access
- Bank signatories
- Recent reconciliations
- Budget commitments
- Annual reporting deadlines
- Membership fees
- Event income and costs
- Refund procedures
- Financial records and supporting documents
Both volunteers should agree the position at the handover date.
Where the club requires multiple signatories or approvals, update these promptly. Do not leave a former treasurer with unnecessary access to banking or payment systems.
Arrange a Practical Walkthrough
A handover meeting should include more than discussing a document.
Ask the outgoing volunteer to demonstrate the real systems.
For example:
- Log in to the membership platform
- Show how a new member is added
- Find an attendance report
- Send a test communication
- Locate a policy
- Show where committee minutes are stored
- Demonstrate how an administrator is added or removed
- Explain how an incident record is handled
- Review the annual calendar
The incoming volunteer should complete some of these tasks themselves while the outgoing person is present.
Watching someone click through a system can create false confidence. Doing the task reveals what is still unclear.
Test Whether the Handover Has Worked
Before the outgoing volunteer leaves, ask the incoming person to complete a few realistic tasks independently.
Can they:
- Find the latest committee minutes?
- Identify the next annual deadline?
- Access the correct club email?
- Locate current member information?
- Contact an important venue or partner?
- Produce the report required for a meeting?
- Explain who else can access the system?
- Find the process for an accident or welfare concern?
Anything they cannot do highlights a gap in the handover.
This is not a test of the new volunteer. It is a test of the information and access they have been given.
Remove Outgoing Access Promptly
Once the handover is complete, review every system the outgoing volunteer could access.
Remove or reduce access where it is no longer required.
This may include:
- Website administrator accounts
- Membership systems
- Attendance records
- Email marketing
- Social media
- Shared storage
- Club email
- Payment providers
- Banking
- Committee messaging groups
- Welfare or incident records
Do not leave access active indefinitely simply because the person is trusted.
Removing access protects the outgoing volunteer as well as the club. They should not remain responsible for information or systems after their role has ended.
Where somebody remains involved in a different role, give them the access needed for that role rather than retaining their previous permissions.
Avoid the Most Common Handover Mistakes
Leaving Everything Until the AGM
A rushed conversation after somebody is elected is not a full handover.
Begin earlier and create overlap wherever possible.
Passing Over Unsorted Files
A huge archive without explanation transfers clutter, not knowledge.
Identify the current records and explain the structure.
Sharing Passwords in Messages
Use proper account access and secure recovery arrangements rather than leaving sensitive details in email or WhatsApp histories.
Assuming the New Volunteer Will Ask
People do not always know what they do not know.
Walk through the annual cycle and likely scenarios rather than waiting for questions.
Keeping the Outgoing Volunteer Permanently Involved
A short follow-up period is useful.
Expecting the former role holder to keep fixing problems indefinitely is not.
The handover should allow them to step away.
Copying the Old Role Exactly
The previous volunteer may have taken on too much.
Review the workload before passing it unchanged to somebody else.
Use a 30-Day Follow-Up
Arrange a short follow-up meeting around one month after the handover.
By then, the incoming volunteer will have encountered real tasks and developed more useful questions.
Discuss:
- What is working well
- What remains unclear
- Whether any access is missing
- Whether responsibilities need adjusting
- Whether further documentation is required
- Whether the outgoing volunteer can now step away completely
This meeting prevents small uncertainties from becoming long-term problems.
It also reassures the new volunteer that they are supported without making them dependent on their predecessor.
Running Club Committee Handover Checklist
Before confirming the handover is complete, check that you have covered:
- Role responsibilities
- Annual calendar
- Current priorities
- Outstanding actions
- Important contacts
- Club systems and accounts
- Account ownership
- Recovery details
- Individual access permissions
- Shared files and folders
- Current policies
- Recurring processes
- Committee records
- Membership information
- Financial information where relevant
- Welfare or safeguarding handover where relevant
- Governing-body requirements
- Venue arrangements
- Supplier relationships
- Removal of outgoing access
- Practical walkthrough
- Follow-up date
The checklist should be adapted for each role. A social secretary will not need the same handover as a welfare officer or treasurer.
How Running Club Check-In Can Make Future Handovers Easier
Handovers become harder when club information is scattered across paper registers, personal spreadsheets, private messages and individual laptops.
Running Club Check-In keeps attendance, member records, guest information, welfare actions, incidents and club reports within one connected platform. Appropriate volunteers can have their own access, making it easier to share responsibility and remove outgoing administrators when roles change.
That does not remove the need for a proper conversation or role-specific handover.
It reduces the amount of essential club knowledge that depends on one person’s private system.
You can explore the wider platform on the Running Club Management Software page or review all available Running Club Check-In features.
Key Takeaways
A successful committee handover transfers responsibilities, access, context and confidence.
Start early. Clarify what the role includes, document the annual cycle and explain recurring processes. Review account ownership, organise important records and give the incoming volunteer practical experience using the club’s systems.
Handle personal, financial and welfare information carefully. Remove outgoing access once it is no longer needed, and arrange a short follow-up after the new volunteer has settled into the role.
Most importantly, do not simply pass an overloaded role from one person to the next.
Use the handover as an opportunity to simplify processes, share responsibility and make volunteering more sustainable for the committee that follows.
