Where the Weekly Rest Falls: European Driver Rostering is a Location Problem, Not an Hours Problem

European driver rostering is usually built to satisfy driving and rest hours, and hours are only half of what the law now governs. Since the Mobility Package amendments, a regular weekly rest cannot be taken in the vehicle cab, has to be spent in suitable accommodation the employer pays for, and the undertaking must organise work so that drivers can return to their residence or operational centre within every three or four weeks. Those three rules make the location of the rest a planning output rather than an accident, and most planning systems never model it. Modelling a driver-year across a European cross-border operation puts 89% of weekly rests more than a thousand kilometres from base under ordinary load acceptance, which is why platforms that solve position and hours together, Locus among them, change the answer that rostering alone cannot.

Why Rest Location Matters: The Business Case

The supply side makes this a commercial question rather than a welfare one. IRU’s driver shortage work found around 502,000 unfilled truck driver positions in Europe, a shortage rate of 13%, with roughly 660,500 European drivers expected to retire by 2030 and the gap projected to reach 745,000 positions by 2028 without action. More than half of European truck operators say they cannot expand because they cannot find drivers.

What that research says about causes is the part that bears on rostering. Operators increasingly describe a wage wall, where higher pay alone no longer attracts or retains drivers, and cite cab conditions, secure parking, predictable schedules and time at home as increasingly decisive. Time at home is a planning variable. It is produced or destroyed by the sequence of loads a system accepts, and no pay review changes it.

The exposure is concentrated in exactly the work that pays best. Eurostat records that in 2025 international transport accounted for 24.4% of EU road freight in tonne-kilometres, cross trade 10.7% and cabotage 2.7%, with average distances of 604 km for international and 722 km for cross trade against 97 km nationally. Close to two fifths of the work is long-distance and cross-border, which is where a weekly rest is most likely to fall somewhere inconvenient and where the return-home obligation is hardest to satisfy.

How the Rules Turn Rostering Into a Location Problem

The model below uses explicitly illustrative inputs: a Polish-established operation running cross-border loads across sixteen European hubs, nine hours of daily driving, a weekly rest due after six days, accommodation at €95 a night for two nights when the rest falls away from base, €1.35 revenue and €1.05 running cost per kilometre, and a base radius of 150 km. These are model inputs, not measured Locus averages.

Step 1: The cab stopped being a legal rest location

Article 8(8) of Regulation (EC) No 561/2006 requires that regular weekly rest periods be taken in suitable gender-friendly accommodation with adequate sleeping and sanitary facilities, and not in the cabin of the vehicle. Before that change, a rest falling anywhere was operationally neutral because the vehicle was the accommodation. Now every rest away from base converts directly into a booking and a bill.

Step 2: The employer carries the cost of wherever the plan leaves the driver

Costs for accommodation outside the vehicle are covered by the employer. That turns a planning decision taken weeks earlier into a variable cost line that the planner never sees, because the booking is made by a different team against a different budget. The amount is modest per night and relentless in aggregate, which is the profile of a cost that never gets investigated: too small to trigger a review, too regular to disappear.

Step 3: The return home is an organisational obligation, not an aspiration

Article 8(8a) requires undertakings to organise the work of drivers so that they are able to return to their place of residence or to the employer’s operational centre within each period of three or four consecutive weeks. The Commission’s guidance describes it as an obligation of an organisational nature combined with a requirement to keep corresponding records for checks. An obligation to organise, evidenced by records, is a specification for a planning system.

The distinction between three and four weeks matters operationally. The longer cycle is available where the driver has taken two consecutive reduced weekly rests, so the roster and the return clock are coupled: a decision to run reduced rests in order to keep a vehicle working also changes the deadline by which that driver has to be brought back. An operation that treats the two as separate policies will discover the interaction only when the clock has already expired, and at that point the only remaining instrument is an empty vehicle pointed at base.

Step 4: Ordinary load acceptance strands the driver

Accepting the best available load at each decision point maximises margin per leg and pays no attention to where the sequence leaves the driver when the rest falls due. Over a modelled driver-year:

Step 5: The obligation gets met by emergency repositioning

The return-home requirement is satisfied either by planning toward base or by running the vehicle home empty when the clock expires. Greedy acceptance produced 9.4 forced empty returns a year against 5.5, and 9,204 empty kilometres against 2,382. The regulation is complied with in both cases. In one of them it is paid for in dead mileage rather than in planning.

Step 6: Proximity is achievable, presence is not

The rest-aware plan still left 72.6% of weekly rests away from base. Cross-border haulage geography does not permit a driver to sleep at home most weeks, and a plan promising that is not a plan. What changed is distance: the median fell from 1,118 km to 419 km. The achievable objective is proximity, which determines whether a driver can reach home on a reduced rest or reach familiar accommodation, not presence.

That distinction is worth holding onto because it changes what should be promised to drivers and what should be measured internally. Four hundred kilometres is a reachable distance on a reduced weekly rest and an unreachable one at eleven hundred. It is also the difference between resting at a facility the operation uses repeatedly, where parking is secure and the accommodation is known, and resting wherever the load happened to end. The operational lever is not whether the driver is at home. It is whether the driver is inside a radius the operation has planned for.

Step 7: The cost is real and it lands in the wrong place

Rest-location-aware planning cost about €1,057 per driver per year in the model, in forgone load margin net of the accommodation it saved. That is the honest number, and it is why the change does not happen on its own. Transport operations carries the €1,057. Recruitment carries the benefit.

Hours-Based Rostering vs Location-Aware Rostering: Key Differences

The last row explains the persistence of the problem better than any of the others. A planner measured on cost per kilometre and on hours compliance will produce the left-hand column correctly and repeatedly, because both of its metrics are green.

It is worth noticing how much of the left-hand column’s cost is already being paid without being counted as a choice. The €8,819 of accommodation and the 9,204 empty kilometres in the model are not overheads of doing international work. They are the price of not planning position, and they appear in fuel and in a facilities budget rather than against the routing decisions that produced them. An operation that moved those two lines next to the load-acceptance rule that causes them would be looking at a different set of numbers before it was asked to approve anything.

What to Look for in Driver Management and Planning Software

Position at the rest boundary as a planned output. Ask to see, for a given roster, where each driver will be when the weekly rest falls due. If the system cannot answer that before the week runs, it is scheduling hours and letting geography happen. The follow-up question is more revealing than the first: ask what the system would do differently if you told it that position mattered, because a tool that can display the answer but not act on it changes nothing about next week’s plan.

The return-home clock as a live constraint, not a report. Article 8(8a) is an organising obligation with records. A system that reports breaches after the fact satisfies the record-keeping half and none of the organising half. The clock has to be an input to load acceptance, which is the capability driver and rider management has to carry rather than a rota tool bolted alongside it.

Accommodation cost attributed to the plan that caused it. The booking is made by one team and caused by another. Until the cost appears against the routing decision that produced it, the planner is optimising against an incomplete objective and will keep choosing correctly by their own numbers.

Driver hours and vehicle eligibility solved together. A rota planner optimising driver compliance and a dispatcher optimising vehicle throughput each produce a defensible answer, and the combination is usually worse than either would accept. Cabotage position, urban access windows and rest location are constraints on the same asset at the same time.

Rest location as a driver-visible commitment. Predictability is what the shortage research identifies as decisive. A system that can tell a driver on Monday where Saturday’s rest will be is offering something a pay rise does not, and it costs nothing beyond making the existing plan legible. The commitment only works if the plan is stable enough to keep, so this capability is really a test of how often the operation re-plans in ways it never tells the driver about.

What This Looks Like in Practice: Real-World Results

A Fortune 50 parcel and logistics network across 120 countries ran more than a million freight shipments a year through 51 sites against a driver pool of 4,500 split between captive and third-party capacity, making dispatch decisions site by site with no shared view. Centralising planning and execution on Locus moved weekly execution rate from 75% to 92% and surfaced $14M+ in unused capacity at 99.99% uptime. The capacity finding is the relevant one here. Capacity that no single site could see is the same category of problem as a rest location that no single planner models, and both surface only when position is held centrally.

A global lottery operator running a US field network across 25 or more states carried per-jurisdiction contracts, labour laws, SLA windows and technician skills as simultaneous constraints rather than sequential checks, and recorded 20% lower SLA penalty risk, 18% lower fuel spend and 15% less drive distance and time. The structure matches the European driver problem closely: many jurisdictions, worker-level legal constraints and a route that has to satisfy all of them at once. Solving them together rather than in sequence is what produced the distance reduction.

The model supplies the third result. Holding the network, the rates and the hours rules constant and changing only whether the planner considers position at the rest boundary moved the median rest from 1,118 km to 419 km from base and removed 6,822 empty kilometres a year per driver. The loads available did not change. The order they were accepted in did.

Common Mistakes in European Driver Rostering

Treating Article 8(8a) as an HR policy. It is an obligation to organise the work, evidenced by records. Policies do not organise work. Planning systems do, and a policy without a constraint in the planner produces records of breaches rather than compliance.

Measuring compliance and calling it rostering quality. Two plans can be equally compliant on hours and differ by 700 km in where they leave the driver. Compliance reporting cannot distinguish them, which is why it keeps reporting green while turnover rises.

Paying for the problem instead of planning it. Accommodation and emergency empty returns are the cost of an unplanned rest location. They are easier to approve than a change to load acceptance, and they recur every week, which is what makes them look like a fixed cost of international work rather than the consequence of a decision.

Promising drivers they will be home. Cross-border geography does not allow it, and a promise that fails is worse than the honest version. Proximity and predictability are deliverable. Presence mostly is not.

How Locus Approaches Driver Position and Hours Together

Locus, the world’s first Decision-Intelligent, Agentic TMS, treats driver state as a property of the asset rather than as a compliance check applied to a finished plan. The Capacity and Dispatch agents hold each driver’s hours position, each vehicle’s cabotage position and the return-home clock at the same time, so load acceptance is evaluated against where a sequence leaves the driver as well as against what it earns. That is the mechanism the model relies on, because the difference between the two columns above is not a better rota. It is the same solver being given position as an objective rather than as a constraint checked afterwards.

The platform reasons across more than 250 real-world operating constraints over 1.5B+ deliveries, 360+ enterprise customers and 30+ countries at 99.99% uptime, with $320M+ in aggregate logistics cost savings. Locus has been recognised by Gartner for seven consecutive years, including the 2026 Gartner Hype Cycle for Supply Chain Execution and Logistics Technologies and the 2026 Gartner Market Guide for Multicarrier Parcel Management Solutions, where ShipFlex is featured as a Representative Vendor. Locus holds Leader designation in the QKS SPARK Matrix for Transportation Management Systems 2025 and the #1 position for Route Planning in G2’s 2026 Best Software Awards.

In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

European driver rostering has been treated as an hours problem since long before the rules changed, and the rules now govern place as firmly as duration. A regular weekly rest cannot be taken in the cab, the employer pays for wherever the plan leaves the driver, and the return home is an organising obligation evidenced by records. Modelling a driver-year shows ordinary load acceptance leaving 89.3% of weekly rests away from base at a median of 1,118 km, against 72.6% at 419 km when position is planned, at a cost of roughly €1,057 per driver per year that is repaid in retention rather than in transport margin. Locus makes that trade visible by holding hours, cabotage position and the return-home clock in the same decision. Request a Locus assessment to run this against your own network and establishment country.

FAQs

Can a driver take the regular weekly rest in the vehicle?

No. Article 8(8) of Regulation (EC) No 561/2006 requires regular weekly rest periods to be taken in suitable gender-friendly accommodation with adequate sleeping and sanitary facilities, and states they cannot be taken in the cabin of the vehicle. Costs for accommodation outside the vehicle are covered by the employer.

What does the return-home obligation actually require?

Article 8(8a) requires transport undertakings to organise the work of drivers so that they are able to return to their place of residence, or to the employer’s operational centre in the Member State of establishment, within each period of three or four consecutive weeks. The Commission describes it as an obligation of an organisational nature, combined with an obligation to keep corresponding records for checks.

Does planning for rest location cost money?

Yes, and the model quantifies it at roughly €1,057 per driver per year in forgone load margin, net of accommodation saved. It is not a free optimisation, which is why it rarely happens by itself. What it buys is a median rest position 699 km closer to base and a 74% reduction in empty repositioning.

Can a cross-border operation get drivers home every week?

Not realistically. Even the rest-location-aware plan in the model left 72.6% of weekly rests away from base, because the geography of long-distance international work does not permit otherwise. The achievable objective is proximity and predictability rather than presence.

Why does compliance reporting miss this?

Because two rosters can be identically compliant on driving and rest hours while differing by hundreds of kilometres in where they leave the driver. Hours compliance is a necessary condition and says nothing about position, so a compliance dashboard shows green in both cases.

Where does the benefit of location-aware planning show up?

Mostly in retention. IRU’s shortage research describes a wage wall where pay alone no longer attracts or retains drivers, and identifies time at home and predictable schedules as increasingly decisive. Those are planning outputs, so the return appears in recruitment and turnover rather than in transport cost per kilometre.