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

at deliveryat risk · 79

Northline Industrial · Harrisburg, PA → Newark, NJ

TMS source record

TMS · TMS-24021

Dispatcher / owner

Jordan Brooks

Carrier / driver

Ironwood Transport · Priya Shah

Equipment

Dry van · (555) 016-3121

Origin

Harrisburg, PA

Destination

Newark, NJ

Pickup appointment

12:00 AM

Delivery / current ETA

2:00 PM / 8:00 AM

Operational timeline

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

Customer notification

8:00 AM · 1h ago

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

Human communication · FreightFlow event layer

Tracking checkpoint

5:00 AM · 4h ago

Last location reported near Harrisburg, PA.

Automated tracking · FreightFlow event layer

Carrier communication

4:00 AM · 5h ago

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

Human communication · FreightFlow event layer

Shipment status updated

9:00 PM · 12h ago

Moved to at delivery.

Operational event · FreightFlow event layer

Exception created: Customer update overdue

9:00 PM · 12h ago

Customer-facing update missed its service-level deadline.

Operational event · FreightFlow event layer

Exception created: Delivery appointment risk

7:00 PM · 14h ago

Current ETA is trending past the delivery appointment.

Operational event · FreightFlow event layer

BOL received

10:00 AM · 23h ago

BOL attached to the shipment record.

Document event · FreightFlow event layer

Driver dispatched

6:00 AM · 27h ago

Priya Shah assigned to the load.

Operational event · FreightFlow event layer

TMS record synchronized

12:00 AM · 57h 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.