# Exception management for active loads

RunaboutX is building an exception manager for active loads: detect a meaningful change, show who and what it affects, and let an operator review a recovery action. Its public homepage example is a simulation, not proof of live automated recovery.

## A late-arrival example

If a truck is delayed, the operations team needs the affected load, next appointment, latest credible ETA, driver context, and customer communication status. A proposed action might update the appointment and notify the driver, but a person should check the impact and approve the change first. The event and decision should remain attached to the load.

## Define ownership before automation

For each exception type, set an owner, escalation threshold, and closure criterion. A stale tracking ping is not the same as a confirmed missed appointment. The [track-and-trace exceptions guide](/resources/learn/track-and-trace-exceptions/) offers a triage framework, while [human-in-the-loop AI](/resources/learn/human-in-the-loop-ai/) covers approval controls.

Ask in a [demo](/#contact) which signals and actions are currently available and how your team can override a recommendation. See the broader [trucking operations software](/trucking-operations-software/) workflow.

---

Canonical: https://www.runaboutx.com/features/exception-management/
Last reviewed: 2026-09-26