Route miles and paid miles should not be strangers
When planned, dispatched, driven, and paid miles disagree, the difference deserves a name.
A single load can carry several mileage numbers: customer miles, practical route miles, dispatched miles, odometer miles, and driver-paid miles. Differences are normal. Unexplained differences are where margin disputes and driver frustration begin.
A carrier should define what each number means and which one controls each workflow. Customer billing may follow a contract mileage source. Driver pay may follow practical miles or actual miles. Fuel and maintenance need actual movement. Dispatch needs a route that accounts for restrictions and service commitments.
The useful report does not force every number to match. It highlights the variance and its reason: approved detour, fuel stop, shop visit, repositioning, road closure, incorrect geocode, or unauthorized out-of-route travel. A named variance can be improved; an invisible one simply repeats.
Industry sponsor
Keep every mile and every document connected.
Take a closer look ↗
Drivers should be able to raise a mileage question with the route visible. Payroll should answer from the same load record dispatch used. When each department maintains a separate story, even a correct payment can feel arbitrary.
Route check
- Define every mileage field in plain language.
- Record a reason for material variance.
- Let dispatch and payroll work from the same load history.