When a driver quits, the reason offered is often money. It is the easiest thing to say, it is never wrong exactly, and it sends carriers straight to the most expensive possible fix.
Sometimes the rate genuinely is uncompetitive. Often the rate was fine and something else made the job harder than it needed to be — and raising the rate simply means paying more for the same friction.
Predictability is the thing being bought
A driver is running a small business inside yours. They are planning around income they expect and time at home they were promised. Both of those are forecasts, and a carrier that keeps breaking its forecasts is expensive to work for regardless of the rate.
Three forecasts matter most.
The settlement. Can the driver predict what Friday's check will be, and reconstruct it when it arrives? Not approximately — actually. If the number is a surprise, even a pleasant one, the model is opaque, and opacity reads as risk.
Home time. A date that moves is worse than a later date that holds. Drivers plan their lives around this, and a carrier that misses it twice has told them something about the third time.
The next load. Sitting is not just lost revenue. It is hours burned on a clock that is finite, and it feels like the company wasting something the driver cannot replace.
Settlement transparency is cheaper than a raise
The pay model — per mile, percentage of gross, per-mile split, flat rate — matters less than whether the driver can follow the arithmetic.
What makes a settlement arguable on facts rather than on feelings:
- The miles used, and where they came from
- The rate applied, and which pay model produced it
- Every deduction, itemised, with what it was for
- Escrow or maintenance holdbacks shown as balances, not just subtractions
There is a specific failure worth avoiding: pay terms that change without the historical statements changing with them. If you adjust a rate and old settlements silently recalculate, every past statement becomes untrustworthy. A settlement should record the formula that was in force when it was generated, so a statement from March still reconciles in November.
That is a small technical decision with an outsized trust consequence, and it is the kind of thing that is very hard to retrofit once drivers have stopped believing the numbers.
Dispatch quality is a retention feature
Most of what drivers experience as "this company is disorganised" is dispatch:
- Being routed somewhere with hours they do not have
- Detention that nobody bills, so nobody at the office treats the wait as real
- Paperwork chased days later, when the details are gone
- Assignments that change after the plan was made
None of that is a pay problem. All of it makes the job harder in ways a rate increase does not touch — and all of it is fixable with process rather than money.
Find out why people actually leave
Most carriers do not have the data to answer this, so they default to the pay hypothesis, which is the one that costs the most to act on.
Record the reason at exit. Not a form nobody reads — a field somewhere that can be counted. One driver leaving because of home time is a person's circumstances. Twelve is a scheduling problem you can name and fix.
The same applies to what makes people stay. Drivers who have been with you for years are the ones who know which parts of the job work.
Where the software fits
Retention lives in the ordinary machinery: settlements the driver can reconstruct, dispatch that respects hours, and paperwork captured at the dock instead of chased.
In TFS Fleet, settlement line items snapshot the pay formula used at the time, so historical statements stay reconcilable after a rate change. Drivers see their own loads, pay and documents through a role-scoped view, and hours-of-service clocks and inspection status sit next to the dispatch board so a plan is checked against reality before it becomes a promise.
See Accounting & Factoring, HR & Payroll and Fleet & Telematics.
The short version
Pay has to be competitive; past that, it is a weak lever. What keeps drivers is a settlement they can predict and verify, home time that holds, and dispatch that does not waste their hours. Those are process problems with process fixes — and they are considerably cheaper than the raise you would otherwise be paying to paper over them.