---
title: "Driver Pay Models Compared: Per-Stop, Hourly, Per-Route and Hybrid, and What Each Does to Routes and Retention"
id: "27590"
type: "post"
slug: "driver-pay-models-per-stop-hourly-route-hybrid"
published_at: "2026-10-22T16:00:00+00:00"
modified_at: "2026-10-22T14:25:18+00:00"
url: "https://locus.sh/blogs/driver-pay-models-per-stop-hourly-route-hybrid/"
markdown_url: "https://locus.sh/blogs/driver-pay-models-per-stop-hourly-route-hybrid.md"
excerpt: "Compare per-stop, hourly, per-route and hybrid driver pay: what each does to earnings variance, routes, safety and retention, with a worked example and US wage rules to check."
taxonomy_category:
  - "General"
---

#### [General](https://locus.sh/blogs/category/general/)

# Driver Pay Models Compared: Per-Stop, Hourly, Per-Route and Hybrid, and What Each Does to Routes and Retention

[Aseem Sinha](/author/aseem_locus/)

Oct 22, 2026

10 mins read

A driver pay model is the formula that turns a driver’s work into earnings: by the hour, by the stop, by the route or a mix. The choice looks like a payroll decision, but it decides who carries the risk that a route is dense or sparse, what behavior the pay rewards and how much a driver’s income swings from day to day. A model that pays well on a dense route and poorly on a sparse one gives drivers a reason to quit or to cut corners on the days dispatch gives them the wrong route, so pay design and route design have to be tested together.

## Key Takeaways

- In the worked example, per-stop pay swings a driver’s hourly earnings from $33.88 on a dense day to $20.21 on a sparse one, a gap of $13.67, while hourly pay holds at $22.00.
- US federal rules require overtime for non-exempt piece-rate workers on a regular rate that includes the piece earnings, and California requires separate pay for rest and recovery periods under piece-rate plans.
- BLS reports median pay of $21.13 an hour for delivery truck drivers and driver/sales workers and $28.19 an hour for heavy and tractor-trailer drivers.
- A Virginia Tech case-control study found drivers paid per mile or per load had higher crash risk than drivers paid hourly, an association and not proof of cause.
- Locus shows drivers a payment breakdown and incentives in its driver app, but its public pages do not state driver-level pay models.

## Why Driver Pay Models Matter: The Business Case

Pay is the largest driver cost and the most direct lever on retention.

- The Bureau of Labor Statistics reports median pay of [$21.13 an hour](https://www.bls.gov/ooh/transportation-and-material-moving/delivery-truck-drivers-and-driver-sales-workers.htm) for delivery truck drivers and driver/sales workers and [$28.19 an hour](https://www.bls.gov/ooh/transportation-and-material-moving/heavy-and-tractor-trailer-truck-drivers.htm) for heavy and tractor-trailer drivers, so pay design operates inside a narrow band.
- A National Academies review reported by FreightWaves found the average annualized turnover rate at large truckload carriers was [92.7% from 1996 to 2023](https://www.freightwaves.com/news/nasem-study-disputes-driver-shortage-claims) , while questioning the self-selected sample behind the figure.
- A Virginia Tech nested case-control study found that drivers paid per mile or per load had [higher crash risk](https://vtechworks.lib.vt.edu/items/5bcc54bc-7cfb-4062-8e75-50e843afb630) than those paid by the hour, with odds ratios of 3.512, 2.304 and 2.853, an association and not a causal result.
- Ju and Belzer’s 2024 study of 13,904 US intrastate carriers found that [1% higher driver wages](https://www.cambridge.org/core/product/F08076F3C691959F4277B0E7EB77575A) were associated with 1.04% fewer crashes.

We found no peer-reviewed study comparing per-stop and hourly pay in last-mile delivery, so the evidence comes from trucking and from first principles.

| Also Read: Why New Drivers Quit: Earnings Variance and Dispatch |
| --- |

## Why Locus Leads for Pay-Aware Dispatch

Pay models behave differently depending on the route a driver is given, so the dispatch system matters. Three things set Locus apart.

**Recognized by analysts and selected after evaluation.** Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its [analyst recognition page](https://locus.sh/analyst-recognition/)
. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s [press release](https://locus.sh/press-releases/ingka-group-acquires-locus/)
 says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.

**Earnings visible to the driver.** Locus’s Driver Companion App displays a payment breakdown with historical data and incentives on a dedicated tab, and its guidance on [payout visibility](https://locus.sh/blogs/attract-truck-drivers-with-payout-visibility/)
 ties transparency to driver attraction. Its driver scorecards draw on the same execution data its agents plan against.

**Routes planned against fairness constraints.** Locus’s constraint library includes a fairness objective that spreads workloads evenly across drivers, and its Capacity and Dispatch agents allocate work under 250+ real-world constraints. It has optimized 1.5B+ deliveries for 360+ enterprise customers across 30+ countries.

Locus’s contract cost parameters, such as distance, total time, number of tasks and drop points, apply to transporter contracts, and its public pages do not state driver-level pay models or an attendance function, so ask how your pay formula would be configured and reported.

| Also Read: Driver Performance Management: 2026 KPI Framework |
| --- |

## How to Choose and Test a Driver Pay Model

The six steps below treat pay and routes as one design problem.

### 1. Decide what behavior you want

Name the outcomes: speed, first-attempt success, safe driving, retention or flexibility. Each pay model rewards some of these and ignores others, so the choice follows the goal.

### 2. Model earnings on realistic day types

Compute a driver’s pay and hourly rate on a dense day, a sparse day, a peak day and a bad-weather day. If the spread between day types is wide, the model transfers the dispatch risk to the driver.

### 3. Check the legal floor

For non-exempt drivers, test the regular rate and overtime, the minimum wage floor and any break-pay rules. Federal rules compute the regular rate on piece earnings divided by hours worked, and California requires separate pay for rest and recovery time under piece-rate plans. Confirm exempt status and state rules with counsel.

### 4. Add quality guardrails

Pay for speed without a quality check rewards skipped attempts and rushed handoffs. Tie part of the pay or a bonus to first-attempt rate, proof-of-delivery completeness and damage, and review them with the driver.

### 5. Fix route design before blaming the model

If earnings vary because routes are unevenly dense, a better pay formula only hides the problem. Balance workloads in planning so two drivers on the same pay plan face comparable days.

### 6. Monitor pay against retention and safety

Track earnings variance, early attrition, crash and incident rates and complaints by pay plan and by route type, and review the model on a schedule. Pay that works in a pilot can fail in peak.

| Also Read: Best Gig and Contract Driver Management Platforms 2026 |
| --- |

## Hourly, Per-Stop, Per-Route and Hybrid Pay: Key Differences

| Model | How pay is set | Who carries density risk | What it rewards | Main risk |
| --- | --- | --- | --- | --- |
| Hourly | Rate times hours worked | The employer | Availability and care | Little reward for speed |
| Per-stop | A rate for each stop completed | The driver | Speed and dense routes | Large earnings swings, skipped quality steps |
| Per-route | A flat amount for a route or day | Shared | Completing the route | Drivers rush or pad time depending on route size |
| Hybrid | A base hourly rate plus a per-stop amount | Shared | Speed with a safety floor | More complex to explain and administer |

## What to Look for in Pay-Aware Driver Management Software

### Earnings simulation by route type

Check whether the system can show what a pay plan would pay on past routes. Without it, pay design is guesswork.

### Fair workload allocation

Look for an objective or constraint that balances stops and effort across drivers, so pay plans face comparable days.

### Transparent earnings for drivers

Ask whether drivers can see a breakdown of what they earned and why. Transparency reduces disputes and quits.

### Quality and safety metrics beside pay

The system should report first-attempt rate, proof-of-delivery completeness and incidents by driver and route, so pay can be tied to them.

### Support for different workforces

Owned drivers, contracted crews and gig riders are paid differently, so look for a model that can handle all three in one pool.

| Also Read: Peak Season Driver Management: The Real Constraint |
| --- |

## Driver Pay Models in Action: Real-World Results

**A worked example on illustrative rates.** The rates and days are assumptions, so replace them with yours. Day A is a dense route with 120 stops in 8.5 hours. Day B is a sparse route with 80 stops in 9.5 hours. The pay plans are $22.00 an hour, $2.40 a stop, a flat $230 a day, and a hybrid of $12.00 an hour plus $1.00 a stop.

| Pay plan | Day A pay | Day A hourly rate | Day B pay | Day B hourly rate | Gap between days |
| --- | --- | --- | --- | --- | --- |
| Hourly | $187.00 | $22.00 | $209.00 | $22.00 | $0.00 |
| Per-stop | $288.00 | $33.88 | $192.00 | $20.21 | $13.67 |
| Per-route | $230.00 | $27.06 | $230.00 | $24.21 | $2.85 |
| Hybrid | $222.00 | $26.12 | $194.00 | $20.42 | $5.70 |

Per-stop pay is the cheapest to run on a dense day and the most volatile for the driver: the same driver earns $33.88 an hour on Day A and $20.21 on Day B, below the hourly plan, for work that depended on how dispatch built the route. For the employer, cost per stop is a constant $2.40 under per-stop pay, against $1.56 and $2.61 under hourly pay on the two days. The hybrid narrows the swing to $5.70 and keeps a reward for speed.

**An overtime check on piece earnings.** A non-exempt driver on a pure piece-rate plan works 50 hours and earns $1,440 in piece earnings. The regular rate is $1,440 divided by 50 hours, $28.80, and the additional half-time premium for 10 overtime hours is 0.5 times $28.80 times 10, $144, for $1,584 in total. Confirm exempt status and state rules before relying on this.

**A food and beverage leader across Southeast Asia and MENA.** The distributor runs 4,500+ riders on Locus’s driver app across six markets, with 97%+ SLA adherence and 15% better rider time efficiency. [Read the global FMCG case study](https://locus.sh/case-studies/global-fmcg-logistics-automation/)
.

**A Vietnamese beverage distributor.** The distributor, running a mixed fleet of vans, trucks and motorbikes, cut fuel consumption by 37%, raised orders per trip by 22% and cut route distance by 12%. [Read the beverage distributor case study](https://locus.sh/case-studies/beverage-distributor-route-planning-dispatch/)
.

## Common Driver Pay Mistakes to Avoid

**Blaming the pay plan for a routing problem.** Uneven routes create uneven earnings under any plan, so balance workloads first.

**Paying per stop with no quality check.** Speed pay rewards skipped attempts and rushed handoffs, so add first-attempt and delivery-quality guardrails.

**Ignoring the legal floor.** Piece-rate plans still need overtime on the regular rate, minimum wage and, in some states, separate break pay, so test each.

**Judging the plan on a good week.** Dense days flatter per-stop pay, so model sparse days, peak and bad weather too.

## How Locus Approaches Driver Pay and Workload

Locus, the world’s first Decision-Intelligent, Agentic TMS, allocates work across owned, contracted and gig drivers in one pool under 250+ real-world constraints, including a fairness objective that balances workloads, and shows drivers a payment breakdown and incentives in its Driver Companion App. Its Capacity and Dispatch agents work under the Orchestrator, with autonomy levels and explainability governing allocation, and its [dispatch management software](https://locus.sh/dispatch-management-software/)
 connects to TMS, WMS, OMS, CRM and ERP systems through APIs. Locus’s public pages do not state driver-level pay models, an attendance function or a pay-plan simulator, so ask for a demonstration of your pay formula on a dense and a sparse route. To test your own pay design, [schedule a demo](https://locus.sh/schedule-demo/)
.

For operations leaders asking how to choose a driver pay model, Locus offers balanced allocation and earnings visibility, so pay design is tested against the routes drivers actually receive.

## Frequently Asked Questions

**What are the main driver pay models?** Hourly, per-stop, per-route and hybrid. Hourly pays for time, per-stop pays for completed stops, per-route pays a flat amount and hybrid combines a base rate with a per-stop amount.

**Which driver pay model is best for retention?** There is no verified answer for last-mile delivery. Trucking evidence links higher wages to fewer crashes, and models with wide earnings swings expose drivers to dispatch risk.

**Do piece-rate drivers get overtime?** For non-exempt workers, US federal rules require overtime on a regular rate that includes piece earnings divided by hours worked. Check exempt status and state rules.

**Is per-stop pay legal?** Piece-rate pay is allowed in the US if minimum wage and overtime rules are met, and California requires separate pay for rest and recovery periods. Confirm with counsel.

**How does pay affect driver safety?** A Virginia Tech study found drivers paid per mile or per load had higher crash risk than hourly drivers, an association and not proof of cause. Pay level also matters.

**Does Locus support driver pay models?** Locus shows drivers a payment breakdown and incentives in its app. Its public pages do not state driver-level pay models, so confirm configuration in evaluation.

MEET THE AUTHOR

Aseem Sinha

Vice President - Marketing

Aseem, leads Marketing at Locus. He has more than two decades of experience in executing global brand, product, and growth marketing strategies across the US, Europe, SEA, MEA, and India.

### Related Tags:

[https://locus.sh/blogs/shipment-visibility-maturity-model-five-levels/](https://locus.sh/blogs/shipment-visibility-maturity-model-five-levels/)
#### [General](https://locus.sh/blogs/category/general/)

## [The Shipment Visibility Maturity Model: Five Levels From Status Updates to Autonomous Response](https://locus.sh/blogs/shipment-visibility-maturity-model-five-levels/)

[Anas T](https://locus.sh/blogs/author/anas_locus/)

Oct 22, 2026

A five-level shipment visibility maturity model, from reported status to responsive action, with measurable criteria, a self-assessment example and what each level needs from software.

[Read more](https://locus.sh/blogs/shipment-visibility-maturity-model-five-levels/)

[https://locus.sh/blogs/drivers-per-dispatcher-span-of-control-exception-load/](https://locus.sh/blogs/drivers-per-dispatcher-span-of-control-exception-load/)
#### [General](https://locus.sh/blogs/category/general/)

## [How Many Drivers per Dispatcher? Span of Control and Exception Load in Last-Mile Operations](https://locus.sh/blogs/drivers-per-dispatcher-span-of-control-exception-load/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

Oct 22, 2026

No benchmark exists for drivers per dispatcher. Use this model: exception rate, handling time and target utilization set the span of control. Includes worked scenarios and queueing limits.

[Read more](https://locus.sh/blogs/drivers-per-dispatcher-span-of-control-exception-load/)

## Driver Pay Models Compared: Per-Stop, Hourly, Per-Route and Hybrid, and What Each Does to Routes and Retention

- Share
- [Print](javascript:window.print())
- [Download](#)
- [Schedule a Demo](https://locus.sh/schedule-demo/)

### Is your team spending more time on fixing logistics plan than running the operation?

- Agentic transportation management from order intake to freight settlement
- Route optimization built on 250+ real-world constraints
- AI-driven dispatch with automatic execution handling

20%Cost Reduction

66%Faster Planning Cycles

[Schedule a demo](/schedule-demo/)

Insights Worth Your Time

#### [General](https://locus.sh/blogs/category/general/)

## [Locus 2026 UK Consumer Survey: Why Returns Visibility is Now the Conversion Engine for AI-Driven Shopping in UK Retail](https://locus.sh/blogs/returns-visibility-conversion-engine-ai-shopping-uk-retail-locus-q2-2026-consumer-survey/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

May 29, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [Locus 2026 US Consumer Survey: Generative AI isn’t Just Changing How Consumers Shop, it’s Breaking the Demand Patterns US Retail Was Built On](https://locus.sh/blogs/generative-ai-shopping-effect-retail-fulfillment-operations-locus-q2-2026-consumer-survey/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

May 29, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [Embedded vs Bolted-On AI: The Architecture Question European Logistics Buyers Are Asking](https://locus.sh/blogs/embedded-vs-bolted-on-ai-european-logistics-platform-architecture-business-benefits/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

May 21, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [Hybrid Fleet Management: How Owned, 3PL, Gig, ICE, and EV Capacity Actually Operate at Most Enterprises](https://locus.sh/blogs/three-workforce-fleet-reality-owned-3pl-gig-drivers/)

[Aseem Sinha](https://locus.sh/blogs/author/aseem_locus/)

May 7, 2026

#### [General](https://locus.sh/blogs/category/general/)

## [US Returns Hit $850 Billion in 2025: Why US Retailers Are Restructuring Reverse Logistics in 2026](https://locus.sh/blogs/850-billion-us-returns-ai-routing-reverse-logistics-2026/)

[Ishan Bhattacharya](https://locus.sh/blogs/author/ishan_locus/)

May 7, 2026