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

pod pending

Brightwell Manufacturing · Kansas City, MO → Omaha, NE

TMS source record

TMS · TMS-24015

Dispatcher / owner

Maya Chen

Carrier / driver

Oakline Transport · Jordan Brooks

Equipment

Flatbed · (555) 016-3115

Origin

Kansas City, MO

Destination

Omaha, NE

Pickup appointment

6:00 AM

Delivery / current ETA

6:00 AM / 2:00 AM

Operational timeline

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

Tracking checkpoint

9:00 AM · 1m ago

Last location reported near Kansas City, MO.

Automated tracking · FreightFlow event layer

Customer notification

9:00 AM · 1m ago

EMAIL · Checkpoint update sent with current ETA and next action.

Human communication · FreightFlow event layer

Exception created: POD missing

5:00 AM · 4h ago

Delivered shipment has no verified proof of delivery.

Operational event · FreightFlow event layer

Carrier communication

2:00 AM · 7h ago

PHONE · Driver reports a short delay at the previous stop.

Human communication · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to pod pending.

Operational event · FreightFlow event layer

BOL received

4:00 PM · 17h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

Driver dispatched

12:00 PM · 69h ago

Jordan Brooks assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

6:00 AM · 99h 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.