Truck & Trade Trends

In trucking, we measure almost everything except the pressure sitting in the dispatch chair.

We track on-time percentage, empty miles, fuel burn, HOS, maintenance cost, claims, and revenue per truck. But dispatcher overload, the one thing quietly distorting all of those numbers, is usually treated like a personality issue instead of an operating condition. That is a mistake.

A dispatcher who is overloaded does not just feel stressed. They start making weaker decisions. Small changes get missed. Load handoffs get sloppy. Appointment windows are misunderstood. Drivers stop getting clean information. After-hours calls rise. Then leadership blames execution, as if execution failed on its own.

It did not. The system overloaded the person running the middle of it.

And this matters even more right now. U.S. trucking is still operating in a market where margins remain tight, non-fuel operating costs are elevated, and carriers are being forced to run lean while still handling volatile freight patterns and customer changes. ATRI’s 2025 cost update showed non-fuel operating costs hit a record high, while truckload margins stayed under pressure. At the same time, detention continues to destroy productivity, with ATRI reporting that 39.3% of stops involved detention and that lost productivity tied to detention reached 136 million hours. Add in shifting tender behavior and more deliberate use of spot freight, and dispatch desks are being asked to absorb more volatility with less room for error.

That is where the Dispatch Cognitive Load Index comes in.

The real problem is not weak dispatchers, it is unmanaged mental traffic

Most fleets size dispatch based on truck count alone.

That sounds logical, but it is incomplete.

A dispatcher handling 28 trucks in a stable, repeatable network with disciplined customers is not doing the same job as a dispatcher handling 22 trucks with constant appointment changes, late tenders, live-load delays, breakdown escalations, driver issues, and after-hours fire drills. Those are two completely different jobs wearing the same title.

This is where many internal systems are broken. Management says a dispatcher has “only” 20 or 25 trucks, so they must have capacity. But capacity is not truck count. Capacity is truck count multiplied by volatility.

That is the part fleets do not measure.

The result is predictable. Once overload becomes normal, dispatchers start operating in survival mode. They stop planning three moves ahead and start reacting one crisis at a time. The operation looks busy, but it is actually becoming fragile.

Why this is worse now ?

Dispatch has become more mentally demanding, not less.

Yes, fleets have more technology. But technology has also increased the volume of inputs. More alerts, more visibility tools, more customer messages, more driver pings, more live tracking exceptions, more check calls, more compliance triggers. Good software helps, but only if it filters noise. In many fleets, it just accelerates the noise. Industry technology vendors are openly pushing AI and connected operations tools to manage workflow bottlenecks and data overload, which tells you the problem is no longer hidden. It is now recognized at scale.

There is another layer. FMCSA’s current Hours of Service environment gives fleets more flexibility in some areas, including expanded sleeper berth options under the pilot, but flexibility only helps when dispatch has the time and judgment to use it correctly. A flexible rule in a chaotic operation often becomes one more variable the dispatcher has to mentally juggle.

So no, this is not just a people problem. It is an operations design problem.

---

The Dispatch Cognitive Load Index

Here is the framework.

You track three things for every dispatcher, every shift, every week:

1. Trucks per dispatcher This is your base load. Not revolutionary, but still necessary.

2. Active changes per shift These are same-day or in-shift disruptions that force a decision or rework. For example:

• appointment moved
• load cancelled
• driver swap
• breakdown
• trailer issue
• customer delay
• repower
• HOS conflict
• last-minute tender
• route change
• after-dispatch instruction change

Do not count passive updates. Count only changes that require thinking, communication, or replanning.

3. After-hours disruptions These are calls, texts, or issue escalations outside the dispatcher’s normal shift that still require attention or create next-shift damage.

Now create a simple score:

Dispatch Cognitive Load Index = (Trucks × 1.0) + (Active Changes × 1.5) + (After-Hours Disruptions × 2.0)

That weighting is practical, not academic. You can adjust it later. But start there.

Why heavier weight on disruptions? Because one dispatcher can handle a reasonable truck count if the day is stable. What crushes performance is not the fleet size alone. It is interruption density.

Where the threshold usually shows up

Most fleets wait too long to admit performance is dropping.

Do not wait for a major service failure. Watch for the point where these four symptoms rise together:

• missed appointments
• increase in driver complaints
• more preventable communication errors
• more next-morning cleanup work

That is your threshold.

In a disciplined operation, you will notice that once a dispatcher crosses a certain DCLI range for multiple shifts in a row, quality falls fast. Not slowly, fast.

That threshold will be different by network type. A dedicated operation with fixed customers may tolerate a higher truck count and lower change count. Open-board truckload or mixed operations will hit the wall earlier.

So do not copy another fleet’s number. Find your own threshold by reviewing 60 to 90 days of dispatch activity against service failures.

Operating example

Let’s say Dispatcher A manages 24 trucks.

On paper, that sounds manageable.

But in one shift they deal with:

• 11 active changes
• 4 after-hours disruptions from the previous night bleeding into the morning
• 2 drivers already frustrated because they got changed twice yesterday

Their score becomes:

24 + (11 × 1.5) + (4 × 2.0) = 48.5

Now compare that with Dispatcher B managing 28 trucks in a cleaner network:

• 3 active changes
• 1 after-hours disruption

28 + 4.5 + 2 = 34.5

Dispatcher B has more trucks. Dispatcher A has the harder job.

That is the whole point. The wrong fleets staff by truck count and wonder why the “same headcount model” works in one terminal and fails in another.

---

What this solves immediately

This framework solves three ugly problems that usually get misdiagnosed:

1. Errors Not because dispatchers are careless, but because overloaded brains skip steps.

2. Missed appointments Not because the fleet lacks software, but because too many moving pieces are being managed by one person at once.

3. Poor decision-making Not because dispatch lacks experience, but because overload turns planning into reaction.

It also helps with driver retention. Drivers rarely say, “My dispatcher’s cognitive bandwidth is too low.” They say, “Nobody tells me anything on time,” or “Every day changes at the last minute.” That is often the same problem wearing a different face.

---

How to use it in real life, not in a meeting deck

Here is the practical rollout:

For the next 30 days, make every dispatcher log truck count, active changes, and after-hours disruptions. Do not overcomplicate it. A shared sheet or TMS tag structure is enough.

At the same time, track:

• missed appointments
• load fallout
• driver complaints
• service recovery events
• after-hours calls by terminal

Then line them up.

You are looking for the score range where service starts slipping. That becomes your operating threshold.

Once you find it, act on it:

• rebalance truck assignments
• split volatile accounts from stable accounts
• create an escalation lane for high-disruption customers
• reduce unnecessary after-hours contact
• assign planners or night support where repeated overload shows up
• stop pretending one strong dispatcher can absorb a broken system forever

That last point matters. Hero dispatching is not a strategy. It is deferred failure.

---

The trucking industry is full of hidden capacity problems, and dispatch overload is one of the most expensive ones because it spreads quietly. It affects service, safety, driver trust, planning quality, and ultimately margin.

No one measures dispatcher overload because it has been treated as intangible.

It is not intangible. It is measurable. It is manageable. And once you start tracking it, you will probably find that some of your service problems are not customer problems, not driver problems, and not software problems.

They are cognitive load problems.

And that is good news, because once a problem is visible, it can finally be run like an operation.