What happens if a driver doesn't complete required training?

Overdue training is a common reality for any fleet, and the platform makes it visible rather than invisible. When a required course passes its deadline, the driver moves to an overdue status on the dashboard, and reminder emails continue on a configurable cadence. Admins can escalate directly — send a manager notification, place a training hold on the driver's record, or move the driver to a restricted role until they're current.

For regulated training with legal implications (ELDT, hazmat), the audit trail also reflects that the training was required but not completed, which protects the employer in any subsequent review. The documentation of "training was assigned and the driver did not complete by deadline" is structurally different from "no training was assigned" — the first reflects an employer compliance posture that included assignment, even if the individual driver didn't follow through; the second reflects an employer compliance gap. Auditors and insurers treat the two differently, and the audit log captures the distinction.

Fleets with persistent overdue patterns often have structural causes that reminder cadence alone won't fix. A driver consistently overdue may have unrealistic deadline expectations relative to their actual workload; a team consistently overdue may have a manager who isn't reinforcing training as a priority; a region consistently overdue may have logistics issues that prevent drivers from accessing the platform reliably. Diagnostic dashboards identify these patterns at the cohort level rather than treating each overdue driver as an individual case. The structural fix typically produces lasting improvement; individual escalation produces only short-term compliance with the same pattern recurring at the next cycle.