Why Weak Fleet Records Are Losing Operators Their Licences in 2026
Written by FleetForge editorial team · Published 21 September 2026 · Reviewed for UK fleet compliance guidance · 5 min read

Why Weak Fleet Records Are Losing Operators Their Licences
Traffic Commissioners published several significant regulatory decisions in the weeks leading up to September 2026. Reading through them, a pattern is impossible to ignore: in case after case, operators did not lose their licences because their vehicles were mechanically dangerous. They lost them because they could not produce the records to show that vehicles were being properly managed.
That distinction matters. It means compliance is not just about what your operation does. It is about what your operation can prove.
The core problem: Doing the work and being able to demonstrate the work are two separate disciplines. Most operators understand the first. Far fewer have systems that reliably deliver the second.
This article looks at what the 2026 decisions actually say, what records DVSA and Traffic Commissioners expect to see, and what a reliable audit trail looks like in practice.
What the 2026 Decisions Actually Say
Four Traffic Commissioner regulatory decisions published between April and September 2026 are worth examining in detail. Taken together, they tell a consistent story about where operators are falling short.
CR Steel Construction Limited (May 2026)
CR Steel held a restricted goods vehicle operator licence authorising a single vehicle. Deputy Traffic Commissioner Giles Pengelly revoked the licence and disqualified the director after DVSA identified the following:
-
Vehicles not presented for safety inspections at the declared intervals
-
Ineffective driver defect reporting arrangements and missing records
-
Poor tyre and wheel management despite existing DVSA guidance
-
Defects identified between inspections not dealt with effectively
-
Required records could not be provided to DVSA when requested
DTC Pengelly concluded that the failings had put road safety at risk over an extended period and had undermined fair competition with compliant operators. The director was found to have been personally involved in decisions that compromised safety, and was disqualified.
David William Dyer (April 2026)
This case involved a mechanical prohibition rate of 50% against a national average of 23.21%, and annual test failure rates of 60% (initial) and 53% (final) against national averages of 10.56% and 7.13% respectively. The DVSA examiner found:
-
No brake assessments carried out on any PMI
-
PMI records not signed as roadworthy
-
Mileages between PMIs not accurately recorded, if at all
-
No driver defect reporting system in place
-
PMI records not readily available when requested, and appearing to have been completed that afternoon
The licence was revoked and the operator disqualified for 12 months. The examiner's note about records appearing to have been completed on the day of the visit is particularly telling: incomplete records, presented under pressure, do not satisfy a Traffic Commissioner.
LZtrans Limited (September 2026)
The LZtrans decision, published 17 September 2026, is instructive because the Traffic Commissioner explicitly did not find deliberate deception. DVSA had requested raw tachograph data; the operator sent a report generated by their compliance system instead. The Commissioner noted: "I do not consider this to be a deliberate attempt to deceive, but nor was it acceptable since it was not what DVSA had asked for."
The licence was permanently curtailed to 10 vehicles. The Commissioner cited the accumulation of failures: poor record keeping, lack of written policies, informal systems, and an inability to demonstrate that drivers were completing checks properly. The operator was required to engage a transport consultant and commission an independent compliance audit.
Pioneer Transport Ltd (September 2026)
The Pioneer Transport decision, also published in September 2026, included missing tachograph data that prevented DVSA from conducting a full compliance assessment, no evidence of driver licence checks, no formal induction or toolbox training records, and a failure to supply the required documentation even after being directed to do so by the Traffic Commissioner. The licence was curtailed from 20 vehicles to 8.
What these cases share: None of these operators were found to have deliberately put dangerous vehicles on the road. What they shared was an inability to demonstrate, through organised and retrievable records, that their systems were working. The records were either missing, incomplete, not signed, or not produced when requested.
What DVSA and Traffic Commissioners Actually Expect to See
Understanding what regulators look for removes the guesswork. The DVSA Guide to Maintaining Roadworthiness and the Operator Compliance Audit framework set out the specific records an operator must be able to produce. These are not aspirational standards; they are the baseline against which your operation will be assessed.
The core record categories
| Record type | What it must show | Minimum retention |
|---|---|---|
| Daily walkaround checks | Driver identity, time, vehicle, nil-defect or specific defects found | 15 months |
| Defect reports | Date, time, vehicle, defect description, photographs where relevant | 15 months |
| Defect rectification | When defect was reviewed, repaired, and closed | 15 months |
| PMI records | Vehicle, date, mileage, inspector identity, items checked, brake test results, sign-off | 15 months |
| Forward planner | Scheduled inspections at least 6 months ahead, covering all vehicles | Current and rolling |
| VOR records | Date vehicle declared off road, reason, return-to-service inspection | 15 months |
| Tachograph / driver card data | Downloaded at least every 14 days (driver card) and 42 days (vehicle unit) | 12-24 months |
Key point on retention: The 15-month window runs from the date of each record, not from the date of a visit. If a DVSA examiner arrives today, they expect to see a continuous, unbroken file going back 15 months. A gap of even a few weeks is a finding.
Inspection intervals: what the rules actually say
There is no single statutory interval for safety inspections. Operators set their own frequency based on vehicle age, mileage, load type, and operating conditions, declare it on the operator licence, and are then held to it. Common practice runs from 4 to 13 weeks:
-
Every 6 weeks is the interval DVSA uses as a default benchmark for most HGV operators and is typical for heavily used, older, or arduous-condition vehicles
-
Up to 13 weeks is acceptable for newer, lightly used vehicles where the operator can justify a longer interval with evidence of vehicle condition
-
Shorter than 6 weeks may be appropriate for high-mileage or specialist operations such as tippers, tankers, or refrigerated vehicles
The Traffic Commissioners have consistently emphasised that the declared interval is an undertaking, not a target. An operator who sets a 6-week interval and allows vehicles to run to 8 or 9 weeks is in breach of their licence, even if no defect is found at the overdue inspection.
What auditors check during a compliance visit
When DVSA conducts a compliance audit, the minimum evidence reviewed includes:
-
The forward planner, to confirm inspections were scheduled and met
-
PMIs for a period covering no fewer than four scheduled inspections
-
All defect reports within the sample period (where no defect report is provided, the auditor assumes nil defects were recorded, which raises questions about whether checks were completed)
-
Tachograph lead-in reports, to confirm walkaround checks happened before the vehicle moved
-
VOR records, cross-referenced against drivers' hours data
-
Brake test results at every inspection
-
Wheel and tyre policy documentation
The sample size scales with fleet size: operators with 1 to 3 vehicles must produce all records; operators with 4 to 20 vehicles face a sample of at least 3 vehicles and 4 drivers.
The Gap Between Doing the Work and Proving It
The LZtrans case illustrates the gap most clearly. The operator used a recognised compliance system for tachograph monitoring. When DVSA requested raw data, the operator submitted a report from that system. The Traffic Commissioner rejected it. The request was for raw data; a processed report is not the same thing.
This is not a technicality. It reflects a fundamental point about how regulatory scrutiny works: DVSA and Traffic Commissioners need to examine your underlying records, not a summary of them. If your system cannot export the raw data, or if your team does not know how to retrieve it, that is a compliance gap regardless of how well the underlying operation is running.
Three failure modes that appear repeatedly
The 2026 decisions point to three distinct ways that record-keeping breaks down in practice:
1. Records completed but not retained Walkaround checks happen, defects get reported verbally, repairs are carried out, but nothing is written down or stored. The operation is running correctly, but there is no evidence trail. When DVSA arrives, the operator has nothing to show.
2. Records retained but incomplete PMIs are filed, but brake test results are missing. Defect reports exist, but there is no corresponding rectification record to show the defect was resolved. Walkaround checks are logged, but without timestamps or driver identification. Incomplete records are treated by Traffic Commissioners as inadequate records.
3. Records exist but cannot be retrieved Paper forms are stored somewhere. Spreadsheets exist across multiple folders. The maintenance contractor has some records; the operator has others. When DVSA requests the full file, it takes days to assemble, and gaps appear. In the David Dyer case, the examiner noted that PMI records only became available when the operator's brother arrived and presented forms that appeared to have been completed that afternoon.
The practical implication: An operator who can produce complete, timestamped, retrievable records on the day of a visit is in a fundamentally stronger position than an operator who ran the same operation but kept records informally. The record is not the proof that the work happened; in the eyes of the regulator, the record is the work.
Building a Record-Keeping System That Holds Up
The question for any operator is not whether they are running a safe fleet. Most operators who end up in front of a Traffic Commissioner believe they are. The question is whether their record-keeping system would survive scrutiny on any given day, without advance notice and without time to locate missing documents.
A system that holds up under that standard has four characteristics.
It captures records at the point of activity
Records completed after the fact are weaker than records completed in the moment. A driver completing a walkaround check on a mobile device generates a timestamped record tied to a specific vehicle and date. A driver filling in a paper form at the end of a shift, or a manager transcribing verbal defect reports into a spreadsheet later in the week, creates a record that is harder to verify and easier to challenge.
The tachograph lead-in report is a useful example of how regulators verify this. DVSA auditors check the time between a driver inserting their card and the vehicle moving, to confirm that a walkaround check actually took place before departure. The check is not taken on trust; it is verified against data.
It links defects to outcomes
A defect report that sits in a folder without a corresponding rectification record is an incomplete file. DVSA auditors specifically look for defect reports within the sample period that show a live defect, and then trace those defects through to resolution. If a defect was reported and repaired but the repair was not recorded, the file shows an open defect. That is a finding.
The full chain is: defect identified, defect reported, defect reviewed by management, repair authorised, repair completed, vehicle cleared. Each step needs a record.
It keeps a live forward planner
A forward planner showing scheduled inspections at least six months ahead is a minimum requirement under the DVSA Earned Recognition audit standards. The planner is not just an administrative document: it is how you demonstrate that inspections are being managed proactively rather than reactively. When an examiner lays the planner against the actual PMI reports and counts the gaps, any overdue inspection becomes visible immediately.
It is retrievable without preparation
The test of a record-keeping system is whether a manager can pull the complete compliance file for any vehicle within minutes, not hours. If the answer involves contacting the maintenance contractor, searching through filing cabinets, or reconstructing records from memory, the system is not fit for purpose. DVSA requests for documentation have deadlines; the Pioneer Transport case showed what happens when those deadlines are missed.
A practical checklist for operators reviewing their records:
-
Can you produce 15 months of walkaround checks for every vehicle, with timestamps and driver identification?
-
Does every defect report have a corresponding rectification record showing when and how it was resolved?
-
Are your PMI records signed, dated, and do they include brake test results?
-
Does your forward planner extend at least 6 months ahead and show no overdue inspections?
-
Can you produce raw tachograph data (not just reports) for any requested period?
-
Are VOR records cross-referenced against drivers' hours for the same period?
-
Can all of the above be retrieved and produced within a working day?
What This Means for Your Operation
The September 2026 decisions are a useful prompt for any operator to review their own position, not because a public inquiry is inevitable, but because the standard being applied is consistent and clear. Traffic Commissioners are not looking for perfection; they are looking for evidence of organised, systematic management.
The operators who faced the most serious consequences in 2026 were not necessarily running unsafe fleets. Some had maintenance contractors, some had compliance systems, some had drivers completing checks. What they could not do was produce organised, complete, retrievable records that showed their systems were working.
The practical takeaway is straightforward: if your records would not survive scrutiny today, the time to address that is before a DVSA visit, not during one.
Organising vehicle records, driver checks, defect reports, maintenance schedules, and compliance documents in one place, with clear visibility of what is overdue and what is approaching, is what FleetForge is built to support. Explore FleetForge at fleet-forge.com.
Four UK operators went before Traffic Commissioners this year.
None of them were found to have deliberately put dangerous vehicles on the road.
All four lost or had their licences curtailed.
The reason in every case was the same: they could not produce the records to show their systems were working.
Missing PMI sign-offs. Defect reports with no rectification record. Tachograph data that could not be retrieved when DVSA asked for it. Walkaround checks that may have happened but left no evidence trail.
One operator's PMI records only appeared when a family member arrived with forms that looked like they had been completed that afternoon.
This is the part most operators miss. Compliance is not just about what your fleet does. It is about what your fleet can prove, on any given day, without notice.
DVSA and Traffic Commissioners are not looking for perfection. They are looking for organised, retrievable, complete records. The operators who kept those records came out of 2026 intact. The ones who did not are rebuilding from a curtailed licence or a disqualification.
If you are not confident your records would survive a visit today, that is worth addressing before one arrives.
I have written up the four 2026 decisions in detail, including what DVSA specifically looked for and what a compliant audit file should contain.
Link in the comments.
#OperatorLicence #FleetCompliance #DVSA #TransportManager #FleetManagement
Tags: