Supplying temporary staff into the NHS is one of the most compliance-intensive operations in UK recruitment. The requirements go beyond standard pre-employment checks — and they vary by trust, by role, and by framework.
For agencies operating at scale, this isn’t a compliance problem. It’s a systems problem.
What NHS compliance actually requires
Beyond the standard DBS, Right to Work, and reference checks, NHS placements typically require:
Occupational health clearance. Including immunisation records, fitness-to-work assessments, and sometimes role-specific screenings. These have different validity periods and different requirements by trust.
Mandatory training. Not just that training was completed — but that it was completed through an approved provider, covers the correct modules, and is within its validity window.
Framework-specific requirements. Agencies on NHS frameworks like HTE or neutral vendor arrangements face additional compliance layers: specific document formats, additional checks, and defined evidence standards.
The bottleneck problem
At low volumes, a compliance team can manage this manually. At scale — 50, 100, 200 candidates per month — the process breaks down.
Candidates wait days for compliance clearance. Placements are delayed. Revenue is lost. And the compliance team is permanently firefighting rather than managing.
Solving throughput without sacrificing standards
The answer isn’t hiring more compliance officers. It’s removing the manual steps that don’t require human judgement.
Document collection, database queries, expiry tracking, follow-up communications — these are execution tasks. They can be automated without touching the compliance decision itself.
When the system handles execution, the team handles exceptions. Throughput increases. Standards don’t decrease.