Your Carrier's OOS Rate Looked Fine. The OOS Order Is Why You're Getting Sued.

A broker I know tendered a load to MC-1247893 in February. They'd screened the carrier at onboarding six weeks earlier — authority age 26 months, OOS rate 3.1% (below the 5.3% national threshold), no Unsafe Driving or Crash Indicator alerts. The pull looked clean. They tendered without re-checking.

What they didn't know: three days before the tender, a roadside inspector in Indiana had placed that carrier's primary power unit out of service under 49 CFR § 396.9(c). Brake defect. The driver never corrected it. The carrier dispatched the truck on that load anyway.

There was an accident on I-65. Cargo destroyed, driver injured, shipper named in the suit. And when discovery came around, plaintiff's counsel pulled the inspection report and showed the timeline: OOS order dated February 14th. Load tendered February 17th. Broker had zero documentation of any check between onboarding and tender.

The broker's defense was, essentially, "our OOS rate check looked good." The plaintiff's attorney explained to the jury what an OOS rate actually is. That didn't go well.

---

Let me explain the distinction, because I talk to brokers every week who genuinely don't know there's one.

An OOS Rate Is Historical Data. An OOS Order Is a Legal Prohibition Right Now.

Your carrier's OOS rate — the number you see in SAFER, the one that feeds into the Vehicle Maintenance and Driver Fitness BASICs — is a rolling 24-month calculation. FMCSA takes all the roadside inspections a carrier had in the past two years and calculates what percentage of them resulted in an out-of-service violation. One OOS violation per inspection = that inspection counts as "out of service." The rate is recalculated monthly using FMCSA's SMS algorithm.

A 3% OOS rate means 97% of that carrier's inspections over the past two years didn't result in an OOS citation. That's genuinely useful information about their historical compliance pattern. It tells you something.

What it does not tell you: whether that carrier's trucks are legally operable today.

An OOS order is different. It's an enforcement action — a legal directive from FMCSA or a roadside inspector — that prohibits operation. There are three flavors, and they work differently:

Vehicle-specific OOS orders come from roadside inspections. A Level I or Level II inspection turns up a critical brake defect, a cracked rim, lights that don't function. Under 49 CFR § 396.9(c), the inspector places the vehicle out of service on the spot. That truck cannot legally move until the violation is corrected and documented. The driver is supposed to coordinate with the carrier to get it fixed before continuing. Some do. Some don't.

Driver-specific OOS orders under 49 CFR § 395.13 typically come from HOS violations. A driver who's been behind the wheel too long gets placed out of service — they're prohibited from driving until they've gotten the required rest. The truck can be moved by someone else. The driver can't operate it.

Carrier-wide / imminent hazard OOS orders under 49 CFR § 386.72 are the nuclear option. FMCSA issues these when an investigation reveals a pattern of egregious safety violations that present an imminent danger to the public. The entire operation is shut down. Every truck. Every driver. Until FMCSA says otherwise. These are relatively rare, but they happen, and when they do, the carrier's BASIC percentiles often haven't caught up yet.

Here's the critical point: none of these orders update your carrier's OOS rate in real time. The rate is a monthly calculation from inspection data. An order placed on a Tuesday doesn't change next month's SAFER numbers until after it's been processed through the SMS cycle. You could have a carrier sitting at a 2% OOS rate while actively under an imminent hazard order.

Where to Actually Find Active OOS Orders

The SAFER Company Snapshot is where most brokers spend their time — the BASIC percentiles, the insurance status, the authority status. But there's a field most people blow past: "Operation Classification."

On the SAFER snapshot, under the carrier's basic info near the top, there's an operation classification field. If the carrier is under an active out-of-service order at the carrier level, it will say "Out of Service" right there. Not buried. Right there. Most brokers never scroll past the BASICs to read it.

For imminent hazard orders specifically, FMCSA also maintains an enforcement action database on their website. It's searchable by company name and MC number. It's not the most pleasant interface, but it's publicly accessible.

Vehicle-specific OOS orders are harder. Those live in FMCSA's ASPEN inspection database, and while SAFER shows aggregate inspection data, it doesn't give you a real-time lookup of whether a specific VIN is currently tagged as OOS. That's a practical limitation of what's publicly available. The closest you get is verifying that the vehicle's OOS rate is low and that there are no carrier-wide orders — and then monitoring for changes.

Why This Matters More After Montgomery

Before May 14, 2026, a broker in the 7th or 11th Circuit could argue FAAAA preemption and get a negligent-selection case dismissed at the federal level. The Supreme Court killed that in Montgomery v. Caribe Transport II. Unanimous. Justice Barrett, writing for the court: the FAAAA does not preempt state-law negligent-selection claims against freight brokers.

That changes what "reasonable care" has to look like. A state court jury is going to hear the facts and decide. And here's what those facts look like when an OOS order was active:

The inspector tagged the truck OOS. The carrier dispatched it anyway. You tendered the load to that carrier. You didn't check whether they were OOS because you checked their historical OOS rate six weeks ago.

"We checked the rate" is going to sound like exactly what it is to a jury: a broker who looked at the wrong number and called it vetting.

That's not a strong defense. It might not be any defense at all.

The Paper Trail That Actually Holds Up

Here's what defensible looks like: you checked SAFER at onboarding, you documented the operation classification status and the BASIC percentiles with a timestamp, and you set up monitoring so that any status change — including an OOS order — triggers an alert before the next tender.

That's the combination that works. Initial screening to establish the baseline. Continuous monitoring to catch what changes between screenings. A re-filed Carrier Selection Record that reflects what you knew at the time of each load.

In DOTScreener, when you add a carrier to Continuous Monitoring, the system re-screens them on an ongoing basis and logs the record with a timestamp. If something changes — carrier goes OOS, insurance lapses, BASIC scores spike — you get an alert. And the screening history creates a documented timeline: here's what the carrier's status was on February 14th, here's what it was on February 17th when you tendered. If there was an OOS order between those dates, you'll know. If there wasn't, you can prove it.

That's the difference between "we checked the rate" and "we verified carrier status at the time of tender, and here's the documented record that proves it."

How I Document This

When I pull a carrier's SAFER snapshot before tender — not just at onboarding, every time for new lanes or after any gap of 30+ days — I document:

1. Date and time of pull. The timestamp matters. It needs to predate the load tender.

2. Operation Classification status. Not implied. Explicitly noted: "Active, not OOS as of [date/time]."

3. Authority status. Common/Contract carrier, active. Screenshot or carrier file entry.

4. BASIC alerts or lack thereof. Which BASICs are above threshold, which aren't, and what decision I made based on that.

5. Insurance verification. Separate from the BASIC check — this is the FMCSA L&I database pull, not the ACORD.

For carriers on continuous monitoring, the re-screening timestamp is the documentation. The system shows no OOS status at the time of tender. That's your proof that the check happened.

The goal isn't to look like you tried. The goal is to actually have verified that the carrier was legally allowed to operate when you put freight in their truck. One is a checkbox. The other is evidence.

A low OOS rate is a useful historical signal. It's not a substitute for knowing whether the carrier has an active order against them right now.

The plaintiff's lawyer who deposed my broker friend didn't care what the historical rate said. They cared what the status was on February 17th. My broker friend couldn't answer that question. That's the gap worth closing before you're sitting in a deposition room trying to explain it.

---

How I Document This

• Pull SAFER snapshot within 24–48 hours of tender for any carrier not on continuous monitoring
• Explicitly note "Operation Classification: Active" with the pull timestamp
• For carriers on Continuous Monitoring in DOTScreener, the re-filed Carrier Selection Record timestamp is your tender-day proof
• If any BASIC is at or above alert threshold, document why you proceeded (policy exception with written justification) or don't proceed
• Keep screenshots or PDF exports in the carrier file — not just "we checked," but here's what we saw

— Mason Lavallet

Founder, DOTScreener.com