Every dispatch plan clears your ops lead first.
This is the approval-gated dispatch pattern from our Freight & Logistics track, running on synthetic US–Mexico load tenders. The co-pilot reads each tender, checks driver hours and customs status, and proposes a plan with its reasoning attached. Nothing writes to the TMS until you approve it. Work the queue below.
All loads, drivers, and rates above are synthetic. The gate is the point: zero plans commit without a named approver.
Three components, one acceptance metric.
The production build runs against your TMS and ELD feed instead of synthetic data. Acceptance is measured on empty miles, agreed before kickoff and measured before invoice.
Tender ingestion
EDI 204 tenders and rate-con PDFs land in one queue. Every extracted field stays grounded in the source document, with the original one click away.
Constraint engine
Hours of service from the ELD feed, customs broker status, equipment, and lane history score every candidate plan before one is proposed.
Approval gate & audit log
Every commit carries the plan, the reasoning, and the name of the approver. The log is append-only and holds up when a customer disputes a load.
Run this on your lanes.
A 9-week pilot against your TMS, scoped from a real reference engagement on US–Mexico lanes. One metric, agreed before kickoff: empty miles.