Driver hours of service

This module logs driver hours against FMCSA 49 CFR 395 — the daily limits (11-hour driving, 14-hour on-duty window) and the rolling weekly totals (60 hours / 7 days, 70 hours / 8 days).

Record a driver day

1. In the Record a driver day form, pick the site and choose the driver from your workforce roster.
2. Set the log date and enter the driving hours and on-duty hours for that day.
3. Leave 30-minute break taken ticked if the driver took the required break (it defaults to checked); untick it if they drove past 8 hours without one. Under 395.3(a)(3)(ii), a day with more than 8 hours of driving and no 30-minute break is a violation.
4. Tick Day follows a 34-hour restart when this day comes after a 34-consecutive-hour off-duty break (395.3(c)) — it resets the rolling 60/70 clock (see below).
5. Choose Record day. The day appears in the log with Flags — a red >11h drive or >14h window badge when a daily limit is exceeded, a no 30-min break badge when the break rule is broken, a 34h restart marker on a restart day, or ok when the day is clean.

Check a weekly summary

1. Type a driver's name into Weekly summary for driver and choose Check.
2. The banner shows the driver's 7-day and 8-day on-duty totals through the latest logged date, and turns red with OVER 60 / OVER 70 when a rolling weekly limit (395.3(b)) is exceeded.
3. A 34-hour restart resets that rolling clock: the weekly summary counts only from the most recent restart forward, excluding days before it. Log restart days so the 60/70 totals reflect the reset.

Read the log

• Filter the log by Site, then scan the flags column — days with a daily violation are highlighted red so problem shifts stand out.
• Export HOS log CSV downloads the 49 CFR 395 record-of-duty-status (RODS) day log — api/hos/log.csv.

What happens automatically

• Dashboard rollup: the dashboard shows an HOS violations (14 days) count, plus a Drivers over weekly HOS limit tile (warn), so both recent daily violations and drivers over their rolling weekly total are visible numbers, not just red rows in a table.
• Escalation: a sweep raises an overdue notification to the Safety Team queue, with a link back to this page. It covers both:
  • every daily violation in the last 14 days — naming the driver, the date, and which limit was exceeded (11-hour driving, 14-hour window, the 30-minute break rule, or a combination); and
  • every driver over a rolling weekly limit (395.3(b), 60h/7d or 70h/8d) within the 14-day window, anchored to the latest log date — noting that a 34-hour restart resets the clock before the driver may continue. Re-running the sweep doesn't pile up duplicate reminders.
• Violations older than 14 days stay in the log for history but stop escalating.
• To work the queue, open My work and type Safety Team into Showing work for.

Tip: enter every driving day, even light ones — the rolling 60/70-hour totals are only accurate when the week is complete.

Related

• Driver qualification files (DQF) — Same driver-compliance file for each CDL driver
• Fleet & DVIR — Daily DVIR vehicle inspections in the same fleet program
• Carrier profile (FMCSA) — Your FMCSA carrier record and BASIC measures