Why Drivers Decline Loads: Log the Reason, Reassign Faster
Why drivers decline loads, and why nobody writes it down. Tender rejections held at 13.45% on September 10. Structured rejection reasons speed up the reassign.

Drivers decline loads for a short list of reasons, and the list is knowable. Almost every decline comes down to one of eight: a scheduling conflict, an equipment mismatch, no truck available, too far, pay too low, an unsafe load, a personal emergency, or something else that needs explaining. Most fleets never learn which of those they are actually hitting, because the no arrives on a phone call and nobody writes it down.
That is two problems, not one. You have to re-route the load before the pickup window closes, and you have to know why it came back so the same no does not show up again next week. A fixed reason code helps with both. A text thread helps with neither.
What does the 13.45% tender rejection rate have to do with your drivers?
The industry measures one rejection rate obsessively. FreightWaves reported on September 10, 2026 that the Outbound Tender Rejection Index held at 13.45 percent, calling it significantly above the same period in prior years, and noted that the Labor Day bump was more pronounced than in any of the previous three years. Same piece put the National Truckload Index van spot rate at $3.43 a mile including fuel surcharges, with retail diesel approaching $6 a gallon.
That index tracks carriers saying no to shippers. It gets watched to the decimal because everyone agrees it means something about capacity.
Inside your own fleet there is a mirror number, and it is almost always zero on paper. Drivers reject dispatch too. Nobody counts it, so nobody manages it. In a market where a loaded van moves at $3.43 all-in and fuel is eating that number from underneath, a run that comes back to the board is expensive twice over, once in the scramble and once in whatever you end up settling for.
Here is the part worth sitting with. A driver saying no to a load that pays is a cost. A driver saying no for a good reason is information. You cannot tell those two apart if the only record is a call you half remember.
What happens in the 15 minutes after a driver says no?
The clock starts the moment the decline lands, and the dispatcher is solving four things at once.
- Does the pickup window still hold if the next driver has to deadhead in?
- Which trucks are genuinely available right now, not just unassigned on the board?
- Does this load need a different trailer than the one you just pulled off it?
- Does the rate still work once you add the new driver's empty miles?
Now run it with a real shape. Laredo to Oklahoma City, dry van, pickup window 8 to 10 AM. The driver declines at 7:20. If all you get is "he passed on it," your first move is a call back to ask why, and that call costs you six or seven minutes you do not have. If what lands instead is "equipment mismatch," you already know the shipper wants a 53-foot and the assigned truck pulls a 48. You skip the call and go straight to the driver with the right trailer.
That is the whole argument. The reason is not paperwork. The reason is the thing that tells you where to look next.
There is a second failure mode in the same window, and it is quieter: the no that never comes. A load sits pending, the driver has not opened it, and nobody notices until the window is gone. Howdy Dispatch flags that with a red chip on the HQ jobs page when any load has been awaiting acceptance for more than 15 minutes.
How does structured rejection capture work?
It is deliberately small. While a load is pending acceptance, the driver can decline it from the iOS app, and the app requires picking one of eight reasons before the reject button does anything:
| Reason | What it means |
|---|---|
| Scheduling conflict | Cannot make the pickup window |
| Equipment mismatch | Trailer wrong for the load |
| No truck available | Assigned truck is down |
| Too far | Pickup or drop outside my range |
| Pay too low | Not worth the run |
| Unsafe load | Weight, securement, or hazmat concern |
| Personal emergency | Family, medical, urgent |
| Other | Tell dispatch what is going on |
The driver can add up to 500 characters of context along with the reason. On decline, the load drops back to draft, the driver and truck come off it, the truck is released back to available, and the rejection with its reason lands on that load's status timeline, which the dispatcher reads on the job page in HQ. The reason picker is one of the driver app capabilities listed on the Howdy Dispatch features page.
Say plainly what this is not. No AI picks the reason. No AI re-routes the load. Nothing gets reassigned automatically. This is data capture at the one moment the information exists and would otherwise evaporate. The dispatcher makes every call that follows, same as always.
Worth noting, since it is the other half of the loop: drivers get a push notification when a load is assigned to them, so a decline is a response to something they actually saw, not a load that sat unopened on a screen in a truck stop parking lot.
What a month of reason codes tells you
One decline is an anecdote. Thirty of them sorted by code is a set of operating decisions you could not have made otherwise.
Pay too low, clustering on one lane. That is not a driver attitude problem. That is your drivers pricing a lane more accurately than your rate sheet does. Take it into the next rate con conversation with that broker and quote the pattern.
Equipment mismatch, repeating on one driver. That is almost never the driver. That is a pre-loaded assignment list pointing at the wrong truck record, and it will keep generating declines until somebody fixes the row.
Too far, repeating on one driver. Also not a bad driver. That is a home-time or lane-planning mismatch, and it is the kind of thing that turns into a resignation in four months if you read it as attitude instead of as a scheduling fact.
Personal emergency, spiking. That one is human and it is the reason the code exists at all. A driver dealing with something at home should not have to compose a text explaining themselves to dispatch. One tap and you both move on.
The pattern only exists if the vocabulary is fixed. Eight codes give you something you can count. Free text gives you thirty different spellings of the same problem.
A Monday-morning version for fleets not running our app
You do not need software to start this. You need one column.
Add a decline reason column to whatever spreadsheet runs your board, and constrain it to the same eight values. Put free text in a separate note column so it never contaminates the one you sort on. Then, every Friday, read that column next to the rate cons you booked that week.
Two months of that and you will know things about your own operation that you currently believe you already know. Most fleets are surprised by the distribution. The reason people assume is dominant, usually pay, often is not.
What Howdy Dispatch is not
Worth restating on a post that touches driver decisions.
We are not an ELD and not a compliance product. We are not a freight broker, not a carrier of record, and not a load board. We do not optimize routes, we do not rank or select loads, and we do not decide who drives what. The dispatcher and the driver keep every piece of that judgment.
Two-way chat is not part of this feature, and it is not something we ship today. Rejection reasons replace the text thread for exactly one moment, the decline, and nothing else.
The one AI capability that is live is rate-confirmation intake, where a broker rate-conf PDF gets parsed and the load is pre-filled for the dispatcher to review. That is a separate thing from what this post describes, and you can read where the rest is headed on the AI dispatch platform built on both sides.
Start logging the reason
The decline is going to happen either way. The only question is whether it leaves a record you can sort, or a memory of a phone call at 7:20 in the morning.
If you want the structured version without building it yourself, Howdy Dispatch runs on a 14-day free trial, no payment method required.
Market figures from FreightWaves, "Tender rejections at 13.5%: tight market or fade?", published September 10, 2026.
READ NEXT
Drivers Won't Open a Dashboard: What a Trucking Driver App Has to Get Right
Most trucking software dies because drivers ignore the app. Here is what a driver app has to get right, and the one-tap load flow Howdy Dispatch ships today.
Driver Turnover Cost for a Small Fleet in a Tightening Market
Driver turnover cost for a small fleet: ATRI puts small-fleet turnover at 32% vs 70.7% at mega carriers. What one lost driver really costs a 10-truck fleet.


