The BASIC Score You're Looking at Is Already 60 Days Old

A broker I know pulled SAFER on a dry-van carrier in mid-June last year. Vehicle Maintenance BASIC: 44th percentile. Unsafe Driving: 31st. Nothing alerting. He tendered a load, a 48,000-lb shipment of commercial HVAC equipment from Memphis to Columbus. Twelve days later, that carrier's trailer had a brake-induced jackknife on I-65 outside of Nashville. Took out a guardrail and caught a pickup that had slowed for construction.

Discovery happened fast. Plaintiff's counsel subpoenaed the carrier's inspection history. Turns out CVSA's Roadcheck Blitz had run May 19-23 — three weeks before my colleague's pull — and this carrier had gotten hit hard: seven violations across two roadside inspections, including brake-out-of-service orders on both drive axles of the tractor. At the time of tender, none of that had shown up in BASIC yet.

That's the problem I want to talk about.

How BASIC data actually flows

Everyone knows BASIC scores are built on a 24-month rolling window of inspection data. What most brokers don't think hard enough about is the time between when an inspection happens and when it shows up in BASIC percentiles.

The FMCSA SMS methodology documentation is clear on this: data is submitted by state agencies, processed monthly, and folded into the scoring algorithm on a batch basis. Depending on when in the monthly cycle a state submits its data — and whether any inspections require administrative review before entry — the lag between an inspection occurring and that inspection appearing in BASIC can run 30 to 60 days. For inspections that involve contested OOS orders or appeal proceedings, it can stretch longer.

So the BASIC score you're looking at today reflects inspections through roughly April or early May. Anything that happened during CVSA Roadcheck in late May, or a targeted enforcement sweep in early June? Not there. You're looking at a rearview mirror with a two-month delay, and most brokers treat it like a live feed.

This isn't a system flaw that FMCSA is going to fix. It's a structural feature of how state inspection data flows into federal databases. It's been this way for years. The issue is whether you account for it or ignore it.

The timing traps

CVSA Operation: Roadcheck happens every May — three days, tens of thousands of inspections concentrated in a short window. Any carrier that got hammered during Blitz Week won't have that data in their BASIC until July or August. If you're vetting carriers in June and July, you are systematically working with pre-Blitz data.

It's not just Roadcheck. CVSA runs targeted enforcement programs throughout the year — brake safety, driver fitness, HOS compliance. FMCSA runs its own compliance reviews and targeted investigations, which generate inspection activity. When a carrier gets hit with a concentrated enforcement event, they can accumulate violations fast. A carrier sitting at the 55th percentile on Vehicle Maintenance on May 18th might be at the 78th percentile by August 1st once those inspections get scored.

The Unsafe Driving BASIC has a shorter lag in practice because it incorporates police-reported crashes, which flow through different channels and process faster than roadside inspection data. But the Vehicle Maintenance BASIC, Driver Fitness BASIC, and Controlled Substances/Alcohol BASIC are heavily inspection-driven. The lag hits those the hardest — and Vehicle Maintenance is the one most directly connected to the brake failures, tire blowouts, and lighting violations that cause catastrophic crashes.

Inspection count changes everything here

A carrier with 40 inspections in the last 24 months and a 44th percentile Vehicle Maintenance BASIC is a different risk profile than a carrier with 8 inspections in the same window at the same percentile. The carrier with 40 inspections has a real sample. The carrier with 8 inspections — any one recent inspection with three or four violations can swing that number significantly.

This matters for the lag problem because when a carrier has a thin inspection history, recent inspections carry more weight in the score. If the most recent inspection was good, the BASIC looks clean. If they just got destroyed in a Blitz inspection and that data hasn't processed yet, the score you're looking at is built almost entirely on older inspections — while the carrier's actual current condition is missing.

The inspection count is on SAFER's company snapshot. It's right there. I look at it every time I pull a new carrier. A carrier with fewer than 10 inspections in 24 months doesn't have enough data for me to trust the BASIC percentile without supplementing it.

The L&I detail is faster than BASIC

Here's a practical workaround that most brokers don't use: the individual inspection records under FMCSA's Licensing and Insurance database, accessible through the SAFER company snapshot. The violation-level inspection history — date, location, violation codes, OOS flags — updates faster than the BASIC percentile, because it doesn't have to wait for the full monthly scoring batch. It still lags, but usually by less.

When I pull a carrier and their BASIC looks acceptable, I click into the inspection history and look at everything from the last 90 days. I'm looking at the violation codes directly. 49 CFR § 393.45 is brake hoses and tubing. § 393.52 is brake performance standards. § 393.75 is tires. These show up as specific violation codes in the inspection record — sometimes as OOS items, sometimes as non-OOS — before they've been rolled up into a BASIC percentile.

If I see a cluster of recent inspections with brake violations, especially OOS-level items, I treat that as an alert regardless of what the headline BASIC percentile says. The percentile is downstream. The inspection record is closer to the source.

This isn't a perfect solution. The inspection detail goes through the same pipeline, just ahead of the scoring step. But there's usually a two-to-three week advantage versus waiting for the percentile to update. In a world where you're trying to catch a recent problem before you tender, that window matters.

The phone call

I keep coming back to this because it keeps working. Before I tender a load on a carrier I haven't used before — especially one with thin BASIC data or a recent inspection gap in the SAFER history — I call.

The question is simple: have you had any roadside inspections in the last 60 days? Any violations? Any OOS orders?

A carrier who's had a clean stretch will usually tell you exactly what they had and where. "Yeah, we got pulled in Elizabethtown three weeks ago — clean." A carrier who got hammered will either stumble, get vague, or overexplain. Either way, you've learned something you wouldn't have learned from BASIC alone.

49 CFR § 390.15 requires carriers to maintain accident registers and make them available to FMCSA on request. There's no corresponding obligation to disclose recent inspection history to a broker voluntarily. But asking is free. Documenting the answer is the part that matters — and I'll get to that.

The phone call also tells you something about the operation. If you ask about recent inspections and the person you're speaking to doesn't know where their equipment was inspected three weeks ago, that's a data point about how this carrier runs.

What changes after Montgomery

Before the Supreme Court's May 2026 decision in Montgomery v. Caribe Transport II, a broker in the 7th or 11th Circuit could lean on FAAAA preemption as a backstop. State negligent-selection claims got thrown. That's done now. The Court held unanimously that state-law negligent-selection claims against brokers aren't preempted — brokers can be sued in state court for negligently selecting an unsafe carrier, and that exposure is real in every jurisdiction.

The specific relevance to the BASIC lag problem is this: if you tendered a load to a carrier who had been visibly hammered in an inspection event one month earlier, and you either didn't know because you didn't look at the inspection detail, or you didn't call, or you didn't document either — that's a gap a plaintiff's lawyer will fill with an expert witness explaining how the data lag works and why you should have known to account for it.

"I pulled BASIC on the day of tender and it showed 44th percentile" is going to sound thin when the opposing expert explains that the score was missing six weeks of inspection data and that a phone call would have surfaced the OOS orders.

How I document this

This section is short because the process isn't complicated — it just has to be consistent.

For every new carrier tender, I log: the date and time I ran the SAFER pull; the specific BASIC percentiles at that moment; the date of the most recent inspection visible in the L&I detail; whether I saw any recent violations and what I did about them. If I called — date, time, who I reached, what I asked, what they told me. If the carrier confirmed clean inspections, that's in the record. If they gave me something evasive, that's in the record too, and so is my decision about whether to proceed.

For carriers with fewer than 15 inspections in the 24-month window, or any recent inspection activity in the last 60 days, this supplemental step is not optional. The BASIC score alone isn't enough data.

The goal is to be able to sit across from a plaintiff's attorney in a deposition and explain what you knew, when you knew it, and every step you took to close the gap between what BASIC showed and what the actual current safety picture was. The BASIC lag is a known problem. Treating it as if it doesn't exist is a choice — and it's the kind of choice that looks bad in front of a jury.

The score you're looking at today is already history. Know that before you tender.

---

— Mason Lavallet

Founder, DOTScreener.com