What dispatching actually is
Dispatching is the operational heart of a trucking business. It is the practice of matching freight to drivers, making sure the load gets picked up on time, arrives clean, and comes back with the paperwork a carrier needs to get paid. On paper it sounds simple. In practice, every independent carrier learns that dispatch is where revenue is made or lost — and where a small fleet either scales or stalls.
For owner-operators and small fleets, the dispatcher is often the owner, a spouse, or a single hire wearing several hats at once. That person is simultaneously a customer service rep, a compliance officer, a debt collector, and a coach. The role touches brokers, shippers, receivers, drivers, factoring companies, and the IRS before a single wheel turns.
Good dispatching is the difference between a fleet that grows from five trucks to fifteen and a fleet that plateaus at five and burns out the owner in the process. Bad dispatching is not usually visible in a single day — it shows up in the cumulative effect of missed POD uploads, late invoices, undetected deadhead, and drivers who leave because they never knew what they were running next.
How dispatching has changed
Ten years ago, most small-fleet dispatch happened on a phone, a legal pad, and a big whiteboard in the office. The dispatcher took calls from brokers, wrote lanes on the board, and called drivers to assign them. Paper rate confirmations came through the fax or email, were printed, and lived in a folder on a filing cabinet. IFTA was a spreadsheet someone reconstructed at the end of every quarter from a stack of fuel receipts.
That model worked because it had to. But it relied on the dispatcher remembering everything — which load was where, which driver was due home, which broker still owed a rate con, which invoice had bounced back with a missing signature. When the dispatcher was sick or on vacation, the operation wobbled. When the fleet grew past a handful of trucks, the paper fell apart.
Software changed the baseline. Modern dispatch tools do not replace the dispatcher — they remove the parts of the job that were never about dispatch in the first place. Remembering where the rate con is filed, re-typing load details into an invoice, hunting for a fuel receipt from two months ago, and reconstructing miles per state for IFTA are not dispatch. They are overhead that a good TMS absorbs so the dispatcher can do the parts of the job that actually require a human.
Core responsibilities of a dispatcher
Strip away the tools and the job comes down to a short list of responsibilities that every small-fleet dispatcher carries, whether they think about it that way or not.
- Load intake and qualification. Every lane that comes in needs to be weighed against the truck that might take it. The dispatcher asks whether the rate pays, whether the driver has the hours, whether the customer pays, and whether the pickup window is realistic.
- Assignment. Matching a specific load to a specific truck and driver is not a clerical task. It is a judgment call that trades off driver home time, lane preference, equipment fit, and the next planned load down the line.
- Communication. The dispatcher is the single point of contact between the broker, the driver, the shipper, the receiver, and sometimes the factor. A missed message or a late callback at any one of these touchpoints costs money.
- Compliance. Hours of service, DOT permitting, hazmat, overweight, and customer-specific paperwork requirements all land on dispatch. Missing any one of them puts the load, the driver, and the operating authority at risk.
- Documentation. Rate confirmations, BOLs, PODs, weigh tickets, lumper receipts, and detention paperwork all need to be captured and attached to the right load before that load can be invoiced.
- Billing handoff. A completed load is not a paid load. Getting clean documents to billing or to the factor quickly is part of dispatch whether the title says so or not.
Dispatch KPIs that actually matter
There is no shortage of metrics a carrier can track. Most of them are noise. For a small fleet running its own book of freight, four numbers do almost all of the work — and if any of them drift, the business feels it before the month is out.
Deadhead ratio is empty miles divided by total miles. Every empty mile is fuel, tire wear, and driver hours that produced no revenue. An honest deadhead ratio sits somewhere in the ten to fifteen percent range for most small fleets with planning. If yours is creeping toward twenty-five percent, the load board is running the dispatch, not the other way around.
Revenue per loaded mile is the gross revenue of a load divided by the loaded miles it took to deliver. It is the number every broker and every driver cares about. When it climbs, the fleet can afford to grow. When it drops, everyone feels it — the driver in their settlement, the owner in their bank account.
On-time delivery rate is the percentage of loads delivered inside the receiver's appointment window. Brokers and direct shippers both watch this number even when they do not say so. An on-time rate above ninety-five percent keeps the phone ringing with the loads you want. A rate that slips into the eighties quietly loses you the best customers.
Driver utilization is the percentage of available driving hours actually spent moving freight versus sitting in a yard, waiting at a shipper, or deadheading for lack of a next load. This is where dispatch decisions show up most clearly. Good planning keeps the wheels rolling inside the driver's legal hours. Poor planning burns hours in detention and empty backhauls.
Every other metric — average revenue per load, cost per mile, fuel burn per hundred miles — is useful, but if the four above are healthy, the business almost certainly is too.
Manual dispatch versus software — an honest comparison
There is nothing wrong with running a one-truck operation out of a phone and a notebook. For a single owner-operator who knows the freight, knows the lanes, and knows which brokers pay, the overhead of any software system has to earn its place.
Manual dispatch has real strengths. It costs nothing to start. It moves at the speed of the dispatcher's memory, which can be faster than any software for someone who has been doing it for twenty years. It requires no training. It does not break because a login page is down. And it gives the dispatcher full control — no feature flag hides a button they need.
Manual dispatch has real costs, too. The paper trail is fragile. A single lost rate confirmation can mean thirty days of chasing a payment. IFTA at quarter-end becomes a multi-day exercise of recreating what happened from fuel receipts and memory. When the dispatcher is out sick, nobody else can pick up the thread quickly. And the data needed to make real decisions — deadhead ratio, revenue per mile, on-time rate — does not exist as a number anywhere because nothing is recording it.
Software does not make a bad dispatcher good. It does not negotiate better rates or wake up at 4am to check on a driver at a pickup. What it does is catch the small things — a missing POD, an unbilled load, a late invoice, an uncaptured fuel receipt — that individually look trivial and collectively drain tens of thousands of dollars a year from a small fleet.
When to stop dispatching in spreadsheets
The honest answer is not a truck count. Plenty of five-truck fleets run clean on a spreadsheet. Plenty of two-truck operations have no business being in one. The signal is operational, not numerical.
Stop dispatching in spreadsheets when you notice any of the following, because each one is a symptom of the model breaking down:
- You are reconstructing information at billing time. If you cannot produce a clean invoice for a completed load without calling the driver or digging through email, your intake process is dropping data.
- You are missing paperwork and eating the cost. Every month a load gets invoiced late because the POD never came in, or a detention claim gets denied because the paper timeline is gone, you are paying a manual-dispatch tax in lost revenue.
- IFTA takes more than one sitting. Quarterly IFTA should be a couple of hours, not a weekend. If it is the latter, miles and fuel are not being captured cleanly enough during the quarter.
- You cannot answer a simple question from a customer in real time. If a broker calls asking where a load is and you have to call the driver and call back, you have no visibility — and the broker has learned that.
- You are the single point of failure. If the business stops working when you take a day off, you have a job, not a fleet.
Any one of those is a signal. Two or three at once and the spreadsheet is costing you more than the software would.
What to look for in dispatch software
The TMS market is full of products that look impressive in a demo and get in the way on a Tuesday morning. For a small-fleet dispatcher who needs the tool to help — not audition itself — the feature list that matters is shorter than most vendors suggest.
Fast load entry. The single most common action in a dispatch day is entering a new load and assigning it. If that takes more than a minute of clicks, the software is going to lose you hours every week. Time this in the demo on real, realistic data.
Document handling on a phone. Drivers are not sitting at a desktop. If scanning a rate con or a BOL from a phone camera is awkward, the documents will not make it into the system. That means billing will not happen. That means cash flow breaks.
Driver-facing app that is actually usable. If the driver app requires a tutorial, drivers will not use it. The best driver tools show one load at a time, one action at a time, in large tap targets — because that is how the tool gets used in a cab at 5am.
Invoicing and factoring handoff. A completed load should become an invoice in one action. The invoice should export in a format the factor actually accepts. Every minute spent reformatting invoices is a minute the factor is holding your cash.
IFTA that captures miles and fuel as you go. Per-state miles and per-gallon fuel purchases need to be recorded in the normal flow of work, not reconstructed at the end of the quarter. If the tool requires a separate IFTA workflow, it is the wrong tool.
Per-load profitability. Revenue is not profit. A load that grosses twenty-two hundred dollars can net three hundred after fuel, tolls, per-diem, and factoring. The tool should tell you the net — not just the gross — because that is the number you actually steer by.
Support you can reach. The best software will still break at some point. When it does, the question that matters is how long it takes to get a human who understands the business on the other end. Founder-led support beats a ticket queue for the kind of operation most small carriers run.
Common dispatch mistakes that cost carriers money
Most of the margin a small fleet loses in a year does not come from a single dramatic mistake. It comes from the same handful of small mistakes repeated across hundreds of loads.
Taking loads without a real profit calculation. A rate that looks fine at the moment of booking can lose money once fuel, deadhead, tolls, per-diem, and factoring fees come off it. Dispatchers who book on gross revenue alone are flying blind, and the margin leakage compounds.
Letting deadhead drift upward. Every empty mile is a loss. Dispatchers who do not actively plan for the next load before the current one delivers will accept whatever the load board offers — which is often an empty sixty-mile deadhead to a low-paying origin.
Slow document collection. A load that delivers Monday and does not have a POD in the system by Wednesday will not be invoiced that week. A factor that does not get clean documents pays slower — and sometimes kicks the invoice back entirely for a missing signature.
Poor driver communication. A driver who does not know what the next load is after delivery, or who finds out about a reassignment by text from the broker instead of from dispatch, disengages quickly. Turnover is a hidden dispatch cost — and it shows up as the same recruiting fee, the same training time, and the same learning curve on every new seat.
No backup when the dispatcher is out. A one-person dispatch operation is a single point of failure. When that person is out sick, loads go uncovered, drivers do not get assignments, and customers learn they cannot rely on the fleet. A basic written process and a shared system fix this without needing a second hire.
Ignoring detention. Detention claims get paid when the paperwork supports them. Dispatchers who do not capture pickup and delivery times cleanly — or who do not push the claim with the broker — leave real money on the table. Five hundred dollars of detention once a week is twenty-six thousand dollars a year.
Building a dispatch workflow that scales
A dispatch workflow that works at three trucks and collapses at twelve is worse than no workflow at all — because it is invisible until it breaks. The goal for a small fleet is to build a process that is boring, repeatable, and survivable when the person who built it is not in the chair.
Start with intake. Every load that comes in — whether from a broker, a board, or a direct customer — should hit the same process. Lane, rate, pickup window, delivery window, commodity, required documents, and customer contact captured the same way every time. If the intake data is clean, everything downstream is easier.
Standardize driver communication. Drivers should know where to look for their next load, how status updates are expected, and what paperwork needs to go in at each stop. If every driver has a slightly different relationship with dispatch, the fleet is running ten different micro-operations at once.
Close the loop on every load. A load is not done when the driver delivers. It is done when the POD is in, the accessorials are captured, the invoice has gone out, and the payment has cleared. A dispatch workflow that ends at delivery is leaving money uncaptured by design.
Track the four KPIs weekly. Deadhead, revenue per loaded mile, on-time delivery, and driver utilization reviewed once a week tell you whether the operation is getting better or worse. A weekly review takes fifteen minutes and catches problems before they compound into a bad month.
Document the process. A short written SOP — even a one-page document — means a second dispatcher can pick up when the first is out, and a new hire can get productive in days instead of months. The best test of a workflow is whether it can be handed off.
How HaulerPro approaches dispatch differently
HaulerPro was built for the size of fleet most of this guide is written about: owner-operators through fifteen-plus-truck operations. It was built by someone who built the software around how carriers actually work. That changes some of the product decisions in ways that are worth naming honestly.
The dispatch screen is designed around the action that happens most often: assigning a load to a driver. From a new load to a dispatched load is under a minute, because that is what dispatchers actually spend their day doing. Everything else in the product — documents, invoicing, IFTA, expenses — was built so the fastest thing in the day stays the fastest thing in the day.
Load visibility is done through driver status updates rather than GPS. Drivers tap a status when they pick up, when they roll, when they deliver. Dispatch sees the update. The broker sees the update. Visibility goes through the driver, not around them.
Pricing scales with fleet size, starts free, and does not push a small operation into an enterprise plan the moment it grows past a handful of drivers. That matters because the operations that need dispatch software most are the ones least willing to pay to find out whether a tool works for them.
Support is founder-led. When something breaks on a Friday night, the person who answers understands the business — not a tier-one queue reading from a script. For a fleet owner who has been doing this for a decade, that is often the single biggest reason to switch.
None of that changes what dispatching actually is. The job is still judgment, communication, and documentation. The right tool just takes the overhead out so the dispatcher can do the parts of the job that only a human can do.