The Working Time Regulations for mobile workers, and how they differ from drivers' hours

It's easy to assume drivers' hours rules — the 9-hour daily driving limit, the 56-hour weekly cap — are the whole picture for how long a professional driver can legally work. They're not. The Road Transport (Working Time) Regulations 2005 sit alongside drivers' hours rules as a separate legal framework, covering total working time rather than just time spent driving, and the two need to be understood — and complied with — independently.

What the Working Time Regulations actually limit

The regulations cap a mobile worker's working time at an average of 48 hours a week, calculated across a reference period, with an absolute limit of 60 hours in any single week. Night work — broadly defined around specific overnight hours depending on the type of vehicle — carries its own tighter limit, generally capped at 10 hours within a 24-hour period where night work is performed at all. There's no individual or collective opt-out available from the 48-hour average, which distinguishes road transport mobile workers from many other sectors where opting out of the standard Working Time Regulations limit is possible.

Working time versus driving time: genuinely different things

This is the distinction that trips people up most often. Drivers' hours rules limit time spent actually driving. The Working Time Regulations limit total working time, which includes driving but also loading and unloading, vehicle checks, cleaning, and other duties carried out as part of the job — a broader category that can run well beyond the hours recorded as driving on a tachograph. A driver could be entirely within their drivers' hours driving limit for the week while still being over the Working Time Regulations' 48-hour average, if enough of their time is spent on loading, admin or other non-driving duties on top of driving itself.

What counts as working time, and what doesn't

Working time under the regulations covers time spent driving, loading and unloading, assisting passengers, cleaning and technical maintenance of the vehicle, and other work intended to ensure the safety of the vehicle, its cargo or passengers — broadly, anything the driver is required to do as part of their duties. Periods of availability — waiting time where the driver isn't required to remain at their post and knows the wait duration in advance — are typically treated differently and don't count in full toward working time, though the exact boundaries of what qualifies as a genuine period of availability are worth confirming against current guidance rather than assumed loosely, since misclassifying working time as availability is a straightforward way to end up non-compliant without realising it.

Record-keeping obligations

Employers are required to keep records of working time and to be able to demonstrate compliance with the weekly and average limits, separately from the tachograph record that already captures driving time and breaks under the drivers' hours rules. In practice, a fleet that's only tracking tachograph data has a genuine gap here — the tachograph doesn't distinguish loading time from driving time in the way that's needed to properly assess Working Time Regulations compliance, so a separate or supplementary record of total working activity is generally necessary to actually demonstrate the 48- and 60-hour limits are being respected.

Night work, and why it's treated more strictly

The tighter cap on night work reflects the additional fatigue risk of working through hours the body is naturally inclined toward rest, and it applies specifically when any part of a shift falls within the defined night period for the relevant vehicle type. A driver whose shift only partly overlaps the night window still triggers the night-work limit for that shift as a whole under the regulations, rather than only the specific hours that fall within the night period being counted — which is a detail worth checking carefully for any schedule that regularly starts or finishes near the edge of the defined night window.

Why this matters even when drivers' hours records look clean

An operator that only reviews tachograph data for drivers' hours compliance can have a driver whose driving-time record looks entirely clean while their total working time — driving plus loading plus other duties — is quietly breaching the Working Time Regulations most weeks. This is a genuinely separate compliance risk from the kind of tachograph infringements that show up in driving-time analysis, and it needs its own review process rather than being assumed to be covered by the drivers' hours checks already in place.

How the averaging period actually works

The 48-hour figure is an average over a reference period, not a hard weekly cap on its own — which means a driver can legitimately work more than 48 hours in a particular week, provided it's balanced out by shorter weeks elsewhere so the average across the whole reference period stays within the limit, and provided the separate 60-hour absolute cap on any single week is never breached regardless of the average. This distinction matters for schedule planning: a fleet that reads the 48-hour figure as a strict weekly ceiling is actually applying a stricter standard than the regulations require, while a fleet that ignores the averaging requirement entirely and only checks the 60-hour absolute cap is missing a genuinely separate obligation. Confirming exactly how the reference period is defined and calculated for a given operation is worth checking against current guidance, since it's a detail that affects how a fleet should actually be reading its own working-time data.

Self-employed drivers and agency arrangements

The application of the Working Time Regulations can differ depending on a driver's employment status, and a fleet using self-employed owner-drivers or agency staff shouldn't assume the same obligations, or the same party bearing responsibility for record-keeping, apply identically to how they'd apply to a directly employed driver. Given how much this can vary by specific arrangement, it's worth confirming the current position for any non-standard employment relationship directly, rather than applying a blanket assumption across a mixed workforce of employed, agency and self-employed drivers.

Drivers splitting their week across more than one employer

Much like the driving-time limits, a driver's total working time under the regulations doesn't reset per employer — a driver working part of the week for one operator and part for another, whether through an agency or a second direct role, still has one combined working-time total that applies across both engagements. Neither employer can safely assume the driver has their full weekly allowance available purely based on what that employer itself has scheduled, which mirrors the same gap that makes driver-hours compliance for multi-employer drivers hard to manage without the driver's active, honest disclosure of hours worked elsewhere.

Building working time into schedule design

Much like drivers' hours compliance, the practical fix for Working Time Regulations pressure is largely a scheduling one — building rotas that account for total working time, not just driving time, with enough margin that a longer-than-usual loading window or an unplanned delay doesn't push a driver over the 48-hour average or the 60-hour absolute cap. A schedule built purely against the drivers' hours driving limits, without separately checking the Working Time Regulations position, can look compliant on the tachograph while quietly breaching a different set of rules entirely — which is exactly the kind of gap that's easy to miss without deliberately checking both frameworks side by side.

Enforcement and how breaches come to light

Working Time Regulations compliance isn't checked at the roadside in quite the same routine way drivers' hours and tachograph records are — it's more commonly examined as part of a wider DVSA investigation, or in response to a specific complaint or incident, which means a genuine breach can persist for a long time without being caught unless an operator is actively monitoring its own position. That's a further reason to treat working time as its own tracked compliance area with a real record behind it, rather than something addressed only if and when it's ever specifically questioned.

Where confusion most often causes a real problem

• –Assuming a driver within drivers' hours driving limits is automatically within Working Time Regulations limits too
• –Treating loading and unloading time as unrecorded 'downtime' rather than working time
• –Misclassifying genuine working time as a period of availability to avoid it counting toward the weekly total
• –Not maintaining a separate working-time record beyond the tachograph, which doesn't capture non-driving duties
• –Applying a single blanket policy across employed, agency and self-employed drivers without checking how obligations actually differ