route & fleet
Compliance

Driver Qualification Files That Survive an Audit

What belongs in a driver file, how to keep it current across a workforce, and the automation that prevents the expiry nobody noticed.

Illustration: Driver Qualification Files That Survive an Audit
Advertisement
Ad space · activate by adding your AdSense publisher ID to lib/manifest.js

The driver qualification file is the evidence that the person you put behind the wheel was entitled and fit to be there. Missing documents are among the most common audit findings, and they are entirely preventable with a register and a reminder.

What a file typically contains

Requirements differ by jurisdiction, but a defensible file usually includes:

DocumentNotes
Application for employmentWith full employment history for the required period
Driving licenceCorrect categories, current, with periodic re-checks
Licence check recordEvidence of verification against the licensing authority
Medical certificationWhere required for the vehicle class, with expiry tracked
Certificate of professional competenceWhere the regime requires periodic training
Previous employer enquiriesWhere mandated
Driving record / abstractObtained at hire and at intervals
Annual review of driving recordDocumented, with a decision
Training recordsInduction, vehicle-specific, refresher, safety
Road test or competence assessmentWhere required or advisable
Disciplinary and incident recordLinked, retained appropriately
Working time and tachograph recordsHeld under separate retention rules

The variation between jurisdictions is significant. Build your list from the regulation that applies to you rather than from a template — including this one.

The only reliable control is that an expired mandatory document removes the driver from the roster automatically, not as a discretionary decision.

The recurring failure

Almost every driver file finding falls into one of three categories:

  1. Expiry not tracked. A licence category lapses, a medical expires, a periodic training deadline passes. The driver keeps driving because nobody was told.
  2. Verification not evidenced. The check was done but not recorded, so there is no proof.
  3. Files incomplete for leavers and returners. Agency drivers, seasonal staff and re-hires with fragmented documentation.

All three are solved by the same thing: a single register with expiry dates and automated escalating reminders, and a rule that an expired document stops the driver.

Advertisement
Ad space · activate by adding your AdSense publisher ID to lib/manifest.js

Automation that works

Central register holding every driver, every document type, issue date, expiry date and verification evidence.

Escalating reminders to multiple recipients: driver at 90 and 60 days, line manager at 30, compliance manager at 14, automatic escalation at 7. Single-recipient reminders fail when that person is on leave.

Automatic licence checking where your jurisdiction supports it — periodic electronic verification against the licensing authority, with the frequency set by risk. Drivers with endorsements or recent incidents should be checked more often.

Document upload from the driver's app, so renewals reach the register without an email chain.

Roster integration, so an expired document prevents assignment rather than merely generating an alert.

Audit export, producing a complete file for any driver on demand.

Agency and subcontracted drivers

The weakest area in most operations, and often the one with the greatest exposure. Whoever is legally responsible for the operation generally retains duties regardless of who employs the driver.

Practical controls:

  • Contractual obligation on the agency to supply and maintain documentation
  • Your own verification before first use — not reliance on the agency's assurance
  • The same register, with the same expiry tracking
  • A named agency contact accountable for compliance
  • Periodic audit of agency-supplied files
  • A rule that undocumented drivers do not drive, however urgent the shift

Data protection

Driver files contain sensitive personal data — health information, criminal record data in some regimes, employment history.

  • Access strictly limited to those with a need
  • Retention aligned to legal requirements, and deletion when the period expires
  • Secure storage with an access log
  • Transparency with drivers about what is held and why
  • A defined process for subject access requests
  • Particular care with medical information, which typically attracts additional protection

Holding files indefinitely "just in case" is a common and unlawful default in many jurisdictions.

Advertisement
Ad space · activate by adding your AdSense publisher ID to lib/manifest.js

Frequently asked questions

How often should driving licences be checked?

Set the frequency by risk: more frequently for drivers with endorsements, incidents or higher-risk vehicle classes, less frequently for clean records. Many operations check quarterly to annually, and use continuous electronic checking where the jurisdiction offers it.

What do we do if a licence has expired?

Remove the driver from driving duties immediately and record the decision. Continuing to allow driving after discovering an invalid licence exposes the operator to serious liability, and insurance cover may be affected.

Are electronic driver files acceptable?

In most jurisdictions yes, provided they are complete, retrievable, secure and demonstrably unaltered. Electronic files are generally easier to defend at audit than paper because expiry tracking and retrieval are far more reliable.

Who is responsible for agency driver compliance?

Responsibility usually rests substantially with the operator running the vehicles, whatever the contract says about the agency's obligations. Verify independently rather than relying on assurances, and keep your own records.

How long should we keep files after a driver leaves?

For the period required by the applicable regulation, plus any period needed for potential claims — then delete. Both under-retention and indefinite retention create risk, in different directions.

Nil Masferrer Jiménez · Editor

Nil writes and edits Route & Fleet. It is an informational reference compiled from public sources — vendor documentation, regulator publications and published industry research — not consultancy, and not based on first-hand experience of running a fleet. Corrections are welcome and get published.

How we research and review our articles

This article is editorially independent. Route & Fleet is funded by advertising displayed on the page; advertisers have no influence over our research, recommendations or conclusions. See our advertising disclosure.

Keep reading

Related articles

Compliance

Hours of Service and ELD Rules Explained

How hours-of-service limits and electronic logging work, what fleets must record, the common violations, and how software should support compliance.

31 July 2026 · 5 min read

Compliance

Preparing for a Fleet Compliance Audit

What auditors examine, how to run an internal audit before they do, and the record-keeping practices that turn an audit from a crisis into a formality.

19 July 2026 · 4 min read

Advertisement
Ad space · activate by adding your AdSense publisher ID to lib/manifest.js