Recording a DBS Check Is Not the Same as Enforcing It

It is a Tuesday evening in September. Twenty eight juniors are on the pitch, three coaches are running the session, and one of those coaches is working with an enhanced DBS check that lapsed in March.

Nobody hid anything. Nobody cut a corner. The check was done properly in 2024, the certificate number was typed into a notes field on the member's profile, and a box on a compliance checklist was ticked. Then eighteen months passed, and there was nothing anywhere in the club's systems capable of noticing that the certificate had quietly stopped being current.

That is how safeguarding usually fails at club level. Not through negligence, and almost never through anyone deciding to skip a check. It fails because the record was made once and then nothing in the world was watching it.

Why the spreadsheet decays

Most clubs track this in a spreadsheet, and the spreadsheet is accurate on the day it is made. From then on it only gets worse. A new coach joins in November and gets added late. Somebody renews their first aid certificate and mentions it in passing at training rather than to whoever keeps the file. The volunteer who built the sheet stands down after the AGM, and the person taking over inherits a tab they did not design and are not sure they trust.

None of that is the real problem though, because you could keep a perfect spreadsheet and still end up with a lapsed coach on the pitch on Tuesday. The real problem is structural: the record and the rule live in different places.

The record is in the spreadsheet, or in a notes field, or in the secretary's inbox. The rule, the one that says an uncredentialed adult does not take a junior session, lives in somebody's head. Nothing connects them. So when a coach is added to a session, no part of the process consults the record, because nothing is capable of consulting it. A certificate number stored as free text has no expiry date attached to it, which means no software on earth can tell you it has run out.

Recording a check and enforcing it are two different jobs. Almost all club software does the first one and quietly leaves you to do the second one from memory.

Credentials that know when they expire

ClubPal has changed the first half of that. A qualification used to be a word typed into a box. It is now a record in its own right, with a page of its own at Admin > Membership > Qualifications.

You define what your club tracks once. The create form suggests the common ones, and deliberately not only the British ones: DBS Enhanced and DBS Basic, PVG for Scotland, AccessNI, Garda Vetting, Working With Children Checks, and SafeSport, alongside first aid certificates and coaching awards. ClubPal runs in twenty six countries, and a club in Dublin or Melbourne has exactly the same problem as a club in Doncaster with a differently named piece of paper.

Every record then carries an award date and an expiry date against the member holding it, which is the part that changes what is possible. Because the platform knows when something runs out, it can work out where each credential stands rather than waiting for somebody to remember. Five states cover it: Valid, Expiring soon, Expired, Renewing, and No expiry recorded for a record that arrived from an import without a date.

You set the warning window yourself, separately for each qualification, because a DBS check and a first aid certificate do not need the same amount of notice. And the dashboard opens on everything that is not currently valid, sorted by whatever lapses first, filtered by qualification or by state, and it exports. Somebody looking at that list on a wet Sunday afternoon can see the club's whole safeguarding position in about fifteen seconds.

One small thing that matters more than it sounds: qualifications are no longer editable by members on their own profile page. A record that now carries dates is not something a person should be setting for themselves.

The half everybody skips

Knowing a certificate has lapsed is worth something. Stopping the lapsed coach walking onto the pitch is worth considerably more, and it is the half that club software almost never does.

A ClubPal session can now carry its own rules for who may be added to it as a coach, separate from the rules about who may book on to it as a participant. Require a qualification, an age range, membership of a group, or a value in a profile field. Age on its own answers "coaches must be over 18" with nothing else to configure.

Two details do the actual work here.

The first is that the check runs wherever a coach is added. Not on the sign-up form, where a determined administrator can go round it, but in the booking layer underneath, so a committee member adding somebody by hand at nine o'clock the night before is held to exactly the same rule as a coach adding themselves. Adding several people at once tells you which of them were refused and why. There is no back door, which is the entire point: a rule with an override that anyone can reach is a suggestion.

The second is that the check runs against the date of the session rather than against today. A certificate expiring in November is refused now for a session in December, while there are still eight weeks to get the renewal in, instead of failing on the night when the only remaining options are bad ones. Assigning a session leader is checked the same way when the session is saved.

Cover, while there is still time to fix it

The other way a junior session goes wrong is more mundane. Nobody is uncredentialed, there are simply not enough adults, and no one finds out until 6.15pm.

Set a ratio, one coach for every so many participants, and the number of coaches a session requires works itself out as bookings arrive. It never drops below the fixed minimum you set, and if an administrator has decided that one particular night needs four coaches, four is what it needs, whatever the formula says.

Admin > Sessions > Cover then lists every session in the next 28 days that is short of coaches, or whose coaches will not hold what the session requires on the day it runs. One row per occurrence, soonest first, showing cover against required, the expected attendance, and the reason for the gap. Twenty eight days is not arbitrary: it matches the default booking window, so a problem surfaces while the session can still be filled.

Expected attendance is the detail worth understanding. It is the average of confirmed bookings across the last six times that session ran. A ratio can only follow the bookings actually taken, so a session three weeks out with six of its usual twenty four booked needs one coach on paper and looks perfectly covered. Reading the expected number beside the required one shows you the real gap while it is still cheap to close. And a Review cover tile appears on the admin dashboard when sessions need attention, staying hidden when none do, so somebody actually looks.

What this does not do

Some honesty about the edges, because safeguarding is the wrong subject for overselling.

The ratio is advisory. It sets the required number, drives the warnings and fills the cover list, and it never turns a member away or strands a booking that is already confirmed. If you want a hard block on participants, that is what booking limits are for.

Ticking Renewal in progress on a lapsed certificate turns it amber rather than red, so a dashboard full of known-in-hand renewals stays worth reading. It does not satisfy an eligibility rule. An expired certificate is expired, whatever is in the post.

And ClubPal tracks credentials, it does not issue them. Running the check, verifying the certificate and holding the safeguarding policy remain your club's job and your governing body's. What has changed is that the answer now lives somewhere the software can act on, instead of somewhere a person has to remember to look.

Where to start

Half an hour at Admin > Membership > Qualifications defining what your club tracks, then adding the records you already hold, gets you the dashboard. Adding a coach eligibility rule to your junior sessions gets you the enforcement. Setting a ratio on the sessions where cover is a safety rule rather than a preference gets you the cover page. Sessions with no ratio behave exactly as they did before, so there is no need to do all of it at once.

The safeguarding feature page has the overview. The step by step is in the member qualifications documentation and the coaches documentation.

The Tuesday evening in September is the point of all of it. Not the audit, not the affiliation form, and not the policy document nobody opens. Just knowing, on the night, that the three adults on the pitch are the three adults who should be there.