AI dispatch assistants for fleets: what dispatch history they learn from

What does an AI dispatch assistant try to predict?#

An AI dispatch assistant tries to predict what a capable dispatcher would do next: which driver and tractor should take a load, whether the assignment fits the driver's remaining hours, and what to do when a pickup slips. Some tools rank candidate drivers for each open load. Others watch loads in transit and suggest reassignments or draft status updates for the customer.

Each of those predictions is learned from, or tested against, past decisions. A model that has only seen load tenders can guess at lane patterns, but it cannot learn judgment. Judgment shows up in a record only when the fleet kept the assignment, the conditions at the time and the result side by side.

That is why developers of automated dispatch tools look past volume. A carrier with years of linked assignments, reassignments and outcomes can teach more than a larger fleet whose TMS overwrites each load's history when the load closes.

The dispatch decision record: load, hours, equipment, constraint, choice, outcome#

The dispatch decision record is the unit an AI dispatcher learns from: one assignment, captured with what the dispatcher knew and what happened afterward. Most fleets already hold every piece somewhere. The work is joining the pieces by load number, driver ID, tractor number and time.

The constraint and outcome fields carry most of the value. A load given to a driver with plenty of hours teaches little. A load swapped late at night because the first driver's clock would run out before a dock appointment, with a note explaining the swap, teaches the exact trade-off an assistant has to learn.

Which systems hold dispatch history, and how well do they link?#

Dispatch history for most fleets is spread across the TMS, the ELD and telematics platform, the maintenance system and the dispatchers' email and messaging. A carrier running McLeod for orders and Samsara for hours and GPS, for example, holds the assignment in one system and the driver's clock and location trail in the other.

The join key is the weak point. Some fleets push load numbers into the ELD workflow so every stop event carries the load ID. Others can link only by tractor and timestamp, which still works but takes more preparation. Telematics vendors and plans differ in how far back detailed history can be exported, so check the plan and the vendor's documentation before assuming the data is there. Six months is a regulatory minimum for keeping records of duty status, not a limit, so a fleet can choose to keep ELD history longer.

Free text matters as much as structured fields. Dispatcher notes on the load, driver messages sent through the in-cab tablet and emails with shippers about a missed appointment often hold the only explanation of why a load moved the way it did.

What makes a dispatch archive weak?#

A dispatch archive is weak when it records the final state of each load but not the path to it. The common gaps show up quickly in a short review with whoever administers the TMS.

• 1Reassignments overwrite the original driver, so the first choice and the reason for changing it are gone.
• 2Dispatcher notes were purged in a cleanup or did not migrate when the TMS was replaced.
• 3ELD history was kept only for the six-month minimum that FMCSA sets for records of duty status and supporting documents, so hours at the moment of assignment cannot be rebuilt for older loads.
• 4Status codes changed meaning over the years, such as a single late code that was later split into shipper-caused and carrier-caused delays.
• 5Outcomes live only in billing, so detention appears as an accessorial charge with no link to the stop that caused it.
• 6Brokered and power-only loads sit in a separate system with different identifiers.

Illustrative: a regional reefer carrier reviews its dispatch history#

Illustrative: a fictional refrigerated carrier hauls grocery and dairy freight out of a single Midwest terminal. Its TMS holds orders and assignments, its ELD platform holds hours and GPS breadcrumbs, and its dispatchers have logged reassignment reasons in a free-text field for years.

When the COO reviews the records, the team finds that the TMS kept every reassignment as a separate timestamped line and that load numbers were pushed to the ELD, so stop events carry the load ID. Reefer temperature alarms sit in a third system linked by trailer number. The gap is outcome: late deliveries are coded, but detention shows up only on the invoice.

The carrier scopes a package of assignments, reassignments with notes, hours at assignment, temperature events and coded delivery outcomes, with detention linked through the invoice by load number. Driver names and cell numbers become stable pseudonymous IDs, and home addresses and nearby GPS points are removed before anything is shared.

What comes out before dispatch history is shared?#

Dispatch history carries personal and confidential details that are removed or transformed before any license. Drivers are identifiable through names, cell numbers, license and medical card details, pay records and location trails that end at their homes. Shippers and receivers appear with names, rates and facility details that customer agreements may treat as confidential.

In-cab audio and inward-facing video raise separate consent and biometric questions, and they are usually left out of dispatch packages entirely.

How SourceX approaches dispatch history#

SourceX treats a fleet's dispatch archive as one candidate package within the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The fit check uses metadata only, such as system names, years of accessible history and how loads link to ELD records, so nothing leaves the fleet during the initial assessment.

If the fleet proceeds, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and the fleet's release authorization. Large telematics histories stay in the carrier's own storage or ship on encrypted drives. The records are licensed, not sold, and the carrier keeps ownership and approves every step.