The Dispatcher Handoff Problem
Why a dispatch playbook built in one person's head does not survive a handoff.
The new dispatcher started Monday. By Wednesday, four things had gone wrong.
One driver was sent to a shipper that requires 24-hour advance notice. Nobody told the new dispatcher. The shipper turned the truck away. Six hours of detention, unbilled.
A regular customer called and asked for "Mike" by name. The new dispatcher introduced himself, took the load, and quoted the standard rate. The customer hung up and called a competitor. Twenty minutes later the owner found out and spent the next hour on the phone trying to recover the relationship.
A broker confirmed a load by text, the way she always does. The text went to the old dispatcher's phone, which the new dispatcher did not have access to. The confirmation never reached the dispatch sheet. The driver showed up to a load that did not officially exist.
None of these were the new dispatcher's fault. They were the inevitable cost of letting one person carry a fleet's worth of operating context in their head.
The unwritten playbook
Every small fleet has a playbook. Most of them have never written it down.
The playbook is the accumulated set of decisions a dispatcher has made over years about how to run the fleet profitably. Some of these are written somewhere. Most are not.
- Driver rules. Who runs nights and who does not. Who refuses certain lanes. Who can be relied on for a hot turn. Who needs a 24-hour rest after a long run no matter what the HOS clock says.
- Customer rules. Who pays detention without being asked. Who needs the BOL faxed. Who wants the rate confirmed in writing before the load is picked. Who gets confused by accessorial line items and needs them grouped on the invoice.
- Broker habits. Who confirms by text instead of email. Who lowballs at first and comes back with a real number. Who pays in 60 days despite Net-30 terms. Who is worth the effort and who is not.
- Appointment quirks. Which receiver has an unmarked back gate. Which shipper's dispatcher takes a long lunch. Which DC closes early on Fridays without telling anyone.
- Lane patterns. Which lanes are hot this season. Where the deadheads kill. Where the backhauls reliably appear. Which loads are worth chasing and which look good on paper but always have problems.
None of this is in the dispatch spreadsheet. Some of it is in the dispatcher's text history. Most of it is just in their head, learned the hard way over the last three years.
Four kinds of handoff that all fail the same way
Carriers usually only discover their dispatcher's tribal knowledge problem when a handoff forces it into the open. Different handoffs, same root cause.
| Handoff type | What triggers it | Where it breaks |
|---|---|---|
| Vacation handoff | Two weeks off, hopefully nothing major. | Day three, customer calls asking for the dispatcher by name. Day five, a regular load falls through because nobody knows the broker likes a same-day reload pitch. Day eight, the owner is fielding calls and starting to take notes. |
| Second-dispatcher hire | The fleet has grown enough that one dispatcher cannot keep up. | The new dispatcher learns the spreadsheet in a week. Then spends six months learning what is not in the spreadsheet by making mistakes. During those six months, the original dispatcher is correcting them in real time and getting less done themselves. |
| Owner stepping in | Dispatcher quits unexpectedly. Owner takes the seat for "a few weeks" until a replacement is found. | The owner has not actually dispatched in years. They knew most of the customers when they started, but the relationships are with the dispatcher now, not with the company. Loads start falling. The "few weeks" becomes three months. Customers drift. |
| Full replacement | Dispatcher leaves the company. New person takes over the seat, the spreadsheet, and nothing else. | The slowest possible recovery. Three months minimum to learn the customers. Six months to learn the drivers. A year before judgment calls land consistently. During that time, the fleet runs at lower margin and a quiet portion of the customer base disappears. |
Why training does not fix it
The instinct, after the first painful handoff, is to train better. Make a binder. Write a SOP. Pair the new person with the experienced one for a month.
Training works for the mechanical parts. It does not work for the judgment parts.
Judgment is built by watching the same patterns repeat over months. A dispatcher learns that a specific broker tends to underestimate detention by sitting on enough of their loads to feel the pattern. A binder cannot transfer that pattern. The new dispatcher will only recognize it after experiencing it themselves.
The trap is that owners assume two weeks of shadowing substitutes for two years of pattern recognition. It does not. The new dispatcher graduates with confidence and very little context, and learns the rest by making the same mistakes the previous dispatcher already paid for.
Your dispatch system is not documented if it only exists in someone's head.
What "documented" actually has to mean
The advice every owner gets after a bad handoff is the same: document everything. The advice is correct. The problem is what most carriers mean by documented.
A binder is not documented. A folder of Word docs is not documented. A wiki the dispatcher updated once two years ago is not documented.
Documented, in the sense that survives a handoff, means the context lives in the same place as the work.
- Customer rules attached to customer records. When the new dispatcher opens the customer's page, they see the pay terms, the accessorial preferences, the BOL format, the after- hours phone number. Not in a separate document. On the customer.
- Driver preferences attached to driver records. When a load is being assigned, the driver's page shows the routing constraints, the home-base preference, the lane history, the recent conversations. The new dispatcher reads it before they call.
- Broker habits attached to broker records. The pay history. The detention negotiation pattern. The rate-con confirmation method. Whether they accept text confirmations or require email.
- Conversation history attached to trips and loads. What was promised, when, by whom. The new dispatcher does not have to ask the old dispatcher what was discussed Tuesday. They open the trip and read the thread.
Documentation that lives separately from the live data goes stale within a quarter. Documentation that lives inside the live data updates every time the dispatcher does the work. There is no second step to forget.
What good handoffs look like
The carriers who handle handoffs cleanly have one structural thing in common: their dispatcher's job is partly to externalize their own knowledge.
Every customer note goes into the customer record. Every broker quirk goes into the broker record. Every driver preference goes into the driver record. Every promise made on a load goes into the load record. The dispatcher does this not as documentation but as the normal way of doing the work. The system reads back to them when they need it; it reads to anyone else when they need it.
That is the entire trick. The dispatcher externalizes once, the system holds it forever, and any handoff (vacation, second hire, owner stepping in, full replacement) becomes a matter of reading the system instead of reading the dispatcher's mind.
Carriers who run on this principle are the ones whose new dispatchers come up to speed in weeks instead of months. Carriers who do not are the ones whose fleet slows down every time their dispatcher takes a Friday off.
Frequently asked questions
How long does it actually take to train a new dispatcher?
Two to four weeks for the mechanics: how the spreadsheet works, who the customers are, where the rate confirmations live. Six to twelve months for the judgment: which broker pays late, which driver should not run after dark, which receiver gets confused by the standard BOL format. The first phase is teachable; the second is the part that has to be lived. Carriers who underestimate the gap end up with a dispatcher who can dispatch but cannot make the small decisions that keep the fleet profitable.
What does "tribal knowledge" actually mean in dispatch?
Everything the dispatcher knows that exists nowhere else. The phone number for the gate at a specific receiver. The fact that a particular broker only confirms by text, never by email. Which driver will not deadhead more than 200 miles. The rate at which a specific customer pays detention without being asked. None of this is in the dispatch spreadsheet. None of it is in the rate confirmation file. It evaporates the moment that dispatcher leaves, takes vacation, or gets pulled into another conversation.
Can I just have my dispatcher write everything in a Word doc?
You can, and most carriers eventually try, but the document goes stale within a quarter. The dispatcher updates the live system (the spreadsheet, the file folders, the texts) and forgets to update the document. Three months later, the document describes a system that no longer exists. New dispatchers read it, get confused, ask questions, and the whole exercise becomes a parallel system to maintain. Documentation that lives separately from the live data does not survive contact with daily work.
How do I onboard a backup dispatcher faster?
Speed is not the bottleneck. Legibility is. The carriers whose backup dispatchers come up to speed in weeks instead of months are the ones whose live system carries the context: customer rules attached to customer records, driver preferences attached to driver records, broker quirks attached to broker records, conversation history attached to trips. The new dispatcher learns by reading the current state of the system, not by being told. The cost of that legibility is paid up front by the primary dispatcher entering things in fields rather than knowing them in their head.
What happens if I get hit by a bus tomorrow?
For an owner-dispatcher fleet without documented handoff, the answer is brutal. The fleet either runs at half capacity for a month while a family member figures out the spreadsheet, or it stops. Customers learn within two weeks. Drivers learn within one. The most painful version of this story is the carrier whose owner-dispatcher had a stroke and whose family had to call every customer to explain that the loads they had been dispatching for ten years were not going to be picked up that week. Fleet sold within six months at a discount.
Is hiring a second dispatcher the answer?
Only if the system can hold both of their work simultaneously. Two dispatchers on the same spreadsheet trying to dispatch the same loads is a coordination problem, not a capacity solution. The second dispatcher does not actually create capacity until the first dispatcher has externalized enough of their tribal knowledge that the second person can act independently. Carriers who hire a backup before fixing the system end up with two dispatchers each doing 60 percent of one dispatcher's job.
See dispatch knowledge that survives handoff
We'll walk through how a system that connects customers, brokers, drivers, loads, and conversations in one place actually works in practice. So the next person who sits in the chair has the full context, not just access to the spreadsheet. 30 minutes, no commitment.
Schedule a walkthrough