ARK Tracking

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

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.

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.

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.

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.
• Customer notification email is missing or incorrect: update the customer contact before sending notifications.