The driver self-certified. That's what the operator told DVSA when the compliance notice arrived.
Six weeks of working-time records that were either not kept or not checked. A driver who'd been consistently running 60-plus hours a week because dispatch was short-staffed and the work was there to be done. A transport manager who trusted the weekly self-declarations and didn't pull the actual tachograph data to cross-reference.
The self-certification defence didn't hold. The 2005 Regulations place the obligation on the employer — specifically that the employer must take all reasonable steps to ensure the limits are complied with. Delegating compliance to the driver's own declaration and leaving it at that isn't 'all reasonable steps'. It's paperwork that looks like a system and isn't one.
What the 2005 Regulations actually require from operators
The Road Transport (Working Time) Regulations 2005 (SI 2005/639) are the operative rules. The employer's obligations under these Regulations aren't optional reporting requirements — they're active duties.
Operators must:
- Keep adequate records to show compliance with the working time limits
- Retain those records for two years from the date they're created
- Make records available for inspection by enforcement bodies
- Inform drivers of their working time obligations
- Actively take reasonable steps to ensure limits are not exceeded
'Taking reasonable steps' is where the duty gets teeth. DVSA and enforcement officers interpret this as requiring the employer to have a system that actually monitors working time — not just collects declarations. If you're downloading tachograph data anyway (which you have to do, separately, for 561/2006 compliance), the working-time information is in there. Choosing not to look at it as part of your working-time monitoring is not a reasonable step.
Record-keeping separately: the obligation runs for two years from the date of the record. That's distinct from the 12-month obligation on tachograph records under 561/2006, and from the operator licence record-keeping obligation. Different retention periods, different purposes. An operator who deletes WTD records at the same time as they discard the oldest tacho printouts may be in breach of the WTD record-keeping requirement regardless of whether the tachograph records are in good order.
The dispatch problem
The practical source of most working-time breaches in small and medium fleets isn't malice. It's dispatch.
A driver finishes a tramping week. Dispatch calls on Friday with a loading for Monday morning. Driver says yes. Monday's loading leads to a long day that takes the week to 58 hours by Thursday. Dispatch calls Thursday night with something that needs doing Friday. Driver says yes again.
Nobody at the dispatch desk is looking at a cumulative working-time total. They're looking at whether the driver is available and rested under EU 561 — daily rest taken, weekly rest planned. EU 561 compliance and WTD compliance are separate calculations, and in a small fleet, the 561 compliance is usually what gets the attention because that's what DVSA scrutinise at roadside.
The WTD breach builds quietly across the reference period. It shows up when you pull the records — which DVSA may do at a premises inspection or following a complaint. By then, the breach is already several weeks old and there's limited remediation available.
What reasonable dispatch systems do differently: flag when a driver is approaching the 48-hour average within the reference period and build in cushion before allocating further work. This requires the dispatch system to be aware of working time, not just driving time and rest.
The transport manager's position
A transport manager who signs off on working-time records they haven't reviewed has a compliance gap regardless of how the records are presented. If an enforcement officer requests working-time records and the records don't show the cross-checking and monitoring that 'reasonable steps' implies, the TM's name is on the licence and the licence is the thing at risk.
For CPC-qualified transport managers specifically, a finding that working-time obligations were systematically ignored is relevant to repute — the Traffic Commissioner considers whether a person is of good repute to hold the TM CPC, and persistent non-compliance with working-time law is precisely the kind of finding that puts that assessment in question.
This isn't hypothetical. Traffic Commissioner decisions that touch on working-time compliance do exist. They're usually in conjunction with other compliance failings, but the pattern of ignoring WTD as a secondary concern to 561 compliance appears regularly in decisions that go against operators.
What a reasonable monitoring system looks like
For a small fleet — say, five to fifteen vehicles — a working-time monitoring system doesn't need to be complex. It needs to:
- Record actual working time (not just declared hours) using tachograph data as the primary source, supplemented by timesheets for non-driving work
- Calculate the rolling average against the reference period for each driver
- Flag when a driver is approaching the 48-hour average with weeks still to run in the period
- Record when and how the transport manager reviewed the data
- Retain the records for two years
The tachograph analysis software most operators already use can produce working-time reports. Many operators have this capability and don't use it because nobody set it up and nobody thought to ask. If you're already downloading tachograph data at 28-day (card) and 90-day (vehicle unit) intervals, the working-time analysis should be a standard output from that process — not a separate exercise.
When drivers' self-declarations matter and when they don't
Self-declarations are relevant for non-tacho time — off-tacho work that forms part of working time but isn't captured by the vehicle's recording equipment. Administrative tasks at the depot, loading without a tachograph running, training days. That time needs to be declared by the driver and added to the working-time record.
Self-declarations are not a substitute for analysing the tacho data. If the declaration says 40 hours and the tacho data shows 62, the declaration is wrong. The employer who accepted the declaration without checking is not protected by that discrepancy — if anything, it's evidence that the monitoring system wasn't working.
The agency driver complication
Where agency drivers are involved, working-time monitoring gets more complicated. A driver who works 30 hours for one hirer and 25 hours for another in the same reference week has worked 55 hours of working time in that week — 5 hours above the 60-hour single-week cap, and above the 48-hour average if the pattern continues. Neither hirer necessarily knows about the other's allocation.
The 2005 Regulations require agency drivers to declare their working time from other employers so each employer can take it into account. In practice, this declaration mechanism is poorly understood and inconsistently operated. Agencies rarely have systems that aggregate a driver's hours across multiple hirers. The working-time risk sits on the driver's health, the employers' compliance, and the road — not on anyone's spreadsheet.
If you're a transport manager dealing with regular agency drivers, ask the agency what system they use to monitor cumulative working time across placements. If the answer is 'we ask the driver to tell us', you know where the gap is.
Tracking driver availability and working time for both compliance and dispatch purposes — in one place, automatically — is what ShiftOwt is built to do. £5.99/mo for drivers, fleet pricing available.