King of Freight · Concept prototype
The TMS remains the system of record for loads, contracts, customer master data, and accounting. This fictional demonstration shows how FreightFlow could surface what needs attention, who should act, and whether it was resolved.
Synthetic data · fixed Sep 8 scenario · saved in this tab
FF-24023
pod pendingCedar Grove Foods · Kansas City, MO → Omaha, NE
TMS source record
TMS · TMS-24023
Dispatcher / owner
Marcus Hill
Carrier / driver
Northstar Haulage · Jordan Brooks
Equipment
Dry van · (555) 016-3123
Origin
Kansas City, MO
Destination
Omaha, NE
Pickup appointment
4:00 PM
Delivery / current ETA
10:00 PM / 12:00 PM
Operational timeline
Imported TMS milestones alongside FreightFlow work, communications, documents, and exceptions.
Tracking checkpoint
7:00 AM · 2h agoLast location reported near Kansas City, MO.
Automated tracking · FreightFlow event layer
Customer notification
6:00 AM · 3h agoEMAIL · Checkpoint update sent with current ETA and next action.
Human communication · FreightFlow event layer
Carrier communication
2:00 AM · 7h agoPORTAL · Driver reports a short delay at the previous stop.
Human communication · FreightFlow event layer
Shipment status updated
9:00 PM · 12h agoMoved to pod pending.
Operational event · FreightFlow event layer
BOL received
8:00 AM · 25h agoBOL attached to the shipment record.
Document event · FreightFlow event layer
Driver dispatched
10:00 PM · 59h agoJordan Brooks assigned to the load.
Operational event · FreightFlow event layer
TMS record synchronized
4:00 PM · 89h agoAuthoritative load and appointment data received from TMS.
Operational event · FreightFlow event layer
Operations notes
Keep handoffs clear for the next broker or dispatcher.