.png)
BPSS is a baseline standard, but running it well is an operational discipline. In 2026, the teams that succeed are the ones that keep BPSS consistent across roles, hiring managers and case volumes, without letting checks stall in email threads or manual follow-up. BPSS is widely used in the public sector and beyond, and the core requirement is simple: apply the right checks with clear evidence and clear consent.
At a high level, BPSS comprises four core checks, plus the need to account for significant periods abroad and employment gaps. In practice, delivery tends to break down when teams treat these checks as separate tasks, rather than one joined-up workflow with standardised outcomes.
Employment history is where BPSS programmes most often slow down. The standard requires at least three years of history to be verified, and expects significant gaps to be understood. Many teams still default to traditional references, even though BPSS does not mandate references and they frequently introduce delays and inconsistency. In 2026, a growing number of organisations are treating digital, consent based employment verification as best practice, using Konfir to return consistent, decision ready evidence from trusted sources. The strongest programmes are explicit about which evidence routes they accept, when follow-up is required, and how they keep outcomes consistent across reviewers.
Confirming name, date of birth, address and National Insurance number sounds straightforward, but consistency matters. The challenge is ensuring evidence is captured in a repeatable way, and that reviewers can see what was verified without ambiguity.
Right to Work checks are often well understood, but the friction comes from process gaps: missing evidence, unclear ownership, and delays created when steps are repeated or handled in different places. In stronger programmes, Right to Work is treated as part of the same end-to-end journey, not a separate handoff.
Criminal record checking is a defined step, but operationally it still depends on clear consent capture and clear case notes, so teams can evidence the check was completed correctly and consistently.
One practical takeaway that matters across all four checks is governance. BPSS guidance distinguishes between mandatory, recommended and optional requirements, and teams need internal rules that map to that language so cases are handled consistently at scale.
