Dispatch operations

Dispatch Operations Control

Real-time visibility across load intake, driver readiness, and release decisions — all unified in one record.

145 Active loads 96% On-time delivery 9 At risk 24 Blocked

Load intake command path

Shipper intake stays connected to dispatch release, driver readiness, proof, and settlement impact.

The form is still part of the demo. A customer load request creates the operating record; dispatch then clears driver, HOS, equipment, documents, proof, and release status before the load can move.

Interactive dispatch subset

Open the dispatch board from inside the dispatch overview.

The embedded board shows load intake consequence, driver and carrier readiness, document gate, route context, post-trip proof, and the exact release condition behind a load.

Dispatch proof in motion

Load intake should feel tied to the desk, the driver, and the route before release.

These proof scenes show the work BOF is organizing: shipper requests, dispatch desk review, pre-trip handoff, route packet control, and the evidence that explains why a load is ready, delayed, at risk, or blocked.

Dispatch office with load board monitors and paperwork

Load board office

New tenders need release status, driver fit, equipment fit, and next action visible together.

Driver pre-trip clipboard and route packet before dispatch

Pre-trip handoff

Rate confirmation, BOL draft, insurance, cargo photos, and equipment evidence move with the record.

Route board and tablet review for dispatch planning

Route review

HOS available time, ready-again timing, route context, and fuel planning can become dispatch facts.