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

at pickup

Brightwell Manufacturing · Reno, NV → Phoenix, AZ

TMS source record

TMS · TMS-24035

Dispatcher / owner

Maya Chen

Carrier / driver

Oakline Transport · Avery Patel

Equipment

Flatbed · (555) 016-3135

Origin

Reno, NV

Destination

Phoenix, AZ

Pickup appointment

10:00 AM

Delivery / current ETA

12:00 AM / 12:00 AM

Operational timeline

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

Driver dispatched

4:00 PM · 17h ago

Avery Patel assigned to the load.

Operational event · FreightFlow event layer

Exception created: Stale tracking

11:00 AM · 22h ago

Tracking has not updated within the operating threshold.

Operational event · FreightFlow event layer

BOL received

8:00 PM · 37h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

TMS record synchronized

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