A fleet of ten drivers runs on one spreadsheet and one person who knows everybody. At sixty, that person is checking insurance certificates at 11pm and still misses the MOT that expired on Tuesday. The back office does not grow at the same pace as the fleet, and delivery driver compliance is where the gap shows first: licences, insurance and right to work permissions expire quietly, and the operator finds out at the roadside, at renewal, or in a claim.
This guide is the working version of what has to be on file for every UK driver, how to keep it current with a renewal cadence you can actually run, what an audit file looks like, and how to hold subcontractors to the same standard. It assumes a mix of employed and self-employed drivers, because that is what most fleets between ten and two hundred drivers actually have.
What has to be on file for every driver
Start from the documents, not from the software. Every UK operator needs the following for each driver, and each one has its own check, its own source of truth and its own expiry.
| Document or check | How you verify it | What lapses |
|---|---|---|
| Driving licence | DVLA check code from gov.uk/view-driving-licence, valid 21 days; shows categories, points, disqualifications | Photocard expires every 10 years; points accrue between checks |
| Right to work | Online share code check, or manual check of a British or Irish passport, done before day one. From 1 October 2026 the duty also covers self-employed couriers and sub-contractors' drivers | Time-limited permission needs a follow-up check on or before expiry |
| Criminal record | Basic DBS certificate, £21.50, the only level a courier role is eligible for | No update service for Basic checks; a certificate is a snapshot |
| Insurance | Certificate and schedule showing hire and reward use on the vehicle actually used | Annual renewal; cover can be cancelled mid-term for non-payment |
| Vehicle roadworthiness | MOT status from the registration on gov.uk; daily walkaround check record | MOT annually; the walkaround record is per day |
| Training | Certificate per module, linked to the driver profile | Whatever refresh interval you set; write it down |
| Policies | Signed acknowledgement of the driving for work policy and code of conduct | Re-sign on every change |
| Drivers' hours | Weekly record sheet or tachograph under the GB domestic rules | Per week |
Two of those rows carry legal specifics that operators of light vans often assume do not apply to them. The GB domestic drivers' hours rules apply to goods vehicles including vans: no more than 10 hours driving in a day, no more than 11 hours on duty, recorded on a weekly record sheet or a tachograph. And DVSA's van daily walkaround check guidance says DVSA can ask for a record of the check at the roadside, and that using a van in a dangerous condition carries an unlimited fine and a possible prison sentence.
The licence, right to work and DBS rows are covered in detail in our courier background checks guide, including what a self-employed driver's own certificate proves and what it does not.
One system of record, with the fields that make audits repeatable
Define a single place where a driver's record lives, and standardise the fields before you standardise anything else. The system can be a database, a compliance platform or, for ten drivers, a well-designed spreadsheet. What matters is that every region and every manager captures the same fields in the same format.
The fields worth standardising from day one:
- Full legal name as it appears on the licence, and the ID type checked
- Licence categories, issuing country, photocard expiry, points at last check and the date of that check
- Vehicle registration, MOT expiry, insurance policy number, insurer, use class and expiry
- Right to work check type, date, outcome and, for time-limited permission, the follow-up date
- DBS outcome record: date of issue, level, certificate reference, position, decision
- Training certificates with completion date and the refresh date you have set
- Policy acknowledgements with version and date
Store structured metadata for every file, not just the file. A PDF of an insurance certificate is useless in an audit if nobody typed in the expiry date; the date is what the reminder engine reads and what the auditor filters on.
This is the part of the job Service Club ® built its Compliance product around: one record per driver, with the expiry dates, re-check cadence and destruction dates tracked per document. The principle holds whatever tool you use.
Onboarding that gates each step
Fast hiring does not need to be risky hiring, as long as each onboarding step gates the next. A driver who has not passed the licence check cannot be booked on the insurance; a driver whose insurance is not approved cannot be scheduled. The sequence that works for most fleets:
- Identity capture and a match against a government-issued ID
- Right to work check, before any start date is agreed
- Licence validation through the DVLA check code
- Insurance proof collected and the use class checked, with the vehicle registration recorded
- Training modules assigned, completed and logged
- Policies signed, including data use and the driving for work policy
- Final approval recorded with a timestamp and the approver's name
Automate the mechanical parts: date parsing from documents, expiry reminders, alerts for missing items. Do not automate the judgement calls, which are the insurance use class and anything that comes back on a DBS certificate. A human reads those.
The driver recruitment funnel post covers why every extra day between application and approval loses candidates, and our guide to recruiting delivery drivers puts these checks in hiring order. The compliance answer is not to skip steps but to run them in parallel where the law allows, and to be honest with the driver about which ones cannot be rushed.
The 30, 14 and 3 day renewal cadence
Compliance is not a hiring event. Licences, insurance policies and permissions expire on their own schedule, and a document that was valid at hire is worth nothing on the day after it lapses.
The pattern that works: notify the driver and their manager 30 days before expiry, again at 14 days, again at 3 days, then automatically suspend access to shifts on the expiry date until a new document is uploaded and approved. Three staged reminders give the driver time to renew; the hard stop on the day means nobody drives on an expired document because a reminder went into a spam folder.
Why three reminders and not one
One reminder at 30 days gets forgotten. One at 3 days gives a driver whose insurer needs a week no chance. Three spaced reminders cost nothing to send and turn a compliance failure into a scheduling inconvenience.
What to do on the expiry date
Suspend, do not terminate. The suspension is automatic, visible to the driver and the planner, and lifts the moment an approved document lands. If a driver is suspended more than once a year for the same document, that is a conversation, not a reminder.
Monitoring that feeds compliance rather than replacing it
Operational data supports the document file. Log incidents, near misses and customer complaints, tagged to the driver and the vehicle. If you run telematics, use it to spot patterns such as persistent speeding or harsh braking before they become claims. Coaching and a targeted refresher module cost less than an excess.
Two limits. Telematics data about a driver is personal data, and the ICO's guidance on monitoring workers expects you to tell drivers what is collected and why, to run a data protection impact assessment for driver behaviour monitoring, and not to use the data for a purpose you did not state. And if your drivers are self-employed, managing their driving style as you would an employee's is an employment status risk. Our driver performance post covers where that line sits.
The audit file you can export in a minute
Audits, whether from an insurer, a client or a regulator, are easy when the evidence is one export away. Practise producing a complete file for a randomly chosen driver that includes:
- A checklist of every requirement with its pass status and date
- Every document with its approval timestamp and approver
- Training history and policy acknowledgements with versions
- Incident and coaching records
- Current eligibility status and, if suspended, the reason
Then run internal spot checks monthly. Pick a random sample per region, verify each file end to end, and record what you found. A monthly sample of five files catches a process gap while it is five files wide rather than fifty.
Regions, subcontractors and the contract
Regulations vary by country and sometimes by city, so as you expand, assign a named owner per region who documents the local requirements and keeps them current. Your checklist should have universal items and region-specific ones, and a new market should be opened by cloning the template and adapting the local rows, not by starting from a blank page. A London fleet, for example, has the ULEZ compliance of each vehicle on its list; a Manchester fleet does not.
Most growing fleets also rely on subcontractors or third-party courier partners, and this is where compliance most often breaks. The subcontractor's driver is stopped with no hire and reward cover, and it is your parcels at the roadside and your customer on the phone. The contract should specify:
- Document standards, meaning the same list you hold your own drivers to
- Renewal timelines, meaning the same cadence
- Audit rights, so you can request the file for any driver working your routes
- Data sharing terms, so those requests are lawful under UK GDPR
Then give partners the same onboarding flow and the same dashboard your own team uses. A subcontractor with a different form and a different standard is a compliance gap with a company name on it.
Data protection built in from the start
A driver file is sensitive personal data, and criminal record information is special category data. Encrypt it at rest and in transit, restrict access by role, log every view and change, and set retention schedules that match the legal requirement for each document rather than one blanket period. Right to work evidence is kept for the duration of employment plus two years; a DBS certificate itself is not kept beyond the recruitment decision, only the outcome record. Give drivers a straightforward way to see their own record and ask for corrections.
Frequently asked questions
What documents does a UK delivery operator need on file for each driver?
At minimum: a DVLA licence check result with its date, right to work evidence, a Basic DBS outcome record, the insurance certificate and schedule showing hire and reward cover on the vehicle, the MOT expiry date, the training certificates the role requires, signed policy acknowledgements, and for van drivers the daily walkaround check and drivers' hours records the law expects to exist.
How often should a fleet re-check driving licences?
At hire and then at least once a year, more often for drivers with points or a recent incident. Most fleet insurers write a licence check frequency into the policy, so read yours. The DVLA check code a driver generates at gov.uk is valid for 21 days and shows categories, points and disqualifications.
What is the 30, 14 and 3 day renewal cadence?
A reminder to the driver and their manager 30 days before a document expires, a second at 14 days, a third at 3 days, and an automatic suspension of shifts on the expiry date until a new document is approved. Three staged nudges give the driver time to act; the hard stop makes sure nobody drives on an expired document because a reminder was missed.
Do GB drivers' hours rules apply to vans under 3.5 tonnes?
Yes. The GB domestic rules apply to goods vehicles generally: no more than 10 hours driving in a day and no more than 11 hours on duty, with hours recorded on a weekly record sheet or tachograph. Some light vehicles used for specific purposes are exempt from the duty limit, but a parcel or food delivery van is not one of them.
Are subcontracted couriers my compliance problem?
Operationally, yes. If a subcontractor's driver is stopped on your route with no hire and reward insurance, it is your parcels sitting at the roadside and your customer asking questions. The contract should set document standards, renewal timelines, audit rights and data sharing, and the subcontractor should be onboarded through the same flow your own drivers use.
The fleet that can produce a file in a minute
Compliance at scale is a list of documents, an expiry date on each, three reminders and a hard stop. Everything else is making that list exportable. If you would rather not build the reminder engine yourself, Service Club Compliance tracks the documents, the re-check cadence and the retention dates per driver, for your own fleet and your subcontractors' drivers alike.