Automation

And a rejection is a business rule, not a button. You can reject a load and send it straight back through the TMS and the EDI connection. Or you can reject it internally first and offer it elsewhere inside the EDI expiration window — where the rule holds the clock, because a tender that times out instead of being canceled programmatically counts as a service failure to the shipper.

The rule sits on top of the optimization rather than ahead of it: if the recommendation is accept, then accept. The rule does not guess at the right answer. It carries out the one the recommendation produced.

Commodities resolved. Customer codes resolved. The SCAC corrected, so the tender reaches the division that should have received it. The list keeps going, and it is different for every customer.

And the corrections a CSR makes from memory every single time this customer tenders — the ones that exist nowhere but in their head — written down once and applied from then on.

A load can be offered to one division or affiliate first, then waterfalled against the available capacity of the others. It can be evaluated for your own assets through the optimization and then moved to brokerage when the margin does not clear your threshold.

A load that always runs as two legs can be split the moment it is tendered rather than when somebody gets to it — a local fleet on the first leg, OTR on the second. The value is not the click. It is the lead time, and on a split load lead time is what the second leg is short of.

And where a first leg runs on your US operation before handing to an affiliate carrier at the border, the handoff and its documentation travel with the load from the moment of tender.

Sometimes it is sold. Recruiters put a set of routes in front of a candidate and tell them this is what you will run — a series of origin-destination pairs built to fill out the week.

Sometimes it is engineered. A dedicated circuit runs a driver from a raw materials facility to a manufacturing plant, on to a distribution center, then to a recycling center and back to raw materials. Somebody designed that loop, and every leg of it has a reason to be there.

Either way it is a commitment made in advance, and the freight has to be found to honor it.

A driver bid is awarded on a driver’s seniority or their performance with the company, and it lets them run the lanes they want — the same customers every week, or simply a schedule they can count on.

Not every fleet runs driver bids. The ones that do are using them to keep drivers.

The first is recognition. A CSR has to spot the lane when it arrives and know that it belongs to a particular driver, or find the pairs that complete a driver’s tour. Miss it, and that driver does not get the week they were promised — which is how a retention tool turns into a reason to leave.

The second is that a driver bid is usually not the optimal answer for the network. That is a trade a fleet makes deliberately, and it is worth naming rather than hiding: the load might have run better somewhere else.

From the moment a tender is received, the system already knows which lanes belong to which driver. Recognizing it stops being a CSR’s job to remember.

A designed circuit only works if every leg materializes. When one of them does not, the driver is sitting, and the freight that was supposed to follow it is still sitting further down the week.

The gap in that driver’s schedule is recognized, loads are identified to keep them moving, and they are put back on their tour schedule. The circuit resumes rather than unravels.