Tachograph Infringements: The Operator's Duty

Most guidance on tachograph infringements is written for drivers: what counts as a breach, how to avoid one. The operator's side is a different question, and a more consequential one — because liability for a driver's infringement can land on the undertaking, and whether it does turns on what the undertaking did before the breach happened.

There is a second thing worth knowing up front, and it is the part almost nobody states plainly: there is no statutory infringement procedure. No law tells you to run a debrief, produce a signed acknowledgement, or escalate through warnings. What the law imposes is a duty to organise and to check. The paperwork everyone builds around that is a way of proving the duty was discharged, not a duty in itself.

General guidance, not legal advice. Drivers' hours and tachograph obligations are enforced by DVSA and the Traffic Commissioners. Check current GOV.UK guidance for your operation and take advice where enforcement action is in prospect.

The Duty That Actually Exists

Assimilated Regulation (EC) No 561/2006, Article 10(2) sets it out:

"A transport undertaking shall organise the work of drivers referred to in paragraph 1 in such a way that the drivers are able to comply with Regulation (EU) No 165/2014 and Chapter II of this Regulation. The transport undertaking shall properly instruct the driver and shall make regular checks to ensure that Regulation (EEC) No 3821/85 and Chapter II of this Regulation are complied with."

Three obligations, in a specific order: organise, instruct, check. Not "discipline". Notice that the first is about how the work is planned — a schedule that cannot be run legally is itself the breach, before a driver has turned a wheel.

The tachograph-side equivalent is Regulation (EU) No 165/2014, Article 33(1):

"Transport undertakings shall be responsible for ensuring that their drivers are properly trained and instructed as regards the correct functioning of tachographs, whether digital or analogue, shall make regular checks to ensure that their drivers make correct use thereof, and shall not give to their drivers any direct or indirect incentives that could encourage the misuse of tachographs."

Same shape. Train, instruct, check, and do not create an incentive to cheat.

The Liability Test

This is the provision to understand before you build any process. Article 10(3) of 561/2006:

"A transport undertaking … shall be liable for infringements committed by drivers of the undertaking, even if the infringement was committed on a territory other than the territory in which it is established. Liability is conditional on the transport undertaking's infringement of paragraphs 1 and 2. Evidence that the transport undertaking cannot reasonably be held responsible for the infringement committed can be considered."

Read the middle sentence twice. Undertaking liability is conditional on the undertaking's own breach of paragraphs 1 and 2 — the pay rule and the organise-instruct-check rule. An operator who genuinely organised the work properly, instructed the driver, and checked the records is in a materially different position from one who did none of those things, even when the same infringement appears on the same printout.

And the last sentence is the reason to keep evidence: "Evidence that the transport undertaking cannot reasonably be held responsible for the infringement committed can be considered." That evidence is your download history, your check records and your instruction trail. Without them there is nothing to consider.

The Pay Rule Nobody Reads

Article 10(1) is short and catches more small operators than it should:

"A transport undertaking shall not give drivers it employs or who are put at its disposal any payment, even in the form of a bonus or wage supplement, related to distances travelled, the speed of delivery and/or the amount of goods carried if that payment is of such a kind as to endanger road safety and/or encourages infringement of this Regulation."

Per-drop bonuses, mileage supplements and delivery-window incentives all sit inside the description. They are not automatically unlawful — the test is whether the payment is "of such a kind as to endanger road safety and/or encourages infringement". But if you pay per drop and your drivers show a pattern of short breaks, the payment structure is the first thing an examiner will connect to the pattern.

Article 10(4) extends the same logic up the chain: "Undertakings, consignors, freight forwarders, tour operators, principal contractors, subcontractors and driver employment agencies shall ensure that contractually agreed transport time schedules respect this Regulation." A customer's impossible delivery window is not a defence, but it is also not solely your problem in law.

What "Regular Checks" Means in Practice

The regulation says "regular checks" without defining an interval. DVSA's guidance on the responsibilities of vehicle operators supplies the operational shape:

• "Make regular checks of charts, manual records and digital data to ensure compliance."
• Download driver cards "at least every 28 calendar days"
• Download vehicle units "at least every 90 calendar days"
• "Be able to produce records to enforcement officers for 12 months."
• "Take all reasonable steps to prevent breaches of the rules"

The download intervals are the practical floor on your check cycle. You cannot check data you have not downloaded, so a 28-day card download is also a 28-day review rhythm — which is why operators who let downloads slip usually have an infringement backlog rather than an infringement problem. Our tachograph downloads guide covers the mechanics, and the tachograph analysis guide covers whether you need software to do the analysis or can stay manual.

Record retention runs on a separate clock. Article 33(2) of 165/2014:

"Transport undertakings shall keep record sheets and printouts, whenever printouts have been made to comply with Article 35, in chronological order and in a legible form, for at least a year after their use, and shall give copies to the drivers concerned who request them."

"In chronological order and in a legible form" is doing real work in that sentence. A shoebox of printouts satisfies neither.

The Debrief: Expected, Not Prescribed

Having read the guidance, here is what it does not say. DVSA's operator-responsibilities page sets a duty to make regular checks and to take all reasonable steps to prevent breaches. It does not prescribe a debrief procedure, a documentation format, or a remedial process after an infringement is found.

What fills that gap is Traffic Commissioner expectation rather than statute. The Senior Traffic Commissioner's Statutory Document No. 3 lists among a transport manager's duties "to contribute to relevant training and subsequent disciplinary processes as required", and requires "that all drivers hours records are kept for a period of no less than 12 months and are made available upon request."

So the honest framing is this: the recorded conversation with the driver is not a legal requirement. It is the cheapest available evidence that you instructed and checked, which is a legal requirement — and it is what a commissioner will ask to see. Build it because it works, not because a regulation names it.

A Cycle That Satisfies the Duty

Four steps, on the 28-day rhythm the download interval already forces:

1. Download and analyse. Cards every 28 days, units every 90. Analyse at download, not at quarter end — a breach spotted six weeks late cannot be prevented, only recorded.
2. Separate the causes. Missing-mileage and manual-entry errors are a training issue. Repeated short breaks under a tight schedule are an organisation issue under Article 10(2), and disciplining the driver for one of those is treating a planning failure as a conduct failure.
3. Record the conversation and the outcome. Date, infringement, what was said, what changes. One page. Signed by both.
4. Review the pattern quarterly, not just the incidents. Three drivers showing the same breach on the same route is a schedule problem, and Article 10(2) puts that squarely on the undertaking.

Where It Ends Up If It Is Not Done

Drivers' hours findings feed the maintenance-and-compliance picture a Traffic Commissioner sees, and the route from there runs through section 26 of the Goods Vehicles (Licensing of Operators) Act 1995 — including "that any undertaking recorded in the licence has not been fulfilled". Drivers' hours compliance is one of the things operators undertake to secure when the licence is granted, which is why an infringement backlog is a licence issue and not only a driver issue. Our O-licence audit guide covers what an examiner asks for, and the OCRS score guide covers how findings score.

To see where your own operation sits before anyone else looks, the free O-Licence Compliance Health Check covers the drivers' hours section alongside maintenance.

Sources

• Assimilated Regulation (EC) No 561/2006, Article 10 — legislation.gov.uk
• Assimilated Regulation (EU) No 165/2014, Article 33 — legislation.gov.uk
• Drivers' hours: responsibilities of vehicle operators — GOV.UK
• Senior Traffic Commissioner, Statutory Document No. 3: Transport Managers, version 17.0 (PDF) — GOV.UK