Driver document portal: the UK compliance guide for fleet managers
Transform your fleet management with a driver document portal. Ensure audit-ready compliance and streamline driver file management today.
Driver document portal: the UK compliance guide for fleet managers
A properly configured driver document portal inside your TMS will make your driver files audit-ready for DVSA and Traffic Commissioner inspections and demonstrably support a transport manager’s continuous and effective management duties. The three actions to take now: deploy the portal inside your TMS, migrate priority driver files (starting with those expiring within 90 days), and enable expiry alerts before your next compliance review.
The evidence base is clear. The Goods Vehicle Operator Licensing Guide requires operators to maintain an effective system ensuring drivers are qualified and compliant, and to produce records on request. Vehicle safety inspection records must be kept for at least 15 months; WTD records for 24 months. A portal that cannot retrieve a specific driver file within minutes is not meeting that standard, regardless of how well-organised it looks on a shelf.
- Deploy the portal inside your TMS so documents sit alongside job and dispatch records
- Migrate high-risk and near-expiry driver files first
- Enable configurable expiry alerts for licences, DQCs, CPC periodic training and medicals
Key takeaways
A driver document portal only delivers compliance value when it combines tamper-proof audit trails, configurable expiry alerts, and verified driver files retrievable within minutes.
| Point |
Details |
| Deploy inside your TMS |
Documents must sit alongside job and dispatch records, not in a separate system. |
| Migrate near-expiry files first |
Prioritise drivers with documents expiring within 90 days to close the highest-risk gaps immediately. |
| Meet statutory retention rules |
Vehicle safety inspection records: 15 months minimum; WTD records: 24 months; tachograph downloads on defined cadences. |
| Run a one-month pilot |
Measure audit pack production time, file completeness, and expired document count before full rollout. |
| Logivo for audit-ready compliance |
Logivo’s driver app, role-based access, and exportable reports are built to meet DVSA and Traffic Commissioner expectations. |
Table of Contents
What do UK regulators expect from electronic driver document systems?
Electronic systems are fully accepted by DVSA and Traffic Commissioners, provided they are secure, complete, and allow immediate retrieval of originals or high-quality copies. The Guide to Maintaining Roadworthiness is explicit: electronic maintenance and inspection systems must be tamper-proof, provide a clear end-to-end audit trail, and permit instant access to downloaded inspection results and reports. That same standard applies to driver documentation.
Retention timelines operators must build into their system:
- Vehicle safety inspection records: minimum 15 months
- WTD records: 24 months
- Tachograph downloads: vehicle unit at least every 90 days; driver card every 28 days (per Statutory Document 3 on transport managers)
- Driver licence, DQC, CPC and medical records: retained for the duration of employment and a defined period after
Regulation 54 sets out the transport manager’s duty to access originals of core business documents and verify contracts, vehicle management records, and driver records. A portal that stores scans without verification metadata does not satisfy this. The system must record who checked each document, when, and what was verified.
DVSA audit standards assess documented evidence, version control, and management systems proportionate to the operator’s size and span of control. Larger fleets face deeper sampling; smaller operators are not exempt from the same evidence requirements.
Essential portal features that turn storage into demonstrable control
Storage alone fails inspections. The features below are what separate a compliant driver documentation system from a digital filing cabinet.
Mobile driver upload with automatic indexing. Drivers must be able to submit licence photos, Driver Qualification Cards, CPC certificates, medicals, and signed declarations from a mobile app. Files should be automatically categorised on upload, not left in an unsorted inbox for an admin to sort later.
Admin verification workflow. Every uploaded document needs a verifier, a timestamp, and a “verified by” entry. This is the tamper-proof audit trail regulators look for. Without it, you have evidence of receipt, not evidence of compliance.
Configurable expiry alerts and escalation. Driver document expiry alerts should fire at configurable lead times: 90 days for DQC renewals, 28 days for CPC periodic training deadlines, and custom windows for medicals and insurance. Batch reminders for CPC cohorts approaching their five-year deadline are particularly useful for larger fleets.
Integration with tachograph, telematics, and maintenance systems. Automated tachograph downloads (vehicle every 90 days, driver card every 28 days) should feed directly into the portal rather than sitting in a separate system. Maintenance records, telematics data, and job/dispatch records should link to the same driver profile so an auditor sees a complete operational picture, not a collection of disconnected files.
Role-based access, encryption, and GDPR controls. Not every user needs access to every driver’s medical history. Role-based permissions, encrypted storage, regular backups, and exportable audit-ready reports are baseline requirements. Compliance services that meet enterprise security standards such as SOC 2 or ISO 27001 offer an additional layer of assurance.
Pro Tip: When evaluating any driver document capture solution, ask the vendor to demonstrate a live audit export. If they cannot produce a packaged driver compliance report within two minutes, the system will not hold up under inspection pressure.
How should the portal behave during audits, roadside checks and a public inquiry?
The Operator Compliance Audits guidance on GOV.UK confirms that audits are usually conducted at an operator’s premises, documents may be scanned or photographed for transmission, and auditors may accept remote access to online compliance systems at the operator’s discretion. Your portal must be ready for all three scenarios.
| Scenario |
What the portal must deliver |
Format |
| On-site DVSA audit |
Immediate screen access to any driver’s full file |
Live system access |
| Remote Traffic Commissioner request |
Packaged export of sampled driver records with timestamps |
PDF or structured export |
| Public inquiry |
Complete driver compliance register, CPC/DQC evidence pack, tachograph download log, maintenance history |
Bundled document set |
| Roadside check |
Single driver’s current licence, DQC, and tachograph card status |
Mobile or printed summary |
Auditors sample across operation types. Gaps appear most often in agency driver records, tramper files, and subcontractor documentation. Your portal workflows must explicitly capture these categories, not just permanent employed drivers. A sample that excludes agency drivers is incomplete evidence of continuous oversight.
How to implement a driver document portal inside your TMS
Step 1: Scope your document classes and integration points
List every document type you are legally required to hold: driving licences, DQCs, CPC records, tachograph downloads, MOTs, maintenance records, insurance certificates, transport contracts, driver medicals, and training records. Map each to its retention rule and identify which systems currently hold the data (tachograph unit, maintenance software, telematics platform).
Step 2: Prioritise migration
Migrate drivers with files near expiry first. For legally critical declarations, retain a scan of a wet-ink signature or a verified digital signature. Do not rely on an unsigned digital upload for documents where driver acknowledgement is a legal requirement.
Step 3: Design the verification workflow
Decide who verifies what. Licence checks should follow a defined cadence; for agency and new drivers, verify CPC before the first shift. Assign named verifiers for each document class and build escalation rules so unverified uploads trigger an alert to the transport manager within 24 hours.
Step 4: Run a one-month pilot
Select a cohort of 10–20 drivers across your operation types (permanent, agency, tramper). Measure: time to produce an audit pack, percentage of drivers with complete files, number of expired documents at month end. A one-month guided trial gives you enough data to confirm audit readiness before rolling out to the full fleet.
Step 5: Train and communicate
- Driver app onboarding: a short walkthrough covering how to upload documents and what happens when a file is rejected
- Operations and admin training: verification workflow, escalation rules, and how to run an audit export
- Monthly compliance register review: one named owner, one scheduled review date
A driver compliance register covering licence numbers, DQC expiry dates, CPC hours, and last check dates, reviewed monthly, is the practical backbone of continuous oversight.
Operational policies that must sit alongside the portal
The portal generates evidence. These policies determine whether that evidence holds up.
- Licence and CPC check cadence: define the frequency in writing, assign sign-off responsibility, and record every check in the portal with a timestamp
- Agency and subcontractor verification: treat every temporary driver as a compliance risk until their file is complete; never dispatch without a verified licence and DQC on record
- Defect reporting and driver declarations: require a scan of a wet-ink or verified digital signature for critical responsibilities; an unsigned acknowledgement is not a defence
- Access control and change management: define role permissions in writing, maintain an approver list, and audit configuration changes at least quarterly
- Retention and backup policy: align document retention periods to operator licence undertakings and DVSA guidance; confirm backups run daily and that a disaster recovery test has been completed in the past 12 months
When adding drivers to a fleet insurance policy, the same document verification process should apply. A portal that gates dispatch on verified insurance status removes a common compliance blindspot.
How do you measure whether the portal is actually working?
Core compliance KPIs:
- Time to produce a full audit pack (target: under 30 minutes)
- Percentage of drivers with complete, up-to-date files
- Number of expired documents at month end
- Audit findings count per inspection cycle
Operational efficiency metrics:
- Admin hours saved per month on document chasing and filing
- Reduction in licence-check errors
- Time saved on tachograph download handling
For a small fleet (under 20 vehicles), a one-month pilot with a baseline measurement taken in week one is sufficient to calculate payback. Medium fleets (20–100 vehicles) typically see the largest efficiency gains in tachograph handling and CPC renewal tracking. Larger operations benefit most from the audit export function and role-based access controls, which reduce the time a transport manager spends preparing for inspections. Small fleet operators often see disproportionate benefit because centralised digital evidence equalises their ability to present professional, organised records at a fraction of the administrative cost.
Why most operators fail inspections before they even open a file
The most common reason operators struggle at audit is not missing documents. It is disorganised ones. A folder full of scanned PDFs with no verification metadata, no expiry tracking, and no clear ownership tells an auditor that the transport manager is not in continuous and effective control, regardless of what the files actually contain.
Smaller operators often assume that a basic cloud folder is sufficient. It rarely is. Regulators expect documents to be retrievable in a categorised, demonstrable format. Disorganised digital folders fail inspections just as reliably as paper ones.
The other pattern worth noting: operators invest in the portal but not in the policies around it. Technology paired with driver understanding, signed acknowledgements, and a defined verification cadence is what reduces enforcement risk. A portal without those controls is still just storage.
A guided trial is worth doing precisely because it forces the discipline. You measure against real KPIs, with real driver files, before the auditor arrives.
Logivo gives you a driver document portal built into your TMS
Compliance without the admin overhead is the concrete difference Logivo delivers. The driver app supports document capture in over 20 languages, with mobile upload, walkaround checks, defect reporting, and ePOD capture sitting inside the same platform as job allocation, dispatch, and invoicing. Role-based access, encrypted storage, and exportable audit-ready reports map directly to the DVSA and Traffic Commissioner requirements covered in this guide.
The one-month guided trial is structured as a validation step: a setup call, a defined pilot cohort, and a compliance checklist you measure against at the end of the month. You leave with documented KPIs confirming audit readiness, or a clear picture of what still needs fixing. For courier and distribution operators, the integration between document capture, driver progress tracking, and invoicing workflows means compliance evidence and operational data sit in one place. Start your guided trial at Logivo.
Sources
The primary sources below set the legal and regulatory baseline every UK operator should read before configuring a driver documentation system.
FAQ
What documents must a driver document portal hold?
At minimum: driving licences, Driver Qualification Cards, CPC periodic training records, tachograph downloads, MOTs, maintenance records, insurance certificates, transport contracts, driver medicals, and training records. Each must be retrievable with verification metadata.
Are electronic driver records accepted by DVSA and Traffic Commissioners?
Yes, provided the system is tamper-proof, maintains a clear end-to-end audit trail, and allows immediate retrieval of originals or high-quality copies, as confirmed by the GOV.UK roadworthiness guide.
How long must vehicle maintenance and driver records be kept?
Vehicle safety inspection records must be kept for at least 15 months and WTD records for 24 months, per the Goods Vehicle Operator Licensing Guide. Tachograph downloads are required every 90 days for the vehicle unit and every 28 days for the driver card.
Can Logivo support DVSA audit preparation?
Logivo’s platform includes role-based access, exportable audit-ready reports, and a driver app for mobile document capture, all of which map to the evidence requirements set out in DVSA audit standards and Regulation 54.
What is the fastest way to validate a new driver documentation system?
Run a one-month guided pilot with a defined cohort covering all operation types, measure audit pack production time and file completeness at the end, and compare against your baseline before rollout.
Recommended