Your Most-Used Carrier Just Crossed Every Threshold. Here's the Protocol.
The hardest carrier to cut is the one who's never given you a problem — until they do. Here's what to do when a long-term carrier's BASIC scores go red, including the exact documentation you need before you fire them.
The hardest carrier to fire is the one who's never given you a problem. Until they do.
I had a carrier — call them MC-1247893, based out of Rockford, DOT-3567102 — that moved dry van freight for us for eighteen months straight. Never a late pick-up. No damage claims. Drivers called on schedule. When I pulled their SAFER snapshot the first time, everything looked clean. So I stopped looking.
Fourteen months later, a shipper's traffic manager mentioned that the carrier's name had come up in a monitoring alert. I pulled the snapshot. Their Unsafe Driving BASIC was at 71%. Vehicle Maintenance was at 68%. OOS rate had climbed from 9% to 44% in twelve months — three inspections, all vehicle OOS, two in the previous six weeks. And I'd tendered them six loads in the meantime, each one around $8,500 in freight value, without ever re-checking the data.
Nothing had gone wrong yet. But something was going to. And if it had, my carrier file for those six loads was going to look very bad.
That's the scenario nobody trains you for. Not the brand-new carrier with no track record — everyone knows to watch those. The one you've worked with for two years who gradually crosses every threshold while you're not paying attention.
Why Familiarity Kills Vetting Discipline
Here's the honest reason it happens: when a carrier performs well operationally, you stop verifying. Load covered. No damage claim. Driver didn't ghost the pick-up window. Good enough. The SAFER pull you did during onboarding gets treated as a permanent clearance rather than a snapshot in time.
FMCSA updates BASIC data monthly. An OOS rate can move from 12% to 44% in a year without triggering any notification. There's no FMCSA alert that says your approved carrier just crossed an intervention threshold. You have to pull the data yourself, or you need a monitoring service that flags changes. Either way, if you're not actively looking, you don't know — and your paper trail doesn't show that you knew, which is somehow worse.
Post-Montgomery v. Caribe Transport II (Supreme Court, May 14, 2026, unanimous), the due diligence question isn't frozen at the original carrier onboard. A plaintiff's attorney isn't just going to ask what you checked when you first approved the carrier. They're going to ask what you checked the last time you tendered a load to them. If the answer is "nothing, they were already in our approved list," you have a problem. Being in an approved list is not a standard of care. It's administrative convenience.
What Should Trigger a Re-Pull
Most brokers doing any monitoring at all are using a commercial tool — Carrier411, MyCarrierPackets, or a TMS with built-in carrier scoring. These tools vary widely in how quickly they reflect FMCSA data changes, and some have lag of two to four weeks between an FMCSA update and their next sync.
The practical minimum for any active carrier: monthly SAFER pull and quarterly BASIC review. For a carrier you're tendering more than four times a month, do a full BASIC read quarterly and a manual SAFER check every 30 days. That's eight minutes of work per carrier per month. It's not excessive. It's the baseline.
Beyond the calendar, certain events should force an immediate off-cycle pull:
- Any OOS order appearing on SAFER
- A shipper or driver reporting an equipment or driver performance issue
- Word-of-mouth from other brokers that a carrier is having problems — yes, that counts as intel
- A carrier suddenly offering rates more than 15% below market to fill capacity
- Rapid driver turnover — different drivers on consecutive loads is a yellow flag for small carriers
That last one is subtle but consistent. When a small operation loses experienced drivers, maintenance discipline usually goes with them. The company that sent the same three drivers for eighteen months and now it's a different face every load is worth a closer look.
What the Thresholds Actually Mean
Under FMCSA's CSA methodology, percentile rankings above certain levels trigger what FMCSA calls "intervention consideration":
- Unsafe Driving BASIC: 65th percentile
- HOS Compliance: 65th percentile
- Crash Indicator: 65th percentile
- Driver Fitness: 80th percentile
- Vehicle Maintenance: 80th percentile
- Controlled Substances/Alcohol: 80th percentile
These numbers aren't absolute cutoffs — they're administrative thresholds where FMCSA begins considering whether to send a warning letter, open an investigation, or conduct a compliance review. A carrier at the 66th percentile in Unsafe Driving isn't automatically dangerous. A carrier below that threshold isn't automatically safe.
But here's the operational reality: those thresholds exist in the record whether you cite them or not. When you tender a $12,000 load to a carrier sitting at the 71st percentile in Unsafe Driving and that driver injures someone, a plaintiff's attorney is going to explain to the jury exactly what that number means — and then ask you to explain why you loaded them anyway.
If you can explain it — a specific understanding of the underlying violations, a documented improvement trend, a phone call with the carrier's safety director where you got a credible account of what happened and what changed — you're in much better shape. If you can't explain it because you never looked, you're not. That gap is what separates a defensible carrier selection file from one that hands the case to the plaintiff.
The Cut Decision
When a carrier crosses multiple thresholds and can't give a satisfactory explanation, you cut them. Not "we'll monitor for another quarter." Not "they've always been reliable, let's give them one more." You cut them and you document it. Here's how.
Step 1: Document what you found. Pull the full SAFER snapshot — power units, driver count, last MCS-150 date, authority status, active insurance filings. Pull the full BASIC scorecard with percentile ranks. Note the OOS rate and how many inspections are in the denominator period (under 49 CFR § 390.19, the MCS-150 alone won't tell you this — go to L&I for the inspection detail). Save PDFs. Date-stamp everything.
Step 2: Identify the specific violation pattern. If the Vehicle Maintenance BASIC is at 68%, don't just record the number — pull the inspection results from L&I and look at what's actually driving it. Brake violations on a single unit are different from mixed defects across multiple vehicles. One is a mechanical problem on a specific truck. The other is systemic maintenance neglect across the fleet. That distinction matters both in assessing the risk and in explaining your decision.
Step 3: Call the carrier before you pull the plug. This isn't just courtesy — it creates a documented record of whether the carrier knew about the problem and what they said. If their safety director doesn't know their OOS rate is 44%, that tells you everything about their safety management culture. If they explain that the brake violations came from one unit that's since been taken out of service and they have the maintenance records to prove it, that's a different conversation. Document who you talked to, what they said, and when.
Step 4: Write the decision memo. One paragraph. Something like: "On June 2, 2026, I reviewed the BASIC data for MC-1247893 and found Unsafe Driving at 71st percentile, Vehicle Maintenance at 68th percentile, OOS rate of 44% with all three vehicle OOS citations occurring in the last 120 days. I spoke with [safety director name] on [date]. Based on the violation trajectory and the inability to document corrective action, I have removed this carrier from our approved list effective today." That's it. That's what survives discovery.
Step 5: Update the approved list with a reason and a date. Not just removing the carrier from the active file — recording why, when, and who made the call. Three years from now, when an attorney subpoenas your carrier file, they'll see the date you acted and the basis for it. That's worth more than any amount of policy language about your commitment to carrier vetting.
The Awkward Question: What About the Prior Loads?
If you discover today that a carrier you've been tendering for fourteen months has been running degraded BASIC scores for the last eight, you have a legitimate question about those prior loads. I'm not a lawyer and I won't play one here.
What I'll say practically: the prior loads are what they are. If nothing went wrong, that's good luck. The question going forward is whether your file shows that once you found the problem, you acted on it. What you absolutely don't want is a discovery record showing that you pulled the data, saw the scores, and kept tendering for another two months without any documented rationale. That's not a defensible position.
The cut decision — and the paper trail behind it — is what separates the broker who exercised reasonable care from the one who didn't. Post-Montgomery, that distinction is worth fighting for in state courts across 47 states.
How I Document This
When a monitoring alert or a manual pull flags threshold crossings, my carrier file note includes:
1. Date of discovery — when I pulled the data and what it showed, not when I got around to acting on it
2. BASIC scores with percentile ranks — the specific violations driving the high BASICs, not just the number
3. OOS rate and inspection count — the denominator matters; a 44% OOS rate on three inspections is different from 44% on thirty
4. Authority and insurance status — any lapses, cancellations, or pending changes
5. Phone call record — who I spoke to at the carrier, what explanation they gave, and whether the explanation was credible
6. Decision and rationale — why I cut them or, if I conditionally kept them, what conditions I imposed and what timeline I set for re-evaluation
7. Approved list change — date of removal, name of person who made the call
The carrier relationship doesn't make this optional. It makes it more important. The longer you've used a carrier, the more a plaintiff's attorney can argue that you had ongoing responsibility to know what their safety profile looked like. Document that you did know — and that when the numbers changed, you changed your decision.
— Mason Lavallet
Founder, DOTScreener.com
Automate your carrier vetting
DOTScreener runs every check in this article automatically — live FMCSA data, documented decisions, tamper-evident audit trail.
Related Articles
\"Conditional\" Is Not a Middle Grade. It's a Finding. And \"Not Rated\" Is Not a Clean Bill of Health.
Most brokers treat FMCSA safety ratings like letter grades: Satisfactory is an A, Conditional is a C, Unsatisfactory is an F. That's wrong, and it's the kind of wrong that shows up in a deposition.
Broker GuidesWhy I Check Unsafe Driving Before I Ever Look at the Crash Indicator
The Crash Indicator is a lagging signal — it counts crashes that already happened. The Unsafe Driving BASIC tracks what the driver was actually doing in the cab before the next one. After Montgomery, that distinction isn't academic. It's the difference between a defensible approval decision and a smoking gun.
Broker GuidesThe ACORD 25 Certificate Is Not Proof of Coverage
Every broker collects ACORD 25 certificates. Most don't notice the disclaimer printed right on the form: the certificate confers no rights and doesn't prove coverage exists. Here's what to actually check — and where the ACORD 25 fails you when it matters most.