What Happens When Your Dispatcher Gets Sick
The single point of failure most small fleets never plan for.
Talk to any owner of a small fleet long enough and you will hear some version of this story.
The dispatcher had a bad cold. Tried to push through. Got worse. Sent home Monday afternoon. Out for the rest of the week.
By Wednesday, three loads had been canceled because nobody knew the customer wanted the BOL faxed instead of emailed. By Thursday, two drivers were sitting empty in Dallas because the rate confirmations were in a folder on the dispatcher's desktop. By Friday, a regular customer was on the phone with the owner asking why nobody had returned their calls.
The dispatcher came back the next Monday. The fleet recovered in about ten days. Nobody put a number on what that week cost. Nobody changed anything.
What is actually in the dispatcher's head
The reason this hits so hard is that the dispatcher in a small fleet is not just doing dispatch. They are also the keeper of every operational decision the company has ever made and never written down.
- Customer preferences. Which broker wants 24-hour notice on detention. Which shipper sends their lumper agreement by text instead of email. Which receiver gets confused if the BOL is not in their specific format.
- Driver routing rules. Which driver will not run after sundown. Which one will not take a load west of Denver in winter. Which team can do a hot California turn and which one will say yes but then call from Albuquerque asking for a relay.
- Broker patterns. Which brokers pay late. Which ones lowball at first then come back. Which factoring relationship handles which broker cleanly.
- Accessorial agreements. Verbal detention deals nobody wrote down. Lumper reimbursements that are billed differently for different customers.
- The trip context. Which trips have already been called in. Which drivers have been messaged about their next load. What was promised to who, and when.
None of this is in the dispatch spreadsheet. None of it is in the rate confirmation file. It lives in the dispatcher's head, in their text history, and in their relationship with the people they talk to every day.
What breaks on day one
The fleet does not stop the day the dispatcher is out. That would be too easy. Instead, things break in slow motion across the week.
| What breaks | How it shows up | Recovery cost |
|---|---|---|
| Trip handoffs | Drivers waiting for next-load instructions. Whoever is filling in does not know which trips are already lined up and which are speculative. | Empty miles, deadhead, drivers parked overnight on nobody's clock. |
| Customer relationships | A customer calls expecting their usual contact. Gets someone who does not know who they are. Gets put on hold, transferred, or ignored. | Long-term: customers learn the carrier is fragile and start hedging. Short-term: lost loads that week. |
| Billing and rate confirmations | Rate cons in personal email. Accessorial agreements only the dispatcher remembers. Invoices delayed by a week or sent with missing line items. | The leak compounds. Late billing ages into bad debt. Missed accessorials never recover. |
| Compliance | The expiring CDL the dispatcher was tracking on a sticky note. The annual inspection that was coming up. None of it is anywhere visible to a fill-in. | Worst case: a driver runs on an expired medical card and gets pulled. Best case: a week of compliance backlog to dig out from. |
| Driver morale | The driver who texts at 6am asking about a load and gets no answer. The driver who shows up to a wrong dock because the customer's instructions never made it out of the dispatcher's inbox. | Drivers do not forget the week the office fell apart. It costs trust that takes months to rebuild. |
The Monday morning fire drill
When the dispatcher comes back, the recovery is its own event.
Every customer call from the week needs returning. Every mis-dispatched trip needs reconciling. Drivers who sat empty need to be made whole somehow. The bookkeeper has a stack of invoices that did not go out. The owner has a list of brokers whose calls were not returned.
The dispatcher walks back into a week of work compressed into a Monday, on top of running the regular Monday. By Wednesday they are caught up. By Friday everyone has mostly forgotten it happened.
Until the next time. Which is usually within a year.
A fleet that cannot run a single week without one specific person is not a fleet. It is a job that hires drivers.
Why scaling makes this worse before it makes it better
The instinct, when this happens, is to hire another dispatcher. Cross-train them. Document things. Make sure we never get caught flat again.
The trap is that adding a second dispatcher to the same spreadsheet system creates more problems, not fewer. Two people now both need to know which loads are real and which are speculative. Two people both have to update the same files. Two people's tribal knowledge has to stay in sync.
Most small fleets that hire a second dispatcher discover within a quarter that they are now spending real time on coordination problems they did not have before. The new dispatcher cannot fully cover for the first one because the system itself is not legible enough.
What "documented" actually has to mean
The advice every owner gets after a bad week is the same: you need to document things. The advice is correct. The problem is what most fleets mean by documented.
A folder of Word docs nobody reads is not documented. A wiki the dispatcher updated once two years ago is not documented. A training packet for new hires is not documented.
Documented, in the sense that lets a fleet survive a week without its main dispatcher, means the operational state of the fleet is visible without explanation.
- Anyone can open the dashboard and see what is happening right now. What is dispatched, what is in transit, what is waiting on a driver, what is waiting on a customer. Not interpreted from a spreadsheet, just shown.
- Customer and broker rules live in fields, not memory. Pay terms, accessorial preferences, billing format. Whoever is sitting in the seat reads them, applies them, moves on.
- Driver assignments and routing rules are attached to drivers, not to the dispatcher. When a fill-in opens the driver's record, they see the constraints the regular dispatcher would have already known.
- Conversations are logged. What was promised to which broker, when, and on what terms. The fill-in does not have to text the dispatcher asking what was discussed Tuesday.
None of this requires the dispatcher to do extra work. It requires a system that captures the work being done anyway, in a place anyone can read it.
Frequently asked questions
How big is the continuity risk really if my dispatcher is reliable?
Reliability is not the question. Even reliable people get sick, take a vacation, have a death in the family, or get a job offer. The question is what your fleet does that day. If the answer involves any of "I would have to figure it out from scratch", "ask the drivers what they were supposed to do today", or "call the customers and ask them to send the rate cons again", you have a continuity problem regardless of how reliable the dispatcher is.
What is "tribal knowledge" in a small fleet?
It is everything the dispatcher knows that exists nowhere else. Which broker pays late and how to dunning them. Which driver does not run after dark and which one will not deadhead more than 200 miles. Which lane is hot this season. Which customer needs the BOL faxed instead of emailed. None of this is in the spreadsheet, and none of it transfers when the dispatcher is out.
Cannot I just hire a backup dispatcher?
You can, and most growing fleets do, but a backup dispatcher is only as effective as the system they walk into. If the system is the existing dispatcher's spreadsheets and head, the backup spends the first three months learning the same tribal knowledge from scratch. They do not actually become a backup until the knowledge has been moved out of the head and into the system.
What is the smallest version of fixing this?
Stop letting any operational decision live only in the dispatcher's head. Customer preferences, driver routing rules, broker terms, accessorial agreements: write them down where the next person in the chair can find them. This is unglamorous work, but it is the work that lets a fleet survive a week without its main dispatcher.
How do TMS systems actually help with continuity?
Two ways. First, by making the operational state of the fleet legible without explanation: any qualified person should be able to open the dashboard and see what is dispatched, what is in transit, what is waiting on a driver, and what is waiting on a customer. Second, by capturing the rules. Customer pay terms, driver pay rates, broker accessorials, lane preferences, all live in fields that anyone can read instead of in one person's memory.
My dispatcher is also my owner. Does this still apply?
Yes, and arguably more so. The owner-dispatcher single point of failure is the most common one in small fleets, and the most painful to recover from. The fleet that cannot run a single day without the owner is the fleet that the owner cannot ever step away from. That is a business that runs the owner, not a business the owner runs.
Make your fleet run without you
We'll walk through how a system that captures the operational state of your fleet (instead of leaving it in one person's head) actually works in practice. 30 minutes, no commitment.
Schedule a walkthrough