HOS clocks and duty status
This module shows how much driving, on-duty and break time a driver has left in the current duty period and cycle, keeps an electronic log of duty status, and supports the day-to-day compliance work: claiming unidentified driving, acknowledging infringements and exporting data for a roadside inspection.
Who it's for
The driver sees their own clocks and duty status in the mobile app and records status changes there. The compliance officer monitors clocks and infringements across the fleet, acknowledges infringements and produces exports for inspections. The safety manager receives notifications about predicted violations alongside the compliance officer.
Key concepts
- HOS (Hours of Service) — the driving, duty-window, break and cycle limits that the live clocks track.
- RODS (Record of Duty Status) — the electronic duty-status log: a series of entries with a status, a start/end time and a full edit history.
- ELD (Electronic Logging Device) — the logging device that auto-switches to a driving status past a speed threshold; its malfunctions start a repair countdown.
- Personal conveyance / yard moves — special categories: authorized personal use of the vehicle (doesn't count as driving) and movement within a yard (doesn't count as driving; counts as on-duty, not driving).
Live HOS clocks
For a selected driver you see the full set of clocks that follow from the effective compliance profile (see Compliance overview) — driving time, duty window, break and cycle — each with the time remaining before the limit and, while the driver is driving, the projected moment of breach. The view refreshes on its own, so it stays current without a manual reload. The exact limit values differ by jurisdiction — see that country's page in this section.
Duty-status log
Every log entry keeps its original, immutable record alongside the current effective values and the full edit history. You can add an annotation (a note that doesn't change the record) or an edit (a correction to the status or times, with a reason) — entries the logging device generates automatically for key events stay non-editable; they can only be annotated.
Unidentified driving and infringements
Driving recorded with no driver logged in lands in the unidentified-driving queue — a driver (or the compliance officer) claims such a segment, assigning it to themselves or another driver, with a reason. Detected hours-of-service infringements land on a list that the compliance officer reviews and acknowledges with a note; in jurisdictions with supply-chain liability, an infringement is additionally flagged as relevant to the whole chain, not just the driver.
Malfunctions and the eRODS export
A malfunction or diagnostic event on the logging device starts a repair-or-replace countdown; malfunctions still unresolved after that window show up on a list for follow-up. For a roadside inspection or an audit, you generate an eRODS export for a chosen driver and date range — a file in the format ready to hand to an inspector.
In the background
Every active driver's HOS clocks are recalculated on a recurring schedule, and a predicted violation raises a notification to the compliance officer, the safety manager and the driver themselves. A separate daily job checks whether unresolved device malfunctions have exceeded their repair window, and another flags records that have reached the end of their required retention period.