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

in transit

Summit Appliance Co. · Dallas, TX → Atlanta, GA

TMS source record

TMS · TMS-24008

Dispatcher / owner

Marcus Hill

Carrier / driver

Atlas Creek Transport · Elena Rodriguez

Equipment

Reefer · (555) 016-3108

Origin

Dallas, TX

Destination

Atlanta, GA

Pickup appointment

5:00 PM

Delivery / current ETA

1:00 AM / 7:00 PM

Operational timeline

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

Carrier communication

9:00 AM · 1m ago

PORTAL · Driver reports clear roads and steady progress.

Human communication · FreightFlow event layer

Tracking checkpoint

7:00 AM · 2h ago

Last location reported near Dallas, TX.

Automated tracking · FreightFlow event layer

Customer notification

6:00 AM · 3h ago

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

Human communication · FreightFlow event layer

BOL received

11:00 PM · 10h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to in transit.

Operational event · FreightFlow event layer

Exception created: Customer update overdue

2:00 PM · 19h ago

Customer-facing update missed its service-level deadline.

Operational event · FreightFlow event layer

Driver dispatched

11:00 PM · 34h ago

Elena Rodriguez assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

5:00 PM · 64h 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.