Who’s current and who’s behind. Overdue = past its due date (Fixable 5 days, Not fixable 10). Fixed and Avg days to fix come from violations that dropped off the official report — proof the correction actually landed.

Answers both at once: the last 10-hour reset and what’s left (drive / 14-hr window / weekly), and whether the 16-hour Big Day was used in the past 168 hours — with the date it’s available again.

Measures every duty tour to the hundredth of an hour (13.78h, not “about 14”), grouped by Route ID from dispatch. Routes averaging over 13 hours are manufacturing 14-hour violations — this is where you fix the schedule instead of coaching the driver.

One row per incident, not per re-trigger. Consecutive days of the same driver + type collapse into a single violation (a 70-hour that re-fires all trip counts once). Flags multi-day incidents and likely stuck-in-drive.

Days with a recorded sensor/ELD failure, grouped by vehicle and site — find the trucks that keep breaking. Heavy pull; runs in batches.

Every log edit in the last 7 days across all fleets, split driver vs. manager/office. Heavy pull — runs in batches. After it loads, ask the Assistant “who made the manager edits at [site]?” for the per-person breakdown.

Every edit for that site and period — who edited, the line, when, and whether it was re-certified. Longer periods pull in windows, so 6 months takes a bit.

Private analysis engine — peels every layer, rebuilds stuck-in-drive logs. Hidden from site users. Set the code once with wrangler secret put ADMIN_PASSCODE.

Upload the official HOS Violations Detail Report (Omnitracs → Reports → HOS Violations) on the Upload tab. It is the only source that reflects corrections: new violations are added, and any the report no longer lists (corrected) are marked Fell Off to remove. Driver-log PDFs and 1-pagers you attached before are restored automatically from backup on each upload — you only upload logs for the few that have none. The Omnitracs API pull is intentionally off here because it over-reports corrected violations.

Re-audits driver logs already in storage — useful after an engine update. It never overwrites a ruling, action, or comment you’ve entered. Every violation is now ruled automatically on arrival, so this is only for refreshing older rows.

Re-renders the stored 1-pager PDFs with the current engine. Re-enrich only updates the tracker fields — the PDF is a file saved when the log was first uploaded, so after a memo change it stays old until you rebuild. Rebuilds every open log's 1-pager and refreshes engine fields (fixable / root cause / action) on rows you haven't ruled. Your rulings, comments, and uploads are never touched. (Rendering is rate-limited; if some are deferred, run it again.)