Load Tracking

Tracking helps your team monitor pickup, transit, delivery, ETA changes, and exceptions.

Tracking options

Your workspace may use one or more tracking methods, such as driver phone tracking, visibility providers, or manual updates. Use the method that matches the carrier, customer expectations, and shipment urgency.

Before starting tracking

• Confirm the load is dispatched or ready to dispatch.
• Confirm the carrier, driver, dispatcher, and contact details.
• Confirm pickup and delivery stops are correct.
• Confirm customer tracking expectations before sending updates.

Tracking workflow

1. Open the load.
2. Choose the tracking action.
3. Select the tracking method.
4. Confirm contact and notification details.
5. Send or start tracking.
6. Monitor location, ETA, stop events, and exceptions from the load details.
7. Update customers and internal teams when timing or service changes.

Tracking updates

Tracking may update location, ETA, pickup status, delivery status, arrival events, departure events, and exceptions. Users can still update status manually when the visible status does not match the real shipment state.

Tracking health

Waiting for first update means no provider location has arrived yet. Delayed or stale means the latest provider ping is older than the expected update interval. A last ETA is historical context, not always a fresh ETA; compare it with tracking history before updating customers.

Maps show routed lines when route geometry is available and fall back to stop-to-stop lines otherwise.

Tracking notes and history

Use tracking notes to preserve customer, carrier, or driver context that should stay with the load. Use tracking history to review what happened, when updates arrived, and whether a manual update is needed.

Customer tracking updates

If a customer expects tracking emails, confirm the customer tracking email, timing, and notification settings before starting tracking. Include exception notes when delays, missed appointments, or delivery changes affect the customer.

Provider notes

ARK Tracking can prompt you to switch a dispatch to a linked driver record when the same phone number already belongs to an app account for that carrier. If prompted, switch to the linked driver and start tracking.

Cancel, TONU, repower, or dispatch delete actions may attempt to stop provider tracking. Follow any warning if a manual stop is still needed.

project44 forwards visibility updates for mapped customers. Start tracking with an active tracking provider first; project44 is not selected from Start Tracking.

Troubleshooting

• If tracking does not start, confirm carrier and driver contact details.
• If updates stop, confirm driver participation and the selected tracking method.
• If tracking is waiting, delayed, or stale, review the latest ping and tracking history before changing status.
• If status looks wrong, compare the latest tracking event with manual status changes.
• If a customer needs tracking emails, confirm the customer tracking email and notification settings.
• If delivery is complete but billing is blocked, check POD and document status.