How often should employers check driving licences?

Check a person's driving entitlement before authorising them to drive a vehicle for work, then repeat the check at a frequency set by the risks of the role and your fleet policy. Recheck sooner after a relevant change or concern. The current DVLA employer service lets an authorised checker see vehicle categories, penalty points and disqualifications using information supplied by the driver. HSE says employers must manage work-related road-safety risks and consider the driver, journey and vehicle. The reviewed primary sources do not prescribe one universal “every three months” or “every year” DVLA checking interval for all employers and vehicles. Avoid presenting a vendor's preferred schedule as a blanket legal rule.

The answer can differ for a van driver, a heavy-goods driver, a home-care worker using their own car and an occasional employee who drives to client sites. The important question is whether your process gives you reasonable, timely assurance that each driver remains entitled to drive the actual vehicle and is suitable for the work, with a defensible record of the decision. This guide is about GB driving-licence checking. It does not replace driver CPC, operator-licence, medical, insurance, tachograph or vehicle-roadworthiness duties where those apply.

What the official DVLA check shows

The GOV.UK check-someone's-driving-information service can show the vehicle categories a person is entitled to drive and any penalty points or disqualifications. To use it, the checker needs a check code from the driver and the last eight characters of the driver's driving-licence number. The current service says a code must be used within 21 days and can be used once; another check needs another code. The driver can generate a code through the view/share driving-licence service. The checker must have the correct information and permission: GOV.UK warns that obtaining someone else's personal information without permission is a criminal offence.

A photograph of the plastic card is weaker than checking the current record. It may not show current endorsements or a disqualification, and it cannot tell you whether a category has changed. The DVLA result is a snapshot when checked, not a promise that the entitlement stays the same until the next calendar reminder. Record the date, relevant categories/restrictions, result, checker and any action; protect the personal information under a suitable retention and access policy. Do not copy more data than needed simply because a system allows it.

Is there a legal interval?

In the reviewed current DVLA and HSE primary sources, there is no single statutory repeat-check interval specified for every employer's driver-licence check. The legal backdrop includes ensuring the person is entitled to drive the class of vehicle: section 87 of the Road Traffic Act 1988 addresses driving without a licence and causing or permitting that driving. HSE's work-related road-safety guidance requires employers to manage the health and safety risks of work driving, including grey-fleet vehicles. These duties support a sensible checking system, but the exact cycle should reflect the role and risks rather than a fabricated universal number.

Contracts, insurer terms, licensing regimes or specific operator procedures may set a tighter cadence. Check those separately. A government department's six-month policy or an insurer's recommendation may be a useful example of one organisation's choice; it is not a GB-wide law. If your company chooses six-monthly or annual checks, label that as your policy, explain why it fits the risk, and adjust it when evidence changes.

Build a risk-based checking schedule

Use a baseline check at recruitment or before the first work journey, then classify drivers. The following are illustrative policy decisions, not statutory intervals:

Do not automatically put every driver with points into one category without considering the actual offence, category, restrictions, role, mileage and risk. Equally, an apparently clean record is not a reason never to recheck. A policy should say who owns the schedule, how reminders work, what the driver must report, when a manager escalates and what happens if a check is missed.

HSE's work-related road-safety overview uses the “safe journey, safe driver/rider, safe vehicle” approach. Licence checking addresses only part of the safe driver element. It does not replace training, fitness to drive, fatigue controls, vehicle maintenance or journey planning. For grey fleet, the vehicle and insurance questions remain even if the driver's entitlement is valid.

Events that should trigger an earlier check

Do not wait for the calendar date after a reported disqualification, new endorsement, medical restriction, category change, change of role or vehicle, serious road incident, insurance issue, or reliable concern about fitness to drive. The driver policy should require prompt reporting of relevant changes and explain who decides whether to suspend work driving pending confirmation. A driver may be able to drive a car yet not a heavier vehicle, trailer combination or passenger vehicle needed for a revised role. Recheck the actual category and restriction for the assigned vehicle.

If a worker turns up without a valid check code, do not call a photograph or last year's screenshot a current DVLA check. Decide whether the person can carry out non-driving duties until the official result is obtained. The GOV.UK service also explains help and postal routes, but those may not meet an immediate authorisation need. Your policy should define the fallback before a delivery or journey is due.

A practical check-and-record process

1. Define who drives for work. Include employees, temporary staff and grey-fleet drivers where appropriate. Record the vehicle classes and tasks, not just “has a licence.”
2. Obtain permission and a fresh code. Ask the driver to generate the code through the official service. Use it within the current 21-day window and remember it works once only.
3. View the DVLA result. Check identity, relevant vehicle categories, expiry or restrictions shown, points and any disqualification. Compare with the actual vehicle to be driven and any required vocational qualification.
4. Record the decision. Keep date, checker, role/vehicle, result, relevant issues and authorisation outcome. Protect the driver's personal information; the record need not be a broad copy of everything visible.
5. Set a next review. Apply the company policy, record the reason for any shorter interval and arrange reminders. Check insurer/client/operator conditions.
6. Require change notification. Tell drivers what to report and who to contact. If a concern arises, reassess before the next drive.
7. Audit exceptions. Review overdue checks and whether drivers were nevertheless assigned work. Fix the process, not just the spreadsheet colour.

For a large fleet, GOV.UK's employing-people-to-drive guidance describes an Access Driver Data route subject to DVLA accreditation and contract. Do not imply that an ordinary document-management platform automatically has that access. The public check-code route is a distinct process requiring the driver's cooperation.

Example: a role changes from van to heavier vehicle

A maintenance worker has been driving a light van and is now asked to drive a different class of vehicle. The office already holds a scan of the worker's licence and a check from the previous quarter. Those records do not answer the new question. The manager asks for a current official check, confirms the entitlement and any restrictions for the proposed vehicle, and checks any additional training or qualification requirement. If the category is absent or unclear, the worker does not drive that vehicle until the question is resolved. The old check remains an audit record of a previous decision, not a substitute for the changed role.

Mistakes to avoid

• Claiming a universal legal cycle. Set and document a risk-based cycle, then obey any stricter applicable sector, contract or insurance term.
• Confusing a valid physical card with live entitlement. Use current DVLA information and match the category to the vehicle.
• Checking only company vehicles. Work-related road-safety duties also cover grey fleet; assess the driver, journey and vehicle.
• Treating code validity as check frequency. A 21-day, one-use check code controls access to a single DVLA lookup; it does not mean a licence must be rechecked every 21 days.
• Letting expired consent or a missed check slide. Define who can authorise driving and a fallback when a current result is unavailable.
• Saving everything indefinitely. Keep a proportionate record with controlled access and retention.
• Assuming a record system performs the DVLA check. Separate stored licence data or reminders from an authorised live DVLA lookup.

Where Complys may fit

The live Complys trades page mentions driver check requests and fleet records, while the transport compliance guide discusses licence-check history. Those statements are marketing evidence, not proof of current integration. Verify the implementation and exact host before saying Complys connects to DVLA, obtains driver consent, makes live checks, or automatically applies a risk-based frequency. If current features allow administrators to store the date/result of an official check and set reminders, describe that limited support accurately. A useful CTA is to test whether the verified workflow helps keep your driver-check policy and decisions organised, while the employer continues to use the official DVLA route.

Source, claim, owner, product, links and writer-side QA

Terminal writer-side disposition: READY.