Driver compliance management for GB goods fleets: records, checks and action

Build a practical driver-record workflow for licences, Driver CPC, hours, tachograph data and follow-up actions using current DVSA and DVLA guidance.

Driver compliance management is the routine of knowing which people may drive which vehicles, what rules apply to their journeys, whether essential evidence is current, and what happened when a check found a problem. A list of expiry dates is only one part of that routine. An operator also needs a way to assign the right checks, review the results and record decisions before a driver is allocated work.

This guide is for a Great Britain goods vehicle operator building a practical driver-level process. The applicable hours and tachograph regime depends on the vehicle and its use. DVSA's current goods vehicle manual applies to England, Scotland and Wales and points readers to separate Northern Ireland guidance. Passenger services have their own guidance. The examples below are process examples, not a decision that a particular vehicle or journey is in scope.

The starting point is to separate three things that are often mixed together: a legal requirement, a regulator's explanation of that requirement, and an operator's own management practice. A check schedule may be a sensible internal control without being a statutory interval. A software field may help people remember a task without verifying that the task was done correctly.

Define the driver and journey before setting a checklist

Do not give every driver the same compliance template merely because they work for a transport business. First record the work each person actually performs and the vehicles they may use. A goods vehicle driver on an in-scope tachograph journey can have a different evidence set from a local driver operating under Great Britain domestic hours rules. A passenger driver, taxi driver or Northern Ireland operation needs its own source check.

The DVSA goods vehicle manual says the vehicle's size, construction and use determine the hours rules. Its sections distinguish assimilated rules, AETR rules, Great Britain domestic rules and mixed driving. An operator should therefore record the relevant regime for each vehicle and journey pattern, with the source and date used for that decision. If the operation changes, revisit it. A new international route, a different vehicle or a different use can make an old checklist unsuitable.

Keep the decision practical. A driver profile can note the licence category needed for the allocated vehicle, whether Driver CPC is required for that work, whether a driver card and tachograph records are relevant, which hours regime has been assigned, and who reviewed the assignment. These are proposed management fields. They are not a government-prescribed driver file format.

For the wider vehicle maintenance and walkaround picture, use current DVSA roadworthiness guidance. This page stays focused on the driver record and the decisions that make it usable.

Check the driving licence with the driver's permission

An operator needs to know that the driver has the entitlement appropriate to the vehicle and work. A photocopy supplied months ago can be a starting document, but it does not replace a current check when a check is needed. The DVLA service for checking someone else's driving licence shows the online method. The operator needs a check code from the driver and the last eight characters of the licence number. The code can be used once within 21 days. The service warns against obtaining another person's personal information without permission.

Record what the check actually showed: date, person who performed it, relevant vehicle categories, restrictions or endorsements relevant to the allocation, and what follow-up was required. Store only the information needed for the purpose and follow your privacy and retention policy. If an entitlement is unclear, do not mark the driver approved simply because a file has been uploaded. Ask the right person to examine the record and resolve the allocation.

There is no universal annual licence-check interval stated on that DVLA service page. Set a risk-based schedule for your operation and check after material changes or a reported issue. Describe the schedule as company policy unless an applicable rule or contract supplies a specific requirement. A policy might distinguish a routine review from an immediate reassessment after a disqualification, medical restriction or vehicle-category change. The critical control is that the driver tells the operator about changes and that the operator acts on them before assigning unsuitable work.

The profile should have an owner as well as a date. If a driver has supplied a code but nobody has completed the check, the record is pending. If a check shows a restriction, the outcome is review required. If the right entitlement has been confirmed for the proposed work, record who made that decision and when. These status labels are suggestions for operating a clear process, not official DVLA categories.

Handle Driver CPC as a scoped requirement

Driver CPC can be essential for professional goods vehicle driving, but it is not a blanket requirement for every person who drives a van or every journey. Check the work and any exception against the current GOV.UK Driver CPC guidance. For a qualified driver who must keep Driver CPC, GOV.UK says that the qualification lasts five years and that 35 hours of training must be completed before the five-year deadline shown on the card.

A useful driver record holds the applicable qualification, card deadline, training evidence and a named reviewer. The training total should be checked against the official Driver CPC record where necessary. A course booking is not the same as completed training. A document with a future expiry date does not show that the driver has completed the required hours. If a driver is close to the deadline, arrange the training and confirm completion before further professional driving that requires the qualification.

For a driver who is outside Driver CPC scope, record the reason and source rather than leaving an unexplained blank field. That makes a later review possible when duties change. If one person drives both goods and passenger vehicles, check the deadlines and qualifications that apply to that person's actual work rather than assuming one card entry answers every question.

Training management can include more than Driver CPC. Familiarisation with a vehicle, load-security procedures and instruction on hours and tachograph use may be relevant. DVSA's operator-responsibilities guidance says operators under the assimilated and AETR rules must ensure drivers are properly trained and instructed on hours rules and correct tachograph use. Your company may also have its own induction standard. Label the official duty and the company procedure separately.

Match hours records to the correct regime

Driver compliance management becomes unreliable when the file merely says “tachograph compliant” without naming the rules that apply. The DVSA manual has separate sections for assimilated and AETR rules, Great Britain domestic rules and mixed driving. The GOV.UK domestic-rules guidance explains that those rules apply to most relevant goods and passenger operations that do not have to follow assimilated rules, subject to exceptions. It also makes clear that Northern Ireland has separate rules.

For an in-scope operation, record the regime at the point work is planned. Scheduling should account for the driver, vehicle, route and recent work. The operator cannot make a driver compliant by simply telling that person to take breaks. Under the assimilated and AETR rules, DVSA says operators must schedule work so the rules can be met. A dispatch plan that requires an impossible journey time is a management problem before it becomes a driver infringement.

The hours record then needs human review. Check whether the data for the relevant period is present, whether an apparent breach is real, what explanation the driver gave, what action was taken and whether the planning process needs to change. A dashboard alert is an invitation to investigate; it is not a legal determination. Equally, a clean-looking report can be misleading if a driver card download is missing.

Avoid copying a single set of hours limits into a generic driver checklist. Limits and exemptions depend on the regime and journey. Link staff to the current official section for the rule that actually applies. The guide's job is to make the record workflow clear, not to replace the official manual.

Manage tachograph downloads and exceptions

For a digital tachograph operation subject to the assimilated or AETR rules, DVSA's operator-responsibilities section sets at least every 90 calendar days for vehicle-unit downloads and at least every 28 calendar days for driver-card downloads. It lists earlier event-driven downloads, including before control of a vehicle is transferred and before a driver ceases employment, as well as situations where data may be lost. The guidance expressly mentions agency drivers in the departure trigger.

Those numbers are not a universal calendar for all company drivers. They belong to the operation and equipment covered by that DVSA section. A firm should classify its vehicles and drivers before adding deadlines. If a driver sometimes works under another regime, document the transition and check the relevant official mixed-driving guidance. If a card or unit malfunctions, use DVSA's instructions for the circumstances rather than treating a failed download as a completed one.

An effective download register links the person or vehicle to the last successful download, the next due date, any earlier trigger, the person responsible, the location of the retained record and any exception. Separate “attempted” from “successful.” If a download failed on time, the unresolved exception should remain visible until the cause and recovery are recorded. A scheduled reminder alone does not show that data was preserved.

The records also need regular scrutiny. DVSA says operators should make regular checks of charts, manual records and digital data and take reasonable steps to prevent breaches. A review can note an apparent infringement, the driver's account, any supporting records, the reviewer decision and any corrective action. This is more useful than an unannotated red flag. Where a matter is disputed or complex, seek qualified transport advice; do not let a generic article or software status decide it.

Give agency and occasional drivers a complete handover

An agency driver may be with the operator briefly, but the work still has a driver, vehicle, shift and record trail. Before allocating a shift, confirm the entitlement and qualifications needed for that actual task and arrange access to the relevant vehicle and route instructions. Do not assume another business's file covers the operator's own responsibilities.

The end of the placement needs equal attention. DVSA's download guidance says the driver card should be downloaded immediately before the driver ceases employment with the undertaking and notes that this also applies to agency drivers. A casual “we will collect it next month” handover risks losing evidence. Plan who performs the download, how the driver is told, and how a failed attempt is escalated.

For an occasional driver, do not create a permanent green status based on one historic check. Record the dates of the engagement and the basis on which the person was authorised for the shift. If the work changes from local to international, or the vehicle changes category, review the regime and qualifications again. This is a management practice designed to avoid stale assumptions.

Turn a driver file into an action system

A practical file has four layers. The first is identity and role: who the driver is, which business or agency supplies them, and who supervises their work. The second is eligibility: licence entitlement, any applicable Driver CPC position, driver card and training relevant to the work. The third is operating evidence: hours and tachograph records for in-scope work, instructions given and checks performed. The fourth is action history: concerns, explanations, decisions and closure.

Each layer needs a defined owner. A document may arrive by email, but somebody still has to decide whether it is readable, current and relevant. An expiry reminder may appear, but somebody still has to confirm renewal and update allocation. An infringement report may be generated, but somebody still has to examine context and act. This is why a driver record is better viewed as a controlled workflow than as a folder of PDFs.

Suggested status categories are “evidence needed,” “review needed,” “authorised for defined work” and “allocation paused.” Give the decision a date and a name. A paused allocation should remain visible until the reason is resolved. Avoid a global “compliant” badge that hides the question of which vehicle, journey and rule set were assessed.

Keep policy dates separate from legal dates. Your business may choose to review licence records quarterly, for example, but do not present that choice as a universal statutory frequency. The Driver CPC deadline and the relevant tachograph download deadlines come from official guidance. The internal review cadence is an operational choice that should be justified by the work and reviewed when risks change.

A worked driver-record example

Imagine a GB goods operator adding an experienced driver for a short agency placement. The dispatcher needs the person for a vehicle and journey that the operator has classified under the assimilated hours rules. The operations lead first checks the licence entitlement using the DVLA method with the driver's permission and code. They check whether Driver CPC applies to that professional work and, if so, the card deadline and completed training. They confirm the driver has appropriate hours and tachograph instruction for the allocation.

Before the first shift, the record shows the vehicle, journey pattern, assigned hours regime and named person who authorised the allocation. The scheduling team considers the driver's recent work and plans a feasible shift. After the work, the operator collects the applicable tachograph data, reviews any apparent infringement and records an explanation and action. Before the placement ends, the operator arranges the card download required by DVSA's agency-driver departure guidance.

If the driver cannot provide a valid check code or evidence is unclear, the allocation remains pending. If an apparent hours breach is found, it is investigated and documented rather than silently marked resolved. This example illustrates the decision trail; it does not decide that all agency jobs have the same legal classification.

Build a review rhythm without inventing rules

At onboarding, classify the intended work and confirm the initial evidence. Before each allocation, consider whether the recorded authorisation still matches the vehicle and journey. At the official deadline, complete any required card or vehicle-unit download and preserve the result. On an event, such as a driver leaving, a restriction being reported, a failed download or an apparent infringement, assign immediate follow-up. Periodically, review open exceptions and whether the company's own check policy still matches how the operation works.

This rhythm can be run with a carefully controlled spreadsheet and clear responsibility, especially in a small operation. A larger fleet may want software to make ownership, due dates and exceptions easier to see. Do not buy on the claim that a platform “makes the fleet compliant.” Ask a provider to demonstrate exactly which driver records, reminders, document permissions and review steps are available today, and test them with your own scenarios.

If you are comparing software, ask Complys for a demonstration against your driver-record workflow and compare other vendors against the same case. The scope of any licence, Driver CPC or tachograph function must be confirmed in the current released product before it is relied on. This guide remains the driver-process owner rather than a general software ranking.

Check the record before calling a driver ready

The useful final question is not “do we have a document?” It is “do we know this driver is authorised for this work, on this date, under the right rules, and can we show how we reached that decision?” A complete driver compliance management process connects the source rule, evidence, reviewer and action. It also shows what is still open.

Check the current DVSA goods vehicle guidance, Driver CPC rules and DVLA licence-check service whenever your vehicles, routes or guidance change. If your operation is in Northern Ireland, is a passenger service or has mixed or unusual use, start from the guidance for that exact scope. Then write the process your team can actually follow and review it when the work changes.

Next step: Map one real driver and journey against these checks. If you are evaluating a system to help manage the records, ask Complys to demonstrate its current workflow against that example and confirm each required function before adopting it.