SAFER Can't Tell You What Other Brokers Already Know About That Carrier

Three weeks ago I was on a call with a broker in Memphis. He'd just dispatched a load of electronics — $180,000 freight, high-value shipper, lanes he runs regularly. The carrier had a clean SAFER. No BASICs alerting. OOS rate below the national average. The MCS-150 was current. By every metric you can pull from FMCSA, this was a fine carrier to book.

Load went sideways. Driver went dark at a fuel stop in Arkansas. Equipment sat unattended for nine hours before dispatch tracked it down. Shipper was furious. Cargo insurance claim opened. And when the broker started asking around, he found out two other brokers in that market had flagged that same MC — same pattern, equipment abandonment — over the previous four months.

Neither of those brokers had SAFER data to point to. SAFER didn't know. FMCSA didn't know. The BASIC scores didn't reflect it yet. But the market knew. And the broker in Memphis had no way to access what the market knew.

That gap is what I want to talk about today.

SAFER is a lagging indicator, and everyone in this industry already knows it

FMCSA's compliance review process is infrequent. Many carriers never get a full compliance review at all — or get one once in five years. The BASIC scoring system ingests roadside inspection data, which covers some carriers better than others depending on where they run and how often they get pulled in. A carrier that operates in rural lanes, runs lightly, and keeps their nose clean at weigh stations can accumulate a genuinely bad performance history in the real world while their SAFER record stays green.

49 CFR Part 396 requires carriers to systematically inspect, repair, and maintain all motor vehicles they operate. Section 396.3 is explicit: every part and accessory must be in proper adjustment and good working order. But whether a carrier actually does that is a compliance question that only comes to light when an inspector catches them, when they crash, or when their equipment starts failing in the field. That's your broker's problem before it's FMCSA's problem.

The BASIC percentile on Vehicle Maintenance tells you something about what inspectors have found. It doesn't tell you that two brokers in your market watched that carrier's equipment fall apart on their loads in the last 90 days. Those are two very different data points.

The gap between inspection and reality

Take a carrier like the one my Memphis contact used. Let's call them MC-1247893 / DOT-3621044. Eight trucks, running dry van, mostly regional lanes in the mid-South. They might get two or three roadside inspections a quarter. If those inspections happen on a day when the trucks are in good shape, the Vehicle Maintenance BASIC stays clean. Meanwhile, the carrier is running equipment that overheats on a three-hour haul, dispatching drivers who go dark at fuel stops, and leaving brokers holding the bag on freight claims.

None of that shows up in SAFER until the pattern is severe enough and the inspection sample is large enough to push a BASIC percentile into alert territory. By then, brokers have already eaten the losses.

The same gap exists on the broker side. A carrier wondering whether to take a load from a broker has almost no FMCSA data to rely on. The BMC-84 surety bond ($75,000 minimum) tells you the broker has posted financial security, but it doesn't tell you whether they actually pay carriers. FMCSA doesn't track non-payment complaints. A broker who has stiffed six carriers in the last year has the same FMCSA-visible fingerprint as one who pays in 30 days every time.

Peer-reported intelligence is the missing layer

The answer isn't to ignore FMCSA data. SAFER is still the baseline — you pull it every time. But it's a floor, not a ceiling. The carriers and brokers in your market see things that FMCSA doesn't. When a carrier shows up to a facility with the wrong trailer, when a broker issues a rate confirmation and then ghosts on payment, when a carrier's driver abandons a load — the people who experience that have information the agency never will.

DOTScreener's Network Flags surface that intelligence. Carriers can flag brokers for non-payment, fraud, or unprofessional conduct. Brokers can flag carriers for equipment problems, double-brokering, abandonment. Every submission goes to a DOTScreener admin before it's visible to anyone else. Nothing is published until it's reviewed and approved. That moderation step isn't bureaucracy — it's necessary. When you're attaching a flag to a named MC number or broker docket, the defamation and abuse exposure is real. A moderated system keeps the bad actors out of the database and protects the legitimate entities from unsubstantiated hits.

When you pull a carrier on DOTScreener, you see the FMCSA data — authority status, safety rating, BASIC scores, insurance filings — alongside any approved network flags from other organizations. A carrier with three approved flags for equipment abandonment in the past six months looks very different from the same carrier without that context, even if their SAFER record is identical.

What this means post-Montgomery

On May 14, 2026, the Supreme Court decided Montgomery v. Caribe Transport II, LLC. Unanimous. Justice Barrett wrote the opinion. The holding: the FAAAA does not preempt state-law negligent-selection claims against freight brokers.

That decision changed the discovery calculation for every broker in this country. It used to be that plaintiff's counsel had to defeat preemption before they could even get to the merits of how a broker selected a carrier. Now they go straight to the merits. And the merits question is: what did you know, or what should you have known, when you tendered this load?

SAFER data is part of that answer. But peer-reported flags are another part, and the legal standard doesn't care whether the information lived in a government database or an industry platform. If there were flags about this carrier's equipment reliability, and you didn't check, and you can't show you checked, that's a problem in deposition.

That's not hypothetical. Discovery in trucking negligence cases is thorough. Plaintiff's attorneys ask for every data source you consulted when selecting a carrier. If you only checked SAFER and didn't check the peer-reported layer, you've left a hole in your selection record. If peer flags existed and you'd have found them on any reasonable vetting run, the argument that you exercised reasonable care gets harder to make.

I'm not a lawyer. I can't tell you what the legal standard is in your specific state. But I can tell you what a well-documented carrier selection file looks like, and it includes every relevant data source that was available at the time. Post-Montgomery, you want to be the broker who can prove they checked everything that was available.

When the flag is there and you proceed anyway

Here's the thing about network flags: they're not always a hard stop. Sometimes a carrier has a single flag from two years ago and a stellar record since. Sometimes the flag describes something that doesn't apply to your lane or freight type. Sometimes you dig into it and determine it's not disqualifying.

That's fine — as long as you document it.

If you see a flag and still proceed, your file needs to reflect that decision. What was the flag? When was it filed? What did you do to investigate? Who did you talk to? What did the carrier say? What was your conclusion and why? That reasoning belongs in the screening record, not just in your head.

The alternative — seeing the flag, proceeding anyway, and having nothing in the file — is the version that loses in court. If something goes wrong with that load, you've now got a flag in the record that shows you had notice of a potential problem, and no documentation that you addressed it.

How I document this

When I run a carrier screen on DOTScreener and see an approved network flag, here's what goes into the file before the load tenders:

What the flag says. Type of complaint (equipment, payment, fraud, conduct), date filed, date approved by DOTScreener admin, brief description of the reported issue.

What I did to investigate. Did I call the carrier's dispatch? Did I contact the organization that filed the flag? Did I review the carrier's full inspection history and recent BASIC trends to see if the flag is consistent with other signals? Document all of it.

My conclusion. One or two sentences. Either "This flag is not disqualifying for this load because [reason]" or "This flag is disqualifying and we're not using this carrier."

If I proceed. Any additional safeguards I'm adding — Verifi live truck location, a check-call requirement, a COI pulled same-day rather than relying on what's on file.

If I'm not proceeding, that gets documented too. "We declined MC-1247893 due to two approved network flags for equipment abandonment, dated [dates]. See attached screening record."

That's the paper trail. It takes three minutes to build. It's the difference between a reasonable-care defense and a deposition where you're explaining why you ignored a red flag.

SAFER is still the first thing you check. But it's not the last.

The Memphis broker I mentioned earlier runs the same lane he always did. Same shippers. Same freight. What changed is he doesn't stop at SAFER anymore. He treats community-flagged intelligence as part of the required baseline, the same way he treats BASIC scores and insurance filings. When there's a flag, he investigates and documents. When there's no flag, he documents that too — the timestamp on a clean screening record matters as much as the contents.

FMCSA data is what the government knows. Network flags are what the industry knows. Post-Montgomery, you need both.

— Mason Lavallet

Founder, DOTScreener.com