Tachograph analysis that stands up to a DVSA check

A DVSA check is not passed by having data somewhere on a server. It is passed by showing that we download tachograph records, review them in good time, identify risk, speak to drivers, correct bad habits, and keep evidence of what we did. That is what tachograph analysis is for in practice.

For transport managers, the real test is simple. If DVSA or the Traffic Commissioner asks what happened after an infringement, a missing mileage exception, repeated manual-entry issues or unexplained unknown periods, can we show the report, the investigation, the driver follow-up and the outcome? If not, the analysis has not done its job.

What tachograph analysis is really for

In UK operator-licence compliance, tachograph analysis is not just the act of collecting driver card and vehicle unit downloads. It is the ongoing review of that data so we can manage drivers hours, Working Time issues where relevant, vehicle use, and the standard of control expected on an operator licence.

That matters because raw files do not explain anything on their own. A download may show an apparent rest reduction, a missing manual entry, a vehicle movement without a card, or mileage that does not match the rest of the fleet record. Until somebody reviews it, asks questions and records the answer, it is only unprocessed evidence.

Operators use tachograph analysis for several practical reasons:

• to spot drivers hours infringements early
• to identify repeated behaviour by driver, depot or vehicle
• to pick up gaps in card use, manual entries and unknown periods
• to reconcile activity against routes, jobs, fuel and mileage
• to support driver debriefs and retraining
• to demonstrate effective management control to DVSA
• to build a defensible file for any Public Inquiry before the Traffic Commissioner

For UK goods and passenger operators, this is part of the wider operator-licence duty to run safely and compliantly. The expectation is not perfection. The expectation is control. A well-run system shows that we know what the reports are telling us, we can distinguish a one-off from a pattern, and we act before a minor issue turns into a licence problem.

There is also a practical point on mixed fleets. Some operators run in-scope HGVs or PSVs alongside vans or support vehicles that are outside tachograph scope. Tachograph analysis still matters because the in-scope activity must sit coherently within the wider fleet record. If a driver, vehicle or route pattern looks wrong, the tachograph record should help explain it, not create more questions.

Where UK and EU rules differ, we need to work to the rules that apply to the operation being carried out. For domestic UK work, transport managers normally focus on the UK enforcement position and operator-licence expectations. For international work, including where EU drivers hours rules apply, the review process needs to reflect that. The key point is that the analysis routine must match the legal regime the vehicle and driver were operating under at the time.

What a transport manager should review in the reports

A useful tachograph report is not one that produces the most pages. It is one that allows a transport manager to review the main exceptions quickly and then drill into the underlying detail.

The first area to review is infringements. That includes daily driving, breaks, daily rest, weekly rest and any other exceptions flagged by the analysis package. We should not stop at the headline count. A single report with ten low-level entries may matter less than one serious event, or less than a repeated pattern across several weeks. The transport manager should look at severity, frequency and whether the issue is isolated or habitual.

The second area is missing mileage. Large unexplained gaps between recorded tachograph activity and vehicle mileage can point to missed downloads, use without the correct card activity, workshop movement, ferry or train treatment entered incorrectly, or a basic data mismatch. Missing mileage does not prove wrongdoing, but it does require an explanation. If the explanation is legitimate, it should be recorded.

Unknown periods matter for the same reason. A report that shows regular unknown periods can indicate that a driver is not making proper manual entries, is inserting the card too late, or is not accounting correctly for other work, availability or rest. At a DVSA check, repeated unknown periods with no follow-up can suggest weak management control.

Manual entries deserve separate attention. They are often the point where otherwise decent drivers fall short. The issue is not only whether a manual entry exists, but whether it makes sense against shift times, previous rest, other work and the next recorded activity. If we see repeated errors by the same driver, the answer is not just to note the infringement. It is to debrief the driver and check whether the driver understands what must be entered and when. Our guide to manual tachograph entries that stand up at a DVSA check covers the practical points.

Rest patterns should be reviewed over time, not just event by event. A driver who regularly runs close to the limits, takes breaks late, or reduces rest in a way that is technically recoverable may still present a compliance risk. The transport manager should look for fatigue-related patterns, pressure points on certain contracts, and any route planning that makes lawful compliance difficult in practice.

Repeat issues by driver or vehicle are often the most important management signal in the whole report set. Examples include:

• the same driver repeatedly failing to make manual entries
• the same vehicle repeatedly showing movements without a card
• a depot where infringements cluster around start times or return times
• agency drivers who generate more unknown periods than employed drivers
• a route or customer schedule that leads to repeated break or rest pressure

This is where tachograph analysis becomes a management tool rather than a filing exercise. If the same issue appears month after month, the question is no longer what happened. The question is why our system allowed it to continue.

It also helps to compare tachograph findings with other records. If a driver says a vehicle defect or breakdown affected the day’s record, we should be able to see that in the defect reporting and VOR history. If workshop time is given as the reason for mileage movement, the maintenance record should support it. If a driver claims training or non-driving duties, that should fit with rota or payroll records.

A structured process for tachograph infringement reviews and driver debriefs makes this much easier to evidence.

How often should tachograph data be downloaded and checked?

The right routine is one that is regular enough to catch problems early and realistic enough that the reports are actually reviewed. A timetable that looks strict on paper but slips in practice is weaker than a routine we can prove we follow every week.

We should separate three things. First, the downloading of driver card data. Second, the downloading of vehicle unit data. Third, the review of the reports and the escalation of exceptions. Those are related, but they are not the same task.

For most operators, the workable approach is to set a fixed schedule for downloads and a shorter internal schedule for report review. In practice, that usually means we do not wait until the next formal download cycle before looking at serious exceptions. If a card download comes in and shows a significant issue, it should be reviewed promptly, not left until month end.

A sensible routine usually includes:

• a defined frequency for driver card downloads
• a defined frequency for vehicle unit downloads
• a review point for new infringement and exception reports
• a named person responsible for first review
• a named transport manager responsible for escalation
• a target timescale for driver debriefs and acknowledgements
• a process for urgent action where a driver should not be planned until the issue is reviewed

We should also allow for event-driven downloads. If a driver leaves, a vehicle is sold, a serious incident occurs, or DVSA requests records, waiting for the next routine cycle is not good enough. The same applies where an agency driver has worked only a short period but has generated concerns.

For operators with multiple depots, owner-drivers, or a heavy use of agency labour, consistency matters more than complexity. The best system is usually one that gives the same review path for each card and vehicle download, regardless of who uploaded it or where it came from.

This is one reason many operators move away from separate spreadsheets, email reminders and local folders. A central system helps us see what has been downloaded, what has been reviewed, what is overdue and what is still awaiting acknowledgement. Our tachograph analysis tools for operator compliance are built to sit alongside the rest of the operator file, rather than leaving tachograph records in a separate silo.

We are not giving legal advice on download intervals here, and operators should work to the rules that apply to their vehicles and operations. The practical point is that whatever schedule we adopt, we must be able to show it is understood, followed and monitored.

What evidence should be kept for DVSA and the Traffic Commissioner?

If DVSA visits or a case reaches the Traffic Commissioner, it is not enough to say that reports were available. We need to show a clear audit trail from data receipt to management action.

At minimum, we should retain the underlying download records and the analysis reports generated from them. But that is only the start. The stronger evidence is everything that shows what we did next.

That usually includes:

• infringement reports by driver and by vehicle
• exception reports for missing mileage, unknown periods and manual-entry issues
• notes of transport manager review
• driver debrief forms or meeting records
• driver acknowledgements, whether signed digitally or in writing
• copies of retraining notes or toolbox talks
• escalation records for repeat or serious breaches
• evidence of any disciplinary action where appropriate
• records showing the issue was checked again afterwards
• management summaries showing trends across the fleet

For a DVSA check, clarity matters. An examiner should be able to pick a driver, a date range or a vehicle and see the sequence. Download received. Report generated. Exception identified. Driver spoken to. Explanation accepted or rejected. Further action taken. Follow-up completed.

Where the explanation depends on another record, we should keep that link. For example:

• a defect or breakdown report linked to a VOR period
• workshop paperwork linked to vehicle movement
• rota or duty records linked to non-driving work
• ferry or train movement details linked to the day’s rest pattern
• agency booking records linked to a temporary driver’s activity

This is where a proper audit trail helps with credibility. If a report was reviewed two months late, altered without trace, or acknowledged by nobody, it will not stand up well under scrutiny. By contrast, a complete record with dates, actions and named users is much easier to defend.

Operators should also keep evidence of the management routine itself. That can include internal compliance calendars, assigned responsibilities, review logs, and proof that overdue items were chased. If the Traffic Commissioner asks how the system works, we should be able to show not only individual cases but the framework around them.

At Operator Compliance, we see the strongest files as the ones that combine tachograph evidence with the rest of the operator record. That means the tachograph review is not floating separately from licence checks, maintenance deadlines, MOT bookings, annual-test dates, insurance and driver qualification records.

Where tachograph analysis fits into wider operator compliance

Tachograph analysis is one part of management control. It becomes far more useful when it is connected to the rest of the compliance system.

Start with drivers. If a driver shows repeated tachograph issues, we should be able to check the driver’s licence status, previous DVLA check dates, Driver CPC position and DQC expiry without opening three different systems. A transport manager looking at an infringement trend often needs the wider picture straight away. Is this a newly qualified driver? An agency worker? Someone whose CPC training is due? Someone already under review?

Then look at vehicles and trailers. A tachograph exception may make more sense when viewed against inspection schedules, MOT bookings, annual-test dates, defects and VOR periods. If a vehicle was off the road, in the workshop or waiting on parts, the record should support that. If it does not, the tachograph report may be the first sign that the wider file is not being maintained properly.

This wider view also matters for operator-licence undertakings. A Traffic Commissioner will not look at tachograph control in isolation if there are also gaps in maintenance planning, inspection records or driver administration. Weakness in one area often prompts questions in another. That is why we recommend keeping one coherent compliance file, whether the fleet is five vehicles or fifty.

For many operators, that file now needs to cover more than the classic HGV or PSV record. Mixed fleets may include vans, trailers, PHV support vehicles or specialist assets. Insurance checks may involve askMID data from the Motor Insurers' Bureau, or MIB records used to confirm cover. Workshop and planning teams may need data passed through a REST API or webhooks. Some operators also want links with tools such as Fleetalyse or Logivo.AI. The point is not to create a technology stack for its own sake. The point is to keep the compliance evidence joined up.

The same applies to the formal operator-licence record. If we need documents for VOL, a site audit, or a hearing, we should not be searching through inboxes, shared drives and depot folders for the last signed debrief. We should know where the record sits and who closed it.

That is the practical difference between having tachograph data and having tachograph control. Good analysis tells us what the data says. Good compliance management makes sure the finding is reviewed, acted on and retained as evidence.

OperatorCompliance was built around that day-to-day reality. Fleeta Limited runs trucks under an operator licence itself, so the system is designed around the records transport managers actually need to produce when DVSA asks questions. The aim is simple, keep tachograph analysis, driver records, vehicle deadlines and signed evidence in one place, in a format that stands up when somebody checks.

If your current process still relies on separate exports, email chases and manual filing, the risk is not only missed infringements. It is being unable to prove that the issue was managed. That is usually where a routine DVSA check becomes a wider compliance conversation.