Back to queue Live shipment record

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-24063

pod pending

Cedar Grove Foods · Kansas City, MO → Omaha, NE

TMS source record

TMS · TMS-24063

Dispatcher / owner

Marcus Hill

Carrier / driver

Northstar Haulage · Jordan Brooks

Equipment

Dry van · (555) 016-3163

Origin

Kansas City, MO

Destination

Omaha, NE

Pickup appointment

12:00 PM

Delivery / current ETA

6:00 AM / 6:00 AM

Operational timeline

Imported TMS milestones alongside FreightFlow work, communications, documents, and exceptions.

Exception created: BOL missing

3:00 AM · 6h ago

Bill of lading is not attached to the shipment record.

Operational event · FreightFlow event layer

Exception created: POD missing

1:00 AM · 32h ago

Delivered shipment has no verified proof of delivery.

Operational event · FreightFlow event layer

Driver dispatched

6:00 PM · 63h ago

Jordan Brooks assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

12:00 PM · 93h ago

Authoritative load and appointment data received from TMS.

Operational event · FreightFlow event layer

Operations notes

Keep handoffs clear for the next broker or dispatcher.