Tachograph Irregularities to Find Before DVSA Does is a working discipline, not a paperwork exercise. For an operator licence holder, tachograph records and drivers’ hours evidence are often the clearest test of whether the business is in control before DVSA, a customer audit or the Traffic Commissioner asks harder questions.
The practical risk is straightforward. A small pattern of missed manual entries, late downloads or unexplained vehicle movement can look like weak management control when DVSA reviews the file. Good operators do not wait for a formal audit to find that out. They build a short, repeatable review process and keep evidence that explains what was checked, what was found and what changed.
Where the file usually starts to weaken
The common pattern is not one dramatic breach. It is a file where infringements are printed, signed and stored, but nobody can show what changed afterwards. A reviewer is rarely impressed by volume alone. A smaller file with clear decisions, dates and follow-up often says more about control than a large folder of disconnected records.
The eight irregularities to sample for first
A practical monthly sample of around ten percent of drivers and vehicles will surface most issues before they become trends. Work through these in order and write down what was checked, by whom and on what date.
- Missing mileage. Compare the start and end odometer readings on the VU printout with the daily defect sheet or job ticket. Any gap that cannot be explained by a workshop movement, fuel run or yard shunt needs an entry.
- Manual entries. Check that other work, availability and rest before the card was inserted have been recorded. Empty days at the start of a shift are one of the first things an examiner counts.
- Card use. Look for two-crew shifts where only one card is in, cards left in overnight, or a driver using more than one vehicle in a day without a clean removal and reinsertion.
- Daily and weekly rest errors. Reduced daily rests should be counted against the two-per-week limit. Weekly rest compensation should be visible on the next-but-one week, not promised verbally.
- Unknown driver records. Every VU download will show some unknown driver time. The question is whether someone has attributed it, marked it as workshop or shunt, and signed off the remainder.
- Infringement debrief. The note should explain the cause, the conversation with the driver, the date, and the signature of both sides. A tick box with no narrative is not a debrief.
- Repeat trends. Sort infringements by driver, vehicle and route over a rolling three-month window. The same name, unit or run appearing repeatedly is a planning issue, not a driver issue.
- Evidence of corrective action. For any repeat trend, the file should show what the operator changed: a briefing, a planning adjustment, a route timing review, a vehicle swap or a tighter review date.
That sample approach keeps the review manageable. It also helps the operator spot patterns early, such as one vehicle, driver, depot, supplier or route creating a disproportionate amount of risk.
Questions a competent reviewer will ask
The review should not stop at whether a document exists. It should ask whether the record is complete, whether it was checked at the right time, and whether someone with authority made a decision when the evidence showed a weakness. If the answer depends on one person explaining it from memory, the system needs tightening.
It is also worth checking whether the same standard applies when the business is busy. Many compliance files look acceptable in a quiet week but weaken during holiday cover, agency driver use, vehicle downtime, late customer changes or pressure to keep a vehicle earning. Those are the moments a regulator or auditor will often test because they show how the system works under strain.
How experienced operators use the findings
The strongest operators treat findings as management information. They record the issue, decide whether it is isolated or repeated, and then make a proportionate change. That might mean a driver briefing, a maintenance provider discussion, a planning adjustment, a clearer handbook instruction or a tighter review date.
An anonymised industry pattern is common here. The operator believes the process is working because records exist, but a sample review shows that the same type of issue is appearing again. The key difference is whether management can prove it noticed the pattern and acted before the regulator did.
Liam Gafoor CMILT IOSH notes: “When a public inquiry brief lands on my desk, the first thing I look for is not the infringement count. It is whether the operator can produce a dated debrief, a signed driver acknowledgement and a follow-up note that proves the issue did not repeat. That sequence is what shows control.”
When outside support helps
Internal checks are valuable, but a fresh review can challenge assumptions and test the file in the way an external auditor might. For operators who want that focused check, Tachograph Analysis Services can help identify the evidence gaps and practical fixes before they become harder to explain.
The sensible next step is to choose one recent vehicle, driver or job file and follow the evidence from start to finish. If the trail is unclear, late or dependent on memory, that is the place to tighten first.
Embed this compliance tool
You can now embed the related Operator Licence Compliance Hub tool on your own website. Open the tool in the Operator Compliance Hub, click Embed this tool, then copy the iframe code into the page where you want it to appear. The embedded version includes Operator Licence branding, a link back to the Compliance Hub and the independent-tool disclaimer.
