Tachograph Infringements: An Operator Investigation and Follow-Up Process
A tachograph alert is the start of an investigation, not the conclusion. Use this evidence-led process for debrief, corrective action and follow-up.
Tachograph analysis can flag a possible breach, missing activity or incorrect mode. It cannot always explain why it happened. Treating every alert as proven misconduct risks unfair decisions; accepting every explanation without evidence leaves the compliance system weak.
The operator needs a repeatable path from alert to facts, action and monitored outcome.
An alert is not yet the full finding
First confirm what generated the alert. It may represent an actual drivers’ hours breach, a working-time issue, a manual-entry omission, unaccounted mileage, a device or card problem, incorrect vehicle or driver mapping, or an analysis rule that needs context.
Preserve the original analysis and raw data. Do not edit the event to make the warning disappear. Any correction or explanation should sit alongside the source record.
Triage by seriousness and immediacy
Prioritise:
- most serious or repeated drivers’ hours breaches;
- driving without a card and unaccounted mileage;
- falsification indicators;
- inadequate rest creating current safety risk;
- events involving collision or near miss;
- patterns across a route, planner, depot or driver;
- data gaps preventing a reliable conclusion.
An isolated mode error may need prompt correction and coaching. A suspected deliberate falsification or current fatigue risk needs immediate senior and professional review. Apply company disciplinary procedures fairly and obtain legal advice where necessary.
Preserve the evidence pack
Collect:
- raw driver-card and vehicle-unit data;
- analysis report and exact rule flagged;
- duty roster, job and route plan;
- delivery, ferry, border and waiting evidence;
- timesheets and other-work records;
- manual entries and printouts;
- messages or instructions relevant to the event;
- work for other employers;
- prior related infringements and training.
The goal is to reconstruct the duty without coaching the driver towards a preferred answer.
Interview and debrief the driver
Hold the discussion promptly and privately. Show the event and ask open questions:
- Talk through the duty from the last confirmed rest.
- What work occurred away from the vehicle?
- Were there delays or changed instructions?
- Was the correct mode available and selected?
- Was a manual entry or printout made?
- Did the driver raise concern with the planner?
- Was there pressure, misunderstanding, illness or equipment failure?
- What evidence can confirm the account?
Record the driver’s explanation accurately and allow them to comment on the final note. A signature can confirm receipt and discussion; it should not be represented as an admission if the driver disputes the conclusion.
Decide what actually happened
Classify the outcome:
| Outcome | Example | Response |
|---|---|---|
| Data/configuration issue | Wrong driver mapping | Correct system, retain audit trail |
| Record error | Other work omitted | Complete lawful record where possible; coach |
| Actual isolated breach | Break taken late | Establish cause and proportionate action |
| Planning/system breach | Schedule could not be completed legally | Correct planner process and management control |
| Repeat or serious breach | Similar events after coaching | Escalate under policy and competent review |
| Unable to conclude | Missing source evidence | Record limitation and strengthen capture |
Do not assume the driver is the only cause. GOV.UK operator responsibilities include organising work with full consideration of the rules and giving proper instructions and checks. An impossible schedule is an operator problem even if the driver pressed on.
Corrective action should match the cause
Possible actions include targeted training, device coaching, planner retraining, route-time changes, additional supervision, formal management or disciplinary action under policy, more frequent downloads, agency controls or equipment repair.
Generic annual drivers’ hours training is not a convincing response to a specific recurring planning issue. State what behaviour or process must change, by when and how it will be checked.
For manual-entry errors, use the separate tachograph manual entries guide.
Repeated and serious breaches
Search for recurrence by driver, event type, planner, customer, route and shift. Three similar events may reveal a pattern even when each was handled separately.
Escalation should be defined in policy and take account of seriousness, intent, risk, evidence, prior instruction and employment law. Suspected deliberate interference or falsification needs specialist advice. Do not conceal or retrospectively manufacture records.
Where enforcement contact, a prohibition or an offence occurs, preserve all material and involve the transport manager and appropriate legal adviser promptly.
Earned Recognition: useful benchmark, not universal law
DVSA Earned Recognition audit standards require a robust process, documented investigation and corrective action. They specify driver debrief within 28 days and signed, dated evidence. Those detailed criteria apply to scheme members and applicants; they are not a statutory 28-day rule imposed on every operator.
Even outside the scheme, prompt documented handling is strong practice. Serious safety issues should never wait 28 days.
Trend and verify effectiveness
Report:
- infringements per tachograph day;
- most serious events;
- repeat drivers and repeat causes;
- time from alert to debrief;
- unresolved investigations;
- planning-caused events;
- training actions and recurrence after training.
Review at a consistent interval and sample the underlying cases. A falling number can indicate improvement or missing data; download completeness and unaccounted mileage must be reviewed alongside it.
Digital systems can link analysis, explanation and action. Automated severity labels do not replace competent legal and factual review.
Common mistakes
- Issuing a warning from the alert alone.
- Accepting “traffic” without route evidence.
- Correcting data and deleting the original.
- Training only the driver where the schedule caused the event.
- Treating every Working Time Directive issue as a drivers’ hours offence.
- Closing a case when the driver signs, without checking recurrence.
- Applying Earned Recognition criteria as universal statutory deadlines.
- Ignoring agency or occasional drivers.
Frequently asked questions
Must every alert lead to discipline? No. It must be investigated. The outcome may be data correction, coaching, system action or proportionate formal action depending on facts.
Can a driver explain a breach on a printout? Printouts and notes are required in certain circumstances, but an explanation does not automatically make a breach lawful. Preserve it for competent review.
Who should investigate? A person competent in the relevant drivers’ hours, tachograph and working-time rules, normally under transport manager oversight.
How quickly should debrief happen? Promptly, while evidence is available and risk can be controlled. Earned Recognition’s 28-day criterion is a scheme standard, not a universal waiting allowance.
What proves corrective action worked? Follow-up analysis showing the specific cause did not recur, supported by checks of data completeness and the changed planning or behaviour.
Sources & further reading
Manage checks, defects and records digitally
HauliK gives UK transport operators digital walkaround checks, defect tracking, job management and driver compliance — built around DVSA-aligned workflows.