• KNOWLEDGE HUB

Tachograph Record-Keeping and Analysis: What Operators Must Do

Technical

How often to download driver cards and vehicle units, how long to keep tachograph records, and how to analyse data and act on infringements.

Andy Gilbert
Published
29 July 2026
Last reviewed
29 July 2026

QUICK ANSWER

Downloading tachograph data satisfies only the first of four duties. Operators must also retain the records, analyse them against the drivers' hours and working time limits, and act on the infringements found. It is the analysis and follow-up that a Traffic Commissioner tests - stored files nobody has reviewed will not answer for them.

Four parts to your duty

If you run vehicles fitted with a tachograph, you have a continuous legal duty to download the data, keep it, analyse it and act on what it shows. In practice, that means downloading driver cards at least every 28 days and vehicle units at least every 90 days, keeping the records available for inspection, identifying drivers' hours and working time infringements, debriefing drivers and holding a documented audit trail.

The download is the easy part. The duty the rules really care about, and the one operators most often miss, is analysing the data and managing the infringements it reveals. A box of downloaded files nobody has looked at is not compliance; it is evidence waiting to be used against you.

Downloading the data is the start of the duty, not the end

It is easy to assume that once the data is off the card and the unit and safely on a drive somewhere, the job is done. It isn't. Downloading simply preserves the record. The obligation that actually protects your licence is what you do next.

That duty to check, not just download, is written into the rules. Regulation (EU) No 165/2014 requires transport undertakings to make regular checks and ensure tachographs are used correctly, and Article 10 of Regulation (EC) No 561/2006 makes you responsible for organising drivers' work and checking compliance. GOV.UK puts it plainly: make regular checks of charts, manual records and digital data.

A compliant operator does all of the following, as a routine, every cycle:

  • Downloads driver cards and vehicle units within the legal intervals.
  • Analyses the data for drivers' hours and Working Time Regulations infringements.
  • Identifies missing mileage and data gaps and investigates them.
  • Debriefs drivers on infringements and records the outcome.
  • Takes corrective action where there is a pattern, and keeps evidence that it did.

Miss the last four and you have a filing system, not a compliance system.

How often must you download tachograph data?

Two intervals, and they are not the same. Driver cards must be downloaded at least every 28 days; vehicle units at least every 90 days. Both are maximum intervals - the latest you can leave it - not recommended frequencies.

Driver cards - at least every 28 days

You must download each driver's card at least once every 28 calendar days. The reason is practical as well as legal: a Generation 1 digital driver card holds only about 28 days of activity before the oldest data is overwritten and lost. An “average” day is treated as 93 activity changes, so on busy multi-drop work a generation 1 card can fill in fewer than 28 days.

Part-time and agency drivers are where operators get caught. The 28-day clock runs on the calendar, not on shifts worked, so a driver who only works two days a week still needs their card downloaded every 28 days. If a driver is going on leave, download before they go.

You must also download a card outside the 28-day cycle in these situations:

  • Before a driver leaves the undertaking. This applies to agency drivers too, not just employees.
  • Without delay if the card is damaged or malfunctioning, where a download is still possible.
  • Without delay whenever it is reasonably foreseeable that data is about to be erased.
  • Where the card can only be read through a vehicle unit (for example, a stuck card), before you give up control of that vehicle.

Vehicle units (VU) - at least every 90 days

You must download the vehicle unit at least once every 90 calendar days. A vehicle unit holds roughly a year of average data before the oldest is overwritten, but don't let that lull you. The 90-day maximum (raised from 56 days in 2015) is the legal limit, and a vehicle off the road or away from base can still drift past it. The 90-day window is designed to let many operators fold the download into a scheduled safety inspection.

Don't confuse the two intervals

This is the single most common mix-up: 28 days for cards, 90 days for vehicles. If you remember nothing else, remember that the card interval is the shorter and more frequent of the two, because the card is where data is lost first.

Download more often when the risk is higher

The legal maximums are a backstop, not a schedule. Bring downloads forward where the risk of a gap is higher - for example where vehicles are hired in and out, where drivers are casual or agency, where the work is lots of short urban movements, or where you have a history of missing mileage or repeat infringements. The cost of an early download is nothing; the cost of a lost day of data can be a recordable offence.

When you must download the VU outside the normal cycle

Regardless of where you are in the 90-day cycle, you must download vehicle unit data:

  • Immediately before transferring control of the vehicle to someone else (for example, when it is sold or un-hired).
  • Without delay when permanently removing the unit from service in the vehicle.
  • Without delay on becoming aware the unit is malfunctioning, if a download is still possible.
  • Without delay whenever it is reasonably foreseeable that data is about to be erased.

Lock vehicles in and out with your company card

When a digital or smart vehicle joins your fleet, lock it to your company card (“lock in”); when it leaves (sold or un-hired) lock out. Locking in protects your data so that the full record can only be downloaded with your company card. GOV.UK recommends it because, if a previous operator had locked in and you didn't, you can find you are unable to download your own data. Locking out signals the end of your interest in the vehicle. It is a small habit that prevents a nasty surprise at download time.

Core figures at a glance

What Minimum / interval Notes
Download driver card data At least every 28 days Calendar days. A maximum, not a target. Plus extra triggers - e.g. before a driver (including an agency driver) leaves the undertaking.
Download vehicle unit (VU) data At least every 90 days Calendar days. Plus immediately on sale, un-hire, removal or malfunction (see below).
Produce drivers’ hours / tachograph records to enforcement 12 months DVSA’s stated minimum. Many operators keep longer to cover working time and a possible inquiry.
Keep working time records 2 years (24 months) Two years after the end of the period covered by the records (RT(WT)R 2005, reg 11).
Keep a certificate of undownloadability At least 12 months Issued where a faulty unit’s data cannot be recovered.

How long must you keep tachograph records?

Different records, different retention periods. Underestimating these is the second classic mistake, because the headline “keep it for a year” figure only covers part of the picture.

Drivers' hours and tachograph records - at least 12 months

You must be able to produce records to enforcement officers for 12 months. That is DVSA’s stated minimum for digital VU downloads, driver card downloads and any analogue charts used for drivers’ hours compliance. Keeping them longer is sensible. It costs almost nothing and it covers you if an issue surfaces later.

Working time records - at least 2 years

Records used to show compliance with the Road Transport (Working Time) Regulations 2005 must be kept for at least two years. Specifically, regulation 11 requires an employer to retain them for two years after the end of the period covered by the records. The 48-hour weekly average is calculated over a reference period that is normally 17 weeks (one fixed period each year runs to 18), and can be extended to 26 weeks by a collective or workforce agreement.

Where the tachograph is your only working time record

If tachograph data is the only place a driver's working time is recorded, treat the longer two-year working-time period as the figure that governs how long you keep it. In practice many operators simply retain all tachograph data for two years so they never have to decide which rule applies to which file.

Certificate of undownloadability - at least 12 months

If a unit fails and its data cannot be recovered, the repairing centre should issue a certificate of undownloadability. Keep it for at least 12 months. It is your evidence for why a gap exists.

What records you must actually keep

“Tachograph records” is broader than the downloaded files. A complete record set includes:

  • Digital VU data - the downloaded files from each vehicle unit.
  • Driver card data - the downloaded files from each driver’s card, including part-time and agency drivers doing in-scope work for you.
  • Manual records and printouts - made when a card can’t be used or a tachograph isn’t recording (see below).
  • Analogue charts - if any vehicle still uses an analogue tachograph.
  • Working time records - covering non-driving work, periods of availability, breaks, night work, holidays and sickness, so the 48-hour average can be calculated across the reference period.
  • Your analysis and infringement records - the reports, infringement logs and driver debriefs that show you acted on the data. This is the audit trail, and it matters as much as the raw data.

Separately, drivers must carry records in the cab: the current day plus the previous 28 calendar days for domestic and AETR journeys under the assimilated rules, or 56 days for international journeys to and from an EU member country.

Manual entries and why they matter

Manual entries fill the gaps the tachograph can't capture by itself. Drivers should make a manual entry or printout where, for example:

  • The card is faulty, lost or stolen and they are driving on printouts.
  • They begin or end a duty away from the vehicle and need to record the start or end country and time.
  • They do other work (loading, vehicle checks, paperwork) that the unit won't see if the card is out.

Missing or sloppy manual entries are a common source of apparent infringements and of missing mileage. A driver who forgets to insert their card, or who doesn't record a start location, can turn a perfectly legal day into a data gap that looks like unrecorded driving. Train drivers to make manual entries at the start of duty, not at the end of the month when the infringement report lands.

A manual entry is not a workaround for a forgotten card. If a driver has simply left their card at home, they should not drive an in-scope vehicle fitted with a digital or smart tachograph and then rely on manual records to cover the day. The manual-record allowance is for a card that is lost, stolen or malfunctioning,  not one left on the kitchen table.

Identifying missing mileage and data gaps

Missing mileage is the distance a vehicle has travelled that isn't accounted for by any driver's card record. In the data it shows up as a difference between the odometer reading at the end of one card record and the start of the next. The vehicle moved, but no card was in the slot to record who was driving or how.

It matters because, to an examiner, missing mileage looks like driving that someone is trying to hide. It can indicate a card not being used, a second driver, yard movements, a workshop test drive or a download gap. None of those is necessarily an offence. However, an unexplained gap is a red flag, and a documented explanation is the difference between a non-issue and an investigation.

To investigate, cross-match the vehicle unit data against the driver-card records, and against any other source you hold:  telematics or fuel data, job sheets, workshop and hire records, gate or weighbridge logs. Where a vehicle was driven without a card, identify the driver, get a written explanation, debrief them, and decide whether it needs training, a system change or something more formal.

Whatever you find, record it against the analysis report. “Yard move” on its own proves nothing; “yard move, vehicle [reg], [driver], [date], shunting to the wash bay, confirmed by [manager]” is a closed item that will stand up under scrutiny.

Analysing the data and acting on infringements

This is the heart of the duty, and where outsourced analysis earns its keep. Analysis turns raw downloads into a clear list of what went wrong, why, and what you did about it.

Identifying infringements

Analysis software checks each driver's activity against the drivers' hours rules and the Working Time Regulations (driving time, breaks, daily and weekly rest, the 48-hour average, night work) and flags anything outside the limits. Good analysis distinguishes genuine infringements from data artefacts (a missed manual entry, a ferry, a card pulled at the wrong moment) so you spend your time on the breaches that count.

Debriefing the driver

An identified infringement is the start of a short, repeatable process:

  1. Identify and categorise the infringement (and its severity).
  2. Put it to the driver and get their explanation.
  3. Have the driver acknowledge it - ideally signed or logged.
  4. Decide and record any corrective action, from a quiet word to retraining.
  5. Watch for repeats, because a pattern is what a Traffic Commissioner cares about.

A debrief is not automatically a punishment. Sometimes the right answer is refresher training or better route and shift planning; what matters is that repeat issues show clear management escalation.

Why a documented process matters

A Traffic Commissioner doesn't expect a perfect fleet, infringements happen. What they expect is a system: that you find infringements promptly, deal with them consistently, and can prove it. “We have a process and we follow it” is the single most powerful thing an operator can demonstrate. Ad-hoc checks and a spreadsheet someone updates when they remember do not pass that test.

Storing driver data securely and lawfully

Tachograph data is personal data about identifiable drivers, so the UK GDPR and the Data Protection Act 2018 apply. That doesn't make compliance complicated, but it does mean a few things are not optional:

  • Have a lawful basis. Processing tachograph data to meet your drivers’ hours and working time obligations is generally necessary for compliance with a legal obligation, and for your legitimate interests as operator.
  • Control access. Limit who can see driver data to those who need it, and keep it secure in transit and at rest.
  • Be transparent. Drivers should know their tachograph data is collected, why, and how long it is kept.
  • Don't keep it forever. Retain for the legal minimums above (and a sensible margin), then dispose of it securely. Indefinite retention “just in case” is itself a data-protection risk.
  • Pin down who controls and processes it. If a bureau or software provider handles the data on your behalf, document who controls it, where it’s stored, how long it’s kept and what happens to it when the contract ends. Outsourcing the processing doesn’t outsource your responsibility for the data.

Keeping an audit trail

The audit trail is the evidence that your process is real. “Good” looks like a dated, retrievable record showing, for each cycle:

  • When each card and vehicle unit was downloaded.
  • The analysis output and the infringements identified.
  • The driver debrief, the driver's explanation and acknowledgement.
  • Any corrective action taken, and follow-up on repeat issues.
  • Supporting records - calibration certificates, certificates of undownloadability, manual entries, and any record of system outages or exceptional events.

If you can pull all of that for any driver and any week without a scramble, your audit trail is doing its job.

What DVSA expects you to be able to produce

You don't have to guess what “good” looks like. DVSA’s Operator Compliance Audits guidance sets out, in black and white, the records an operator is expected to produce and it doubles as a checklist to test your own system against. On the tachograph side it asks for:

  • Your process for analysing tachograph data against drivers' hours and working time rules, and who acts on it.
  • Your suite of analysis reports: fleet-level infringement reports, vehicles driven without a card, time since the last vehicle-unit and driver-card downloads, working time reports, workforce agreements and opt-outs.
  • Individual driver infringement reports and the action taken.
  • Evidence the transport manager is involved. For example, signing off infringement debriefs.

If you can produce all of that for a sample of drivers and vehicles covering the last few months, you are in good shape for a desk-based assessment, a site audit or a public inquiry. If you can't, that list is your gap list.

Why this matters for your OCRS and your operator's licence

Your drivers’ hours and tachograph record feeds directly into the traffic-enforcement side of your Operator Compliance Risk Score (OCRS). DVSA uses OCRS to decide whose vehicles to stop and whose records to examine. A higher score means more attention. The score runs on a rolling three-year window, so today’s analysis discipline shapes the inspection pressure you’ll face for years.

DVSA can also ask for your drivers' hours records remotely (a desk-based assessment) or at the depot (a fleet assessment). Records they judge unsatisfactory push your score up. And if matters reach a public inquiry, the question is rarely whether one driver made one mistake. It is whether you had a system capable of preventing, finding and correcting mistakes. A demonstrable analysis process is the answer to that question.

What “good” looks like in practice

Pulling it together, a well-run operation can answer yes to all of these:

  • Cards downloaded inside 28 days, vehicle units inside 90 - every time, tracked, with alerts for anything overdue.
  • Company-card lock-in and lock-out checked for every vehicle entering or leaving the fleet.
  • A clear process for agency and new drivers before they first drive.
  • Every download analysed, not just stored.
  • Infringements identified, put to the driver, and recorded with the outcome; missing mileage investigated and explained.
  • Records retained for the right periods - 12 months for drivers’ hours, two years for working time - held securely and backed up.
  • A complete audit trail that can be produced on demand for any driver or vehicle.

Common mistakes to avoid

The failures that come up again and again are predictable - and avoidable:

  • Downloading driver cards but not vehicle units, so missing mileage and vehicle use go unchecked.
  • Treating 28 and 90 days as the same figure. They are not.
  • Keeping records for 12 months and forgetting that working time records need at least 24.
  • Ignoring agency drivers, hired vehicles, yard movements and vehicles leaving the fleet.
  • Accepting infringement reports that nobody has signed, explained or acted on.
  • Treating a “forgotten card” as something manual records can fix. It can't.
  • Relying on a spreadsheet as the evidence, without keeping the source data and analysis reports behind it.
  • Letting the analysis provider produce reports that nobody in the business reads or acts on.

Taking the burden off your desk

Monitoring download schedules, analysing every cycle and identifying the infringements in the data is what a tachograph analysis bureau does. For most operators the value isn't only the analysis itself; it's having that part done consistently, by people who do nothing else, so the evidence trail is ready and the driver debriefs and corrective action can be built on it. That removes both the routine burden and the risk that a quiet month becomes a problem nobody noticed. This is the service Tacho Agent provides.

External references

This article is provided for general guidance only and reflects our understanding of the rules as they apply in Great Britain as at the date shown on this page. It is not legal advice and should not be relied on as a substitute for advice tailored to your specific operation.
Drivers' hours, tachograph, working time and operator licensing rules are detailed and change over time, and some requirements differ in Northern Ireland and for international journeys. Always check the current guidance on GOV.UK and the underlying legislation on legislation.gov.uk, and consult your transport manager or a qualified compliance professional before acting.
To the fullest extent permitted by law, Tacho Agent Ltd accepts no liability for any loss arising from action taken, or not taken, in reliance on this article. Nothing here excludes or limits any liability that cannot lawfully be excluded, including for death or personal injury caused by negligence or for fraud. Use of this article is also governed by our Terms of Use.

Let us analyse your tachograph data

Tacho Agent reviews your download data, flags the infringements and risks, and shows you exactly where you stand - before DVSA does. Free first report, within 2 working days.

Request a free report →
ON THIS PAGE
Text Link

Related guides