Driver Pay Structures for 5-, 6-, and 7-Day Terminals

Driver pay is the largest cost in a FedEx Ground operation and the strongest lever on both margin and turnover — set it too low and you churn drivers into a training treadmill; set it wrong-shaped and you pay for hours that don't produce stops. There is no universally right structure, but there is a right way to reason about the options, and it starts from a fact many pay conversations skip: terminals run five, six, or seven days a week, and the same pay package means different things on different schedules.

The four basic structures

• Daily rate. A flat amount per day worked. Simple to administer, predictable for the driver, and the most common structure in the industry. Its weakness: it pays the same for a light Tuesday and a brutal Monday, so it needs route balancing to feel fair, and it gives no direct incentive for productivity.
• Per-stop pay. Pay tracks the work: more stops, more pay. It aligns driver incentive with the revenue engine and self-adjusts across light and heavy days. Weaknesses: earnings volatility for the driver, a speed incentive you must balance against safety and service quality, and disputes if stop counts aren't transparent.
• Hourly. Straightforward and legally clean, especially where overtime rules bite. It decouples pay from productivity entirely — fine for training periods and shop roles, risky as the standing structure for route work unless paired with real performance management.
• Hybrids. The common mature answer: a daily base for stability plus a per-stop or performance component for alignment — or a salary for a lead driver who also dispatches. Hybrids trade administrative simplicity for better incentive shape.

The schedule multiplies everything

A pay package is really a weekly cost, and the week differs by terminal:

• Never assume five days. The same daily rate is a very different weekly cost — and a very different annual income offer to a driver — on 5-, 6-, and 7-day schedules. Every comparison (against your economics or against what the terminal down the road pays) must be schedule-adjusted before it means anything.
• Six- and seven-day operations need coverage structures, not just rates: rotations, guaranteed days off, weekend premiums. The pay design question is as much "who works Saturday?" as "what's the rate?" — and a schedule that burns out your best driver is expensive at any rate.
• Salary converts by configured days.If a driver is on a weekly salary, the daily equivalent is salary ÷ scheduled days for your terminal — the one legitimate division by a schedule constant. Everything else should come from observed days actually worked.

Evaluating pay with data (and the honesty rules)

Whether a driver is well-paid, and whether your pay is sustainable, are empirical questions. Two rules keep the analysis honest:

• Compute from observed days and hours only.Daily-rate equivalents, cost per stop per driver, and over/underpaid comparisons should use days the driver actually worked, from worksheets or payroll — never an assumed schedule. If you lack the coverage data for a driver, say "insufficient data" and exclude them from averages rather than guessing; imputed denominators create fictional outliers and then you make pay decisions about fiction.
• Anchor pay to route economics. The sustainable pay ceiling is set by what the route earns: driver cost per stop against revenue per stop, per route. A raise that keeps a great driver on a dense route can be trivially affordable; the same raise on a thin rural route may flip it negative. Pay decisions made without the route's margin math are guesses with salary-sized consequences.

Turnover is a pay cost too

The spreadsheet comparison of two pay structures always flatters the cheaper one, because the spreadsheet doesn't show turnover: recruiting, training weeks at low productivity, service failures during coverage scrambles, and the compounding value of a driver who knows the route. When comparing structures, ask which one keeps your best two drivers for another year — that answer is worth real money and appears on no settlement.

Putting it together

A defensible pay design process: establish your per-route revenue and cost per stop; compute current per-driver economics from observed data; compare against local market conditions (schedule-adjusted); then shape the structure — base for stability, variable component for alignment, coverage design for 6/7-day schedules — and re-check it against route margins. Route Impact's Labor module runs the data side of this from your payroll and worksheet uploads: per-driver daily-rate equivalents and cost per stop from observed days (with coverage disclosed, never imputed), comparisons that respect your terminal's actual schedule, and pay-structure analysis tied to your real settlement revenue. However you run it, the two honesty rules are the difference between a pay strategy and a spreadsheet-shaped hunch.