Hours of Service Rules: What Fleet Owners Have to Enforce Across Every Driver

When one of your drivers gets an HOS violation at a weigh station, it goes on your record — not just theirs. Fleet owners carry compliance liability for every driver running under their DOT number.

Most fleet owners understand this in theory. In practice, many operate with minimal HOS oversight — they trust their drivers to know the rules, review logs only when a problem surfaces, and treat ELD records as documentation rather than a management tool. That approach works until it doesn't: a driver pushes past their 14-hour window to make a delivery, a roadside inspector pulls the ELD logs, and suddenly the fleet owner has an out-of-service order, a CSA points hit, and a civil penalty — for a load that was dispatched without anyone checking the driver's available hours first.

HOS compliance in a multi-driver fleet is not a driver-side problem. It's a dispatch planning problem and an operational oversight problem. The rules are fixed and well-established. The fleet owner's job is to build a system that makes compliance the default outcome rather than something that depends on each driver's judgment under deadline pressure.

This is what the rules require, what the liability looks like, and what a real enforcement system looks like in practice.

The Core HOS Rules for Property-Carrying Drivers

The Hours of Service regulations for property-carrying commercial motor vehicle drivers haven't changed materially since the 2020 Final Rule — but enforcement intensity around them has increased significantly. FMCSA enforcement activity rose 28% between 2025 and 2026, and the 2026 CVSA Roadcheck specifically focused on ELD log integrity and tampering. Inspectors are trained on what compliant logs look like. Gaps, anomalies, and patterns that suggest falsification stand out.

Every driver in your fleet subject to HOS regulations must comply with all of the following:

11-Hour Driving Limit

A driver may drive a maximum of 11 hours after 10 consecutive hours off duty. The 11 hours is cumulative driving time — any driving after a 10-hour break starts the clock. Once the 11-hour limit is reached, the driver cannot drive again until they have taken another 10 consecutive hours off duty.

This is the limit most drivers know. It's also the limit they most commonly violate when loads run long and deadlines create pressure to keep moving.

14-Hour On-Duty Window

This is the rule that catches fleet owners off guard more than any other. Once a driver begins their day — the moment they go "on duty" — they have 14 consecutive hours within which to complete all driving. After 14 hours of on-duty time, they cannot drive regardless of how many driving hours they have remaining.

The 14-hour window cannot be extended by off-duty breaks during the day (except through the sleeper berth provision — see below). A driver who spends 3 hours at a shipper's dock on-duty before their load is ready has consumed 3 of their 14 available hours before moving a mile. When that driver then drives 9 hours, they've used 12 hours of their window — and they're still on duty dealing with paperwork and the next pickup. The window closes at 14 hours regardless.

This is the most common source of HOS violations in fleet operations, and it's almost always a dispatch planning failure: a load was scheduled without accounting for the driver's on-duty start time relative to the full on-duty window needed to complete the run.

30-Minute Break Requirement

After 8 cumulative hours of driving without a 30-minute break, a driver must take a 30-minute break before continuing. The break must be logged as off-duty or sleeper berth status — on-duty non-driving time does not satisfy the requirement. A driver who spends 30 minutes at a fuel stop but stays "on duty" has not taken the required break.

60/70-Hour Weekly Limit

A driver cannot drive after accumulating 60 on-duty hours over 7 consecutive days, or 70 on-duty hours over 8 consecutive days. Carriers operating trucks every day of the week typically use the 8-day/70-hour cycle. Carriers with consistent days off may use the 7-day/60-hour cycle.

These limits reset through the 34-hour restart — 34 consecutive hours off duty, after which the driver begins accumulating hours fresh. The restart is optional: drivers can continue working within their remaining hours without taking a restart, but the 34-hour restart is the mechanism that returns a driver to a full cycle when their hours are nearly exhausted.

Sleeper Berth Provision

Drivers using a sleeper berth may split the required 10-hour off-duty period into two segments under specific conditions. The permitted splits are:

• 8+2: At least 8 consecutive hours in the sleeper berth plus a separate period of at least 2 consecutive hours either off-duty or in the sleeper berth.
• 7+3: At least 7 consecutive hours in the sleeper berth plus a separate period of at least 3 consecutive hours either off-duty or in the sleeper berth.

When the sleeper berth provision is properly used, neither qualifying period counts against the 14-hour driving window — effectively pausing the window during the qualifying sleeper berth time. This is one of the most complex aspects of HOS compliance to monitor at the fleet level because the calculation depends on the sequencing and duration of multiple status entries per driver per trip.

Exceptions and Exemptions Fleet Owners Need to Know

Short-Haul Exception

Drivers who operate within a 150 air-mile radius of their normal reporting location, return to that location at the end of each shift, and do not exceed 11 hours of driving are exempt from both the ELD requirement and the obligation to maintain Records of Duty Status. They also qualify for an extended 14-hour window: on 2 days per 7-day period, short-haul drivers may extend their on-duty window to 16 hours.

For fleet owners with local or regional drivers, the short-haul exception can eliminate significant administrative overhead — no ELD logs to review for those drivers. But the exception is lost for any day a driver exceeds the 150 air-mile radius. If you dispatch a short-haul driver on an out-of-radius run even once, they need ELD coverage for that day.

Adverse Driving Conditions

When a driver encounters adverse driving conditions they couldn't have anticipated — a sudden blizzard, a highway closure due to an accident — they may extend their driving time by up to 2 hours beyond the 11-hour limit, and extend the 14-hour window by 2 hours. The adverse conditions must be documented in the ELD with an annotation. The extension does not apply to conditions the driver should have known about before starting (a forecasted storm, a construction closure that was announced).

Agricultural Operations

Certain agricultural commodity transport operations have seasonal exemptions during planting and harvest that suspend normal HOS rules within a 150 air-mile radius of the source. If any of your drivers haul agricultural freight during those periods, verify the specific exemption applies before treating those runs as exempt — the requirements are specific.

The Fleet Owner's Legal Liability

Fleet owners are motor carriers operating under a DOT number. Federal regulations require motor carriers not to allow or require drivers to operate in violation of HOS rules. The legal standard matters: FMCSA distinguishes between carriers who passively failed to prevent violations and carriers who knowingly and willfully allowed or required them.

Civil penalties per violation in 2026: Up to $19,246 per HOS violation against the motor carrier, up to $4,812 against the driver. Knowing falsification of records (log tampering, instructing drivers to falsify) carries up to $15,846 per entry.

What "knowingly and willfully" looks like in practice: A carrier who regularly dispatches loads that cannot physically be completed within legal hours, and whose drivers have a pattern of driving past their 11-hour limit on those loads, will have difficulty arguing that violations were the driver's individual decisions. Dispatch records, load timing, and ELD logs create a picture. FMCSA investigators read that picture.

CSA score impact: Every HOS violation from a roadside inspection is assigned to your carrier's Hours-of-Service Compliance BASIC. The intervention threshold sits at the 65th percentile. Under the 2026 SMS overhaul, out-of-service HOS violations carry double the severity weight (a multiplier of 2 versus 1 for non-OOS violations). One driver running past their 11-hour limit and receiving an OOS order hits your CSA score twice as hard as it would have before the overhaul.

CSA violations stay on your record for 24 months, with full weight in the first 6 months, reduced weight from months 7–12, and partial weight from months 13–24. A pattern of HOS violations across multiple drivers compounds — you're not carrying one violation, you're carrying a systematic compliance problem that insurers, brokers, and FMCSA investigators all see.

Building a Fleet-Level HOS Compliance System

HOS compliance in a multi-driver fleet requires a system, not just good intentions. The system has three components: visibility into every driver's current HOS status, dispatch practices that check hours before assigning loads, and a log review process that catches problems before they become violations.

Component 1: Real-Time HOS Visibility

Your fleet management platform should show, at a glance, every driver's current status across all five HOS dimensions: driving hours used today, remaining driving hours, time elapsed in 14-hour window, remaining 14-hour window, and cumulative weekly hours.

Most ELD-connected fleet management systems (Motive, Samsara, Geotab) display this dashboard in real time. A dispatcher who can see that Driver A has 4 hours of driving remaining and 5 hours left in their on-duty window, while Driver B has 9 hours of driving remaining and 11 hours left, can make informed load assignment decisions. A dispatcher flying blind on driver hours cannot.

If your fleet management system doesn't provide this view by default, it should — or you need a different system. Making dispatch decisions without HOS visibility is how avoidable violations happen.

Component 2: HOS-Aware Dispatch Planning

Load assignments should never go to a driver whose available hours can't support the load. This sounds obvious. In practice, the failure mode is subtle: a dispatcher checks hours at the time of booking, assigns the load for a pickup 3 hours later, and by the time the driver arrives at the shipper the hours picture has changed. Or a shipper runs long at the dock, consuming on-duty time the dispatch plan didn't account for.

The practical standards every dispatcher should follow:

Build in buffer, not just exact capacity. If a load requires 9 hours of driving and a driver has 9.5 hours remaining, that load creates a compliance problem the moment anything goes slightly wrong. A driver with 11+ hours available can absorb a dock delay, traffic, or an unexpected detour without crossing a limit. Dispatching to exact capacity leaves no margin.

Count on-duty time, not just driving time. Pre-trip inspection, fuel stops, shipper and receiver check-in, detention — all of it is on-duty time consuming the 14-hour window. A 9-hour driving load may require 11–12 hours of total on-duty time. Dispatch planning that accounts for driving only generates violations at the dock or receiver.

Know each driver's start time and running cycle. The 14-hour window started when the driver went on duty at the beginning of their day. If a driver went on duty at 6 AM and it's now noon, they have 8 hours left in their window regardless of how many driving hours remain. Dispatch decisions at noon need to account for where the window started.

Verify hours before a load assignment is final, not at the time of booking. For loads with same-day or next-day pickup, confirm the driver's hours picture is still accurate at the time of assignment.

Component 3: ELD Log Review Process

ELD data is only useful for fleet compliance if someone is actually reading it. Logs that sit unreviewed are evidence of violations the fleet owner didn't catch — which becomes a problem if FMCSA investigates a pattern.

The minimum log review process for a multi-driver fleet:

Daily review of the previous day's logs. Look for: drivers who came close to or exceeded their driving limit, drivers who came close to or exceeded their 14-hour window, unassigned driving time (vehicle movement with no driver logged in), 30-minute break violations, and sleeper berth splits that don't meet the configuration requirements.

Annotation review. When drivers annotate their logs (documenting adverse conditions, correcting location errors, explaining status changes), those annotations should be reviewed. Repeated similar annotations — multiple adverse condition claims on clear-weather days, multiple location corrections on the same routes — can indicate logging problems.

Weekly hours review. At the start of each week, know every driver's carry-over hours from the prior 7-day cycle. Drivers coming into Monday with limited available hours need dispatch schedules that reflect their capacity, not their typical full-week availability.

Unassigned driving time resolution. When the ELD records movement without an assigned driver, that record needs to be claimed by the correct driver or explained in the system. At inspection, unassigned driving records look like the carrier allowed off-the-books operation.

Driver Training: What Every Driver in Your Fleet Must Understand

No fleet compliance system works if drivers don't understand the rules well enough to apply them correctly. Driver training on HOS isn't a one-time onboarding event — it's an ongoing expectation with periodic reinforcement.

Every driver running under your DOT number should be able to answer these questions without hesitation:

• What are your current cumulative driving hours today?
• How much of your 14-hour window remains?
• Where do you stand on your 60/70-hour weekly cycle?
• What is the correct way to log a 30-minute break?
• Under what circumstances can you use the adverse driving conditions exception — and how do you document it?
• What is the correct procedure if your ELD malfunctions during a trip?

If a driver can't answer these questions confidently, they are an HOS violation waiting to happen. The violation will show up on your CSA record.

Training content should cover: the specific rules that apply to their operation (property carrier, sleeper berth if applicable, short-haul if applicable), how to use their ELD correctly for status changes and annotations, what to do during an ELD malfunction (revert to paper RODS, notify compliance within 24 hours, keep paper logs for up to 8 days), and what happens at a roadside inspection (what the officer will ask for, how to display logs, how to transfer data).

Common Fleet-Level HOS Violations and What Causes Them

11-hour driving violation on loads that ran long. Delivery windows slip, traffic adds time, a receiver appointment gets pushed back. A driver who was compliant when they started ends the day over their driving limit. Root cause: dispatch planning that didn't build buffer for delays. Fix: don't dispatch to exact hour capacity.

14-hour window violations from dock time. A driver arrives at a shipper, sits on-duty for 3 hours waiting to load, then drives the full load. The 14-hour window was already partially consumed by the dock time. Root cause: dispatch planning that counted only driving time in the window calculation. Fix: all on-duty time counts — plan accordingly.

30-minute break missed or logged incorrectly. A driver takes 30 minutes at a fuel stop but stays on-duty status the whole time. The break doesn't count. Root cause: drivers who don't understand that the break must be off-duty or sleeper berth status. Fix: explicit training on break logging.

Unassigned driving records. A driver forgets to log in, or logs out at a shipper and drives a short distance within the facility still logged out. The ELD records movement with no driver. Root cause: habit and facility movement. Fix: standing rule that drivers must be logged in before any vehicle movement, including facility moves.

Weekly cycle violations from poor hour tracking. A driver enters a heavy week without knowing they're close to the 60/70-hour limit. They push through and get caught at a Friday inspection. Root cause: nobody checked weekly hours going into the week. Fix: Monday morning hours review as a standing dispatch step.

Sleeper berth split errors. A driver attempts a split that doesn't meet the minimum segment requirements (both segments must meet minimums, and the combined off-duty time must total at least 10 hours). Non-qualifying splits generate violations. Root cause: complexity of the rule and lack of training on specific configurations. Fix: if your fleet uses the sleeper berth provision regularly, invest specific training on correct configurations.

The Relationship Between Dispatch and Compliance

HOS compliance is ultimately a dispatch function as much as a driver function. The driver controls how they log status and how they respond in the moment. The carrier controls what loads are assigned to which drivers with how much available time.

Most HOS violations in fleet operations trace back to dispatch planning failures — not drivers who set out to violate the rules. A driver who accepts a load they can't legally complete isn't usually trying to falsify records. They're trying to get the job done under real deadline pressure from a customer or broker who doesn't care about their hours situation. Fleet owners who remove that pressure — who have a standing policy that drivers don't accept loads they can't legally run, and whose dispatch process confirms hours before assignments are finalized — have materially lower HOS violation rates than fleets who leave those decisions to drivers under pressure.

If you're working with a dispatch partner, HOS visibility should be part of the service. A dispatcher who books loads without checking a driver's available hours isn't dispatching — they're load hunting that creates compliance problems for the carrier. At Atom Dispatch, we build driver availability into every load assignment. If a driver doesn't have the hours to complete a run legally, the load goes to a driver who does, or the timeline gets adjusted. That's the difference between dispatch that protects your operation and dispatch that creates liability.

Bottom Line

Every HOS violation on your fleet's record costs you — in CSA points, in insurance premiums, in broker access, and in potential civil penalties that can reach $19,000 per violation against the carrier. The rules themselves aren't complicated. The enforcement challenge is building a system that applies them consistently across every driver, every load, every day.

That system requires: real-time HOS visibility for every dispatcher making load assignments, dispatch practices that check available hours before finalizing assignments and build in margin for delays, a log review process that catches anomalies before they become patterns, and driver training that ensures everyone running under your DOT number knows the rules and how to apply them in real situations.

Fleet owners who treat HOS compliance as a driver-side responsibility and check in only when problems surface are running an exposure that compounds every quarter. The ones who build it into their dispatch and operational process are running cleaner CSA scores, paying less for insurance, and not finding out about compliance problems at a weigh station.

Set up the visibility. Fix the dispatch process. Review the logs. Train the drivers. That's the system.