All articles
Broker Guides September 8, 2026 7 min read

Your Carrier's OOS Rate Is Not the Same as an OOS Order

Brokers confuse FMCSA out-of-service rates with out-of-service orders constantly — and they're not remotely the same thing. One is history. The other is current legal status. Post-Montgomery, mixing them up is not a minor paperwork gap.

A broker I know moved $180,000 of automotive parts last fall on a carrier they'd vetted 90 days earlier. The SAFER snapshot looked clean enough at onboarding — 28% vehicle OOS rate, a little elevated but within what a lot of brokers accept, authority active, insurance on file. They thought they'd done the work. What they missed: FMCSA had issued a formal out-of-service order against that carrier's operating authority 11 days before the load moved. Two different things. Two completely different levels of risk. And SAFER shows both — in different places, in different formats, with completely different implications for whether you should put that carrier on a load.

Most brokers don't know the distinction. I didn't fully understand it until I started building the tooling. This is the post I wish I'd had earlier.

The OOS Rate: History, Not Current Status

The vehicle OOS rate and driver OOS rate you see in SAFER are percentiles derived from inspection history. They tell you what happened at roadside over the past 24 months. Specifically: of all the times a DOT inspector looked at this carrier's equipment or drivers, what percentage resulted in a vehicle or driver being placed out of service on the spot?

A vehicle OOS rate of 35% means that more than a third of inspections found a violation severe enough to park the truck until it was corrected. Common causes: brakes out of adjustment, load securement failures, lighting violations, tire defects. The national vehicle OOS average floats around 21-22%. A carrier with a 40% rate isn't running into bad luck — their equipment culture is telling you something.

But the OOS rate is backward-looking. It's an average of events that already happened, spread over two years. It's genuinely useful for identifying operating patterns. It is not telling you whether the carrier can legally run tomorrow. A carrier can have a 15% OOS rate and be under an active OOS order right now. Those two things coexist.

An out-of-service order is an affirmative regulatory action. FMCSA or a state authority issues one and tells the carrier: stop moving freight. You're done until this is resolved.

These orders come from different places. Under 49 CFR § 385.325, FMCSA can issue an emergency OOS order against any carrier it determines presents an imminent hazard to public safety — no prior notice required, effective immediately. Under 49 CFR § 386.72, FMCSA can suspend operating authority during an ongoing investigation before the formal compliance review process concludes. A compliance review that ends in an "Unsatisfactory" safety rating triggers a formal 45-day notice and then loss of authority if nothing changes. State enforcement can issue OOS orders too, particularly when a Level I inspection reveals systemic problems rather than isolated violations.

The practical implication of 49 CFR § 385.325 is worth sitting with: "imminent hazard" means the agency concluded this carrier was an immediate threat to public safety. That's not a high OOS rate. That's not a BASIC percentile above intervention threshold. That's FMCSA looking at this specific carrier and deciding they're dangerous enough to stop right now.

At load-tender time, the distinction matters for a few reasons beyond the obvious safety concern. A carrier operating under an OOS order is operating illegally. Their insurance policy may not respond to a loss that occurs while they're in violation of a federal operating order — some cargo policies have exclusions for illegal operations. And post-Montgomery v. Caribe Transport II, a plaintiff's attorney will ask you one question about this in deposition: "Did you know the carrier had an out-of-service order when you tendered them this load?" If you didn't have a system that would have caught it, your answer is worse than "no." It's "I didn't have a way to know."

Where Each Shows Up in SAFER

Here's the mechanical problem. SAFER's company snapshot page has a lot of data, and the OOS rate and OOS order status are in completely different sections that most brokers never both check.

The OOS rates live in the inspection table, mid-page — vehicles, drivers, hazmat, with inspection counts and the national averages alongside each rate. You have to scroll down past the registration data, past the safety rating, past the insurance summary. They're there, but they're easy to skip if you're moving fast.

The OOS order status is near the top of the snapshot in the Operating Authority section. If a carrier is currently under an OOS order, the authority status reads "Out of Service" and there's an OOS date listed. That's the field that tells you their current legal operating status. But it only reflects what's in FMCSA's system as of the last update — which is usually current within a day or two, but not always within hours of an emergency order.

MC-1289403 / DOT-3901247 — the fictional version of the carrier I described above — had acceptable SAFER numbers across the board in April. Vehicle OOS rate 19%, driver OOS rate 8%, no BASIC scores above intervention threshold. What changed: a May compliance review uncovered falsified hours-of-service logs across six drivers, a 49 CFR Part 395 pattern the carrier's safety director had apparently been papering over for months. FMCSA issued a § 385.325 emergency OOS order in late May. Every broker who approved this carrier in April and didn't re-check their SAFER status before each subsequent tender kept putting freight on their trucks through June.

That's not theoretical exposure. That's the kind of situation that generates seven-figure verdicts.

The FMCSA L&I Check Has Lag Too

Some brokers skip SAFER entirely and use the FMCSA Licensing & Insurance portal for status checks. L&I shows active authority, broker registration, insurance filings. But it pulls from the same back-end databases as SAFER, with similar update lag — sometimes 24 to 48 hours on enforcement actions. It's not a real-time OOS order feed. It's a licensing database.

Neither source gives you a live alert when something changes. You get a snapshot of whatever the database reflected when you refreshed the page. If you onboard a carrier in week one and don't check again before week eight's load, you're operating on eight-week-old data.

DOTScreener's Continuous Monitoring watches carrier authority status between your check-ins. When a status change comes through — OOS order issued, authority revoked, insurance lapse — you get an alert before the next tender goes out. That gap between vetting events is where the risk actually lives, not at the moment of onboarding when everyone's paying attention.

The Inspection Count Problem Makes OOS Rates Even Less Reliable Alone

One more layer. An OOS rate means very little if there aren't enough underlying inspections to make it meaningful. A carrier with 4 total inspections and a 50% vehicle OOS rate is statistically much less informative than a carrier with 90 inspections and a 35% OOS rate. SAFER shows the raw inspection count right next to the rate, and you have to read both.

A carrier with 3 inspections and 0 OOS events looks good on paper. It tells you almost nothing about actual equipment discipline — three inspections could be three Level III driver-only checks that didn't touch the vehicle. New authority carriers frequently have this profile: not enough operational history to generate a meaningful inspection record. Low OOS rate, thin count. That's its own risk.

Don't mistake a low OOS rate from a thin inspection history for a clean carrier. Look at inspection count first, then rate.

The Priority Order

When I'm reading a carrier file, I work top-down:

Active OOS order → hard stop, no exceptions. I don't tender. If they're currently approved and monitoring catches an OOS order, they get pulled from the approved list immediately.

OOS rate well above national average with meaningful inspection count → elevated scrutiny. Not an automatic no, but I want to understand the violation pattern, check whether the BASIC scores for Vehicle Maintenance or Driver Fitness are also elevated, and document my reasoning for approval if I proceed.

High OOS rate from a thin inspection count → treat it as incomplete data, not clean data. Apply the same scrutiny I'd apply to a new-authority carrier: more verification, shorter monitoring interval, potentially a lower cargo-value cap until they build more history.

Low OOS rate, healthy inspection count, no active order → proceed normally.

The OOS rate and OOS order are inputs into a decision. Neither one is the whole picture by itself.

How I Document This

In DOTScreener, every carrier approval record captures the SAFER authority status and OOS rates at the time of approval — date-stamped, pulled directly from SAFER. If a carrier is approved with elevated OOS rates, I log a note explaining why the approval proceeded anyway (inspection count too thin to read confidently, BASIC scores within bounds, etc.).

Continuous Monitoring means any post-approval status change generates an alert in the activity record. If an OOS order comes through, there's a dated flag showing when it was detected and what action I took — tender held, carrier suspended from the approved list, broker notified. That chain of events is what I'd produce in discovery.

The deposition question I want to be ready for isn't "did you check OOS rate?" Most attorneys know brokers at least glance at SAFER. The harder question is: "After you approved this carrier, what system did you have to catch changes in their operating status?" "I checked at onboarding" isn't a system. "I had continuous monitoring in place and here's the alert log" is.

OOS rate tells you about the carrier's past. OOS order tells you about their right now. Check both. Don't mix them up.

— Mason Lavallet

Founder, DOTScreener.com

DOTScreener

Automate your carrier vetting

DOTScreener runs every check in this article automatically — live FMCSA data, documented decisions, tamper-evident audit trail.

Go deeper

Related Articles