Skip to content
English - United States
Submit a Ticket Customer portal Sign in
Contact us
  • There are no suggestions because the search field is empty.

HOS Violations

Understand how HOS limits, warnings, and violations work

Overview

To remain compliant with HOS regulations, drivers must stay within limits on:

  • Driving time

  • 30-minute breaks

  • Shift duration

  • Cycle hours

Exceeding any of these limits creates a violation. Maven surfaces warnings to drivers in the mobile app and violations in both the app and fleet portal.

HOS notifications

  • The app shows a warning notification 30 minutes before projected HOS violations.

  • If a violation occurs:

    • A red banner appears on the driver’s logs in the app.

    • A corresponding violation alert appears on the driver’s logs in the fleet portal.

  • In the portal, violations can be filtered using “Logs with HOS violations”.

Types of violations

Shift time violation

  • Occurs when the 14-hour shift limit is exceeded.

  • Common cause: not completing a full 10-hour off-duty reset before the shift timer reaches zero.

Drive time violation

  • Triggered when more than 11 hours of drive time occur within a shift.

Break time violation

  • Occurs when a driver does not take a 30-minute break before reaching 8 consecutive hours of drive time.

  • The 30-minute break can be taken in Off duty, Sleeper berth, or On duty (not driving) status, depending on configuration.

Cycle time violation

  • Occurs when the 70-hour limit over an 8-day period (or 80-hour in some Texas operations) is exceeded.

  • Common cause: not completing a full 34-hour reset.

Valid vs. invalid violations

Valid violations

  • Reflect actual HOS overages.

  • No system correction is needed.

  • Remain visible on logs for 8 days and must be explainable during inspections.

Log errors and corrections

  • Some violations are caused by incorrect logging or device issues (for example, missing data or incorrect duty statuses).

  • These can often be corrected through admin edits in the fleet portal if log data is wrong.

Invalid violations

  • Result from data issues rather than actual HOS overages and cannot be resolved through normal edits.

  • Require investigation and, when appropriate, removal by Maven Support using internal tools.