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-24014
deliveredMeridian Medical Supply · Memphis, TN → Nashville, TN
TMS source record
TMS · TMS-24014
Dispatcher / owner
Tessa Morgan
Carrier / driver
Frontier Cartage · Maya Chen
Equipment
Dry van · (555) 016-3114
Origin
Memphis, TN
Destination
Nashville, TN
Pickup appointment
7:00 AM
Delivery / current ETA
7:00 AM / 1:00 AM
Operational timeline
Imported TMS milestones alongside FreightFlow work, communications, documents, and exceptions.
Customer notification
5:00 AM · 4h agoEMAIL · Checkpoint update sent with current ETA and next action.
Human communication · FreightFlow event layer
Tracking checkpoint
4:00 AM · 5h agoLast location reported near Memphis, TN.
Automated tracking · FreightFlow event layer
Carrier communication
3:00 AM · 6h agoPORTAL · Driver reports clear roads and steady progress.
Human communication · FreightFlow event layer
Shipment status updated
9:00 PM · 12h agoMoved to delivered.
Operational event · FreightFlow event layer
POD received
7:00 PM · 14h agoPOD attached to the shipment record.
Document event · FreightFlow event layer
BOL received
5:00 PM · 16h agoBOL attached to the shipment record.
Document event · FreightFlow event layer
Exception created: BOL missing
6:00 AM · 27h agoBill of lading is not attached to the shipment record.
Operational event · FreightFlow event layer
Driver dispatched
1:00 PM · 68h agoMaya Chen assigned to the load.
Operational event · FreightFlow event layer
TMS record synchronized
7:00 AM · 98h agoAuthoritative load and appointment data received from TMS.
Operational event · FreightFlow event layer
Operations notes
Keep handoffs clear for the next broker or dispatcher.