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

en route pickup

Summit Appliance Co. · Savannah, GA → Charlotte, NC

TMS source record

TMS · TMS-24018

Dispatcher / owner

Marcus Hill

Carrier / driver

Westward Haul · Tessa Morgan

Equipment

Dry van · (555) 016-3118

Origin

Savannah, GA

Destination

Charlotte, NC

Pickup appointment

9:00 AM

Delivery / current ETA

11:00 AM / 5: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 Savannah, GA.

Automated tracking · FreightFlow event layer

Carrier communication

7:00 AM · 2h ago

PHONE · Driver reports clear roads and steady progress.

Human communication · 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

Exception created: Carrier non-response

6:00 AM · 3h ago

Carrier has not acknowledged the last two outreach attempts.

Operational event · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to en route pickup.

Operational event · FreightFlow event layer

Driver dispatched

3:00 PM · 18h ago

Tessa Morgan assigned to the load.

Operational event · FreightFlow event layer

BOL received

1:00 PM · 20h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

TMS record synchronized

9:00 AM · 48h 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.