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

loadedat risk · 78

Harbor & Pine Home Goods · Stockton, CA → Denver, CO

TMS source record

TMS · TMS-24020

Dispatcher / owner

Maya Chen

Carrier / driver

Blue Mesa Freight · Nolan Reed

Equipment

Reefer · (555) 016-3120

Origin

Stockton, CA

Destination

Denver, CO

Pickup appointment

1:00 AM

Delivery / current ETA

1:00 PM / 7:00 AM

Operational timeline

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

Customer notification

9:00 AM · 1m ago

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

Human communication · FreightFlow event layer

Tracking checkpoint

7:00 AM · 2h ago

Last location reported near Stockton, CA.

Automated tracking · FreightFlow event layer

Carrier communication

5:00 AM · 4h ago

PORTAL · Driver reports clear roads and steady progress.

Human communication · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to loaded.

Operational event · FreightFlow event layer

BOL received

11:00 AM · 22h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

Driver dispatched

7:00 AM · 26h ago

Nolan Reed assigned to the load.

Operational event · FreightFlow event layer

Exception created: Stale tracking

4:00 AM · 29h ago

Tracking has not updated within the operating threshold.

Operational event · FreightFlow event layer

TMS record synchronized

1:00 AM · 56h 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.