The BASIC Score That Plays Worst in Front of a Jury

Every juror has driven while tired. Nobody in that box has ever thought about brake adjustment intervals or steering play tolerance. That asymmetry is why the Hours-of-Service BASIC is different from every other score on a carrier's SAFER profile — and why I started treating it like a warning light instead of just another number to scroll past.

The seven BASICs each measure something specific. Unsafe Driving catches speeding and hard lane changes. Vehicle Maintenance catches brake and tire defects. Driver Fitness catches carriers running people who shouldn't have a CDL. All of those matter, and I check all of them before I tender a load. But if you hand a jury a carrier packet showing a 73rd-percentile HOS score alongside a crash at 2 AM, you've already lost the narrative before opening statements. Fatigue is the one thing every juror can imagine doing themselves. And that means it's the one the other side will lead with every time.

What the Score Actually Measures

The HOS Compliance BASIC is built from roadside inspection violations citing 49 CFR Part 395 — the federal hours-of-service rulebook. Part 395 is what caps property-carrying drivers at 11 hours of driving after 10 consecutive hours off duty, limits the on-duty window to 14 hours, and governs the 60/70-hour rolling cycle. It's also where ELD compliance lives since the mandate went into full effect.

When a driver gets pulled in for inspection and the officer finds an HOS violation — a falsified log, a missing record, a driver eight minutes into hour 12 of a 14-hour window — that report becomes a data point in the carrier's HOS Compliance BASIC. FMCSA rolls up violations from the past 24 months, weights them by severity, normalizes for how many inspections the carrier has accumulated, and publishes a percentile.

The alert threshold for property carriers is 65 percent. Above 65 means the carrier's HOS violation rate puts them in the worst 35 percent of carriers in their peer group. FMCSA uses this level as the trigger for direct intervention with the carrier.

Most brokers know this. What I've seen in practice is that brokers often treat the HOS BASIC the way they treat the Hazmat BASIC — they glance at it, note if it's flagged, and move on. The Hazmat BASIC is actually close to noise for brokers not moving regulated materials. The HOS BASIC isn't. It applies to every dry van, flatbed, and LTL load you've ever touched.

The Scenario That Keeps Me Honest

Here's the fact pattern that's been on my mind since Montgomery came down in May.

Carrier MC-1247893 / DOT-3581047 looks fine at first glance. Unsafe Driving at the 51st percentile. Vehicle Maintenance at 58 percent. Crash Indicator at 29 percent. Clean enough to book. But HOS Compliance sits at 72 percent, and in the carrier's 24-month inspection history, there are two citations under § 395.8 — false records of duty status. Not minor overages. Falsified logs.

You book them on a Tuesday. Memphis to Louisville, 5-hour run, 9 PM pickup, guaranteed morning delivery. The driver picks up, loads, gets on I-65. At 1:15 AM, the truck drifts left and hits a passenger car. Driver says he doesn't remember the moment of impact.

Plaintiff's attorney subpoenas your carrier file in discovery. She also pulls the SAFER history and reconstructs the HOS percentile as it stood the day you tendered — that data is timestamped and retained by FMCSA. Your file has an insurance cert, an MC number, a W-9, and a signed carrier agreement. There's no documentation of the BASIC scores at time of tender. No note explaining why you chose this carrier for a late-night run.

Now she has a 10-minute closing: "The broker knew this carrier had drivers who falsified logs to work more hours. The broker chose them anyway. The broker put them on the road at 9 PM for a five-hour run. My client's family is asking you to hold the broker responsible for that choice." The jury doesn't need a technical expert. They just need to understand that a person was tired and a broker had warning.

That case used to get tossed on FAAAA preemption grounds in the Seventh and Eleventh Circuits. Post-Montgomery v. Caribe Transport II, LLC — the unanimous Supreme Court opinion from two weeks ago — it doesn't get tossed anywhere. Justice Barrett's opinion is explicit: state-law negligent-selection claims against freight brokers survive. The case goes to a jury. Juries have been returning seven-figure verdicts on truck cases for years. The SAFER history goes into evidence.

Document the file or explain the gap to twelve strangers.

The Denominator Problem (Read This Before You Cancel Carriers)

Before you start culling carriers at the 66th percentile, it's worth understanding what actually drives the score up, because the inspection count matters.

A carrier running 45 trucks on heavy long-haul lanes accumulates far more inspections than an 8-truck regional carrier. More inspections mean more statistical chances to accumulate violations, but FMCSA's normalization accounts for that. What the raw numbers can still tell you is whether violations are concentrated or diffuse.

Pull the carrier's inspection detail through FMCSA L&I — not just the BASIC summary from SAFER. I do this on any carrier with an HOS percentile above 50 percent. You can see the actual violation codes, the dates, and how they spread across the fleet. A 70th-percentile score built on one bad driver who repeatedly got cited is a different problem than a 70th-percentile score where violations are spread across a dozen drivers over two years. Fleet-wide HOS problems suggest dispatch is pushing drivers past legal limits. Single-driver clusters might be an outlier who's since been terminated.

Both matter. They don't mean the same thing.

The ELD era also changed what the score tells you. Before the full mandate, paper logs were easy to falsify in ways that never got caught at inspection. A false log had to be egregiously wrong to get a roadside officer's attention. Now, the ELD pulls from the engine ECM — actual drive time, actual fuel stops, actual GPS track. Falsification under ELD is still possible, but it takes more work and leaves more artifacts. A carrier whose HOS score is elevated in the ELD era has drivers who are either genuinely running over hours or are actively working around the ELD. Neither is a good answer.

A § 395.8 violation today means more than it did in 2018.

What This Means at Load Tender

49 CFR § 395.3 is the core hours rule for property carriers — the 11-hour driving limit, the 14-hour window, the cycle caps. I can't see a driver's log when I tender a load. I'm not the carrier's compliance department. But the load characteristics I'm booking create conditions, and conditions matter for how likely a fatigued-driving event becomes.

If I'm booking a late-afternoon pickup with a guaranteed next-morning delivery and the transit time is eight hours, I've structured a load that incentivizes the driver to skip the mandatory break, hustle through the window, and deliver on time. Carriers with elevated HOS scores have shown a pattern of exactly that behavior. The combination of a challenging overnight run and an HOS-flagged carrier is the kind of fact pattern that plaintiff's attorneys look for in discovery.

This doesn't mean you never book an overnight load with a carrier who has a 67th-percentile HOS score. Sometimes you don't have another option. What it means is that you document the decision. You note the load characteristics. You call the carrier, confirm driver availability and where they are in their cycle, and write down what you were told. A two-sentence note in the carrier file is worth more than you think when you're sitting in a deposition three years later.

The goal isn't a perfect paper trail that covers every scenario. The goal is to show that you thought about it — that you exercised what the courts call reasonable care. A broker who evaluated the risk and made a documented judgment call is in a different position than a broker who did nothing and is now trying to explain why.

How I Document This

Every carrier file I build gets a SAFER snapshot — PDF, timestamped — at the time of initial vetting and refreshed on every load tender if it's been more than 30 days. The filename is the MC number and date: MC-1247893_SAFER_20260531.pdf. That file captures all seven BASICs as they stood at time of tender.

For any carrier with an HOS percentile above 50, I add a separate note to the file: the score, whether it's above or below the 65-percent threshold, and what I observed in the inspection detail (violation types, date clustering, how many distinct drivers). Takes five minutes.

For overnight loads or expedited runs with tight windows, the carrier note also includes load characteristics: pickup time, delivery commitment, estimated drive time. If I called the carrier to confirm driver availability and cycle status, I log it — date, time, who I spoke to, what they said. Three lines.

None of this is complicated. What it does is create a record showing a broker who considered the specific risks of the load they were booking, checked the HOS history of the carrier they were using, and made a defensible decision. That's the difference between "broker ignored a known risk" and "broker evaluated the risk and used reasonable judgment."

Post-Montgomery, the question isn't whether these cases get filed. They do. The question is whether your file tells the story you want told.

The HOS BASIC is the BASIC every juror walks in already understanding. Make sure your file has an answer for it before the load tendered, not after.

— Mason Lavallet

Founder, DOTScreener.com