SportsFirst

Safeguarding check verification at the accreditation desk

Operational appWorkflow application3-5 week first releaseVerify or inspectPrototype-ready

Problem

Safeguarding checks for contractors, volunteers and academy staff are verified once at onboarding and recorded on a tab in an HR spreadsheet that reception cannot see. Months or years later the same person walks up to the accreditation desk for a matchday or training pass, and whoever is issuing it has no way to know whether that check is still current, or whether it was ever reviewed since. The pass gets issued anyway, because turning away a familiar face with a queue building behind them feels unreasonable, and because there is no screen in front of the desk saying otherwise. When a safeguarding officer needs to establish who had verified access to young athletes on a given date, the answer usually comes from phoning HR, reception and front-of-house in turn, and often lands on 'we assumed it was fine.'

Product idea

A verification screen built into the point where passes are issued, not into HR. The accreditation manager or reception lead searches the person by name, sees their safeguarding check status and the date it was last confirmed, and a clear flag if a review is overdue. Issuing a pass to someone flagged overdue requires a named sign-off and a typed reason, not a silent override. Every check, and every override, is logged with who verified it and when. The safeguarding officer gets a queue of overdue reviews to work through rather than having to ask around after the fact. It does not decide who passes a safeguarding check. It only makes sure the status was looked at before a door opens.

Who it is for

Accreditation managers and reception or front-of-house leads issuing passes day to day, sponsored by the safeguarding officer who needs proof a check happened, not just that one once did.

Possible first version

A single desk screen with a name search against a roster uploaded as a CSV: name, role, safeguarding check date and review interval. Searching a name shows current status; an overdue result forces a named sign-off with a reason before the entry is marked issued, and every check is logged. A daily export lists overdue reviews for the safeguarding officer. Version one has no live connection to the HR system, the DBS (Disclosure and Barring Service) checking service, or the accreditation platform: the roster is refreshed by re-uploading a CSV, and pass issuance itself still happens wherever it happens today.

Build classification
Workflow application
Rough effort
3-5 week first release
Roles involved
Accreditation manager, Reception and front-of-house lead, Safeguarding officer
Relevant to
Professional club, Venue & stadium operator, Academy & youth, Federation / governing body
Systems in play
HR and contractor records, Accreditation platform, Spreadsheets
Product framing
Verify or inspect

Questions we get asked

What do we actually need ready before this could be tried?

A CSV listing who needs a safeguarding check, their role, the date the check was last confirmed, and how often it needs reviewing under your national governing body's safeguarding policy. If that list does not already exist in one place, pulling it together is the real first project, and it is worth doing whether or not this tool ever gets built.

Does this replace our HR system or the DBS check itself?

No. It does not run a DBS (Disclosure and Barring Service) check or decide whether someone passes one; that stays with HR and your national governing body's safeguarding policy. It only makes that outcome visible at the point a pass is issued, which today usually sits in a different building and often a different week from where the check was done.

Our desk is already slow on a matchday. Won't this add a step?

Yes, honestly: it adds one search and one glance at a status field, which costs seconds when everyone is current. Where it costs real time is the overdue case, and that is deliberately the point rather than a flaw. If overdue reviews are common enough to be a problem at the gate, the fix is upstream in HR scheduling, not removing the check from the desk.

What happens if the desk loses signal during a busy kickoff?

The roster and log need to work from a device that can go offline, since a gate on a busy day is exactly where connectivity drops. Entries queue locally and sync once reconnected, with a clear indicator of what has not synced yet. It does not silently wave overdue passes through because the screen could not reach the server; that behaviour would need to be a deliberate decision agreed with your safety officer, not a default.

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 it

More in Security, identity & accreditation