Three months after the accident, the call came from a solicitor's office. They wanted tacho records — driver card data, VU printouts, the lot — going back to the fortnight before the incident. A rear-end shunt on the M1 near Northampton. Nothing serious, no injuries, the car driver's insurance was already on it. But the solicitor acting for the car driver's insurer had done their homework.
The driver had been running legally on the day. But the six weeks before told a different story — a pattern of late rest, two weeks of consistently short daily rests that hadn't been identified or addressed. The solicitor knew how to read an infringement report. The operator's insurance covered the claim. The premium the following year was a different matter.
Why tachograph records matter after an accident
In any HGV accident involving another party — a rear-end collision, a side-swipe, a pedestrian incident — the investigation that follows will almost always include a review of driver hours and rest. This isn't just DVSA or police looking for a prosecution. It's the insurers, the claimants' solicitors, and potentially your own legal representation, all trying to establish what happened and who's liable.
Tachograph data is the closest thing to an objective record of what a driver was doing in the hours and days before an accident. How long they'd been driving that day. When they last took proper daily rest. Whether there were infringement patterns in the preceding weeks. It's all there — on the driver card, in the vehicle unit — and it's all disclosable.
How records get accessed
There are several routes by which tachograph data ends up in front of lawyers after an accident.
Police at the scene. Officers lawfully present at the accident scene have powers under PACE 1984 to seize anything they reasonably believe is evidence of an offence — including digitally stored data. A constable can require that electronic information be produced in a form that can be taken away. If they believe driver fatigue or hours violations contributed to the accident, they can take the vehicle unit data or require it be downloaded at a DVSA testing station.
DVSA follow-up. DVSA examiners, under Section 99 of the Transport Act 1968, can independently compel the production of tachograph records and driver files. A serious accident on a major route will often trigger a DVSA premises inspection within weeks — not because they're looking for a criminal charge, but because it's standard practice for any operator involved in a significant road incident.
Civil disclosure. In a personal injury or property damage claim, both sides in the litigation are required under court rules to disclose documents relevant to the case, including tachograph records. This isn't optional. A solicitor acting for the other party will make a formal request for the records as part of standard disclosure, and the operator must comply. The 12-month retention obligation that operators have for driver card data means these records should still exist — and if they don't, that absence itself becomes a problem in litigation.
Subject access requests. The driver can make a subject access request for their own data under UK GDPR Article 15 — including tachograph records — and may do this to prepare their own legal position. I covered the data rights angle in more detail [in the UK GDPR and tachograph post](/blog/tachograph-data-uk-gdpr-driver-card-subject-access).
What being over-hours at the time of an accident means for liability
Here's the important one, because it comes up in conversations and not everyone gets it right.
If a driver is over their legal hours at the time of an accident — running beyond the 9-hour daily driving limit (or both 10-hour extensions used up), or driving into rest period — this doesn't automatically make the driver or operator liable for the accident. Road accidents involve complex factual questions about speed, road conditions, third-party actions, and driver behaviour. Being over hours is one factor among many.
But it's a significant factor. In a civil negligence claim, a court will consider whether the driver was fatigued and whether that fatigue contributed to the accident. Hours violations are evidence that speaks directly to fatigue risk. A driver who was operating legally and alert is in a very different position from one who was already into an infringement when the collision happened. Expert evidence — accident reconstruction, fatigue science, tachograph analysis — will make that visible to a judge or jury.
For criminal prosecution — dangerous or careless driving — hours violations similarly strengthen the prosecution's case that the driver was impaired by fatigue. Not conclusive, but hard to ignore.
What the Road Traffic Act 1988 says about insurance cover
This is the bit that surprises people. If a driver was in breach of hours rules, or if the operator's maintenance was defective, or if the vehicle was overloaded — does that void the insurance policy and leave the third party with nothing?
No. Section 148 of the Road Traffic Act 1988 prevents insurers from refusing to pay third-party claimants on the basis of certain policy conditions being breached, including conditions related to:
- The physical or mental condition of the driver (which includes fatigue-related impairment from hours violations)
- The condition of the vehicle
- Weight or characteristics of the goods being carried
- The times during which the vehicle is used
This protection is specifically for the third party — the person harmed. The insurer cannot use hours violations as an excuse to leave an injured pedestrian or car driver without compensation. Third-party liability cover pays out regardless of the driver's hours compliance at the time.
What Section 148 does not prevent is the insurer seeking to recover their payment from the operator or driver once they've paid out to the third party. So the claim gets paid — but then the insurer comes back to the operator. In practical terms, this can mean the operator bears the full cost of a large claim while the insurer treats it as a recoverable amount rather than an insured loss.
Own-damage cover — damage to your own vehicle — is a different matter. Policy wording governs what's covered, and a policy may well have conditions that allow the insurer to contest a claim where hours violations contributed to an accident. Check your policy wording, not the Road Traffic Act. The RTA protects third parties; it doesn't guarantee your own vehicle cover in every circumstance.
What the operator should do after any accident
Regardless of severity, the steps are consistent:
- Preserve the tacho data. Don't download and overwrite without retaining the data from the relevant period. The vehicle unit keeps the last 90 days; the driver card keeps the last 28 days of activity. These need to be retained intact and backed up before they risk being overwritten.
- Run an infringement analysis on the period covering the accident and the weeks before. If there are issues, you want to know about them before the solicitor does, not after.
- Notify your insurer promptly — most policies require it, and delays in reporting can complicate the insurer's position.
- Don't destroy or alter records. This is obvious, but worth saying: deliberately withholding or altering tachograph data in the context of an accident investigation is a serious criminal offence.
The pattern no one notices until it's too late
The accident my mate's situation stemmed from wasn't caused by a single day's bad planning. It came out of six weeks where the infringement analysis sat unreviewed in the TM's email inbox. Short rest periods were flagged. Nothing happened. The driver kept running a pattern that wasn't safe, and nobody intervened.
The accident was attributed to road conditions. The driver wasn't prosecuted. But the hours history sat in the claim file and the premium went up significantly at renewal. That's the cost that doesn't make the news but lands on the operator's P&L.
If you're running a fleet and you're not reviewing infringement reports regularly — not generating them, reviewing them and acting — the tachograph is recording a history you'll wish you'd seen sooner. ShiftOwt flags 561/WTD infringement patterns before they become a legal disclosure problem — fleet pricing on request.