What FMCSA Doesn't Know About the Carrier You're About to Book

There's a carrier I'll call MC-1247893 / DOT-3812044. Clean SAFER profile. Satisfactory safety rating. Twenty-two months of operating authority. OOS rate of 8.4% on vehicle and 5.1% on driver — both below national averages. No alerts across any of the seven BASIC categories. On paper, this is a carrier you book without blinking.

Two brokers in my network flagged them last month. One for suspected double-brokering on a $48,000 flatbed move from Wichita to Memphis. The carrier accepted the load, went quiet at the start window, and a different MC showed up at the shipper's dock. The second flag came from a small brokerage in Kansas City: three owner-operators who leased onto MC-1247893 said the carrier pocketed freight charges and left them holding invoices with no recourse. FMCSA has that carrier's SAFER snapshot looking pristine. The agency hasn't touched them.

That gap between what the government knows and what the industry knows is real, it's wide, and in a post-Montgomery world, it matters legally.

Why FMCSA Data Has an Expiration Date

The data in SAFER — inspection results, crash reports, out-of-service violations — is enforcement data. It captures what federal and state inspectors found at roadside, or what made it into a crash report. It's backward-looking by design. A carrier gets inspected, violations get recorded, BASICs update on a 24-month rolling window. That's the mechanism.

What it doesn't capture is anything that didn't surface as a citation or a crash. A carrier that subbed out your load to a broker without telling you. A pattern of non-payment to owner-operators that signals financial distress before the authority lapses. A dispatcher who's been circulating on freight forums under a rotation of company names. None of that shows up in SAFER unless somebody filed a formal complaint and FMCSA acted on it — which takes months, when it happens at all.

The freight industry has always known this. Brokers have always traded warnings informally — in Facebook groups, in TIA chapter meetings, in phone calls to friends. The problem is that informal network is invisible when you're vetting a new carrier, it's inaccessible to anyone outside your personal circle, and it leaves no paper trail. If a warning reaches you by word of mouth and you don't document it, it might as well not exist when a plaintiff's lawyer subpoenas your carrier file three years later.

The Legal Standard After Montgomery

Before Montgomery v. Caribe Transport II, the legal calculus for brokers was simpler. The 7th and 11th Circuits had held that the Federal Aviation Administration Authorization Act preempted state-law negligent-selection claims. Brokers in those circuits had effective immunity unless a claim went federal.

The Supreme Court changed that in May 2026. Justice Barrett's unanimous opinion held that the FAAAA does not preempt state-law negligent-selection claims against freight brokers. Every state, every circuit, every brokerage in the country is now on the same footing: you can be sued in state court if a jury decides you didn't exercise reasonable care in selecting the carrier that caused the accident.

What does "reasonable care" look like? The regulations don't specify. 49 CFR Part 371 (property brokers) requires that brokers maintain records of their carrier transactions and operate with reasonable practices, but it doesn't define a due-diligence checklist. Courts are going to fill that in, claim by claim, and they're going to look at what information was available to you and whether you sought it out.

Here's where peer-reported flags become a legal issue rather than just a practical one. If there's a system where industry participants flag carriers for fraud, non-payment, or safety concerns — and you had access to that system and didn't check it — that's a gap a plaintiff's lawyer can drive through. You didn't just miss a clue. You had a tool and chose not to use it.

The Moderation Problem (and Why It Matters)

Peer reporting systems for carriers have existed informally for years. The problem is that unmoderated flags are a defamation exposure waiting to happen. A disgruntled carrier can flag a broker who denied their rate increase. A competitor can flag a legitimate carrier to push them off a lane. Without someone in the middle reviewing what goes public, you get noise at best and malicious abuse at worst.

That's why I care about moderation more than most people do when they look at this feature. DOTScreener's network flags work like this: when a carrier or broker submits a flag — a warning about non-payment, suspected double-brokering, a safety concern, a fraud pattern — it lands in a pending queue. Nobody sees it until a DOTScreener admin reviews and approves it. Flags with no documentation, flags that read like a grudge, flags that don't pass a basic plausibility check — those don't make it through.

What does make it through looks like the two examples from the top of this post. Specific. Tied to a real load or a documented dispute. Corroborated where possible. Only then does it appear in the carrier's DOTScreener file.

Both directions work. Carriers can flag brokers — non-payment is the obvious one, but also situations where a broker double-brokered loads or pressured drivers into unsafe conditions to meet delivery windows. Brokers can flag carriers. Everything is keyed to the entity's MC or DOT number, so the flag follows the authority, not a DBA name that can change overnight.

What a Flag Actually Tells You

A network flag is not proof. It's a signal, the same way a BASIC alert is a signal. Your obligation is to look at it and think about it in context, not to automatically refuse a carrier because someone flagged them.

What I look for when I see a flag:

The category matters. A non-payment flag from a single owner-operator has a different weight than a double-brokering flag corroborated by two separate brokerages on loads two months apart. Payment disputes happen. Double-brokering your freight without authorization is a hard disqualifier for most lanes I'd be running.

How recent. A flag from two years ago on a carrier that's had clean operations since — that gets less weight than something from last month. I'm looking at it in combination with everything else in the file.

Whether the flag is isolated. If a carrier has a flag for non-payment and also has rising OOS rates and a lapsed insurance window in the L&I history, those things are telling the same story. If a carrier has a single flag and nothing else raises flags, I'm going to dig a little harder before I make a call.

The point isn't to let the flag make the decision for you. The point is that you saw it, you thought about it, and you documented why you booked or didn't book based on everything in the file. That's the defensible position.

The Pre-Tender Record for a Flagged Carrier

49 CFR § 371.3 requires property brokers to keep records of their transactions. After Montgomery, those records are also your litigation defense. If you see a network flag on a carrier and proceed with booking, your file needs to show that you considered it.

This is what I put in the record when a carrier has a flag but I'm proceeding:

Flag reviewed: [date]. Flag category: [payment dispute / operational concern / other]. Flag source: [DOTScreener network flag]. Evaluation notes: Flag is from [X months ago]. Carrier's SAFER profile, inspection history, and BASIC scores do not corroborate the flag. Carrier has [Z loads] completed through our brokerage without incident. OOS rate [X%], authority since [date]. Proceeding with booking on [lane/load description].

If you're not proceeding because of the flag:

Flag reviewed: [date]. Flag category: double-brokering concern. Carrier selected out. Reason: Recent double-brokering flag on a similar dry-van lane is inconsistent with the operational oversight our customer expects on this load. Carrier file closed.

Two sentences. Dated. Referenced back to the specific flag. That's all you need. What you can't do is see the flag and pretend you didn't.

How I Document This

In DOTScreener, network flags appear directly in the carrier's screening file alongside the FMCSA data. I don't go looking for them separately — if there's an approved flag on an MC I'm reviewing, it's in the file. My diligence record includes:

1. Screenshot or export of the full DOTScreener carrier file, including any network flags, timestamped at the point of review.

2. A note in my TMS or carrier record confirming the flag was reviewed and summarizing my evaluation.

3. If I'm proceeding on a flagged carrier for an established customer, a short written rationale (see the language above).

4. If I'm declining, a note in the carrier's record that the flag was the contributing factor — no need to quote the full flag content, just reference it.

The documentation habit matters more than any individual flag. What plaintiffs' lawyers look for is a pattern of inattention — carriers reviewed once and never again, files with no timestamps, approvals that look like rubber stamps. A timestamped file showing you considered all available information is the paper trail that holds up.

The Feedback Loop FMCSA Can't Close

FMCSA has a reporting mechanism for unsafe carriers — the National Consumer Complaint Database. It's slow. It feeds into enforcement actions that may or may not materialize. It's not designed for the working broker who needs to know what's happening in the industry right now.

The industry has always self-corrected informally. What DOTScreener's network flags do is make that self-correction visible and structured — and, crucially, moderated so it doesn't become a weapon. FMCSA tells you what happened in federal enforcement. A moderated flag from two corroborated brokerages tells you what happened on a load last month.

Both belong in your carrier file. Only one of them shows up automatically when you pull an MC number.

How I Document This

When I add a carrier to my approved list, my DOTScreener file shows the state of any network flags at the time of approval. I export that file and save it. If I run that carrier again six months later, I pull a fresh screen — and a flag that landed after my last review will show up. Continuous monitoring handles the ongoing piece: if an approved carrier picks up a new flag or an insurance lapse or a BASIC alert, I get notified, and the carrier's file gets a timestamp showing when that change was detected.

The Carrier Selection Record that DOTScreener files on each screen is my legal contemporaneous record. Network flags that were present and reviewed are part of that record. That's the trail that holds up three years from now, when nobody remembers what they actually looked at before they tendered the load.

— Mason Lavallet

Founder, DOTScreener.com