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

in transit

Harbor & Pine Home Goods · Dallas, TX → Atlanta, GA

TMS source record

TMS · TMS-24000

Dispatcher / owner

Maya Chen

Carrier / driver

Blue Mesa Freight · Elena Rodriguez

Equipment

Reefer · (555) 016-3100

Origin

Dallas, TX

Destination

Atlanta, GA

Pickup appointment

1:00 AM

Delivery / current ETA

5:00 PM / 11:00 AM

Operational timeline

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

Carrier communication

9:00 AM · 1m ago

PHONE · Driver reports clear roads and steady progress.

Human communication · 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: Stale tracking

8:00 AM · 1h ago

Tracking has not updated within the operating threshold.

Operational event · FreightFlow event layer

Tracking checkpoint

6:00 AM · 3h ago

Last location reported near Dallas, TX.

Automated tracking · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to in transit.

Operational event · FreightFlow event layer

Driver dispatched

7:00 AM · 26h ago

Elena Rodriguez assigned to the load.

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.