# AI Tracking: know what changed on a load

The AI Tracking workflow example in RunaboutX brings load status and meaningful changes into the operations discussion. RunaboutX is available to fleets; use your own status sources in a demo to confirm the supported data path. Its purpose is to help a person see which active loads need attention rather than repeatedly checking every load by hand.

## From status to action

A status update should identify the load, last known event, source, and time. If an ETA moves beyond the appointment, the system should surface the exception and present a reviewable next step. The operator remains responsible for customer communication and consequential changes.

For example, an arrival update is useful only if the team can compare it with the scheduled window and know whether the next stop or customer needs an update. The [track-and-trace exceptions guide](/resources/learn/track-and-trace-exceptions/) lays out triage rules and the limits of stale location data.

## Evaluate the actual data path

Ask which status sources are supported for your fleet, how delayed or conflicting updates are marked, and what happens when connectivity disappears. RunaboutX has not publicly confirmed named telematics integrations; discuss the relevant connection in a demo. See [integrations](/integrations/) and [exception management](/features/exception-management/). [Book a demo](/#contact).

---

Canonical: https://www.runaboutx.com/features/ai-tracking/
Last reviewed: 2026-10-14