Driver pay: per stop, per hour, per mile — or a mix?

Every delivery operation eventually has the driver-pay argument. Per hour feels fair to drivers and terrifying to owners on a slow day. Per stop feels efficient to owners and unfair to drivers on a day of long rural drops. Per mile rewards distance, which is sometimes the point and sometimes the opposite of the point.

None of them is wrong. Each one rewards something, and the model you choose is a statement about what you want more of.

Per hour

Rewards: reliability, care at the door, willingness to take the awkward stop. Punishes: the business on quiet days; the fast driver who finishes early.

Per hour is the simplest to explain and the easiest to run. It suits operations with steady, predictable volume and stops where care matters more than speed — pharmacy, furniture, anything with a signature. Its weakness is that it does not distinguish between a productive hour and a slow one, so it needs a dispatcher who plans full days.

Per stop

Rewards: throughput; drivers who plan their own route well. Punishes: drivers assigned the long, sparse route; care at the door when the next stop is money.

Per stop suits dense urban work with many short stops and similar effort per stop. Its failure mode is obvious the first time a driver gets the rural run: forty minutes for one stop paid the same as a two-minute drop. Fleets on per-stop pay usually end up adding a distance component, which is the next model.

Per mile (or per kilometre)

Rewards: taking the far stop; honest coverage of a wide area. Punishes: dense routes; the business when the route is planned badly.

Per-distance pay is fair for spread-out territory and terrible when the route itself is inefficient — you are paying for the planner’s mistakes. It works best when distance is measured from the completed route, not estimated from the plan, and when the planner is good.

The mixed structure most fleets end up with

Most local fleets settle on a base plus components:

• A base (per shift or per hour) that makes a quiet day survivable for the driver.
• A per-stop amount that rewards throughput.
• A per-mile amount that makes the far stop worth taking.
• A bonus for the thing you most want — on-time rate, proof compliance, zero failed attempts.

The proportions are the policy. A pharmacy might weight the base and the bonus for proof; a courier might weight per-stop and per-mile. Write the formula down, show it to drivers, and change it rarely.

Three rules that keep it fair

Measure distance from completed work. If per-mile pay is computed from the planned route, drivers are paid for the plan; if from the completed route, they are paid for the work. The second is fair, and it also gives you a true cost per delivery.

Pay for the failed attempt. A stop where nobody was home cost the driver the same time and fuel. Not paying it turns every failed attempt into an argument. Pay it, record the reason and photo, and fix the notification so it happens less.

Show drivers their earnings live. A driver who can see today’s earnings by stop and by mile in the app trusts the number at the end of the week. A driver who sees a total on Friday does not.

Run the numbers before you change anything

Take one representative week. For each driver, compute what they would have earned under each model — hourly, per stop, per mile, and your proposed mix — from the stops they actually completed and the distance they actually drove. The spread between drivers under each model tells you who a change would help and who it would hurt. Then decide.

PrivateMile computes driver pay from completed work — base, per-stop, per-kilometre and bonuses, configurable per organisation — and shows drivers their earnings live in the app. But the exercise above needs only a spreadsheet and one honest week of data.