Volunteer background check expiry tracker for grassroots clubs
Problem
Whether a coach or parent-helper holds a valid background check lives in a spreadsheet tab, a paper certificate photocopied three years ago, or the volunteer coordinator's memory of who applied last. Renewal dates are not tracked against a calendar; nobody notices a check has lapsed until someone asks, usually after the fact. Team sheets get built on a Friday night in the group chat, adding whichever parent has offered to help run the line, with no check against whether that person's clearance is still current. When the volunteer coordinator or welfare officer changes, the record of who is due for renewal and who is currently unchecked often does not transfer with them, and the club is left assuming everyone already on the list is covered.
Product idea
A workflow that holds one record per volunteer role requiring a background check: check reference, date issued, expiry, and status. It sends renewal reminders at fixed intervals before expiry, escalating from the individual volunteer to the age-group manager and then the welfare officer if nothing is actioned. When an age-group manager builds a team sheet, anyone whose check has lapsed or is not on file shows as flagged rather than being silently included, and adding them requires a welfare officer or designated deputy to confirm an override. It produces a compliance register on request, for when a governing body or insurer asks who is currently cleared. It does not perform or verify a check itself.
Who it is for
Welfare officers who own safeguarding compliance, club secretaries who answer to the governing body, volunteer coordinators who recruited the person in the first place, and age-group managers who build team sheets.
Possible first version
A spreadsheet import of volunteers, roles and check dates, with automated email reminders at set intervals before expiry escalating to the welfare officer if unactioned. A status dashboard shows valid, expiring and lapsed per volunteer. Age-group managers see a flag against anyone not cleared when building a team sheet, with a manual override that records who approved it and when. Out of scope for version one: no direct connection to the Disclosure and Barring Service, Disclosure Scotland or AccessNI checking systems, and no automated verification that a submitted certificate is genuine. Check dates are entered by hand from the physical or digital certificate.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Welfare officer, Club secretary, Volunteer coordinator, Age-group manager
- Relevant to
- Academy & youth, Federation / governing body, League office
- Systems in play
- Messaging groups, Membership and subs collection tools, Shared calendars
- Product framing
- Automate a workflow
Questions we get asked
What do we need to have in place before this is any use to us?
A list of volunteers in roles that require a background check, the date each check was issued or last confirmed, and who currently owns chasing renewals. Without that starting list the tracker has nothing to track, and pulling it together is usually the piece of work clubs have been putting off. Version one imports from a spreadsheet, so the list can be built in whatever format the welfare officer already has it in rather than waiting for a clean data source.
Our welfare officer already keeps a spreadsheet for this. Why change it?
A spreadsheet only works while one person remembers to open it and check it against the fixture list every week, and that stops working the moment they are on leave or the role changes hands. This does not replace their record of who is checked; it takes over the two things a spreadsheet cannot do on its own, sending reminders before a certificate lapses and flagging an unchecked volunteer at the point a team sheet is built, which is when it actually matters.
Does this verify a background check itself, or check with the Disclosure and Barring Service directly?
No. It does not call the Disclosure and Barring Service, Disclosure Scotland or AccessNI, and it does not confirm that a certificate is genuine. It tracks the dates a person enters after seeing the physical or digital certificate, so its accuracy depends on someone updating it when a renewal comes through. That is a deliberate limit for the first version rather than a gap to be quietly filled later, and clubs should keep their existing verification process exactly as it is.
What happens if a flagged volunteer is the only person available for Saturday's match?
The tool blocks the routine path, not the decision. Adding a flagged volunteer to a team sheet needs a welfare officer or a named deputy to confirm an override, and that confirmation is recorded with who approved it and when. If nobody is available to approve it, the person should not be rostered, and that is a staffing problem the tool makes visible rather than one it solves. It does not find a replacement volunteer for you.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in Grassroots, community & youth sports
- Away fixture transport matching for grassroots clubsA workflow that matches players needing a lift to an away fixture with parents offering a seat, replacing ad hoc requests in the group chat.
- Club compliance register for insurance, certificates and affiliationsA single register that tracks every club-level obligation with an expiry date, an owner and evidence, so nothing lapses when the volunteer who knew about it moves on.
- Matchday squad eligibility gate for grassroots clubsA workflow that checks every name on a weekly team sheet against consent, medical and background check records before it can be finalised, and logs any override to the welfare officer.