The Hours of Service BASIC Isn't About Fatigue. It's About How Your Carrier Treats the Rules.

A carrier — call them Ridgewood Transport, MC-1389247, DOT-3782193 — walked into my approved list about three years into building DOTScreener. At that point I was still treating the HOS score the way most of the industry does: as a fatigue indicator. High percentile equals tired drivers equals crash risk. I ran the rest of the numbers. Their Crash Indicator was at the 54th percentile, nothing alarming. Unsafe Driving at 41st. Clean insurance. Four years of authority, eight power units, sixteen drivers. I approved them.

Six months later, one of their drivers hit a minivan on a rural two-lane at 4 AM. Post-crash investigation turned up falsified ELD logs going back at least fourteen months. Three drivers involved, not one. The carrier claimed the drivers acted independently. The logs suggested otherwise. The lawsuit that followed settled for $1.4M — bodily injury to two passengers, one of whom was hospitalized for six weeks and hasn't worked since.

The HOS BASIC score on Ridgewood wasn't just telling me those drivers might be fatigued. It was telling me how that company treated documentation. I reframed my entire approach to HOS percentiles after that load, and I haven't treated the BASIC the same way since.

What the HOS Compliance BASIC Actually Measures

The HOS Compliance BASIC is one of seven FMCSA Safety Measurement System categories. It's built from roadside inspection violations under 49 CFR Part 395 — the Hours of Service regulations — weighted by violation severity and the carrier's inspection exposure over a rolling 24-month window.

The specific violations that move this BASIC most include:

• § 395.8: Falsification of or failure to maintain records of duty status — the highest-severity violation in this category
• § 395.3: Operating beyond the 11-hour driving limit or the 14-hour on-duty window
• § 395.13: Operating while declared out of service for HOS violations
• § 395.8(e): Operating with an ELD showing pattern evidence of manipulation or tampering
• Missing logs, invalid ELD certifications, carriers directing drivers to enter false information

Look at that list carefully. Several of the highest-severity violations under this BASIC aren't "the driver was tired and kept driving." They're "the driver — or their dispatcher — falsified a federal compliance document." That's a very different problem, and treating them the same way produces the wrong analysis.

The Fatigue Framing Is Too Narrow

There's genuine research showing that fatigued driving increases crash risk. The HOS rules exist because of that research. So the intuition that a high HOS BASIC means tired drivers means crashes is not wrong — it's just incomplete.

Here's the problem with stopping there: if you're reading a 78th percentile HOS score as "these drivers might be pushed," you're missing the organizational story. For a carrier to land in the top quartile of HOS compliance violations, there's a pattern. A single roadside inspection that catches one driver over hours moves the percentile, but it doesn't spike it. What generates a sustained high percentile is repeated violations across multiple drivers, multiple inspections, over an extended time period.

That's not a rogue driver. That's a dispatch culture.

A carrier with a system-wide HOS Compliance problem is a carrier where management has either allowed, actively instructed, or at minimum failed to stop a pattern of falsification. That's not a safety culture problem limited to fatigue. That's a compliance culture problem that touches everything.

A Carrier Who Falsifies Logs Is Telling You How They Handle All Paperwork

Think about what 49 CFR Part 395 compliance requires in practice. ELD logs. Driver sign-offs. Line-of-duty documentation. Pre-trip and post-trip inspection records that are supposed to sync with log entries. The whole system is designed to be a paper trail of how a driver's day actually went. A carrier who falsifies that trail isn't just lying about hours — they're demonstrating a comfort level with falsifying federal compliance records.

If they'll do it with HOS logs, the question you should be asking is: what else are they comfortable falsifying?

Driver qualification files under 49 CFR § 391.23 require carriers to document employment history investigations, MVR pulls, road test certifications, annual inquiry letters to prior employers. Those records are often paper-based in smaller operations. If a dispatcher is comfortable telling a driver to adjust their ELD log, I'd want to know how rigorous that same company is being with their driver qual files.

Annual vehicle inspection records under 49 CFR § 396.17 require a signed inspection by a qualified inspector within the previous 12 months. Pre- and post-trip inspection reports under § 396.13 require the driver to report defects and have the carrier certify corrective action. In a falsification culture, those records are the next to go. Not because mechanics stop doing the work — sometimes they do — but because the culture of "just sign it and move on" extends to all the compliance paperwork.

Discovery in trucking fatality cases routinely surfaces carriers where HOS falsification and maintenance record gaps appear in the same file. The correlation isn't coincidental. It reflects a management posture toward federal compliance requirements generally.

Part 395 at Load-Tender Time

Section 395.3 sets the driving limits: 11 hours of driving in a 14-hour on-duty window, 60 or 70 hours in 7 or 8 consecutive days. Section 395.8 requires records of duty status for every day a driver operates a commercial vehicle. These aren't aspirational guidelines — violations are documented at roadside by federal and state inspectors and fed directly into the SMS database that produces the BASIC.

At load-tender time, what a high HOS Compliance percentile tells you is concrete: this carrier has been caught — at least more than once, and probably many more times — with documentation that doesn't reflect their drivers' actual operational hours. The inspectors flagged it. It went into the system. The BASIC moved.

That doesn't automatically mean you don't run the load. Some carriers have specific driving populations or lane profiles that generate more HOS inspection exposure. Some are working through a period of operational growth that created compliance gaps they've since corrected. There are legitimate reasons a carrier might have a high HOS percentile and still be a reasonable choice for the right load.

But you don't get to not know about it. And you don't get to pretend that a Satisfactory safety rating washes it away. A Satisfactory rating is a compliance review from a specific point in time. The BASIC is a rolling 24-month window of roadside data. A carrier can hold both simultaneously — and many do. They're measuring different things, on different timescales, using different methodologies.

Post-Montgomery, using the headline rating as a substitute for reading the BASIC detail is exactly the kind of shortcut that comes up in deposition.

What a High HOS Percentile Should Change in Your Process

A carrier in the 65th percentile or above on HOS Compliance warrants additional scrutiny — not just of their log culture, but of their documentation practices generally.

Ask for their drug and alcohol testing program documentation. A carrier who cuts corners on HOS is statistically more likely to have an informal drug testing operation. An informal drug testing program is an independent liability signal, and plaintiff's counsel knows it.

Add explicit HOS compliance language to your carrier agreement. "Carrier represents and warrants compliance with all applicable FMCSR regulations" is standard boilerplate that doesn't cost you much in negotiation but gives you something in discovery. Go further: "Carrier will maintain complete and accurate records of duty status for all drivers operating under this agreement and will provide those records to Broker upon request within 24 hours of demand." That clause puts the carrier on notice that you take this seriously, and it gives you a contractual hook if they don't.

Look at their power units to drivers ratio. A carrier running sixteen drivers on eight power units and generating HOS violations is running a dispatch function that's optimized for miles at the expense of compliance. The ratio alone doesn't tell you that — but combined with the BASIC score, it tells you something about the operating model.

And document that you saw the HOS percentile. Not as a CYA formality — as a genuine record of your analysis. The paper trail that survives deposition is the one that shows you read the data, evaluated it, and made a conscious decision with it in front of you, not the one that shows you pulled an MC number and checked a "vetted" box.

How I Document This

When I approve a carrier with an HOS Compliance BASIC at or above the 65th percentile, the carrier file gets specific treatment:

The DOTScreener pull that includes the HOS score gets a written notation — not just a screenshot — recording what I saw, when I saw it, and what I decided to do with it. If I'm approving despite the flag, I write down why.

The carrier agreement includes the explicit HOS records warranty and the 24-hour production clause. I get a signed copy through an identity-verified onboarding flow so the signature is tied to someone who can actually bind the company to those terms.

I set a monitoring flag on the carrier in DOTScreener. Any change in their authority status, insurance filing, or BASIC scores before the next load gets flagged. For carriers with elevated HOS scores, I want to see the next update before I tender, not after.

The goal isn't avoiding every carrier with any BASIC flag — you'd run out of approved carriers fast. The goal is demonstrating that you read the signal, considered it, imposed additional conditions where warranted, and continued to monitor the situation. That's what reasonable carrier selection looks like in a post-Montgomery environment.

The HOS BASIC isn't just predicting whether your driver will fall asleep on I-65. It's predicting whether the carrier you selected has a management culture that treats federal compliance as a real obligation or a bureaucratic inconvenience to be managed around. That distinction matters a lot more than it did before May 14, 2026, and I'd argue it matters more than most brokers are treating it.

Know what you're looking at. Document what you decided. Make sure the carrier agreement means something verifiable. That's the job.

— Mason Lavallet

Founder, DOTScreener.com