ARK Tracking

ARK Tracking lets your team request and monitor driver tracking from inside ARK TMS.

Use this page for the broker and dispatcher workflow. Send drivers ARK Tracking for Drivers when they need app setup instructions.

Setup checklist

1. Open Settings, then Integrations.
2. Select ARK Tracking.
3. Confirm tracking access and billing requirements.
4. Confirm the team members who can start tracking.
5. Save settings.

Test workflow

1. Open a dispatched load.
2. Start ARK Tracking.
3. Confirm driver contact details.
4. Send the tracking request.
5. Send the driver ARK Tracking for Drivers.
6. Confirm the driver receives and activates the request.
7. Monitor activation, location, ETA, and events from the load.

Driver request flow

When ARK Tracking starts, the driver experience depends on whether the driver already has an ARK Tracking app account.

Drivers who already have app access receive an app notification for the tracking request. Drivers who are not set up yet receive a one-time text with the ARK Tracking app download link:

https://arktracking.com/download

The text tells the driver that the dispatcher approved load tracking and driver app access for the company. The driver installs or opens ARK Tracking, signs in with the same phone number used on the load, opens the active load, allows location access, and starts tracking.

The driver does not manually respond to each location update. After the driver starts tracking, the app sends location updates in the background while the load is active.

Normal usage

Start tracking after dispatch when driver contact details are known. Review tracking status directly from the load and use manual load updates when operational status changes before a tracking event arrives.

ARK Tracking shows the load as pending until the driver starts tracking in the app. If the driver never activates the request, restart tracking from the load after the pending request expires.

If ARK Tracking shows a linked-driver prompt, switch the dispatch to the linked driver record and start tracking. One app account can only be linked to one driver record.

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

Location and ETA updates

ARK Tracking requests location updates from the driver app about every 15 minutes while the active session is running.

ETA is calculated from the driver's current location, remaining stops, and default truck routing details. ETA does not recalculate on every location update. It recalculates when due, and it recalculates after a departure event so the next leg can refresh.

ETA timing becomes more frequent as the driver gets closer to the final stop:

• More than 6 hours away: about every 2 hours.
• 2 to 6 hours away: about every hour.
• 1 to 2 hours away: about every 30 minutes.
• Less than 1 hour away: about every 15 minutes.

ETA calculations run when the driver is en route. If the driver is dwelling at a stop after arrival and before departure, ETA updates can pause until the driver departs.

Use the latest location, stop history, and ETA timestamp together before updating a customer. A last ETA can be useful context, but it is not always a fresh ETA.

Billing sessions

ARK Tracking is billed per billable tracking session, not by mile, hour, or individual location update.

A session becomes billable when the driver starts tracking and the session is later completed. A cancelled session is billable only after the driver has been actively tracking beyond the 30-minute grace window. Requests that expire or are cancelled before the driver starts tracking are not billable.

Review current-month ARK Tracking usage from Subscription Billing when the module is enabled for your organization.

Notifications

Tracking notifications can be configured for arrival, departure, interval updates, and related load events depending on your workspace setup.

Troubleshooting

• Driver did not activate tracking: confirm the driver received the request and resend if needed.
• Driver phone is incorrect or carrier changed drivers: stop ARK Tracking, update the dispatch driver or phone number, then start ARK Tracking again.
• Linked driver conflict: switch to the linked driver when prompted, or clean up the duplicate driver in People.
• App update required: ask the driver to install the latest ARK Tracking app version.
• Tracking request expired before activation: restart tracking from the load.
• No recent location: confirm the driver’s phone is on, has service, and allows location access.
• ETA did not refresh: confirm the driver has started tracking, the load still has remaining stops, and the driver is not dwelling at a stop.
• Customer notification email is missing or incorrect: update the customer contact before sending notifications.