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

at pickup

Juniper Pet Nutrition · Reno, NV → Phoenix, AZ

TMS source record

TMS · TMS-24019

Dispatcher / owner

Tessa Morgan

Carrier / driver

Lakeside Carrier Group · Avery Patel

Equipment

Dry van · (555) 016-3119

Origin

Reno, NV

Destination

Phoenix, AZ

Pickup appointment

10:00 AM

Delivery / current ETA

12:00 PM / 6:00 AM

Operational timeline

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

Tracking checkpoint

8:00 AM · 1h ago

Last location reported near Reno, NV.

Automated tracking · FreightFlow event layer

Carrier communication

6:00 AM · 3h ago

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

Human communication · FreightFlow event layer

Customer notification

5:00 AM · 4h ago

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

Human communication · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to at pickup.

Operational event · FreightFlow event layer

Exception created: Pickup appointment risk

5:00 PM · 16h ago

Projected arrival is inside the pickup appointment buffer.

Operational event · FreightFlow event layer

Driver dispatched

4:00 PM · 17h ago

Avery Patel assigned to the load.

Operational event · FreightFlow event layer

BOL received

12:00 PM · 21h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

TMS record synchronized

10:00 AM · 47h 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.