A regional freight company with 40 trucks spends most of its technology conversations talking about route optimization. Every logistics conference, every vendor pitch, every industry article is about getting trucks from point A to point B more efficiently.
But route optimization was not their biggest operational cost. Load planning was.
Three dispatchers spent a combined 12 hours per week building load plans. Each truck going out needed a plan that accounted for the weight and dimensions of every shipment, the delivery sequence (last loaded is first delivered), weight distribution for safe transport, and the specific loading requirements for different cargo types. Refrigerated items cannot sit next to heat-generating machinery. Fragile shipments need to be positioned where they will not shift. Hazmat loads have placement rules dictated by federal regulation.
The dispatchers did this work in a combination of Excel spreadsheets and experience. They knew which clients' shipments were always awkward sizes. They knew which routes had weight station checkpoints where an improperly balanced load would get flagged. They knew that Driver 12 had a truck with a slightly narrower door opening that could not accommodate the standard pallet configuration Client A used.
This institutional knowledge lived in three people's heads and a collection of spreadsheets that only those three people understood.
What the tool does
The tool takes the day's shipments — pulled from the order management system — and generates load plans for each truck on each route.
For each truck, it considers the total weight versus the truck's capacity and legal weight limits for the route. It considers the cubic footage of each shipment versus the available space. It accounts for delivery sequence — the shipment going to the last stop loads first, against the front wall of the trailer, and the first stop's shipment loads last, nearest the door.
It applies cargo compatibility rules. Refrigerated and ambient shipments are separated. Fragile items are positioned in stable locations with appropriate bracing notes. Hazmat placements follow DOT regulations for the specific hazard class.
It knows the truck fleet. Truck 12's narrower door opening is in the system. Truck 7's lift gate weight limit is in the system. Truck 23's reefer unit that cycles irregularly above 85 degrees ambient temperature is in the system.
The output is a visual load plan — a diagram showing where each shipment goes in the trailer, the loading sequence, any special handling notes, and the total weight and balance calculation. The dispatcher reviews it, adjusts if needed, and sends it to the loading dock.
What changed
Load planning dropped from 12 hours per week across three dispatchers to 3 hours per week. The dispatchers still review every plan. They still override the tool when their experience tells them something the data does not capture. But the starting point is a complete, compliant plan instead of a blank spreadsheet.
The quality of the plans improved. Not because the tool is smarter than the dispatchers — it is not. Because the tool is consistent. A dispatcher building their eighth load plan on a Friday afternoon might forget that Client A's shipments increased in size last month. The tool never forgets because it pulls current shipment dimensions from the order system every time.
Weight distribution violations at checkpoint stations dropped to zero in the first quarter. Previously, they averaged two per month, each costing $400 to $800 in fines plus the delay. Over a year, that is $10,000 to $20,000 in avoided fines alone.
The $180,000 calculation
The operations manager broke down the savings into four categories.
Dispatcher time recovered: 9 hours per week times 52 weeks times the loaded cost of dispatcher labor. That came to approximately $58,000 per year. The dispatchers were not laid off. They were reassigned to customer-facing coordination work that had been neglected because everyone was buried in load planning.
Weight violation fines avoided: approximately $14,000 per year based on historical average.
Fuel savings from better load balancing: properly balanced trucks use 3 to 5% less fuel than improperly balanced ones. Across 40 trucks running 5 days a week, the fuel savings came to approximately $67,000 per year. This was the number that surprised everyone. Nobody had connected load planning quality to fuel consumption because the effect per truck per day is small. Across a fleet over a year, it is significant.
Reduced damage claims: better load planning with proper cargo separation and positioning reduced in-transit damage claims by 40%. That saved approximately $41,000 per year in claim payouts and the administrative time to process them.
Total: $180,000 per year in quantifiable savings from a tool that took 10 days to build.
Why nobody talks about this
Route optimization is a sexy technology problem. It involves algorithms, real-time traffic data, GPS tracking, and impressive visualizations of trucks moving across maps. Vendors build entire companies around it.
Load planning is a spreadsheet problem. It involves cargo dimensions, weight limits, and regulatory compliance tables. It is not exciting. It does not make a good conference presentation. No vendor is raising venture capital to disrupt load planning.
But the spreadsheet problem was costing this company $180,000 a year. Their route optimization software, which they paid $45,000 per year to license, saved them approximately $30,000 per year in fuel through better routing.
The unglamorous spreadsheet tool produced six times the savings of the impressive routing software. And the company owned the spreadsheet tool. No annual license. No vendor dependency. No feature roadmap controlled by someone else's priorities.
The institutional knowledge problem
The most important outcome was not financial. It was organizational.
Before the tool, if any of the three dispatchers left the company, the load planning process would collapse. Their knowledge was not documented. Their spreadsheets were personal artifacts that only they understood. The company was three resignations away from a crisis.
After the tool, the cargo rules, truck specifications, and compliance requirements are encoded in the system. A new dispatcher can review and approve load plans on their first day because the institutional knowledge is in the tool, not in someone's head.
One of the three dispatchers retired four months after the tool was deployed. The transition was seamless. Under the old process, it would have been a six-month training effort to transfer her knowledge to a replacement.
Get posts like this in your inbox
No spam. New articles on AI strategy, governance, and building with AI for small business.