Booking a load, end to end
A walk through one real booking — search, call, negotiation, confirmation — and where the time goes.
Descriptions of automated dispatch tend to skip the middle. Here is a complete booking with the middle left in.
The setup#
A dry van sitting empty in Fontana on a Tuesday afternoon, with 6 hours of drive time left and a preference for anything heading east.
Search#
Load boards return a few hundred candidates for that origin. Most are immediately wrong — wrong equipment, wrong pickup window, rates that will not cover the lane. Filtering on the posting alone gets it to roughly thirty.
The thirty are ranked on what you know: rate per mile against the lane's history, deadhead, whether the destination is somewhere you can reload, and whether the appointment is reachable inside the driver's remaining hours.
rank = f(rate_per_mile, deadhead_miles, reload_density, hours_feasible)
That ranking is a prior, not a decision. Every term in it is a guess until the call.
The call#
Six calls in parallel, top of the ranking down. Four go to hold. One is already covered — the posting was stale, which is true of something like a fifth of everything on a board by mid-afternoon.
The one that connects:
Broker: ...it's picking up 6am tomorrow in Fontana, delivering Thursday morning Phoenix. Posted at $850.
Dispatch: We've got a van sitting in Fontana now, so we can be there at six. Can you do $925?
Broker: I can do $900.
Ninety seconds. The number moved because availability was established before the ask, which is the pattern that shows up over and over.
The part that isn't glamorous#
What happens after the yes is most of the work:
- Rate confirmation received and checked against what was agreed
- Appointment written into the trip plan
- Driver notified with the actual details, not a load number
- Hours re-checked against the new appointment
- The other five calls cleanly withdrawn
That last one matters more than it sounds. A dispatcher who books a load and leaves five brokers hanging does not get called back. Withdrawing well is part of the product.
Where this goes#
Every step above is legible and checkable, which is deliberate. A dispatcher should be able to read back what happened on any load and disagree with it. Automation that cannot be audited by the person responsible for the truck is not automation anyone should want.