Tank Truck Dispatch Software: Why the Wrong Trailer Costs More Than the Freight

Why a tank fleet is not a truck fleet with a different trailer

It is 5:20am and a dispatcher is covering a load that fell apart overnight. A customer needs a food grade load of liquid sweetener picked up at 9am, and there is a trailer sitting 40 minutes away with a driver on hours. The dispatch board shows the trailer as available. What the board does not show, because nobody typed it in, is that the trailer's last load was a non-food chemical, that its wash was a rinse rather than the caustic and steam cycle the receiving plant requires, and that the wash certificate on file is for a different trailer number entirely. The load gets assigned. Four hours later the plant rejects at the gate, or worse, accepts and finds out later.

That is the difference between bulk liquid hauling and dry van hauling. In a van fleet a trailer is interchangeable capacity. In a tank fleet a trailer is a specific vessel with a history, and the history is part of the product spec. Prior cargo, wash status and certificate, heel remaining in the tank, gasket and hose compatibility, pump type, vessel specification and commodity dedication all determine whether that unit can take that load. Get it wrong and you are not paying a late fee, you are paying for a contaminated batch at the receiver, which routinely runs into six figures on a load whose revenue was under $2,000.

The rules are not optional either. Bulk food transport carries recordkeeping duties around prior cargoes and cleaning under the sanitary transportation rule, receiving plants frequently ask for the last three loads before they break a seal, and chemical shippers publish their own cleaning standards per product. All of it currently lives in a dispatcher's head or in a notes field nobody reads at 5am.

Problem 1: trailer state is the most important data you do not have

Ask any tank carrier what state a specific trailer is in right now and you will get a phone call to a driver. The system knows the trailer is empty and where it is. It does not reliably know the last product, when it was washed, at which rack, to what standard, whether there is a heel, or what gaskets and hoses are fitted. That information exists on paper at the wash rack and in a photo on a driver's phone.

McLeod LoadMaster, Trimble TMW Suite and Prophesy are capable transportation management systems and they are genuinely strong at what they were built for: order to cash, driver settlement, fuel tax, imaging and the dispatch board itself. Their limitation for tank work is that they model a trailer as capacity with attributes you can type in, so prior load and wash discipline ends up as free text or as a scanned document attached after the fact. None of them will stop a dispatcher from assigning a trailer, because none of them holds a rule that says this product cannot follow that product without this wash.

What a custom build does: make trailer state a first class record that changes through events, not through typing. The load completes, the trailer inherits a prior product. The wash is performed, the certificate is captured at the rack with the trailer number, the standard applied and the signature, and the trailer's state changes accordingly. Nothing sets a trailer to clean except a completed wash event. That one rule removes most of the class of failure described above, because it becomes structurally impossible for the board to show a clean trailer that was never washed.

Problem 2: compatibility is a rule set, and it is yours, not the vendor's

Which products can follow which, and after what cleaning, is carrier specific safety logic built from customer requirements, product data sheets, your own incident history and your wash capability. Some pairs are fine after a hot water rinse. Some require caustic, steam and a dry, with a specific certificate. Some products permanently dedicate a trailer. Food grade after non-food is often prohibited outright regardless of wash, no matter what the chemistry says, because the receiving plant's own audit standard says so.

You cannot buy this rule set. It is not a public table, it is an accumulation of what your customers demand and what you have learned, so it lives with your senior dispatchers and walks out when they retire. We have met carriers whose entire compatibility policy was one laminated sheet and one man with 22 years of service.

What a custom build does: encode the matrix explicitly as product to product rules with a required cleaning standard as the outcome, then evaluate it at the moment of assignment. The dispatcher does not have to remember. They see a hard block with the reason, or a soft warning that requires an override with a name attached. Overrides are logged, and reviewing them monthly tells you more about your real risk than any safety meeting will. This also converts Dale's knowledge into an asset the business owns rather than a person the business depends on.

Problem 3: the wash rack is a bottleneck nobody schedules

Washes are treated as an errand. A driver is sent to a rack, waits an unknown time, and the trailer reappears whenever it reappears. Your own rack has finite and invisible capacity. Third party racks vary in cost by standard and location and nobody is comparing. Either way the wash is often why a trailer is not available, and it is the one part of the operation that gets no planning attention.

Transportation management systems treat a wash as a non-revenue stop or an expense line. That is accurate accounting and useless planning.

What a custom build does: treat cleaning as a schedulable resource with duration by standard, then include it in assignment. The planner can then chain loads to minimise washes, which is real money since a full caustic and steam cycle carries both a direct cost and half a day of trailer downtime. It also surfaces the trade: this assignment saves a wash but adds 90 deadhead miles, and here is which one is cheaper for this pair. Carriers running this properly find the biggest savings not in dispatch efficiency but in wash avoidance, because nobody had ever measured it before.

Problem 4: the driver and the site have requirements too

The trailer being right is necessary and not sufficient. The driver needs the tanker endorsement, the hazmat endorsement where the product requires it, current training, and often a site specific induction. Individual plants have their own rules: appointment windows, personal protective equipment, vapour recovery capability, a required hose configuration, sometimes a ban on particular equipment after an old incident nobody at your company remembers.

Site rules almost always live in the customer record as free text, read only when someone thinks to read them. That is how a driver arrives at a plant, is turned away for a missing site induction, and burns four hours and a delivery window.

What a custom build does: make site requirements structured data evaluated at assignment alongside trailer compatibility, so a driver without the required induction or endorsement cannot be assigned. Requirements have expiry dates, and expiry drives a task before it drives a rejection. The dispatcher sees one combined answer: this driver, this tractor, this trailer, this product, this site, allowed or not, with reasons.

Problem 5: proving what happened after a claim

A contamination claim arrives three weeks after delivery. Your defence is the wash certificate, the prior load record, the seal numbers, the driver's confirmation that the seal was intact, and any sampling at loading. If those exist as paper in a folder and a photo in a text thread, you will settle whether you were at fault or not, because you cannot construct the story fast enough.

What a custom build does: build the chain as immutable events. Prior product, wash event with rack, standard, operator and certificate image, seal applied at loading with number and photograph, seal verified at delivery with number and photograph, sample retained and where. Assembling that packet becomes a single export. Carriers tell us the first successful claim defence usually covers a meaningful share of the build cost, and more importantly the customer's quality team stops treating you as the default suspect.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this category prices as follows. A focused first release, meaning event driven trailer state, the compatibility and cleaning rule engine, driver and endorsement matching, and a dispatch board that blocks unsafe assignments with logged overrides, runs $75,000 to $150,000 and ships in 12 to 16 weeks. A full platform adding wash rack scheduling and wash avoidance planning, customer site rule enforcement, an in-cab app for seals, photos and confirmations, and integration to your existing system for billing and settlement runs $180,000 to $400,000 phased over 6 to 12 months.

What pushes the number up in tank operations: the number of commodity groups, since food grade, chemical and petroleum each bring their own rule structure. Owning wash racks, which adds a scheduling and costing subsystem. In-cab connectivity, because drivers work where there is no signal and the app must reconcile later. And integration depth with McLeod or TMW, since replacing billing and settlement is a far larger project than augmenting it.

Build versus buy, stated plainly

Buy if you run under roughly 25 trailers in a single commodity with a stable customer base and one dispatcher who knows every unit. McLeod or Prophesy plus a disciplined paper wash log is genuinely adequate at that size, and a build would be spending money to formalise something that already works.

Build when two or more of these are true. You run more than about 60 trailers, past the point where one person holds trailer state in their head. You haul food grade and non-food in the same fleet. You have had a contamination claim, or a near miss you know was luck. Your compatibility knowledge sits with one or two people and you cannot state your own policy in writing today. Or customers have started asking for prior load documentation before they will unload.

Our position: the transportation management system is not the problem and you should probably keep yours. No general trucking system will ever model a trailer as a vessel with a history, because that concept does not exist in the market they sell to. The safety logic that distinguishes your fleet from a van carrier is not large. It is specific, and no vendor will build it for you.

How to choose a developer for tank fleet software

Ask them how a trailer becomes clean in their model. The right answer is that only a completed wash event with a certificate changes state, and no user can simply set a flag. If they describe a checkbox on the trailer record, they will ship the failure you are trying to eliminate.

Ask how they would handle an override. Dispatchers will need to override at 5am, and a system that forbids it entirely gets bypassed on paper within a month. The right design allows an override with a required reason and an attributable name, then reports on overrides so you can see where your policy and your reality disagree.

Ask about offline behaviour in the cab. Drivers load inside steel buildings and at rural terminals with no coverage, so seal capture and confirmations must work with no signal and reconcile cleanly afterwards. A developer who has not built that will discover it in week 11.

Ask who owns the code and settle it before kickoff. You should hold the repository, the infrastructure accounts and the right to hire anyone else. At Digital Heroes the client owns the code from the first commit.