Three clocks, one run, and the Thursday infringement I didn't see coming
I was four months into agency work before I properly understood that EU 561 doesn't run on one driving limit — it runs on three, simultaneously. Daily. Weekly. Fortnightly. And they don't all reset on the same day, or at the same trigger.
Found that out on a Thursday out of Stafford. Thought I had a solid daily window left. Never checked the weekly total. Woke up to an infringement notice three weeks later that I couldn't dispute, because it was right there on the card data.
This is the thing about EU 561/2006: the individual limits are simple enough when you read them one at a time. But they're never one at a time. They run in parallel, and whichever one you're not watching is the one that flags.
Clock one: daily driving
The daily driving limit is 9 hours, counted from the end of one daily rest period to the start of the next. You can extend it to 10 hours — but only twice in any given calendar week. After those two extensions, every remaining day in the week is back to 9 hours maximum.
This is the clock most drivers know. It resets when you take a valid daily rest: a full 11 hours (regular daily rest), or 9 hours if you're using a reduced rest — you're allowed no more than three reduced daily rests between any two weekly rest periods. Once you've taken rest, the daily accumulation starts fresh.
The bit that trips people up: breaks don't reset this clock. A 45-minute break after 4.5 hours of driving — or the split 15 minutes then 30 minutes in that order, as allowed under Article 7 of the regulation — interrupts your driving window and lets you continue. But your total accumulated driving from the end of your last daily rest is still running. You're not back to zero after a break. You're back to zero after rest.
So the pattern is: 4.5 hours of driving, then take your break (all 45 minutes, or 15 then 30, in sequence), then continue driving — but your running daily total is the whole lot. First 4.5 hours, break, second 4.5 hours, you're at 9 hours total. Plan your runs accordingly.
Clock two: weekly driving
The weekly limit is 56 hours. That's the ceiling for a single week — and the week, for 561 purposes, runs from Monday 00:00 to Sunday 24:00. Not from whenever your rota starts. Not seven rolling days from your first shift. Monday midnight to Sunday midnight.
For permanent drivers on a fixed rota, this is manageable. Your employer's tacho analysis software should flag any risk before it becomes an infringement. On agency it's different. Different yards, different start days, different run lengths — and sometimes no one has the full picture of what your card shows.
I had a week out of DIRFT where I'd done two long runs Monday and Tuesday. By Wednesday afternoon I had 37 hours on the week already. The dispatcher had a run for me Thursday and Friday that would have pushed me to 59 hours. They didn't know. I hadn't checked. I did the first of those runs before I realised.
One more thing: the 56-hour weekly limit doesn't exist in isolation from the fortnight total. Which brings us to clock three.
Clock three: fortnightly driving
Over any two consecutive calendar weeks, total driving time must not exceed 90 hours. That's Article 6(3) of EU 561/2006. It's the one most agency drivers barely think about — until it closes off a run mid-week that they'd already committed to.
The maths that catches people: if week one was 56 hours — legal maximum for a single week — week two can only be 34 hours. Not 45. Not 50. Thirty-four. That's from Monday morning of week two to Sunday night, and if you've got four or five days of work scheduled, you're going to hit that cap before you expect it.
The scenario that gets agency drivers specifically is the busy-then-busier fortnight. Week one, you're out of Birmingham and Immingham, solid week, 50 hours on the card. Week two starts, dispatcher has good jobs, you do three days of 9-hour runs — and by Thursday you've done 27 hours this week, which puts the fortnight total at 77. Friday's job is 15 hours to complete. That's 92 hours fortnightly. That's an infringement, and it's one that's hard to argue against because the maths is there in black and white.
How all three interact on a normal tramping week
Picture it from Monday morning, fresh weekly rest taken. All three clocks start clean — except the fortnight, which carries your previous week's total.
Say week one was 50 hours. Now it's Monday of week two.
Monday: 9 hours driving. Weekly: 9 hours. Fortnight running total: 59 of 90.
Tuesday: 9 hours. Weekly: 18. Fortnight: 68.
Wednesday: 9 hours. Weekly: 27. Fortnight: 77.
Thursday: another 9 hours planned. Weekly would be 36. Fortnight would be 86. Still inside the limit — but just.
Friday: you've got 4 hours left in the fortnight (90 minus 86). Your planned run is 7 hours. That's a 3-hour overshoot on the fortnightly total. You can't do 7 hours. You either cut the run to 4 hours, or you don't do it at all.
Nobody runs this calculation on Monday morning. They run it — if they run it at all — when they're halfway through Thursday's job and something starts feeling off about the week. By which point, you're either already close to the limit or already over it.
The reset that isn't where you think it is
Weekly driving resets at the start of the calendar week: Monday 00:00. Not when you take weekly rest, not when your shift pattern changes — Monday midnight.
And here's the thing most drivers confuse: weekly rest restarts the daily clock, but it doesn't wipe the fortnightly total. The fortnight is always a sum of two consecutive calendar weeks. If you took weekly rest on Thursday and start fresh on Friday, the calendar week still changes on Monday — and whatever you drove Monday to Thursday of week one is still in the fortnight calculation for the next Monday-to-Sunday.
This matters particularly for tramping drivers who take a mid-week weekly rest to get home. You're not clearing the fortnightly slate. You're just starting a new week's accumulation on Monday, added on top of whatever went before.
Agency drivers and the three-operator problem
Permanent drivers have a TM who can pull the tacho analysis report and call them before a problem develops. On agency, you might be working for three different operators across a fortnight. None of them has the full picture. They're each seeing their slice of your card, but not the total.
The agency coordinator knows what jobs they've booked for you. They don't necessarily know what hours you're carrying from a week at a different yard. If you tell them you're fine for hours, they'll book you. If you're wrong — because you haven't run the fortnightly sum — neither of you catches it until the tacho analysis flags it.
Took me three months on agency before I started keeping a running note in my phone. Daily total, weekly total, fortnightly running total. Updated at the end of each shift, while I was still in the cab, before I forgot what the tacho showed. Simple enough — but I should have been doing it from day one.
Dispatch once asked me on a Thursday afternoon if I could take a job the following morning that would have put me at 93 hours for the fortnight. I'd checked the numbers. Said no. They were surprised. But I'd have been the one with the infringement on my card, not them.
What the infringement notice actually says
If the tacho analysis picks up a fortnight overshoot, the infringement is categorised by severity — how far over the 90-hour limit, and by what percentage. A minor overshoot is one category; a significant one is another, with a different penalty band under the graduated fixed penalty scheme.
Graduated fixed penalties for EU 561 infringements at the roadside run to £300 for serious or very serious cases. But the longer-term problem is the OCRS impact on operators — every roadside encounter where infringements are found goes on the record, and that record runs for three years. A cluster of fortnight overshoot infringements across a fleet's drivers in a short window is what starts moving operators from green to amber on the Operator Compliance Risk Score. That's the number that determines how often DVSA stop your vehicles at the roadside and what happens at a Traffic Commissioner review.
For agency drivers: your hours are on your card, and the operator you're working for at the time of analysis picks up the infringement data. The fact that three different operators sent you out this fortnight isn't a defence against the maths on the card.
Tracking it manually — the system that works
You don't need software to track three numbers. At the end of each shift:
- Drive hours today
- Drive hours this week (Monday to Sunday running total)
- Drive hours this fortnight (last week's total plus this week's running total)
Reset the weekly total every Monday. The fortnight is the current week added to last week's finished total — two weeks, always calendar weeks, always running.
Takes 90 seconds. Tells you by Wednesday morning whether Saturday's run is actually possible before you've told dispatch you can do it.
If you're tracking this across multiple drivers — or if you're tired of running numbers in a notebook — [ShiftOwt tracks EU 561 and WTD compliance automatically](/onboarding), flags upcoming limit windows before they close, and gives drivers and operators a shared picture of what the card actually shows. £5.99 a month for drivers, agency pricing available for fleets.
The clock most drivers miss
Ask any agency driver which 561 limit caught them out first. Most will say daily driving — took a longer break than planned, misjudged a run, ended up trying to squeeze an extra hour before rest. That's the rookie mistake and most drivers learn it fast.
The fortnightly cap is what gets experienced drivers. They know the daily rule cold. They've got a handle on the weekly. But the fortnight keeps running between weeks, and by the time it matters it's usually a busy Thursday when you've already committed to the job.
Run all three. Not just the daily. Not just the weekly. All three, at the end of every shift, before you close the cab door.