Back to blog
Compliance1 May 20267 min read

EU drivers' hours vs the Working Time Directive: the overlap that catches HGV fleets out

Two rulebooks. One driver. Your tachograph analyses one of them. I've seen good operators get a Public Inquiry letter because they kept their drivers legal on driving hours and blew the other ruleset.

EU drivers' hours vs the Working Time Directive: the overlap that catches HGV fleets out

Most transport managers I know can tell you the driving-hours rules in their sleep.

Nine hours driving a day. Ten twice a week. Fifty-six in a week. Ninety over a fortnight. Forty-five minutes break after four and a half hours at the wheel. Eleven hours rest, reducible to nine three times between weekly rests. Forty-five hours weekly rest, reducible to twenty-four. The whole litany.

Ask the same transport manager about working time and the face changes. Eyes drift up and to the left. 'Is that the 48-hour thing?' Yes. 'Night work is ten, isn't it?' Yes. 'And break after – six? Four?' Depends.

And then: 'Doesn't the tacho sort that out?'

Not quite.

Two completely separate rulebooks

The driving hours rules – the ones that came out of EU Regulation 561/2006 and are now assimilated into UK law – are about how long a driver can drive, and how much rest they have between shifts. They govern the time a driver is physically behind the wheel or on duty with the tachograph running.

The Road Transport (Working Time) Regulations 2005 are different. They came out of a different EU directive and they regulate total working time – driving plus loading plus unloading plus paperwork plus the time your driver spent arguing with a receiver at a cold-store in Wigan. Working time is broader than driving time. A driver who did eight hours driving, plus ninety minutes loading, plus another hour waiting on a tip before the receiver arrived, has done a little over ten hours working. They've done eight hours driving. Different numbers on the same day.

The tachograph captures driving time, rest, other work, and availability. It's the evidence base for the first rulebook. It's a partial evidence base for the second. 'Periods of availability' – POA – on the tacho can count differently between the two regimes, and this is where honest operators drop stitches.

The working-time numbers

Four numbers matter most.

First: average 48-hour working week. Across a reference period, each mobile worker in scope of the road transport working time regulations must not exceed 48 hours of work per week on average. The default reference period is 17 weeks. It can be extended to 26 weeks if there's a collective or workforce agreement in place saying so – and there usually is in a well-run operation.

Second: an absolute ceiling of 60 hours in any single week. Doesn't matter what the average is. You can't spike above 60 in any one week. This is where the 48-hour average can be misleading; drivers and planners hear 'average' and push a given week hard, assuming they'll catch up on the next one. Then they do 61 in that week and it's a breach regardless.

Third: night work limit of 10 hours in any 24-hour period that includes night work. A 'night' for these purposes is the period between midnight and 4am – if any of your driver's working time touches that window, that day counts as a night shift and the 10-hour cap applies.

Fourth: a break after six hours of working time. Not driving time. Working time. If your driver has been on duty doing 'other work' for five and a half hours without so much as starting the engine, and then drives for another half hour, they've hit six hours of work and need to break. That's a real example. I've seen it caught on a tachograph analysis report that actually bothered to look at the working-time figure as well as the driving figure.

How the overlaps bite

Scenario one. A driver starts at 06:00. Eleven hours shift, nine hours of driving, two hours of 'other work' (loading, paperwork, two fuel stops, thirty minutes waiting at a gate). Driving-hours rules: fine if breaks are taken properly. Working-time: that's 11 hours of work in one day – well within the absolute 60 cap, and the 48-hour average is still manageable if the rest of the week doesn't stack up. All good.

Scenario two. Same driver, but the week before had been 52 hours of work. The week before that, 51. This week 53. Next week 48. Over four weeks that averages 51 – above the 48-hour average. If the rest of the 17-week reference period averages 46.5, he's compliant. If it doesn't, he's in breach. The point: one week tells you nothing. You have to roll it.

Scenario three. Same driver, but tonight he drives from 22:00 to 03:00. That's 'night work' under the definition, and his shift is now in the 10-hour-night-shift regime. His total working time for that shift has to stay within 10 hours unless his workforce agreement has been varied specifically to allow otherwise. A 12-hour night is a breach, even if the driving hours are fine.

Scenario four. Driver on POA – periods of availability – sitting at a port waiting for a boat. Under drivers' hours, POA isn't driving and counts as a break-like activity. Under working time, POA has to be known in advance, its duration known, and has to be something the driver can't use as rest. If he's told at 08:00 'ferry at 13:00' and sits in the cab, that's POA. If he's told at 08:00 'I'll text you when the boat's ready' and he sits for five hours, that's probably other work, which eats his working-time clock.

Getting POA right matters. I've got a spreadsheet of POA rules stuck on the planner's wall. I'd rather he looks it up than gets it wrong.

What the tachograph shows and what it doesn't

A modern digital tachograph records four activity categories: driving, other work, availability, rest. Your analysis software rolls these up against driving-hours rules automatically. Most analysis packages will also tag breaches of working-time rules if you've configured them to. Mine does. It wasn't enabled when I inherited the fleet. I had to turn it on. Check yours.

What the tacho doesn't record is time before the driver logged in. Or after he logged out. If your driver is clocking in at the yard, walking to his cab, doing twenty minutes of yard work or pre-trip checks before inserting his card, that's working time that the tacho hasn't captured. Under working-time rules, it still counts.

This is why your clock-in system matters. If drivers swipe a card at the gate and that time is logged, you've got a record to set against the tacho start. If drivers 'just turn up and start', you don't, and in an inspection you'll be reliant on your drivers' recollection. Which nobody should want to be.

The bit that catches operators out at Public Inquiry

I've seen two operators in the last three years called in by the Traffic Commissioner where driving-hours compliance was broadly fine but working-time compliance was poor. Both were surprised to be there.

The first ran a fleet doing port transfers and had drivers regularly doing 56-hour driving weeks (legal) that stacked up to 62-hour working weeks (illegal) because of the port waiting time being misclassified. The TC took a dim view.

The second ran overnight deliveries with drivers doing 10 hours driving and two hours of other work on consistent night shifts. Nothing individually dreadful. Over 26 weeks the average working time came out at 51. The analysis had never been looked at because the TM was using driving-hours software only. The infringement report from DVSA was forty pages long.

Neither operator lost their licence. Both got heavy curtailments and a lot of homework. Both are now fine, but they aren't growing the way they were.

The simple operator checklist

Five things.

First, have a workforce agreement or collective agreement in writing, extending the reference period to 26 weeks. It is much more forgiving than 17. Get your solicitor to write one if you haven't; it's a day's work, total.

Second, configure your tacho analysis to surface working-time issues as well as driving-hours ones. If the software can't do it, change software. There are several that do. It's not a nice-to-have.

Third, review a rolling 26-week average for every driver, once a month. Doesn't have to be long. Five minutes per driver, once a month.

Fourth, brief drivers and planners on the 60-hour absolute week. Repeat the briefing every year. Write it down.

Fifth, audit POA classification on a sample of trips every quarter. POA is the biggest single source of working-time disputes with DVSA; getting it right means understanding the difference between foreseeable waiting and just 'hanging around'.

One operational tip that's saved me grief

If you're running night shifts where drivers regularly work 10 hours-plus in the night window, and you don't have a collective agreement that varies the night-work cap, you've got a structural problem that won't fix itself. Either rota differently, or get the agreement in place. Don't 'manage it by trying harder'. I tried 'trying harder' one summer. Lasted six weeks before I had a driver over the limit three nights running and had to admit the rota was wrong.

The rules aren't complicated. They're just two sets of rules instead of one. Run both sets. Check both sets. Brief both sets. Your tacho software isn't going to rescue you on the second one unless you tell it to look.

drivers hoursworking 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.