The most common tachograph infringements, and why they keep happening

The infringements that show up most often in tachograph analysis tend not to be dramatic breaches of the headline daily driving limits — they're smaller, technical issues: a break split in the wrong order, a daily rest reduction used more times in a week than permitted, or a missed manual entry when switching between driving and other work.

This pattern matters because it means the fix usually isn't "drive fewer hours" — it's better understanding of the detailed rest and break rules, and a review process that catches these technical breaches after the fact so patterns can be addressed with drivers before they recur.

Repeated infringements, even minor ones, accumulate into an operator's compliance history and feed directly into DVSA's risk assessment — which means a pattern of small, technical breaches can have a disproportionate effect on how closely a fleet gets scrutinised, well beyond what any single infringement might suggest on its own.

Card-related infringements

A meaningful share of common infringements have nothing to do with driving time at all — they're about the tachograph card itself: a driver using someone else's card, driving without their card properly inserted, or failing to manually enter activity when the card was removed. These are treated seriously precisely because they undermine the record's integrity rather than just describing a single missed break — DVSA can't verify actual compliance from a record that doesn't accurately reflect what happened, regardless of whether the underlying hours were genuinely fine.

What happens at a roadside check when an infringement is found

If a DVSA examiner identifies an infringement during a roadside check, the response depends on severity — a minor technical breach might result in guidance or a warning, while more serious or repeated infringements can lead to a fixed penalty, prohibition on the vehicle continuing (if the issue affects the driver's fitness to keep driving, such as being close to or over a driving-time limit), or referral for further investigation. A driver stopped this way is generally in a considerably better position if they can explain what happened clearly and the record shows an isolated issue, rather than one of several recent similar findings — which is part of why patterns matter more than any single incident in how these situations actually play out.

Why infringement review needs to happen regularly, not just after a check

Operators that only look closely at tachograph data after a roadside stop or an external audit are missing the point of having the data in the first place — regular internal review, ideally weekly or fortnightly rather than only in response to an external trigger, is what actually catches a recurring pattern with a specific driver or route early enough to correct it through training or schedule changes, before DVSA finds it during a check instead. A driver repeatedly splitting breaks in the wrong order isn't usually being careless on purpose — more often it's a habit formed early that nobody's corrected, and a quiet word after the second or third occurrence is a far better outcome than DVSA raising it during a roadside stop.

Route and schedule design as an infringement cause

Some infringement patterns aren't really about an individual driver at all — they're a symptom of a route or schedule that's structurally difficult to run compliantly, where meeting the delivery window and staying within rest and break requirements are in genuine tension most days. Where the same infringement recurs across different drivers assigned to the same route, that's a stronger signal pointing at the schedule than at any individual driver's habits, and it's worth reviewing the route itself before assuming the fix is more driver training.

Having the conversation with a driver about a pattern

How a repeated infringement gets raised with a driver matters almost as much as catching it in the first place. A driver told, after the fact and without context, that they've been non-compliant for weeks is likely to feel ambushed rather than corrected — a better approach is treating the review as routine and ongoing, so that a pattern is raised early, framed around the specific rule that's being misapplied (the break order, the rest-reduction count) rather than a general accusation of carelessness. Drivers who understand specifically what they're getting wrong, and why it matters, tend to correct the habit quickly; drivers who only find out something was wrong when it's already become a bigger problem are more likely to feel it's being used against them.

Analysis software and its limits

Tachograph analysis software is genuinely useful for surfacing infringements at scale — flagging a split break in the wrong order or a rest reduction count across an entire roster is far more reliable done automatically than by manually reviewing individual records. But the software identifies what happened, not why, and it's the why that actually determines the right response: a one-off infringement caused by a genuine unplanned delay needs a different response to the same infringement occurring for the third time this month with the same driver on the same route, even though the software might flag both identically. Treating an automated flag as the end of the review, rather than the start of one, misses the judgement that actually makes the review useful.

What this looks like in practice

• –A driver consistently takes their split break in the wrong order across several weeks before anyone reviews the pattern
• –A card is left out of the tachograph during a short stop for loading, with no manual entry made to cover the gap
• –A daily rest reduction is used for the fourth time in a week without anyone tracking the running count
• –An operator only reviews tachograph data after DVSA flags an issue, rather than on a regular internal cadence