Bulk Chemical Tanker Heel, Cleanout, and Washout Station Logistics

Why Heel Decides Profit and Safety

Heel is the liquid that remains in a tank, pump, hoses, and lines after unloading. A small heel may be normal clingage on tank walls. A large heel may mean incomplete unloading, a pump problem, cold product, high viscosity, or a receiver that stopped the unload early. Heel matters for three reasons at once. It is product the customer paid to move but did not receive. It can contaminate or react with the next cargo. And it changes the legal and commercial quantity story when the next shipper loads over it. Carriers that do not measure heel are guessing on all three.

Record heel in a structured way. After unload, the driver or unloader records estimated or measured heel quantity, unit, method of estimate, product name, temperature if relevant, and whether the receiver directed a partial unload. Photograph the gauge or sight glass where fitted. If the tank will be washed, heel must be removed and disposed of or returned according to the product safety data sheet and customer instruction before washing. Sending a tank with a heavy heel to a wash rack wastes wash capacity, increases waste disposal cost, and can create a safety exposure when the wash opens the tank.

The Compatibility Matrix Is a Dispatch Control

A compatibility matrix answers one question before tractor assignment: can this tank, after its last cargo and its planned cleaning, safely and legally carry the next cargo to the required quality standard? The matrix should consider chemical family, hazard class, food grade or Kosher status where applicable, temperature requirements, lining and gasket material, hose and pump dedication, and customer specific prohibitions. Some products require a dedicated tank. Some require a full wash. Some allow a flush. Some are forbidden after certain prior cargoes regardless of washing, because the customer or regulation will not accept the risk.

Build the matrix as data, not as a poster in the dispatch office. Each product record carries prior cargo restrictions, required cleaning level, and certificate requirements. Each tank record carries lining, last three cargoes, last wash method, station, and date. When dispatch tries to assign a tank, the TMS evaluates the pair and returns green, yellow with supervisor approval, or red with a hard stop. That logic belongs in TMS implementation with safety, not in a spreadsheet one planner maintains. Review the matrix whenever a new chemical, customer, or wash method is introduced.

Keep the history long enough to answer customer questions. A shipper may ask what the tank carried before their product and how it was cleaned. If the TMS can show the last cargoes, the heel disposition, the wash station, the method, and the certificate number in one screen, the conversation is short. If the answer requires calling a driver who has left the company, the shipper will choose a different carrier next time.

Cleanout Levels: Flush, Wash, CIP, and Detailing

Not every cleanout is the same. A flush uses a compatible fluid to rinse product from tank and lines. A standard wash adds detergent or caustic, heat, and rinse at a commercial tank wash. Clean in place, or CIP, circulates cleaning solution through the tank, pump, and lines in a controlled cycle with time, temperature, concentration, and flow recorded. Detailing or mechanical entry cleaning addresses hardened residue, polymers, or products that coat walls and sumps. The correct level depends on the prior product, the next product, tank design, and customer specification. More cleaning is not always better if it damages lining, wastes a day, or sends the tank to a station that cannot handle the waste stream.

The wash order must travel with the tank. It should state prior product, heel disposition, required method, chemicals allowed or forbidden, whether hoses and pump must be cleaned or replaced, gasket requirements, and the certificate the station must issue. When the driver arrives at the rack, there should be no oral translation. A structured order also lets billing compare the quoted wash cost with the station invoice and catch charges for services that were not ordered.

Wash Certificates and What Makes One Believable

A wash certificate, sometimes called a cleaning certificate, should identify the tank, tractor or trailer number, prior product, cleaning method, date and time, station name and location, operator, and any tests performed. For CIP, include cycle parameters where available. For food grade work, include the seals applied after cleaning and their numbers. Store the certificate image against the tank wash record in the TMS, not in a cab file or an email inbox. Dispatch should see certificate status at assignment: clean and certified, clean but certificate pending, or not clean. A load should not be spotted for a regulated next cargo on a promise that the paper is coming.

Certificates also expire in practical terms. A tank cleaned three weeks ago and then moved, opened, or used for a different service may no longer be clean for the next shipper. Set validity rules by product family and customer. If the seal is broken or the tank is opened, the status returns to unknown until inspected or rewashed. Seal numbers recorded at the wash, at pickup, and at delivery create a simple chain that resolves many disputes. Our data protection practice helps carriers retain these records with access control and backup so certificates survive staff turnover.

Routing the Dirty Tank: Wash Station Logistics

Wash planning is network planning. The best wash station is not always the closest. It must accept the prior product waste, perform the required method, handle hoses and pumps, and turn the tank within the window for the next load. A station that is cheap but adds 180 deadhead miles and a missed appointment costs more than a nearer qualified rack. Build a station master with capabilities, accepted products, hours, appointment rules, average turn time, waste restrictions, and contact details. Then let dispatch see wash options on the map with the next load origin, so the clean tank, the wash, and the reload form one plan.

Sequence matters. If a tractor unloads Friday afternoon far from a qualified wash, the weekend plan should already show whether the tank waits, deadheads to wash, or swaps for a clean tank at a terminal. Tank swaps, where terminals keep cleaned spare tanks, can save a lane but require disciplined status control. A tank marked clean in the yard must really be clean, sealed, and certified. A SQL data mining review of wash cycle time, deadhead to wash, and reload delay usually finds one or two lanes where repositioning a spare tank pays for itself.

• Station capability first - Match prior product waste and required method before price.
• One plan, three legs - Unload, wash move, and reload shown as a single itinerary.
• Seal discipline - Record seal numbers at wash, pickup, and delivery.
• Cost to serve - Compare wash invoice, deadhead, and delay against lane margin.

Hoses, Pumps, Gaskets, and the Forgotten Surfaces

Many contamination events happen outside the tank barrel. Product sits in the pump, the drop hose, the vapor recovery line, and the sump. A certificate that covers only the tank while hoses carry prior product gives false confidence. The wash order should therefore list every wetted component: tank interior, pump, meter if fitted, hoses by length and diameter, fittings, and gaskets. Dedicated hoses for certain families reduce risk but require inventory control by tank and by product group. Colour tags and hose test dates should be visible in the equipment record.

Material compatibility is equally practical. A gasket that swells in a solvent or a lining that softens at temperature can fail even when the cleaning was correct. Keep lining and elastomer data on the tank record and include it in the matrix check. Maintenance should flag tanks due for internal inspection, lining repair, or hose hydrostatic testing before dispatch assigns a sensitive load. Linking maintenance holds to dispatch availability prevents the familiar call where a loaded tank must be pumped off because an inspection expired.

Driver Workflow at Unload and at the Wash Rack

Drivers execute the system. At unload, the workflow is confirm receiver instructions, monitor unload, record heel, photograph where required, note seal changes, and report any receiver directed partial unload before leaving the site. At the wash, confirm the wash order, verify prior product declaration, wait for certificate and seals, inspect the tank outlet and manway where safe and permitted, and send the certificate image before departure. Do not ask drivers to enter a tank or perform confined space work. Their job is verification and reporting within their training and site rules.

Pay design should support the workflow. If drivers lose money whenever they wait for a proper wash, the system will be bypassed under pressure. Detention, wash wait, and deadhead to wash need clear pay codes tied to the wash record. When pay follows the correct process, heel reporting improves because drivers are not punished for honesty. Safety, operations, and payroll should review heel outliers together monthly, looking for equipment, product, or receiver patterns rather than blaming the nearest person.

Costing Heel and Wash in the Rate

Wash cost is lane cost. A rate that ignores heel disposal, wash charges, deadhead to the rack, clean tank waiting, and the risk of a rejected load will look competitive and lose money. Build lane cost models that include expected wash level by product pair, average station charge, miles to wash, and turn time. That work connects naturally to carrier rate matrix optimization, where accessorial and equipment cycle costs are made explicit. Customers respect a wash pass through with a certificate far more than a vague contamination claim after the fact.

Measure four numbers weekly: heel quantity by product and receiver, wash cost per loaded mile by lane, percentage of tanks assigned without matrix warning, and certificate pending time. Those four reveal whether the problem is unloading, routing, data, or station capacity. Publish them to dispatch and maintenance together. Bulk chemical operations improve when the same facts are on one page.

Audit Readiness and Customer Visits

Chemical shippers audit carriers. They will ask for the compatibility procedure, sample wash certificates, driver training records, heel logs, and examples of rejected assignments. The TMS should produce a tank history packet in minutes: last cargoes, heel records, wash orders, certificates, seals, inspections, and the loads carried after each wash. Run a mock audit twice a year using a tank chosen at random by someone outside dispatch. If the packet takes more than an hour to assemble, fix the filing before a customer finds the same gap. Prepared carriers win hazardous and high purity freight because shippers are buying risk reduction as much as transportation.

Related practice areas for this work include TMS Implementation SQL Data Mining Carrier Rate Matrix Optimization. Each practice page describes scope, deliverables, and how an engagement starts with a short discovery call.

How Strong Tower Consulting Helps

Strong Tower Consulting helps carriers turn a regulatory or operational requirement into a working system inside the TMS rather than a side spreadsheet that only one person understands. The work starts with a data inventory, moves to a controlled pilot on a small set of lanes or customers, and then expands with audit reports that dispatch, safety, billing, and management can all read. Strong Tower Consulting, LLC and Exspeedite LLC are separately organized sister companies under common ownership. That separation keeps consulting advice vendor neutral and focused on the carrier operation.

To discuss your fleet, your lanes, and your current systems, call 763-244-1373 and ask for Scott Elliott. A short call is enough to map the first pilot, the data you already have, and the gaps to close before an auditor, a customer, or a port authority asks for proof.

Frequently Asked Questions