Here's a sentence I've heard in more yard canteens than I care to count: "I've had my forty-five, I'm good."
Which forty-five?
Because there are two of them — two sets of break rules, two clocks, two different laws, and they don't start counting at the same moment. One is the EU/assimilated driving rules, old 561/2006. The other is the Road Transport (Working Time) Regulations 2005, what most of us call the WTD, or the Working Time Directive. Both apply to you. Both matter. And the one that'll catch you out is almost always the one you're not watching.
I've been running under these rules for over a decade. I still occasionally mess it up. A mate of mine running curtain-sided out of Stafford did £300 of graduated fixed penalties in one go last autumn — not for driving too long, but for working too long without taking the right kind of break at the right time. The tacho said he was fine on 561. The WTD analyser said he wasn't.
Let me pull them apart.
561/2006 — the driving break
This is the one everyone knows. 45 minutes after 4.5 hours of driving, minimum. You can split it: 15 minutes first, then 30 minutes. In that order only. Not 30 then 15. The clock starts when the wheels start turning and accumulates only while you're actually driving.
Here's the bit to hold on to: the 561 break rule is about driving time specifically, not working time. You can be at the wheel for 4.5 hours, park up, stand next to the lorry for three hours doing paperwork, and your 561 clock is still fine — you've had three hours of non-driving, which resets the 4.5-hour clock. You don't need a "break" in the WTD sense. You've had one in the 561 sense by virtue of not driving.
If you exceed 4.5 hours of accumulated driving without taking the 45 minutes (or 15+30), you're in an infringement. The graduated fixed penalty for driving between 15 minutes and 1 hour past your break point is £100. Between 1 and 2 hours past, it's £200. More than 2 hours past is £300. DVSA officers generally allow 15 minutes' leeway before issuing a notice, but "generally" is not a guarantee, and repeated use of the leeway will still trigger enforcement.
WTD — the working break
Different animal. Under the Road Transport (Working Time) Regulations 2005, a mobile worker — that's you — cannot work more than 6 consecutive hours without taking a break. The break rule is:
- If your working day is between 6 and 9 hours total, you need at least 30 minutes of break.
- If your working day is longer than 9 hours, you need at least 45 minutes of break.
- Each break must be at least 15 minutes on its own.
"Working time" under WTD is driving plus other work plus training — effectively everything except rest, breaks, and periods of availability (POA). POA is the square/envelope icon on the tacho, the one you select when you're waiting with no control and no obligation to do anything — sitting in a tipping queue, for example.
So: if you've done six hours of mixed driving and loading at the yard with no breaks, the WTD clock says you must take a break. Even if you've only driven three of those six hours. The 561 clock is nowhere near firing yet. But you're already in WTD infringement territory.
The example that makes it click
Here's a real day. Numbers made up to keep it clean.
06:00 — Start shift at DIRFT. Hi-vis on, walkaround, paperwork. Tacho set to other work. (This is working time under WTD. Not driving under 561.)
07:30 — Pull out of the yard. Wheel starts turning. (561 clock starts. WTD clock has been running since 06:00.)
10:15 — Stop at Lymm Services to pick up a coffee and a bacon bap. Ten minutes off the steering wheel. Tacho on other work while I'm in the service station. (561 clock has banked 2h 45m of driving. WTD clock shows 4h 15m of working time with no proper break — ten minutes isn't a WTD break, it's under 15.)
10:25 — Back on the road.
12:45 — Still driving. That's now 4h 45m of driving since 07:30 with no break of 45 minutes. 561 infringement. Also 6h 45m of working time since 06:00 with no break of at least 30 minutes. WTD infringement.
Both fire. Different magnitudes, same underlying cause: one poorly-timed coffee stop instead of a proper break.
The mate I mentioned earlier? His story was this pattern, but worse. Early start doing pre-load paperwork at the yard, late first break. By 11am he was over on WTD and his 561 was also about to fire. The WTD breach he didn't even notice until the monthly report. The 561 breach he copped at a roadside check that afternoon.
Which one bites first — and why it matters
If your shift is all driving and nothing else, the 561 break will fire first. You drove for 4.5 hours straight, you need to stop and take 45 minutes. WTD is satisfied because your 45-minute break covers it.
If your shift has significant non-driving working time — loading, strapping, yard-shunting, customer delays — the WTD break will fire first. You might have only driven three hours when the WTD clock hits six hours of working time. You need a 30-minute break (or 45 if the total day will exceed 9 hours), and it has to be on the tacho as break or rest, not as other work or POA.
Most UK drivers I know doing general haulage end up on the WTD-fires-first side. If you're loading at one end and tipping at the other, you're often doing three or four hours of non-driving work on top of your driving. WTD fires inside your first shift well before 561 would.
Tramping drivers on long motorway runs with pre-loaded trailers and tip-and-return pattern — those drivers tend to be on the 561-fires-first side. But even they can get caught out when a tip queue goes long.
The weekly average trap
WTD has a weekly side that 561 does not.
Under WTD your weekly working time cannot exceed 60 hours in any single week, and your average over a reference period cannot exceed 48 hours per week. The reference period is 17 weeks by default, 26 weeks if your employer has a collective or workforce agreement in place.
48 hours average. 60 hours cap. That's working time — driving plus other work plus training. Not POA, not break, not rest.
A driver doing 56 hours of driving (the 561 weekly cap) and 8 hours of other work is on 64 hours of working time. They've hit 561's weekly driving limit but they've also broken the 60-hour WTD cap for that single week.
Night work is tighter again. If any part of your working time falls between midnight and 04:00 (goods vehicles) or 01:00 and 05:00 (passenger vehicles), you're a night worker for that 24-hour period. Night workers are capped at 10 hours of working time in any 24-hour period. That 10-hour cap can only be exceeded under a collective agreement.
Period of availability — the useful one
POA is the WTD's get-out, and it's the one most drivers under-use. If you're waiting — genuinely waiting, with no obligation to do any work and some idea of how long the wait will be — you can select POA on the tacho.
POA does not count as working time under WTD. So a two-hour ferry queue at Dover, where you're sitting in the cab with your feet up and you know you've got a boarding slot at 14:00, is POA. Your WTD clock pauses. You're still accumulating elapsed time, but not working time.
Here's the catch: POA has to be genuinely "known duration." Sitting at a customer's gatehouse with no idea when they'll tip you isn't strictly POA — you can't plan around it. In practice, most operators will allow POA for known-duration waits of an hour or more. Most won't allow it for "the forklift driver said he'd be ten minutes" because ten minutes has been known to stretch.
Record POA when it's genuinely available. Don't record it to pad your tacho. A pattern of POA that doesn't match reality on the depot CCTV is one of the ways drivers and operators end up in Traffic Commissioner inquiries.
Night work — the one everyone forgets about
If your shift touches the night window — even by 30 minutes — you're a night worker for that 24-hour period. The 10-hour working time cap bites.
A driver starting at 03:00 for a 06:00 tip in Immingham is a night worker. 10 hours of working time, max. Drive 4 hours, tip for 1 hour, drive 4 hours back, that's 9 hours working time — fine. Add another hour of unloading at the other end and you're at the cap.
Operators with no collective agreement on this need to be disciplined about it. I've seen night-work infringements run for months on one driver's analyser before the TM notices, because everyone's busy watching 561 and nobody's watching the WTD 10-hour.
The practical rule I use
Three numbers in my head. I diary each of them at the start of every shift:
- 561 break due. Wheel-rolling time plus 4.5 hours. That's the latest I can drive past without the 45 minutes in.
- WTD break due. Shift-start time plus 6 hours. That's the latest I can be working without the 30 or 45 in.
- Shift-end target. If I'm on a night shift, shift start plus 10 hours is the cap. If I'm day shift, I'm tracking my 48-hour weekly average on a paper total.
Three numbers. I write them on a bit of masking tape stuck to the dashboard if I'm doing a weird shift. Looks daft. Stops me doing £300 in fixed penalties.
The 15-minute minimum, and the split
Quick one: a WTD break has to be at least 15 minutes to count. So you can't tell the analyser "I had three 10-minute breaks, that's 30 minutes total." Ten-minute breaks don't count. You need at least one 15-minute slot on the tacho as break or rest, and on a longer shift, enough 15-minute-plus chunks to hit 30 or 45 minutes total.
This matters for drivers who snack rather than stop. A five-minute tea break every hour isn't a WTD break. Your tacho's showing no break, and your WTD clock doesn't care that you stretched your legs.
I covered the daily and weekly driving limits in this post
If you want the 561 side on its own — the 9-hour daily drive, the 56-hour week, the 90-hour fortnight — I've broken that down separately. Worth reading alongside this one. The two laws talk past each other often enough that knowing both clocks is the only way to stay clean.
Honest CTA
If you're tired of watching two clocks in your head while you drive, ShiftOwt tracks both 561 and WTD breaks automatically — £5.99/mo for drivers, agency pricing on request. Running both clocks in parallel was the first thing I wanted the app to do. The second was flagging when they're about to clash.