I had the download schedule nailed. 28 days for the cards, 90 for the vehicle units, marked on a whiteboard behind the desk. Every download logged in a spreadsheet with a timestamp. I was convinced that was the job done.
The Traffic Commissioner's office thought otherwise. Not because of the downloads — those were fine. What they wanted to see was the working time analysis alongside the infringement records. And that's where I started sweating.
The download cycle — and why most operators have it backwards
The rule is straightforward. Driver card: downloaded at least every 28 days. Vehicle unit: every 90 days. That's your legal minimum under EU Regulation 561/2006 and Regulation (EU) 165/2014 on tachographs, retained in UK law.
What operators keep getting backwards is which interval belongs to which device. I've met transport managers who download the vehicle unit every 28 days out of caution and leave the card for 90. That's not just inefficient — the card has a smaller storage buffer. The driver card stores approximately 28 days of driver activity, which is precisely why the 28-day download window exists. Miss it and you risk overwriting data you're legally required to retain.
The vehicle unit holds considerably more — hence the longer 90-day maximum. Two different devices, two different intervals, for very specific reasons. Get them the wrong way round and you'll end up with a card that's technically been downloaded within 90 days but hasn't captured the last month's worth of activity. DVSA will notice.
From a record-keeping perspective, DVSA expect the downloaded data to be retained for a minimum of 12 months. If the tachograph data is your only source of working-time records — no payroll hours data, no separate WTD log — you need 24 months minimum. That's the less-publicised part of the retention obligation, and it catches small fleets who rely entirely on tacho records and assume 12 months is always sufficient.
What the tachograph analyser actually gives you
Most operators running more than a handful of vehicles use some kind of analysis software to process the downloads. What all these systems do is pull the raw data, parse the activity records, and produce infringement reports categorised by severity. DVSA grades driver hours infringements as minor, serious, or very serious — your software flags them and usually colour-codes the output so you can see at a glance where the reds and ambers are accumulating.
What the analyser does well: it catches the 561 breaches. Daily driving periods over the nine-hour limit. Weekly driving accumulating past 56 hours. Fortnightly totals nudging 90. Missing rest periods. Card not inserted. All of that gets flagged, logged, and reported.
What it doesn't do automatically, for most small fleets: WTD compliance analysis.
And that's the gap that's more likely to bite you at a public inquiry than an amber infringement on a Tuesday.
Two clocks running at the same time
Every HGV driver is running under two separate sets of rules simultaneously. EU Regulation 561/2006 governs driving time and rest — the stuff your tacho analyser tracks. The Road Transport (Working Time) Regulations 2005 — the mobile workers' WTD — governs total working time. Different definitions, different limits, different records.
The 561 side your software handles. The WTD side depends entirely on whether you're feeding it the right inputs and whether you've configured it to produce a working time calculation at all.
Under the WTD, a driver's working time is averaged over a 17-week reference period, with a maximum average of 48 hours per week. The relevant activity categories are driving time, other work, and availability time. Availability time — sitting in the cab waiting to load, on standby between runs, on a ferry — appears on the tachograph as POA (Period of Availability) and is counted differently from active work in the WTD calculation. But it still contributes to a driver's overall working time total.
Here's the problem. A driver spending two or three hours a day on POA at a distribution centre doesn't trip any 561 limit — that time doesn't count as driving. But it does accumulate in the WTD calculation. A driver running 49-hour weeks on the 561 clock could simultaneously be close to the WTD ceiling once POA is factored in. Most tachograph analysers will only show you that picture if you specifically configure them to calculate WTD working time — and most small fleets haven't done that.
I ran that fleet in Coventry for two years before a driver's CPC refresher mentioned the WTD 17-week average and I realised I'd never once checked that figure for any of my drivers. Had all the download logs. Had the 561 infringement reports. Had no idea what the working time exposure looked like.
The infringement communication trail
Before I get to what the TC wanted from the drawer, there's one piece of the compliance picture that operators consistently underestimate: the communication trail after an infringement is flagged.
Finding an infringement on the analysis report is the start, not the end. What DVSA and the Traffic Commissioner want to see is evidence that the operator knew about it, investigated it, told the driver, and took proportionate action. That means a paper trail — or at least a digital one that you can produce on request.
The trail should show: date of infringement, date it was identified in the analysis, what category it was (minor/serious/very serious), what the driver said when asked about it, what action was taken (verbal warning, written notice, training referral), and whether it was a repeat breach. For very serious infringements, the TC expects to see something stronger than a word in the yard.
A lot of small fleets do the analysis and then do nothing formally with the findings. That's a problem. The infringement report with no follow-up looks like a system that catches breaches and files them away. The TC's question will be: what changed to stop it happening again?
What the Traffic Commissioner disclosure request looked like
The request wasn't a full public inquiry — just a call for documentation after a DVSA roadside stop flagged a driver card that hadn't been downloaded on time. Standard stuff. But the disclosure request was broader than just the download record.
They wanted download logs for the previous 12 months — timestamps showing every card and VU download, which device, which driver. They wanted the infringement analysis reports for the same period: what was found, what severity, what action was taken. They wanted evidence of driver communication where infringements had been identified. And they wanted records demonstrating that the operator was monitoring WTD compliance — not just 561.
The download logs were in order. The infringement analysis was mostly there — a couple of serious rest breaches had been documented and the drivers had been spoken to. What didn't exist in any usable form was the WTD side. The data was theoretically available in the tacho software, but we'd never extracted it as a working time analysis, never presented it as a separate record, never sent a driver a notice about their WTD position.
The DVSA officer's comment, roughly: 'You've got the driving time covered. The working time is a different obligation and there's nothing here to show you're meeting it.'
That was an uncomfortable conversation. The outcome wasn't catastrophic — formal undertakings, a requirement to produce WTD records quarterly — but it was entirely avoidable.
Scheduling before the download happens
Here's the fundamental issue with a purely reactive compliance system: by the time you're looking at the download data, the breach has already happened. The WTD exposure is already on the record. The infringement is already in the severity matrix.
The useful question is whether your scheduling process has the information it needs to prevent breaches before they occur. If you're planning a driver's week without knowing their WTD position going into it — how many hours they've worked in the reference period, where they are against the 48-hour average — you're planning without the full picture.
A driver on the Coventry fleet had been doing five 10-hour days for six consecutive weeks before anyone flagged it. His 561 numbers were fine — the 10-hour daily driving extension is allowed twice per week, his weekly rest was compliant, his fortnightly driving total was under 90 hours. But his WTD working time was trending well over the 48-hour average once POA was included, and nobody had noticed because nobody was looking at that figure during the weekly planning meeting.
The scheduling tool needs to know what hours the driver has accumulated, what rest they've had, and what their WTD position looks like across the reference period — not just the current week. A spreadsheet with a vehicle column and a driver column handles the first two. Almost none of them handle the third.
If you're running a small fleet and you're done reconciling 561 records from the tacho analyser with WTD data from a separate spreadsheet, ShiftOwt tracks driver availability alongside 561 and WTD compliance in one place — £5.99/mo per driver, fleet pricing on request. It won't replace your tacho analyser, but it fills the scheduling layer that most analysers leave blank.
The five-component compliance picture
To pull this together: download schedule (28/90 days), record storage (12 months minimum, 24 months if tacho data is the sole WTD source), infringement analysis, driver communication trail, WTD working-time records. Five separate components. Most small fleets have three of them in reasonable shape and are missing the last two.
If a DVSA officer asks for documentation, or you get a disclosure request, those last two are where the conversation gets difficult. Not necessarily because the breach was serious, but because an incomplete compliance system suggests you haven't understood the full scope of the obligation.
The whiteboard with the download schedule was a start. Took me two years and a disclosure request to find out it wasn't the whole job.