Back to blog
Compliance23 October 20268 min read

Road Transport WTD records: the 2-year retention rule your 12-month tacho archive policy misses

Your tachograph analysis is not the same as WTD compliance. Different calculations, different retention periods, different reference periods. I know operators who deleted files they needed. Here is the difference.

Road Transport WTD records: the 2-year retention rule your 12-month tacho archive policy misses

Two rulebooks. One place where they're not the same.

I've said this before in the context of EU drivers' hours versus the Working Time Directive, and I'll say it again here because it keeps catching operators out: tachograph analysis is not WTD compliance. They're different obligations, they require different records, and they have different retention periods.

Most operators understand the download obligations — vehicle unit every 90 days, driver card every 28. They run tachograph analysis software that flags EU hours infringements. They think that's WTD covered too. It isn't — and the reason it isn't is more subtle than most training material explains.

What the WTD records and why it doesn't match tachograph data

The Road Transport (Working Time) Regulations 2005 (SI 2005/639) govern working time for most HGV drivers. The key limits are a 48-hour average over the reference period (17 weeks by default, extendable to 26 weeks by collective agreement), a maximum of 60 hours in any single week, a 10-hour cap on night work, and daily and weekly rest requirements.

Here's where the divergence from tachograph data begins. The tachograph records driving time, rest, breaks, and "other work." It does not automatically distinguish between WTD "working time" and WTD "periods of availability." Those two categories are treated differently under the WTD.

"Working time" under the Regs includes: driving, loading and unloading, assisting passengers, cleaning and maintenance work, all administrative tasks directly linked to transport operations, and any work required by the employer.

"Availability" is time when the driver isn't working but has to be available to start or resume driving — waiting at a loading bay, accompanying in a second seat in a moving vehicle, on-call but not actually needed. Availability doesn't count toward the 48-hour average or the 60-hour weekly maximum.

A tachograph records availability as its own category (the double-bar pictogram). But the tachograph can't always tell the difference between "availability" in the WTD sense and "other work" in the WTD sense. If a driver is sitting at a loading bay waiting — is that "availability" or is it "work" because they're tied to the location by the job? The answer isn't always obvious from the tachograph record alone. And the answer matters, because the two categories feed differently into the 48-hour calculation.

What records operators must keep for WTD

According to the gov.uk guidance (https://www.gov.uk/guidance/drivers-hours-goods-vehicles/annex-2-working-time-rules), the employer is responsible for keeping working time records, making them available for inspection, and informing workers of their obligations.

The records must cover working time, breaks, and availability in a way that lets you — and an enforcement officer — verify that the 48-hour average, the 60-hour weekly cap, and the night work limit have all been respected across the reference period.

If your tachograph data accurately captures the distinction between working time and availability, and your analysis software correctly categorises and calculates against WTD limits, then your download records may serve as your WTD records. Many do. But "may" is carrying a lot of weight there, and whether yours actually does depends on how consistently your drivers record the distinction and how carefully your software maps the tachograph categories to the WTD definitions.

The reference period problem

The default WTD reference period is 17 weeks. That means you're calculating the 48-hour average across 17 consecutive weeks — not week by week, but as a rolling average. A driver can work 60 hours in one week as long as the 17-week average doesn't exceed 48 hours.

Your tachograph analysis software almost certainly checks per-week driving time and per-day rest time against EU hours rules. It may not be calculating a 17-week rolling average for WTD purposes. That's a different calculation, run over a different timeframe, against a different limit.

If you're relying on your tacho software to confirm WTD compliance, look at the software settings — does it actually calculate the WTD reference period average? Does it flag when a driver is approaching the 48-hour average limit across the period, not just the 60-hour single-week cap? If it doesn't, you have a WTD compliance gap your analysis is missing entirely.

The 2-year retention rule

Here's the difference that bites operators at an HMCE or DVSA inspection. Tachograph records used solely for EU/AETR drivers' hours compliance need to be kept for at least 12 months. But working time records under the Road Transport (Working Time) Regulations must be retained for 2 years after the end of the reference period they cover.

So if your tachograph data is your only WTD record — if you're relying on downloaded tacho files to demonstrate WTD compliance — you need to keep those files for 2 years, not 12 months. An operator who routinely purges tacho archives after 12 months is simultaneously compliant with the tachograph records rule and non-compliant with WTD records retention.

I know operators who've been caught on this exactly. A traffic examiner during a premises compliance visit asked for WTD records covering a period 14 months ago. The tachograph files for that period had been deleted — the operator had kept them for 12 months, hit their retention calendar date, and cleaned up the archive. The policy was correct for EU hours records. It wasn't correct for WTD records from the same data.

Multi-employer drivers

This one catches operators with a pool of agency or shared drivers. Under the Road Transport WTD Regs, a mobile worker driving for more than one employer must inform each employer in writing of hours worked for the other employer, and must provide this information in writing if asked.

As an operator, you're responsible for calculating WTD compliance for work done for you. If a driver splits their week between you and another operator, and you don't know the hours they've worked for the other operator, you cannot calculate whether the 48-hour average is being respected across all their work. You need that information to record and verify WTD compliance.

This is why employment agencies and employment businesses have the same record-keeping obligations — if they're the ones paying the worker, the WTD records obligation sits with them, not automatically with whoever the driver drove for that day.

What a traffic examiner checks

At a compliance visit, a traffic examiner can ask for WTD records. They're looking for records that demonstrate the 48-hour average is being managed, not just records that show EU hours infringement analysis. They want to see evidence that someone in the operation is actually calculating the WTD reference period average.

If you can't show WTD records that are distinct from — or at minimum explicitly cover — the WTD analysis, not just EU hours, you're exposed. "We have the tachograph data" is not the same as "we have WTD compliance records." And the distinction is one that Traffic Commissioners take seriously: the WTD and EU hours are two separate regimes, and conflating them is itself a sign of inadequate compliance management.

Practical steps

Review your tachograph analysis software to confirm it calculates the WTD reference period average, not just per-week driving time. If it doesn't, either find software that does or run the calculation manually (or in a spreadsheet) and keep those records separately.

Update your retention policy to keep WTD records for 2 years. If your tacho downloads are your WTD evidence, they stay for 2 years regardless of your 12-month rule for EU hours-only data.

For any driver working across multiple employers, establish a written process for gathering hours-with-other-employers data and document it. When the traffic examiner asks how you manage multi-employer WTD compliance, "we ask them" is not sufficient. "We have a written requirement, here's the form we use, here's the signed records" is.

Night work records — the WTD gap most tachograph analysis misses entirely

The Road Transport Working Time Regulations 2005 impose a maximum 10-hour limit on night work in any single period. Night work is defined as work during the period midnight to 4am. An operator whose drivers regularly work through the night needs records that demonstrate the 10-hour cap is being respected — not just that EU hours limits are met.

Night work hours appear in tachograph data as work periods that span or fall within the midnight to 4am window. But your tachograph analysis software may not be flagging them against the WTD night work limit specifically — it depends entirely on whether your software has been configured to run that check.

If you have drivers on regular night shifts — trunking, overnight deliveries, 24-hour distribution operations — add an explicit night work check to your WTD review. Pull records for the midnight to 4am window, total the working time in those periods, and confirm no period exceeds 10 hours. Document the check. If it's not documented, it's not evidenced.

What "reference period" actually means in practice

The 17-week reference period for the 48-hour average doesn't reset on a calendar date. It's a rolling 17-week window. That means for any given week, you're looking at the 17 weeks ending that week — including weeks that span different calendar months or quarters.

This catches operators who check WTD compliance quarterly. You might check at the end of Q3 and find everything within limits. But if a driver had a heavy twelve-week run in weeks 5 through 16 of your Q4 check, the WTD average for the seventeen weeks ending that week could still be over 48 hours even if the Q4 quarter average is fine.

If your WTD reference period has been extended to 26 weeks by collective or workforce agreement — which is permitted under the Regulations — the same rolling calculation applies, just over 26 weeks rather than 17. The extension doesn't make it easier to stay within limits; it just gives more time to average down a heavy period.

The workforce agreement mechanism

The 26-week extension to the reference period is available to operators whose workforce arrangements meet the requirements of the Road Transport Working Time Regulations 2005, Regulation 5. In simplified terms: either a collective agreement through a recognised trade union, or a "workforce agreement" with elected employee representatives, can extend the reference period to 26 weeks and can also modify some of the other WTD provisions.

If you're operating on an extended reference period, the workforce agreement must exist in writing and must have been properly established under the Regulations. An informal arrangement, or a written policy that wasn't created through the proper representative process, doesn't satisfy this requirement. If you're unsure whether your arrangement qualifies, get employment law advice — the stakes of getting it wrong are 2-year retention periods and potential regulatory exposure, not just administrative tidiness.

working timetachographComplianceDVSA

Run a fleet that has to keep DVSA happy?

FleetPad replaces walkaround paperwork, defect logs, and PMI records with one system the transport manager actually reads.