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

pod pending

Redwood Office Products · Kansas City, MO → Omaha, NE

TMS source record

TMS · TMS-24047

Dispatcher / owner

Elena Rodriguez

Carrier / driver

Prairie Fox Logistics · Jordan Brooks

Equipment

Dry van · (555) 016-3147

Origin

Kansas City, MO

Destination

Omaha, NE

Pickup appointment

10:00 AM

Delivery / current ETA

10:00 PM / 2:00 PM

Operational timeline

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

Exception created: BOL missing

11:00 PM · 34h ago

Bill of lading is not attached to the shipment record.

Operational event · FreightFlow event layer

Driver dispatched

4:00 PM · 65h ago

Jordan Brooks assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

10:00 AM · 95h 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.