Driving licence checks: is three-monthly actually enough?

Ask an operator how often they check driver licences and most will say "every three months" without much hesitation. It's become the default answer across the industry — the figure everyone quotes, including in more than a few compliance policies pinned up in transport offices.
What's rarely mentioned in the same breath is the second half of the sentence: three-monthly is a baseline, not a ceiling. And the gap between "we check quarterly" and "we'd actually catch a problem in time" is usually down to two things operators overlook — risk-based frequency, and what happens between checks.
Where "three months" actually comes from
Three-monthly isn't a figure invented by operators for convenience. It's the widely recognised standard across DVSA-aligned guidance and Earned Recognition-style compliance frameworks, and it's the figure built into our own audit criteria: assessment criterion 7.2.1 calls for a "process to monitor and check driving licences every three months with a risk-based approach to additional checks, including logging of penalty points where appropriate."
That phrase — "risk-based approach to additional checks" — is doing more work than it first appears, and it's the part most operators quietly drop.
The bit that gets left out: risk-based frequency
A flat quarterly check treats every driver identically, regardless of their history. That's not what good practice actually calls for. A driver with a clean licence and no history of endorsements is genuinely lower risk between checks. A driver who's picked up points is not — and the checking frequency should reflect that difference.
The commonly used trigger point is drivers who've accumulated six or more points: once a driver is that close to a totting-up disqualification (12 points for most licence categories), a quarterly check is simply too slow to catch a problem before it becomes an operational one. A driver could be disqualified, keep driving for your business unknowingly or otherwise, and you wouldn't find out until the next scheduled check — potentially weeks after the fact.
A risk-based system doesn't need to be complicated. It typically means: standard checks for the wider driver pool at the baseline frequency, and closer monitoring — monthly, or even more frequent — for anyone whose record puts them nearer the threshold. Some operators extend the same logic to new starters, agency and ad hoc drivers, and anyone under 21, on the basis that unfamiliar or less-tested drivers carry more uncertainty than the fleet you already know well.
The gap most operators don't have covered: self-reporting between checks
Here's the part that causes the real damage. A three-monthly (or even monthly) check only tells you what was true on the day you looked. A driver can pick up a serious offence — or lose their licence entirely — the day after a check, and unless something else catches it, your business has no visibility of that until the next scheduled review.
The fix isn't a faster check cycle on its own. It's a documented obligation for drivers to self-report — in writing, and without delay — any offence, endorsement, disqualification, loss of licence category, or medical condition affecting their fitness to drive, the moment it happens rather than waiting to be asked. This needs to sit inside a written policy that every driver has actually seen and signed, not an assumption that "they'd obviously tell us."
Two things make this defensible on audit: evidence the policy exists and was communicated (induction records, signed acknowledgement), and evidence it's actually used — a self-report on file is proof the system works; the total absence of any self-reports across a whole driver pool, over years, is the same red flag we've written about before with nil defect reporting. It's rarely proof that nothing ever happened. It's usually proof that no one would have said anything if it had.
Why this matters more than it looks
An employer has a legal duty not to knowingly permit someone to drive without a valid licence for the vehicle and category in question. "Knowingly" is the operative word — and a licence-checking system that's too infrequent, or that relies entirely on drivers volunteering bad news unprompted, is precisely the kind of gap that turns "we didn't know" into "we should have known." That distinction matters enormously if an incident ever ends up in front of a Traffic Commissioner, an insurer, or a court.
It also has a direct commercial consequence that's easy to miss: getting this wrong can invalidate fleet insurance. A photocard checked once at induction proves an entitlement was issued in the past — nothing about current points, restrictions or medical status. Insurers increasingly expect to see an ongoing checking regime, not a one-off at the start of employment.
What a proper system actually looks like
Pulled together, a defensible licence-checking process has four elements: a baseline check frequency of no less than every three months for every driver; a documented risk-based escalation for higher-point drivers, new starters, and agency or ad hoc staff; a written obligation on drivers to self-report relevant changes immediately, evidenced by a signed policy; and records that show all of the above actually happening — not just a policy document sitting untouched in a folder.
Where this sits in your compliance system
On audit this falls under driving licence and Driver CPC monitoring (framework section 7.2), and it's almost always assessed alongside recruitment (section 7.1) and management of driver behaviour (section 7.4), because the three sit on the same thread — you can't manage what you're not checking, and you can't rely on a check alone if nobody's obliged to tell you what's changed in between.
What we're really testing on audit is whether the three-month figure is a genuine floor or a ceiling being treated as sufficient regardless of risk — and whether the business would find out about a problem from its own system, or only from DVSA telling them.
If you'd like your driver licence checking process reviewed as part of a full compliance audit, that's exactly what we do. Get in touch at enquiries@ukfleetaudit.co.uk.
References
Driver and Vehicle Licensing Agency (no date) Check a driving licence. Available at: https://www.gov.uk/check-a-driving-licence (Accessed: 4 August 2026).
Driver and Vehicle Standards Agency (2025) Guide to maintaining roadworthiness: commercial goods and passenger carrying vehicles. Available at: https://www.gov.uk/government/publications/guide-to-maintaining-roadworthiness/guide-to-maintaining-roadworthiness-commercial-goods-and-passenger-carrying-vehicles (Accessed: 4 August 2026).
FleetCheck (2026) Driver licence checking: why it matters and what good practice looks like. Available at: https://www.fleetcheck.co.uk/fleetinsights/topics/driver-licence-checking-why-it-matters-and-what-good-practice-looks-like/ (Accessed: 4 August 2026).
Road Traffic Act 1988, c. 52, s.87. Available at: https://www.legislation.gov.uk/ukpga/1988/52/section/87 (Accessed: 4 August 2026).
UK Fleet Audit Ltd (2025) Master Audit Framework, section 7.2, criterion 7.2.1.





Comments