Why Southern European Delivery Operators Are Redesigning Workforce Architecture

Direct answer: How can delivery operators improve gig driver retention?
Delivery operators improve gig driver retention by redesigning the work itself: predictable earnings, fair dispatch, route quality, transparent assignment logic, flexible but reliable scheduling, strong onboarding, fast support, and practical driver infrastructure. In Southern Europe, the durable lever is not simply predicting which driver may churn. It is building a compliant operating model that drivers keep choosing because it offers reliable earning opportunities, workable routes, and fair treatment.

Definition: What is gig driver retention?
Gig driver retention is the ability of a delivery platform, marketplace, or logistics operator to keep independent, contracted, or flexible drivers active over time. In last-mile delivery, it should be measured through repeat activity, active days, completed orders, share of driver hours, reactivation rates, and tenure by workforce tier — not only whether a driver has technically deleted an app.

A Director of Operations at a Madrid-based food delivery platform sits through a vendor pitch on AI-powered driver retention. Predict churn 30 days out, intervene with targeted offers, lift retention. It is a competent product. It also does not address the problem on her desk.

The problem is that Spain’s Riders’ Law changed what “retention” means four years ago. The riders her platform works with sit inside an evolving employment-status conversation. Multi-app driving is the norm, so retention against any single platform is structurally limited. The EU Platform Work Directive is being implemented across member states, including Italy and France where her operation also runs. In a workforce environment shaped this materially by regulation and operating economics, churn prediction solves downstream of the actual problem.

European delivery operators in Spain, Italy, and France are increasingly recognising the same thing: gig driver retention is not primarily a prediction problem. It is a workforce-architecture problem. Predicting which gig driver is about to leave is useful only if there is a viable intervention. In markets where employment classification, algorithmic transparency rules, route allocation, dispatch logic, and multi-app driver economics are all in flux, the meaningful interventions happen at the level of workforce design and execution quality, not at the level of retention algorithms alone.

According to the European Commission’s analysis on platform work, more than 28 million people work through digital labour platforms in the EU, with European delivery and ride-hailing among the largest categories. The EU Platform Work Directive, formally adopted in 2024, is being implemented by member states through 2026. It is the most consequential change to European gig work this decade.

How We Developed This Analysis

This article draws on public regulatory sources, Eurofound research on platform work and algorithmic management, driver-retention research, and Locus’s operational perspective from last-mile routing, dispatch automation, capacity orchestration, and multi-workforce execution.

It focuses on delivery operators in Spain, Italy, and France because these markets sit at the intersection of three forces: evolving employment classification, algorithmic transparency requirements, and high multi-app driver participation. The recommendations are therefore operational rather than purely HR-led: they connect retention to routing, dispatch, workforce-tier design, earnings predictability, and driver-support infrastructure.

---

The Regulatory Reality Reshaping Southern European Operations

Three regulatory contexts shape how delivery operators in Spain, Italy, and France need to think about workforce architecture in 2026.

Market	Regulatory context	Operational implication for delivery operators
Spain	Riders’ Law introduced a presumption of employment for delivery riders working through digital platforms and algorithmic transparency requirements.	Operators need workforce models, earnings structures, and dispatch systems that can withstand employment-status scrutiny and explain assignment logic.
Italy	No single national equivalent to Spain’s Riders’ Law, but multiple court rulings have reclassified specific platform riders as employees in particular cases.	Workforce strategy must account for fragmented legal outcomes across regions, platforms, and court decisions.
France	Platform-worker protections have evolved through multiple legislative cycles, with additional pressure from delivery-sector worker organisations.	Operators need stronger worker-support mechanisms, transparent processes, and regionally adapted workforce models.
EU	Platform Work Directive introduces algorithmic management transparency requirements and presumption-of-employment provisions.	Multi-country operators need auditability, explainability, and workforce-tier flexibility built into their operating systems.

Spain. The Riders’ Law (Ley Rider), passed in May 2021, established a presumption of employment for delivery riders working through digital platforms and introduced algorithmic transparency requirements. The law has materially reshaped how delivery platforms operate across Madrid, Barcelona, and the Spanish market — including triggering the high-profile exit of one major platform shortly after passage. Operators continuing in Spain have re-architected workforce models around its requirements.

Italy. Italy has not enacted a single national reclassification law equivalent to Spain’s, but a series of court rulings — including notable actions in Milan and Rome — have reclassified specific platform riders as employees in particular cases. The legal landscape varies court by court, platform by platform, producing a fragmented but consequential operational reality.

France. France has a long-running platform-worker legal framework, evolving through multiple legislative cycles. French delivery operations in Paris, Lyon, and Marseille operate under specific worker-protection requirements that differ in structure from both Spanish and Italian frameworks. French unionisation in the delivery sector — particularly through coursiers organisations — adds an additional dimension.

The EU Platform Work Directive. Layered over all three national contexts, the EU Platform Work Directive introduces algorithmic management transparency requirements and presumption-of-employment provisions that member states are translating into national law through 2026. Operators planning multi-year workforce strategies are doing so against a regulatory baseline that will shift substantively across the next 18–24 months.

The operational implication for Directors of Operations is straightforward: workforce architecture decisions made in 2026 will be evaluated against a regulatory regime materially different from the one that existed when current platforms were designed.

For last-mile leaders, this is not only a legal issue. It affects how orders are assigned, how route optimisation engines prioritise drivers, how SLA adherence is protected during peaks, how on-time delivery is measured, and how cost-to-serve is allocated across employed, gig, agency, and 3PL capacity.

Also Read: How AI Improves Driver Experience: Route Fatigue to Retention

Why Churn Prediction Misses the Point in This Market

Churn prediction is a technically sound capability. In a stable workforce environment with clearly defined employment relationships, predicting which workers are at risk and targeting interventions can deliver meaningful retention gains.

That is not the environment Southern European delivery operators are in.

Three structural realities limit what churn prediction can deliver in this market.

Churn-prediction assumption	Southern European delivery reality	What operators need instead
A driver is either retained or churned.	A driver may remain registered but shift most working hours to another app.	Measure active hours, completed orders, repeat activity, and share of driver time.
The platform can trigger individualised retention offers freely.	Employment classification and transparency rules constrain compensation, assignment, and scheduling interventions.	Design compliant earnings and dispatch rules at the workforce-architecture level.
Individual risk signals explain churn.	Earnings volatility, route quality, wait time, dead miles, and app-to-app comparisons often dominate.	Improve the operating layer: routing, dispatch, slotting, workload balance, and driver support.

Multi-app driving is the norm. Most active delivery riders in Madrid, Milan, and Paris work simultaneously across multiple platforms. “Retention” against a single platform is structurally bounded by how attractive that platform’s earnings are versus the alternative apps the rider already has open on the same phone. A churn-prediction model that flags a rider as “at risk of leaving” often catches a rider who already left months ago, in the sense of allocating most of their hours elsewhere.

For operators, this changes the metric. The question is not only “did the rider churn?” It is “how much of the rider’s available time do we win, and under what route, earnings, and dispatch conditions?” This matters because Everee’s 2025 Gig Driver Report found that 74% of gig drivers work on two or more platforms at the same time.

The interventions a model can trigger are constrained by employment status. A platform operating under reclassification pressure cannot freely vary individual rider compensation, schedule guarantees, or work allocation in the way a traditional gig platform could. The interventions that retention algorithms typically suggest — bonus offers, route preferences, schedule guarantees — interact with employment classification in ways that legal and compliance teams need to review.

This is where last-mile orchestration matters. If a dispatch system cannot explain why one rider received a route, why another rider was deprioritised, or why a shift was allocated to a specific workforce tier, the retention programme becomes a compliance exposure.

Structural drivers of churn dominate individual ones. Earnings volatility, app algorithm changes, weather, fuel costs, and broader economic conditions drive the largest share of European gig delivery turnover. According to Eurofound research on platform work, structural earnings and working-condition factors consistently outweigh platform-specific retention efforts in shaping rider tenure decisions. A prediction model can identify these patterns but cannot fix them.

Route quality is one of the clearest examples. A driver’s lived experience is shaped by stops per hour, deadhead distance, dwell time at pickup, address accuracy, parking friction, failed delivery rates, and the realism of ETAs. These are operational variables. They determine whether a route feels economically viable and physically manageable.

The result: in Southern European markets, the platforms achieving the strongest retention outcomes are typically the ones that redesigned the workforce architecture upstream of any prediction layer.

---

Why Gig Drivers Quit: The Root Causes Operators Can Actually Fix

Gig drivers usually leave, reduce activity, or shift hours to another app when the work becomes economically unpredictable, operationally frustrating, or procedurally unfair. The most common retention levers are not abstract engagement programmes. They are pay clarity, route quality, dispatch consistency, support responsiveness, safety, onboarding accuracy, and recognition.

Recent driver research reinforces this operating reality:

• Everee’s 2025 Gig Driver Report found that 52% of gig drivers would drive more for their primary platform if earnings were more predictable week to week.
• The same report found that 69% of gig drivers rank clear, transparent pay calculations as a top-three factor in choosing which app to drive for.
• People.Data.Analytics retention data cited by SambaSafety found that 61.7% of drivers with compensation complaints cited inconsistent miles — not the pay rate itself — as the main cause of dissatisfaction.
• Bucketlist Rewards reports that drivers who receive frequent, high-quality recognition from their fleet are 29% less likely to report an intention to leave within the next year.

For gig delivery platforms, the lesson is direct: pay rate matters, but the operating system around pay often matters just as much. A driver who cannot predict daily earnings, trust route assignments, resolve exceptions quickly, or understand why a dispatch decision was made will eventually move activity elsewhere.

---

The Four Workforce-Architecture Decisions That Actually Move Retention

Operators building durable workforce strategies in Spain, Italy, and France are making four architectural decisions that shape retention more than any prediction model.

Retention lever	Operational action	KPI to monitor
Employment-tier mix	Match baseline demand, peak demand, premium SLAs, and specialised deliveries to the right workforce tier.	Tenure by tier, SLA adherence, cost-to-serve by tier, peak fulfilment rate.
Earnings design	Make earnings predictable, transparent, and understandable across tiers.	Active hours, completed orders per active rider, earnings consistency, reactivation rate.
Algorithmic transparency	Produce explainable routing, dispatch, ranking, and deactivation logs.	Assignment auditability, dispute resolution time, route adherence, driver complaints.
Infrastructure and tooling	Reduce friction through better instructions, support workflows, rest facilities, training, and communication.	Dwell time, failed deliveries, driver satisfaction, on-time delivery, grievance closure time.

1. Employment-tier mix. Most large operators now run multi-tier workforces — some combination of employed riders, contracted riders on fixed-term arrangements, true gig riders where legally and operationally viable, and 3PL or agency-supplied riders. The architecture decision is not “should we have gig riders?” — it is “what work goes to which tier, and in what proportion.”

Peak-hour flex can rest on gig and agency tiers; baseline urban density can rest on employed riders; specialty deliveries — high-value, regulated, premium SLA, temperature-sensitive, or customer-critical orders — typically benefit from employed-tier handling.

This is also a capacity planning decision. A gig tier may look cheaper per order during low-complexity peaks but become expensive when failed deliveries, low route density, long wait times, SLA penalties, and driver churn are included. Operators also need to compare employed riders, agency supply, 3PL capacity, and crowdsourced delivery models as part of one orchestration strategy, not as disconnected sourcing channels.

Also Read: AI Route Optimization to Deal with Europe’s Driver Shortage

2. Earnings design across tiers. Compensation transparency is a Riders’ Law requirement in Spain and an emerging norm under the Platform Work Directive. Operators designing earnings systems for predictability — guaranteed minimums, transparent bonus structures, comprehensible tip flows — consistently outperform operators relying on opaque algorithmic compensation. Multi-app driver economics matter here: an earnings system that reliably produces 10% better hourly than the competing app produces retention without prediction.

Transparent incentives also need practical payout visibility. Drivers should be able to understand base pay, bonuses, tips, deductions, minimum guarantees, and timing without escalating to support. For more on this operating principle, see Locus’s perspective on payout visibility for drivers.

In practice, earnings design is not isolated from routing. Poor route density, long pickup dwell, inaccurate ETAs, and unnecessary dead miles reduce effective hourly earnings even when headline pay looks competitive. Automated route planning helps improve this calculation by increasing route feasibility, reducing wasted distance, and making delivery workloads more predictable.

3. Algorithmic transparency. Spain’s Riders’ Law and the EU Platform Work Directive both require that algorithmic management decisions affecting workers — assignment, ranking, deactivation — be transparent and contestable. This shapes how dispatch and routing systems present decisions to riders.

The same algorithm running with audit-grade explainability is operationally identical to one running without it; the difference is regulatory compliance and rider trust. Last-mile execution platforms that produce auditable decision logs for every routing and dispatch choice make this architectural requirement meaningfully easier to meet at scale.

For Locus, this is a core last-mile systems question. Route optimisation and dispatch management for last-mile operations should not operate as black boxes. Operators need to know why an order was assigned to a specific driver, how SLA priority was weighted, whether capacity constraints were respected, and what trade-offs were made between service promise, travel time, route density, and cost-to-serve.

4. Infrastructure and tooling investment. Rest areas, weather gear, training, communication tools, and grievance procedures are not soft benefits — they are operational infrastructure. According to research, operational investments in workforce conditions consistently rank among the highest-leverage retention drivers across gig and contractor workforces, particularly in markets where regulatory pressure is increasing the cost of treating riders as fully disposable.

The same applies inside the delivery workflow. Clear pickup instructions, accurate geocoding, predictable handover times, real-time exception management, in-app communications, and automated proof-of-delivery reduce friction. Strong delivery exception management also reduces avoidable driver-dispatch calls, failed attempts, late deliveries, and route deviations — all of which affect both retention and customer experience.

---

How to Measure Gig Driver Retention

Gig driver retention should be measured as active participation over time, not as a binary account status. A driver may still be registered, receive messages, and appear in the database while allocating most working hours to another platform.

Useful retention KPIs include:

• 30-day, 90-day, and 180-day active retention: the percentage of onboarded drivers who complete at least one delivery in each period.
• Active driver days: the number of days a driver is available, accepts jobs, or completes deliveries.
• Completed orders per active driver: a practical measure of network engagement and route productivity.
• Share of driver hours: the estimated portion of a driver’s available working time captured by the platform.
• Reactivation rate: the percentage of dormant drivers who return after targeted operational or earnings improvements.
• Tenure by workforce tier: retention split across employed riders, contracted riders, gig drivers, agency riders, and 3PL capacity.
• Effective hourly earnings: earnings after wait time, dead miles, pickup delays, failed delivery attempts, and cancellations.
• Route quality metrics: stops per hour, dwell time, route adherence, failed delivery rate, distance per stop, and ETA accuracy.
• Driver-support metrics: ticket response time, grievance closure time, complaint themes, and repeat escalations.

A simple retention formula is:

Driver retention rate = (active drivers at end of period ÷ active drivers at start of period) × 100

For gig delivery, the stronger formula is cohort-based:

Cohort retention = drivers from an onboarding cohort who remain active after 30, 90, or 180 days ÷ total drivers in that cohort

This helps operators identify whether retention problems are concentrated in onboarding, early earnings disappointment, route quality, dispatch fairness, or long-tenure driver fatigue.

---

The Director of Operations Evaluation Framework

Five questions for Southern European Directors of Operations evaluating workforce strategy in 2026.

1. What is our employment-tier mix today, and is it deliberate or inherited?
   Many operators are running tier mixes that emerged organically from rapid scaling, not from intentional design. Inherited mixes rarely survive regulatory scrutiny.
   ? NEW SECTION
   The operational test is simple: can you explain why each order type, delivery zone, service level, and peak pattern is assigned to a particular workforce tier? If not, the model is probably inherited. This is also where operators should reassess in-house fleet vs outsourced fleet management as a strategic design choice rather than a procurement default.
2. Are our earnings structures transparent and predictable enough to compete on a multi-app driver’s screen?
   If a rider running our app alongside two competitors cannot quickly tell which produces the better hour, the retention question is already lost.
   ? NEW SECTION
   Operators should measure not only nominal pay but effective earnings after wait time, route distance, dead miles, cancellations, parking friction, and failed deliveries. Better route optimisation directly affects that calculation.
3. Do our dispatch and routing systems produce auditable decision logs for assignment, ranking, and deactivation choices?
   Both Spain’s Riders’ Law and the EU Platform Work Directive require this. Adding it after the fact is materially more expensive than designing it in.
   ? NEW SECTION
   Auditability should cover dispatch decisions, route sequencing, SLA prioritisation, driver eligibility rules, exception overrides, and any operational decision that materially affects driver opportunity or workload.
4. What is our investment in rider infrastructure — rest, training, communication, grievance procedures — relative to operators we benchmark against?
   Operational conditions show up directly in tenure data.
   ? NEW SECTION
   They also show up in service metrics: route adherence, first-attempt delivery success, on-time delivery, dwell time, and complaint volumes. Driver experience and customer experience are not separate operating domains.
5. Is our workforce strategy designed for the regulatory environment of 2024, or the one expected by 2027?
   The Platform Work Directive’s national implementations will substantively change the baseline within most operators’ current planning horizon.
   ? NEW SECTION
   By 2027, operators should expect stronger scrutiny of employment classification, algorithmic decision-making, worker contestability, and the evidence trail behind platform decisions. Workforce architecture needs to be ready before enforcement pressure arrives.

---

Benefits of a Workforce-Architecture Approach to Gig Driver Retention

A workforce-architecture approach improves retention because it changes the operating conditions that cause drivers to disengage. Instead of relying only on incentives after churn risk appears, operators improve the baseline experience of work.

Key benefits include:

• Higher active driver participation: predictable earnings and better routes make drivers more likely to keep accepting work.
• Lower acquisition dependency: retaining active drivers reduces the need to constantly recruit and onboard replacements.
• Improved SLA adherence: the right workforce tier can be matched to the right order type, zone, and service promise.
• Stronger compliance posture: auditable dispatch, transparent earnings, and explainable algorithmic decisions reduce regulatory exposure.
• Better driver trust: transparent pay and contestable decisions reduce the feeling that the platform is arbitrary or opaque.
• More reliable peak execution: multi-tier capacity planning helps operators flex during spikes without degrading driver experience.
• Lower hidden cost-to-serve: fewer failed attempts, route deviations, support escalations, and churn cycles improve delivery economics.

---

Key Operating Capabilities That Support Gig Driver Retention

Improving gig driver retention requires systems that make the work more predictable, transparent, and fair. The most important capabilities sit across planning, dispatch, execution, and feedback loops.

1. Route Optimisation That Improves Effective Earnings

Drivers experience retention through the economics of a shift. Route optimisation affects drops per hour, dead miles, wait time, ETA realism, and the likelihood of failed delivery attempts. Better route quality can make the same headline pay feel more worthwhile.

2. Dispatch Automation With Explainable Rules

Dispatch systems should apply eligibility rules, SLA priorities, capacity constraints, and routing logic consistently. Operators need decision logs that show why a driver received a route, why another did not, and how the system balanced cost, service level, and driver availability.

3. Workforce-Tier Orchestration

Employed riders, gig drivers, agency drivers, 3PL capacity, and crowdsourced fleets should not be planned in silos. Retention improves when baseline demand, premium orders, peak flex, and exception-heavy work are assigned deliberately to the workforce tier best suited to handle them.

4. Transparent Earnings and Payout Communication

Drivers should be able to understand what they earned, why they earned it, when they will be paid, and how bonuses or guarantees were calculated. In a multi-app market, unclear pay mechanics push drivers toward platforms that feel easier to trust.

5. Driver Support and Exception Workflows

Retention deteriorates when drivers are left alone with blocked pickups, address issues, parking friction, customer no-shows, or app failures. Fast exception resolution protects both the driver’s earnings and the customer promise.

6. Feedback, Recognition, and Grievance Management

Drivers need practical ways to raise issues, contest decisions, and see that feedback leads to change. Recognition also matters: Bucketlist Rewards reports that drivers receiving frequent, high-quality recognition are 29% less likely to report an intention to leave within the next year.

The Real Question for Southern European Directors of Operations

Predicting which rider is about to leave is interesting. Designing a workforce architecture that fewer riders need to leave is the actual lever.

In Spain, Italy, and France — markets where regulatory direction is moving toward employment presumption, algorithmic transparency, and stronger worker protections — the question Directors of Operations should be asking is not “how accurate is our churn model?”

It is: is our workforce architecture deliberate, regulatory-resilient, and competitive on a multi-app driver’s screen — or are we trying to predict our way out of design choices we never made intentionally?

For last-mile operators, the practical answer sits in the operating layer: route optimisation that improves drops per hour, dispatch automation that applies fair and auditable rules, capacity planning that matches work to the right tier, and execution systems that protect SLA adherence without pushing volatility onto drivers.

That is where gig driver retention becomes measurable, manageable, and operationally durable.