Driver Hours Weekly Rest: Reduced Rest, Compensation and Evidence
Driver hours weekly rest is one of the most common areas where tachograph compliance looks acceptable at first glance but weakens when the full pattern is reviewed. The issue is rarely a single missed rest period. It is usually the interaction between duty planning, daily rest, reduced weekly rest, compensation tracking, manual entries, agency work and the operator's follow-up records.
Weekly rest should be checked as part of routine tachograph analysis, not only when software flags a breach. DVSA and Traffic Commissioners expect licence holders to manage drivers' hours actively, investigate repeated issues and keep evidence showing that planners and drivers have been corrected where required.
Weekly rest in context
Most goods and passenger operations are subject to assimilated drivers' hours rules, still widely referred to as EU drivers' hours rules. Some work falls under GB domestic rules. Before judging any record, confirm which rule set applies to the work, the vehicle and the journey pattern.
Under the assimilated rules a regular weekly rest is at least 45 hours. A reduced weekly rest is at least 24 hours but less than 45. Across any two consecutive weeks a goods driver must take at least one regular weekly rest, so two reduced weekly rests back to back is not permitted. The reduction taken from a 45 hour period must be repaid in one block, attached to a rest period of at least nine hours, before the end of the third week following the week in which the reduction occurred.
Official GOV.UK guidance for goods vehicles is available at drivers' hours: goods vehicles. Use that alongside tachograph analysis, driver records and route planning evidence.
What weekly rest checks should review
A proper review looks at the full working pattern across the relevant weeks. A single infringement report is useful, but it will not always explain why the problem happened or whether the operator's planning system contributed to it.
| Check area | Evidence to review | Common weakness |
|---|---|---|
| Weekly rest timing | Driver card data, vehicle unit downloads, duty rosters and shift start and finish times. | The rest period falls late because the prior duty pattern was not monitored. |
| Regular vs reduced | Length of each weekly rest, the pairing across two consecutive weeks and any back to back reductions. | Two reduced weekly rests in a row are missed by the analysis settings. |
| Compensation tracking | Rest owed, attached rest period, and the date by which compensation must be taken. | Managers accept the reduction but do not log when compensation falls due. |
| Manual entries | Card insertion records, periods away from the vehicle, other work and availability entries. | Missing entries hide work that affects rest calculation. |
| Planning pressure | Run sheets, delivery windows, return journeys, traffic assumptions and customer requirements. | Several drivers show the same pattern but only individual warnings are issued. |
| Corrective action | Debrief notes, training records, planner review and the next analysis period. | The infringement is signed off without checking whether the problem stopped. |
Reduced weekly rest and compensation
Reduced weekly rest needs close control because the follow-up requirement can be missed once the driver returns to normal work. The operator should be able to show:
- When the reduction occurred and the length of the rest actually taken.
- The exact number of hours owed.
- The later rest period to which the compensation was attached, taken in one block.
- That the compensation was taken before the end of the third week following the week of reduction.
- That no two consecutive weekly rests were reduced.
Where software flags a reduced weekly rest, managers should still understand the cause. A flag does not prove active management unless the file also shows the driver was debriefed, the planner was challenged where appropriate and the next schedule was checked.
On audit I look for the compensation diary, not the infringement list. If a transport manager can point to the week the rest was reduced, the rest period it was repaid against, and the schedule check that prevented it happening again, that is the file a Traffic Commissioner will accept. A signed printout on its own is not enough.
Andrew Logan, transport compliance adviser
Ferry and train interruption
A regular daily rest period can be interrupted no more than twice by other activity totalling no more than one hour, where part of the rest is taken on a ferry or train and a bunk or couchette is available. Weekly rest is more restricted and is not routinely interruptible in the same way. Where ferry or train work appears in the pattern, the operator should hold sailing or rail tickets, ferry interruption records and the manual entry that matches them. Without that paperwork, the analysis will read as a straight breach.
Planning risk and repeated patterns
Weekly rest problems often come from planning rather than driver choice. Repeated late finishes, unrealistic return journeys, compressed delivery windows or poor agency driver information can all push rest into a reduction. If the same issue appears across several drivers, review the work pattern rather than issue further individual warnings.
A practical example is a trunking operation where Friday return times regularly pushed drivers into reduced weekly rest. The tachograph reports showed individual infringements, but the underlying cause was a customer collection slot that left no traffic margin. The corrective action was a planning change and driver briefing, then a check of the next analysis period to prove the pattern had improved.
Agency and occasional drivers
Agency and occasional drivers create evidence risk because the operator may not know what work was done before the driver arrived. Reasonable steps should be taken to obtain previous duty information, confirm the position on weekly rest already taken, and ensure manual entries are completed at the start of the shift. Without that evidence, a driver record may look compliant while concealing work completed elsewhere.
Driver debrief and evidence
Every weekly rest issue should be debriefed in a way that records the cause and the action. A signature alone is weak evidence. The debrief should state whether the issue arose from driver misunderstanding, missing manual entry, planning pressure, emergency disruption, agency driver information or another identifiable cause.
Where refresher training is needed, keep the training record and check the next analysis period. A strong file shows that the business did more than identify the breach; it changed the control and then verified whether the change worked.
What operators should keep on file
- Driver card and vehicle unit downloads covering the review period and the compensation window.
- Manual entry checks, other work declarations and agency driver information.
- A compensation tracker showing reduction date, hours owed, due date and the rest period the compensation was attached to.
- Debrief notes explaining cause, action and responsible person.
- Planner or customer scheduling review where the pattern suggests route pressure.
- Follow-up analysis showing whether corrective action reduced the issue.
Weekly rest control should sit within the operator's wider transport compliance system. The useful evidence is not simply that software found an infringement, but that the operator understood the pattern, took proportionate action and checked that the risk had been controlled.
Operator Licence Ltd can help review this evidence, identify the gaps and connect you with the right specialist support for drivers' hours and tachograph compliance.
FAQs
What counts as a reduced weekly rest period?
A reduced weekly rest is at least 24 hours but less than the standard 45 hours. Across any two consecutive weeks a goods driver must take at least one regular 45 hour weekly rest, so two reductions cannot run back to back. Operators must record the reduction, track the hours owed and ensure compensation is taken before the end of the third week following the reduction.
How should compensation for reduced weekly rest be recorded?
Compensation must be taken in one block, attached to a rest period of at least nine hours, and completed by the end of the third week after the reduction. Records should show the reduction date, the exact hours owed, the rest period the compensation was attached to and the tachograph or manual entry data supporting it.
What evidence do operators need to prove weekly rest compliance?
Driver card downloads, vehicle unit data, duty rosters, manual entries and a written compensation tracker. Debrief notes and planner reviews demonstrate active management, which is what DVSA examiners and Traffic Commissioners look for alongside the raw tachograph data.
How can repeated weekly rest issues be mitigated?
Review operational planning before issuing more warnings. Adjust schedules, delivery windows and customer collection slots, brief drivers on manual entries, and check the next analysis period to confirm the pattern has improved.
