Dental Locum Onboarding: Simplify Compliance | Airlocum

CQC inspectors treat locums as part of your workforce. When an inspector asks how you verify competence and confirm registration for temporary staff, they expect a documented, repeatable process: how the locum was inducted into your infection control procedures, safeguarding policies, and emergency protocols. A verbal briefing before the morning list is not a process. A practice that cannot demonstrate a consistent onboarding procedure for locum staff has a dental compliance gap, regardless of how strong its permanent-staff records are.

The compliance gaps most practices don't find until inspection day

The most cited failing in CQC dental inspection reports is not a clinical error. It's a governance breakdown. Policies exist but haven't been reviewed in two years. The training matrix shows a completion date but no renewal reminder. Meeting minutes record a discussion but no assigned action, no deadline, and no follow-up. These are structural problems, and the fix requires structure: a named compliance lead, a live action tracker, and a policy register with review dates that someone actually checks before the next inspection arrives.

Infection control failings follow close behind. Inspectors routinely find daily cleaning checklists that were signed but not completed, steriliser cycle logs with gaps, and washer-disinfector maintenance records that cannot be located. The issue is rarely that the practice lacks a procedure, it's that implementation isn't consistently documented. A dental compliance audit should test whether staff are following the procedure, not just whether the procedure exists on a shelf somewhere.

Recruitment and competency documentation failures appear repeatedly across inspection reports, and for locum staff the risk is compounded. There is no HR file built up over time. Each locum engagement needs its own discrete evidence record showing which checks were completed, when they were completed, and where the documents are stored. Missing DBS certificates, references that were never requested, professional registrations that weren’t verified at source. These are findings that inspectors document, and they reflect on the practice's well-led rating, not the locum's.

What to verify before a locum's first appointment

The goal of a locum onboarding process is simple: produce a complete, named evidence file for every locum engagement before the locum treats a single patient. This means gathering documents before the appointment, not on the morning of. When you confirm a locum booking, the pre-arrival checklist goes out at the same time.

We keep one canonical version of the full pre-engagement checklist - with each item marked as a legal requirement, a CQC expectation or sensible practice - in our companion guide, In-house team versus locum staffing [link]. In brief: verify GDC registration on the register itself, confirm indemnity covers the actual work being done, complete right-to-work and Enhanced DBS checks (with a barred-list check for clinical roles) before the first session, and hold evidence of hepatitis B immunity, CPD and mandatory training.

The locum declaration

Alongside these documents, every locum should sign a simple one-page declaration at the point of engagement. The declaration confirms that their GDC registration is current and unrestricted, their indemnity is valid for the work they will perform, they have no conditions on their practice that would affect their duties, and they consent to the practice retaining their documents for audit purposes. This is not a legal substitute for verification, but it creates a signed record that the locum asserted compliance at the point of engagement. It takes ten minutes to draft once, and you can reuse it for every engagement.

Every locum must have a named folder, digital or physical, containing all verification documents, the signed declaration, and a record of which sessions they worked. If an inspector asks for evidence of workforce compliance on a specific date, you need to produce it within minutes. Retention periods vary by record type: decontamination logs should be kept for a minimum of two years in line with HTM 01-05, while some training records warrant longer retention. Follow your own document-retention policy alongside CQC guidance, and specify periods for each record category rather than applying a single blanket rule.

How Airlocum takes the document burden off your desk

Airlocum is connected live to the GDC register: every locum’s registration is verified at sign-up and then automatically re-checked every 28 days, so a lapsed or restricted registration is caught between bookings rather than discovered after one. An in-date Enhanced DBS, indemnity cover and hepatitis B immunisation evidence are also verified before a locum appears in search results. The compliance check is not something you carry out after finding a suitable clinician, it is handled at the platform level before you make a booking. For a practice manager juggling HR, rotas, and clinical operations simultaneously, that removes the most time-consuming part of locum onboarding from your to-do list.

One check stays squarely on the practice side: right-to-work, because the statutory excuse only exists if the engaging practice carries out the check itself. Everything the platform holds - the Enhanced DBS, the indemnity certificate, the immunity evidence - is visible on each locum’s profile, so rather than take anyone’s word for it, open the profile, review the documents and save what your own file needs. The site-specific induction remains yours. What disappears is the chase for paperwork at 8pm the night before.

Each engagement through Airlocum generates a digital audit trail, recording which locum worked, on which date, which documents were verified, and when. For those managing dental compliance across multiple sites, this approach removes the reliance on individual site managers to maintain consistent records. The evidence is held centrally, consistently, and retrievable while the locum’s profile remains live.

One honest limitation is worth knowing. While a locum’s profile is live, every verified document on it can be pulled during an inspection in minutes. If a locum later closes their account and asks for their data to be deleted - their right under UK GDPR - that documentation goes with them. Your retention duty does not: CQC expects you to produce evidence for engagements two or three years back, regardless of where the locum went. So make saving the profile documents into your own locum file part of confirming the booking - it takes a minute. If you would rather not do it yourself, ask the team on live chat to email you copies of the locum’s certificates, or to arrange for the locum to bring paper copies to the shift. Whichever route you take, the evidence ends up where CQC expects it: in your file.

Practices that need to demonstrate supplier governance controls can contact the Airlocum team directly to review what documentation is held on each clinician profile and how the pre-verification process maps onto your existing compliance framework. The aim is to turn locum staffing from a documentation headache into a controlled, transparent process, though practices should satisfy themselves that platform-held evidence meets their own CQC obligations before reducing local verification steps.

Picking the right tools to stay inspection-ready year-round

A locum platform handles the compliance checks at the point of engagement. A separate governance platform handles your audits, policy library, and permanent-staff training records. These serve different purposes, and treating one as a substitute for the other creates gaps.

Dedicated dental compliance platforms

For practices choosing a dedicated dental compliance platform, the main options in the market include Dentistry Compliance, Dentistry Dashboard Practice Hub, and GoAudits for multi-site groups. Smaller practices may find iAuditor by SafetyCulture a workable entry point for audit checklists and basic document storage. Pricing for these tools changes regularly, so check each provider’s current pricing page before committing, figures published in articles can date quickly. These platforms manage audit dashboards, document control, policy libraries, and training matrices. They are governance tools, not staffing solutions, and they work best when the locum compliance piece is handled separately at the point of engagement.

The most practical setup for most practices combines a compliance platform for governance and permanent-staff records with a dedicated locum platform for pre-verified temporary staff. Trying to manage locum compliance through a general governance tool adds manual work and creates inconsistency across engagements. Using each system for what it was built to do is what keeps your inspection-readiness sustainable across both permanent and temporary workforces.

Keeping dental compliance continuous, not cyclical

The core message from CQC guidance is this: compliance is a continuous, documented practice, not a once-a-year folder review. The practices that perform well at inspection aren't the ones with the thickest policy manuals. They're the ones with a small, current system that demonstrates risk was identified, ownership was assigned, action was taken, and effectiveness was checked. That logic applies equally to your governance records and to your locum onboarding process.

Locum staffing adds a distinct layer of verification that many practices are still managing manually and inconsistently. The checklist above gives you a repeatable pre-engagement process. The declaration captures a signed record at the point of booking. Working with a platform like Airlocum means registration, DBS, indemnity and immunity checks are already handled before you select a clinician, so you can book with confidence rather than spending time chasing paperwork.

Practices that want to see it in practice can create a free account and open any locum profile to see exactly what has been verified - or ask the team on live chat how pre-verification fits into an existing inspection-readiness framework.