UK cities
Direct coverage
UK commercial vehicle / tachograph
Tachograph-led accident management for goods vehicles over 3.5 tonnes and PSVs over nine seats. Covers analogue, digital, Smart Generation 1 and Smart Generation 2 v2 devices, retained EU Regulation 165/2014, retained EU Regulation 561/2006 drivers' hours rules, the 365-day vehicle-unit and 28-day driver-card retention windows, fatigue-attribution under the Civil Evidence Act 1995, anti-tamper investigation and Traffic Commissioner public-inquiry preparation.
UK response
Recovery dispatch and live claim handlers, 365 days a year.
UK cities
Direct coverage
Response
First contact SLA
Cost
Upfront to driver
Yes. Tachograph vehicle-unit and driver-card data is admissible in UK civil proceedings under sections 8 and 9 of the Civil Evidence Act 1995. The vehicle unit retains 365 days of activity; the driver card retains 28 days. A written preservation request to the operator and the at-fault insurer inside 24 hours of the collision is the standing first step on any tachograph-led file, citing Article 33 of retained EU Regulation 165/2014 and Civil Procedure Rule 31.
Tachograph data is the single most important documentary record on any accident file involving a goods vehicle exceeding 3.5 tonnes or a passenger-service vehicle over nine seats. Speed at impact, the rest pattern across the preceding fourteen days, the continuous-driving block before the collision, the position of the vehicle at the start and end of the work period and - on a Smart Generation 2 v2 device - at every border crossing and every loading or unloading event are all recorded second by second by a regulated, calibrated head. The regulatory frame is retained EU Regulation (EC) 165/2014 on tachographs and retained EU Regulation (EC) 561/2006 on drivers' hours, brought into Great Britain through the Drivers' Hours and Tachographs (Amendment etc.) (EU Exit) Regulations 2019. The civil-claim admissibility frame is the Civil Evidence Act 1995. This page covers the device generations, the retention windows, the preservation workflow and the fatigue, public-inquiry and anti-tamper angles on the modern tachograph file.
The core tachograph regulation is Regulation (EU) No 165/2014, a recast of the original 1985 instrument. It sets the fitment duty (goods vehicles over 3.5 tonnes and PSVs over nine seats), calibration intervals (every two years at an approved tachograph centre), the operation rules in the cab, the download cycles and the data-retention windows. The companion instrument is Regulation (EC) No 561/2006, which sets the substantive drivers' hours limits: 4.5 hours of continuous driving followed by a 45-minute break (which may be split 15 + 30 in that order), 9 hours of daily driving (extendable to 10 hours twice a week), 11 hours of daily rest (reducible to 9 hours three times between weekly rests) and a 90-hour fortnightly cap. Both regulations are retained in Great Britain through the Drivers' Hours and Tachographs (Amendment etc.) (EU Exit) Regulations 2019; they continue to apply unchanged in substance and are enforced by the DVSA at the roadside and by the Traffic Commissioners at operator-licensing level.
The implementing detail of the device specification sits in Commission Implementing Regulations (EU) 2016/799 and (EU) 2021/1228, which describe Annex IC - the technical specification for the Smart Tachograph Generation 1 (2019) and Generation 2 v2 (2023) devices respectively. The annex is the document a forensic analyst will reach for when looking at the .DDD file structure, the GNSS fix schedule and the event-and-fault log.
The analogue tachograph - Generation 0 in informal usage - used a wax-paper chart rotated by a flexible cable from the gearbox. It is the device fitted to goods vehicles over 3.5 tonnes and PSVs over nine seats first registered before 1 May 2006 and remained in service on those pre-2006 vehicles until the vehicle itself left service. The analogue trace shows speed, distance and activity over a single 24-hour disc cycle; it is read with a magnifying eyepiece and a calibrated ruler. Analogue evidence is admissible in the same way as digital evidence, but the trace is materially less precise than a second-by-second digital record.
The digital tachograph became mandatory from 1 May 2006 for new vehicles. It introduced the personal encrypted driver card, the secure vehicle unit with a rolling-year retention window (the unit was originally specified at 28 days and upgraded across early generations to 365 days; the Annex IC specification now consolidates the 365-day figure) and the standard .DDD download file. Smart Tachograph Generation 1 took the digital baseline and added GNSS positional fixes at the start and end of the daily work period and at the three-hour continuous-driving marker, plus an ITS-G5 short-range radio link by which DVSA roadside readers can interrogate a vehicle as it passes a check point. Smart Generation 2 v2, the current specification, extends the position record to every border crossing and every loading or unloading event, and hardens the device against magnetic and GPS-spoofing attack through paired motion-sensor pairing and forensic-event-log triggers.
Article 33 of Regulation 165/2014 and Annex IC of Regulation 2016/799 set the retention windows. The vehicle unit retains at least 365 days of activity data on a first-in-first-out basis. The driver card retains at least 28 days. The operator is required to download the card on at least a 28-day cycle and the unit on at least a 90-day cycle, and to retain the downloaded data for at least 12 months for inspection by DVSA examiners and the Traffic Commissioner.
The civil-claim consequence is that the 365-day vehicle-unit window is a practical limitation date on a tachograph-led case. A non-fault claimant who instructs a representative at the six-month mark is already inside the back-end of the window. By twelve months, the activity period covering the incident may be partially or wholly overwritten - particularly on a busy fleet vehicle where the rolling window cycles faster than on a lightly worked unit. The first workflow step on any tachograph-led file is therefore to lock down the unit and the card to evidential standard inside the first 24 hours, before the operator's next routine cycle runs.
03
Section 3 of the walkthrough.
Commission Implementing Regulation (EU) 2021/1228 introduced the Generation 2 v2 specification. New vehicles first registered for international transport in or from a contracting party to the European Agreement concerning the Work of Crews of Vehicles engaged in International Road Transport (the AETR agreement) on or after 21 August 2023 must be fitted with the Generation 2 v2 device from manufacture. Vehicles already in international service were required to retrofit an analogue or first-generation digital tachograph to a Generation 2 v2 device by 18 August 2025; first-generation Smart tachographs in international service fall onto the published second-stage timetable that runs into 2026 - operators should verify the current position with the Department for Transport's tachograph guidance and with the calibrating tachograph centre on each vehicle.
Domestic GB-only operation remains subject to the underlying tachograph fitment duty without the international Generation 2 v2 requirement - a vehicle that never leaves Great Britain can lawfully continue on its existing digital or Smart Generation 1 device. In practice many operators standardise on the latest device across the fleet to remove cross-border friction and to access the richer position record on every claim and compliance file.
Tachograph data is admissible in civil proceedings under sections 8 and 9 of the Civil Evidence Act 1995 as a document forming part of a record produced by a person acting under a duty on a device operating reliably. The duty is the operator's analysis-and- retention duty under Article 33 of retained EU Regulation 165/2014; the device reliability is established by the two-yearly calibration certificate held by the approved tachograph centre. The Civil Procedure Rules require the data to be disclosed in standard disclosure where relevant - typically the second-by-second vehicle-speed trace over the 24 hours preceding the collision, the daily-period activity summary for the preceding 14 days and the position record at the start and end of the work period.
Where the operator is the at-fault party and fails to disclose the data on request, the claimant can pursue specific disclosure under Part 31 and, at trial, invite the court to draw an adverse inference under the principle in Wisniewski v Central Manchester Health Authority [1998] - that the failure to produce evidence within a party's control on a matter in issue is itself a fact from which an inference adverse to that party may be drawn. The adverse-inference argument is a recurring lever on tachograph-led files where the unit has been allowed to overwrite the relevant period.
Where the at-fault driver's tachograph shows continuous driving beyond the 4.5-hour limit without a 45-minute break, daily driving beyond the 9- or 10-hour limit, daily rest below the 11-hour minimum or fortnightly driving above the 90-hour cap, the claimant can advance a fatigue-attribution argument. The breach is documentary; the question for the court is whether the breach materially contributed to the collision. On a typical case theory, a driver who has driven continuously for six or seven hours without the regulation break and then makes a lane-change error is presumed by the trace to have impaired attention, and the operator that scheduled the driver inside that pattern bears primary liability alongside the driver's own negligence.
The operator is on the hook in two ways. Vicarious liability for the driver's negligence in the course of employment is the standard route under the line of authority running from Lister v Hesley Hall Ltd to Mohamud v WM Morrison Supermarkets. The operator's own primary duty as a fleet employer to manage drivers' hours under retained Regulation 561/2006 and to act on routine-analysis infringements is the second. Where the breach is repeated and visible in the routine downloads, the case for primary operator negligence is correspondingly stronger and the routine-analysis printouts become a Part 31 disclosure target alongside the incident trace.
Tachograph tampering takes three principal forms. The long-standing magnet attack is placed on the gearbox-mounted motion sensor and causes the device to under-record speed and distance. Modern Generation 2 v2 devices pair the motion sensor cryptographically with the head and log magnet-detection events to the forensic event log; a magnet-attack pattern is therefore typically self-evident on the Generation 2 trace and the trace itself becomes the evidence of the offence. On Smart Generation 1 devices the protection is weaker but the event log still captures motion-data anomalies.
GPS spoofing is the emerging Generation 2 issue. A GNSS-spoofing device broadcasts false satellite signals to make the receiver believe it is in a different location. DVSA and the Crown Prosecution Service investigate spoofing attacks through forensic analysis of the position-trace anomalies - sudden jumps, repeated identical fixes or fixes inconsistent with the recorded distance. Driver-card abuse - sharing a card, using a counterfeit card or driving on a colleague's card - is fraud under section 2 of the Fraud Act 2006 and is investigated alongside the underlying retained tachograph offence. All three patterns undermine the operator's repute on a Traffic Commissioner public inquiry and harden the civil case on contributory negligence and primary operator liability.
The Traffic Commissioners - the independent statutory regulators of the GB heavy goods vehicle and passenger-service-vehicle industries - license operators under the Goods Vehicles (Licensing of Operators) Act 1995 and the Public Passenger Vehicles Act 1981. Section 26 of the 1995 Act sets the powers to call a public inquiry; section 27 the revocation power. A serious collision involving a tachograph-fitted vehicle - particularly a fatal incident or one disclosing apparent drivers' hours breaches - routinely triggers a public inquiry call-up letter from the Office of the Traffic Commissioner to the operator's transport manager.
The Commissioner expects the operator to produce the 28-day driver-card history for every driver involved, the 90-day vehicle-unit downloads for the previous quarter for every vehicle involved and the routine-analysis infringement reports covering the period before the incident. Outcomes range from a formal warning through curtailment (a reduction in the authorised number of vehicles on the operator licence) to revocation of the licence and disqualification of the transport manager. Coordinating the operator's public-inquiry pack with the civil-claim disclosure exercise - so that nothing said at the inquiry contradicts anything said in the civil pleadings, and vice versa - is one of the harder project-management tasks on a serious tachograph-led file.
The vehicle unit is downloaded via its K-line port; the driver card is downloaded through a dedicated card reader. The three principal tool families used at operator and roadside level are the Continental DLD Wide-Range, the Stoneridge OPTAC3 download key and the Tachosys digidown family. Each writes a standard .DDD file containing the encrypted activity record; the file is then read by tachograph-analysis software (TruTac, Tachomaster, Vision FleetWaves, OPTAC3 Office and similar packages) and produces the routine-analysis printout and the infringement reports the operator is required to act on.
For an evidential download in a civil-claim context the priority is chain of custody - recording who downloaded the file, when, onto which device and how it was sealed and stored. CityGrip's standing intake script for a tachograph-led file logs the download tool, the operator-end personnel, the date and time and the file hash on day one, and routes the sealed copy to the at-fault insurer alongside the engineer's report.
Each linked page deepens one element of the commercial-vehicle accident picture. The hub page above sets the four-category map of vehicle-class, trade-audience, regulation and scenario sub-pages. The LGV driver, Driver CPC and commercial- vehicle-insurance pages are the immediate siblings in this wave. The HGV and multi-drop-courier pages are the existing wave-4 cousins that pick up where the tachograph regime intersects each underlying claim pattern.
Step 1
Secure the scene and comply with section 170 of the Road Traffic Act 1988
Stop, set hazards and check anyone involved for injury. Exchange names, addresses, vehicle registration and insurer details with every driver involved. Where injury is present, where details are not exchanged at the scene, or where an animal listed in section 170(8) is hurt, report the collision to the local police force as soon as reasonably practicable and in any event within 24 hours. On a motorway or trunk-road incident follow the National Highways live-lane protocol - do not exit the vehicle in a running lane. Photograph the tachograph head and the printout slot at the scene if it is safe to do so, because the device's serial number and the in-cab installation will both be relevant to any later forensic question about which generation of device is fitted.
Step 2
Issue a written preservation request inside 24 hours
Within 24 hours of the collision, the non-fault driver's representative writes to the at-fault operator and to the at-fault vehicle's insurer asking for an immediate download of the driver card and the vehicle unit covering the 28 days preceding the incident and the 365-day rolling window on the unit. The letter cites Article 33 of retained EU Regulation 165/2014 (the operator's analysis-and-retention duty), Civil Procedure Rule 31 (standard disclosure), the Civil Evidence Act 1995 (admissibility) and the Wisniewski adverse-inference principle. A copy is sent to the Driver and Vehicle Standards Agency where the collision is likely to trigger a roadside or operator-premises investigation in any event.
Step 3
Download the driver card and vehicle unit using a certified reader
The card is downloaded on a dedicated driver-card reader - the Continental DLD Wide-Range, the Stoneridge OPTAC3 download key or a Tachosys digidown family device are the typical operator-grade tools. The vehicle unit is downloaded via its K-line port using the same family of devices. Files are saved in the standard tachograph .DDD format with the date, the vehicle registration, the driver-card number and a one-line description of the incident in the filename. The download is sealed and timestamped to evidential standard, with a chain-of-custody note recording who downloaded it, when and onto which device. The operator's routine analysis output is also preserved.
Step 4
Notify the operator licence holder and prepare for a possible public inquiry
Notify the operator licence holder named on the Goods Vehicles (Licensing of Operators) Act 1995 operator licence - typically the company's transport manager named on OCRS-traceable records. Where the collision is serious or involves a fatality, the Traffic Commissioner may call a public inquiry under section 26 of the 1995 Act. The transport manager should pull the 28-day driver-card history, the 90-day routine vehicle-unit downloads for the previous quarter and the routine-analysis infringement reports. These are the documents the Commissioner expects to see and that establish the operator's compliance posture independent of any single incident.
Step 5
Cross-reference the trace with telematics, dashcam and witness evidence
The tachograph trace gives speed, distance and rest. Independent corroboration usually comes from the operator's telematics provider (Microlise, Webfleet, Samsara, Quartix or similar - each holds its own location, harsh-braking and speed feed), from the in-cab dashcam (forward-facing and increasingly driver-facing in regulated fleets) and from witness statements taken at the scene. CityGrip's evidence pack ties the tachograph .DDD file to the telematics export and to the dashcam clip on a single timeline so the at-fault insurer is faced with a unified record. Where the position trace on a Smart Generation 2 v2 device shows the vehicle at the claimed location at the claimed time, the third-party insurer's room for denying the route narrative narrows to vanishing point.
Step 6
Build the loss-of-earnings and operator-liability case alongside the vehicle claim
Where the non-fault driver is the claimant, build the loss-of-earnings pack from the operator's payslips for PAYE drivers or from the SA302, bank credits and HMRC self-assessment statements for owner-drivers. Where the at-fault driver is the defendant and a fatigue argument is in play, instruct an independent driving-hours analyst to produce a Regulation 561/2006 compliance report on the at-fault tachograph trace for the 14 days preceding the incident. The analyst's report ties any continuous-driving, daily-driving, daily-rest or fortnightly-driving breaches to the case theory on contributory negligence and operator liability, and is admissible in the civil claim as expert evidence under CPR Part 35.
Ranking factors
Tachograph-led files turn on whether the data is preserved before the rolling retention window overwrites the incident period, whether the position trace corroborates the route, whether the drivers' hours record supports a fatigue argument, whether the operator is correctly prepared for a Traffic Commissioner public inquiry and whether any tampering pattern is visible on the forensic event log. CityGrip's intake works each factor on every tachograph file.
A written preservation request to the operator and the at-fault vehicle insurer inside 24 hours of the collision is the single most important step on any tachograph-led file. Citing Article 33 of retained EU Regulation 165/2014, Civil Procedure Rule 31 and the Civil Evidence Act 1995, the letter requires immediate download of the driver card and the vehicle unit covering the 28 days before and the 365-day rolling window. Without it the rolling vehicle-unit window can overwrite the incident period before disclosure ever happens.
Letter dispatched inside 24 hours; chain of custody opened on day one.
The vehicle unit retains 365 days; the driver card retains 28 days. The operator's routine analysis cycle is 90 days for the unit and 28 days for the card. A non-fault claimant who waits even a quarter for the routine cycle is at material risk that the data is overwritten or replaced. CityGrip seals a forensic copy of both files in the standard .DDD format on intake and timestamps the chain of custody before the operator's next routine download cycle runs.
Sealed .DDD files for unit and card, with timestamp and chain-of-custody note.
Smart Generation 1 devices record GNSS position at the start and end of the daily work period and at the three-hour-continuous-driving marker. Smart Generation 2 v2 devices extend the record to every border crossing and every loading or unloading event. The position trace is matched against the operator's telematics provider feed and against any in-cab dashcam to produce a single unified timeline that closes off the third-party insurer's room to deny the route narrative.
Position fixes cross-matched against telematics and dashcam timeline.
Where the at-fault driver's trace shows continuous driving beyond 4.5 hours without a 45-minute break, daily driving beyond the 9- or 10-hour limit, daily rest below the 11-hour minimum or fortnightly driving above the 90-hour cap, an independent driving-hours analyst produces a CPR Part 35 expert report quantifying the breach. The report supports both contributory negligence on the driver and primary liability on the operator under the Lister v Hesley Hall line of vicarious liability authority.
CPR Part 35 expert report quantifying every Regulation 561/2006 breach in the 14 days before the incident.
Where the operator is likely to face a Traffic Commissioner public inquiry under section 26 of the Goods Vehicles (Licensing of Operators) Act 1995, the operator's transport manager pulls the 28-day driver-card history, the 90-day vehicle-unit downloads for the previous quarter and the routine-analysis infringement reports. The civil-claim record and the operator-licensing record are aligned so that nothing said at the inquiry contradicts anything said in the civil pleadings - and vice versa.
Operator's PI pack assembled inside 14 days of the call-up letter from the Office of the Traffic Commissioner.
Tachograph tampering takes three forms - magnet attack on the gearbox-mounted motion sensor, GPS spoofing on the GNSS receiver of a Smart Generation 1 or Generation 2 v2 device, and driver-card abuse (sharing, counterfeit or colleague's-card use). The Generation 2 v2 forensic event log records magnet-detection and position-anomaly events; matching those events against the recorded trace establishes whether the data on the face of it can be relied on. Where it cannot, the case is reframed against the operator on a primary-record-keeping breach.
Generation 2 v2 forensic event log pulled alongside the activity trace; anomalies escalated to DVSA and the CPS where warranted.
Same-day preservation letter to the at-fault operator and insurer, certified .DDD download of the vehicle unit and driver card, CPR Part 35 driving-hours expert report on any retained EU Regulation 561/2006 breach and operator-side preparation for a Traffic Commissioner public inquiry where called. CityGrip Accident Claims (Citygrip LTD).
Calls may be recorded for quality and compliance. We do not provide legal advice. Personal injury enquiries are referred only with your consent to authorised partners.
Visit our team
London office
124 City Road
London, EC1V 2NX