Back to blog
Driver Management18 July 20265 min read

Tachograph infringement review: what operators must do after the data comes off the card

Downloading tachograph data every 28 days is the easy part. Analysing it, recording what you found, and signing off on what you did about it — that's where most operators fall short.

Tachograph infringement review: what operators must do after the data comes off the card

Every 28 days. That's the deadline for downloading your drivers' cards — sooner if a driver is leaving your employment. Every 90 days for the vehicle unit. You probably know that. Most operators do.

What happens after the download is where the gaps appear. Getting the data off the card is step one. Analysing it, identifying infringements, reviewing them with the driver, recording that review, and keeping the record — that's the bit DVSA cares about at an MIV, and the bit that most smaller operators haven't formalised.

Why analysis isn't optional

EU Regulation 165/2014 and the retained assimilated law that governs tachograph use in Great Britain require operators to analyse tachograph data. The download isn't the end of the obligation — it's the start of it. Storing gigabytes of raw data that nobody's looked at isn't compliance. It's evidence of an untriggered obligation.

When DVSA conduct a targeted operator assessment or a maintenance investigation visit, they'll ask to see not just that you've downloaded the data on time, but that you've analysed it. Specifically, they want to see evidence that infringements have been identified and that you've addressed them with drivers. The analysis is what transforms downloaded data into an actual record of driver management.

What the review process should look like

There's no single prescribed format for an infringement review — but there are elements that a credible review includes, and DVSA officers know what a proper one looks like.

First: the analysis itself. Your tachograph analysis software should be producing infringement reports automatically as part of the download process. Most do. If yours isn't categorising infringements by type and severity, you need different software. The categories matter: a missed daily rest period is different from a slightly late break, which is different from a forged record. The response should be proportionate to the severity.

Second: the driver debrief. Minor infringements — a driver who's late starting a break by a few minutes once in a period — can be addressed with a brief written reminder. Serious infringements, or patterns of the same infringement repeating, need a formal documented debrief. That means sitting down with the driver, going through the data, establishing whether the cause was operational pressure, misunderstanding of the rules, or deliberate non-compliance, and recording what was said and what action was agreed.

Third: the record. The record of the infringement review needs to show: what was found, when it was reviewed, that the driver was informed, and what the outcome was. A signature from the driver acknowledging the debrief is good practice — it makes it harder for a driver to later claim they weren't told about an infringement that goes on to become a bigger problem.

How often should you be doing this?

In practice, most operators who are managing this well are running infringement reviews on a monthly cycle — aligned with the driver card download cycle. Download the card, run the analysis, produce the infringement report, debrief within a week or two of the download, file the record. That's the rhythm.

One caveat on timing. The drivers' hours guidance doesn't set a debrief deadline, but DVSA Earned Recognition standard 4.8 does: debrief within 28 days of the infringement itself, not the download. On a full 28-day card cycle an early-cycle infringement can blow past that. I've explained where the 28-day debrief rule comes from and when the clock starts in a separate post.

If you have tachograph analysis software that generates reports automatically, the admin side of this is manageable even for a 20-vehicle fleet. If you're doing it manually from downloaded files — or worse, if nobody's doing it at all because it never got formally set up — monthly is an aspirational target and getting to quarterly at minimum is better than nothing while you build the process.

What happens when infringements aren't reviewed

Here's the risk. A driver accumulates repeated hours infringements. Nobody reviews the data. The driver gets pulled at a roadside stop, a DVSA officer downloads the card at the kerbside, and finds a pattern of missing rest periods going back three months. The officer asks whether the operator was aware. You weren't — because you downloaded the data but didn't analyse it.

That puts you in a difficult position. Not because the infringements are catastrophic individually, but because 'the operator downloaded the data and did nothing with it' is a straightforward failure of the operator's duty to ensure drivers are compliant. It's the kind of thing that features in TC decision documents.

Compare that to: 'The operator downloaded data monthly, identified a pattern of late-break infringements in April, debriefed the driver on 14 April, issued a written warning, and the infringements reduced significantly in May.' That tells a TC a completely different story about how the fleet is managed.

Tachograph records: how long to keep them

Downloaded tachograph data — vehicle unit downloads and driver card downloads — must be kept for a minimum of 12 months. If the tachograph data is your only source of working-time records (which it often is for HGV drivers), the retention period for working-time purposes extends to 24 months.

Keep infringement review records alongside the downloaded data. If a driver debrief happened in April 2025 and DVSA ask about it in July 2026, you need to be able to produce the record. Fifteen months is a reasonable guide for keeping infringement review records — it mirrors the PMI record-retention window and covers most scenarios where the records might become relevant.

The tool question

I've used three different tachograph analysis platforms over the years. Two of them had infringement reporting built in as a standard feature. One didn't — and that's when the review process fell apart, because producing the infringement list became someone's manual job that didn't get done consistently.

If your current setup requires more than a few clicks to produce a list of infringements from the last 28-day download cycle, that's worth fixing. The software exists, it's not expensive for a small fleet, and the alternative is the manual process failing when you're busy — which is exactly when you're least likely to notice it's failing.

tachographInfringementDriver ManagementDVSAComplianceHours

Run a fleet that has to keep DVSA happy?

FleetPad replaces walkaround paperwork, defect logs, and PMI records with one system the transport manager actually reads.