The Carrier SAFER Can't Find

A carrier no one can find

A broker I know got a call last month from a carrier wanting to haul a flatbed move out of Shreveport. The carrier gave him their MC: MC-10348271. He pasted it into SAFER. Nothing. Tried the DOT number, DOT-4219456. Nothing. The carrier's insurance agent called to confirm coverage — but still nothing came up in the system my buddy was checking.

He declined the load. Carrier moved on to someone else.

Here's the thing: that carrier was legitimate. Active authority granted in June 2026. BMC-91X liability on file. Active cargo coverage. The whole file existed — just not in the database he was looking at.

FMCSA rolled out a new carrier registration platform called Motus in May 2026. With it came randomized MC and DOT numbers that can run eight digits or more and follow a completely different format than the legacy sequence. SAFER's MC search still runs against the old legacy database. A carrier who registered through Motus can look like they don't exist — to SAFER, to most third-party tools, to anyone relying on the traditional lookup path.

That's not a minor inconvenience. It creates two distinct vetting problems, and both of them have liability attached.

The two ways this can hurt you

First problem: you tender to a carrier you couldn't verify.

The pressure scenario is easy to imagine. Carrier calls late, load moves tomorrow, customer is already annoyed about the spot rate. You search, nothing comes up, you tell yourself maybe the system is lagging — it does that — and you tender anyway. If something goes wrong, you've got a carrier file showing you tried to pull authority and came up empty. That's not a paper trail. That's a paper trail that ends at "we couldn't confirm this carrier was even licensed."

Post-Montgomery v. Caribe Transport II, that deposition answer gets expensive. The Supreme Court held that the FAAAA doesn't preempt state-law negligent-selection claims. States can hold you liable for who you put on a load. A broker who tendered to an unverifiable MC — and couldn't confirm authority, couldn't confirm insurance — is going to have a very bad time explaining that to a plaintiff's attorney. "The SAFER search came back empty" is not a defense. It's an exhibit.

Second problem: you reject a legitimate carrier because your tool can't find them.

This one is quieter but it's real. Brand-new Motus carriers can have clean records, active authority, and valid insurance. They're not chameleon carriers. But if your lookup returns nothing, your trained instinct is to say no — which is usually right, except when the problem is the tool, not the carrier.

The subtler version: a new Motus carrier who gets rejected repeatedly because brokers can't verify them will start finding workarounds. They'll have their agent call. They'll send screenshots of their FMCSA registration page. Some of those workarounds are fine. Some create openings for fraud, because now you've trained yourself to accept documents as substitutes for system verification. That's a bad habit to build.

What the insurance gap actually looks like

Here's the part that bothers me more than the MC lookup miss.

Carriers have to file financial responsibility forms — BMC-91 or BMC-91X — with FMCSA under 49 CFR § 387.9. The required minimums are $750,000 combined single-limit BIPD for most general freight carriers, $1,000,000 for carriers hauling household goods or certain hazmat. Those filings are supposed to be in FMCSA's system so brokers can verify coverage without relying solely on a certificate of insurance.

Post-Motus, those filings still get made — through the Motus system. But the legacy insurance feeds that most tools read only pull from the pre-Motus database. A carrier who registered in June 2026 and filed their BMC-91X through Motus could show up as "no insurance on file" in a verification tool that never learned to read Motus data. You could be looking at a carrier with a million dollars in active liability coverage and your screen says zero.

That's not a tool quirk. That's a vetting workflow producing systematically wrong answers on every new carrier going forward — and the percentage of active authority holders whose records live fully or partly in Motus will only grow.

New carriers and the Motus overlap

I know the reflex. New authority, no inspection history, no crash record because there's nothing to record yet — this is where the 18-month caution comes from, and it's not wrong.

But the Motus registration issue is separate from the authority-age risk. An eight-month-old carrier with a full Motus file, active BMC-91X coverage, solid early inspection results, and a completed pre-trip attestation is a different animal than a ghost carrier with a 90-day-old MC and nothing on file anywhere. The question isn't just "is this carrier new?" It's "can I actually verify what I'm looking at?"

If your lookup tool returns nothing, you don't know which situation you're in.

The carriers most affected are the newest ones — which means the population most affected is also the population you're already watching more carefully. The overlap of "new authority" risk and "Motus lookup gap" is where vetting failures will cluster. A brand-new chameleon carrier who registered through Motus and has no trackable history anywhere is a harder screen than one who came through the legacy system, because at least with the legacy carrier you know what you're dealing with.

What changed in my vetting process

When a carrier's MC comes back empty on a legacy search, I don't stop there anymore. The Motus registration system has its own lookup — FMCSA's Motus portal resolves the newer MC format even when SAFER's MC search returns nothing. DOTScreener resolves Motus MCs directly now, which means when I pull a screen and get a carrier file back, the lookup already touched both data families. The authority grant date comes from Motus records. Insurance filings from Motus appear on the screen. I know whether I'm looking at a pre-Motus or post-Motus registration, and the timestamp on the screen reflects which source resolved the record.

What I do when a carrier gives me an MC I don't recognize:

Start with a full screen rather than a raw SAFER lookup. If the screen resolves — authority, insurance, inspection history — I work from that. If it doesn't resolve anywhere, I call the carrier back and ask them to walk me through their FMCSA portal directly, not a screenshot, not a PDF. A legitimate carrier registered through Motus can pull their own registration record from the FMCSA site in about 90 seconds. A fraud carrier who grabbed an MC number and is hoping you won't check closely cannot.

I've also stopped treating "came back empty in SAFER" as a go/no-go answer on its own. Empty in SAFER now means "check Motus before you decide."

What I got wrong before I understood this

For about three weeks after the Motus rollout, I missed this entirely. I was screening carriers through a tool that only read legacy data. A carrier with a legitimate Motus registration could show up with incomplete insurance or no insurance at all, and I was interpreting that as a coverage gap rather than a data gap.

The distinction matters because they produce different decisions. A genuine coverage gap is a disqualifier. A data gap is an investigation item. Treating one as the other means you're either approving carriers with no verifiable coverage, or you're rejecting carriers who are fully covered and legitimate.

I caught it when a carrier I'd approved showed "no insurance on file" on a re-screen six weeks later. The carrier hadn't lost coverage — their Motus-filed BMC-91X had always been current. My tool just wasn't reading it. I went back through my recent approvals and found two more carriers in the same situation.

That's when I started asking specifically about Motus data coverage before trusting any vetting tool.

How I document this

For every carrier screen regardless of format:

I record the MC number exactly as provided, the data source the screen resolved against, the authority status and grant date, and the insurance verification method. If the lookup required Motus data to resolve, I note that explicitly: "Authority and insurance confirmed via FMCSA Motus registration data, DOTScreener screen [date/time]."

If I tendered to a carrier whose record was only partial — one source resolved, the other didn't — I note the gap and what additional confirmation I got before tendering. The gap itself isn't automatically disqualifying. Not documenting the gap is the problem.

The Carrier Selection Record I file for that load includes the screen timestamp and a note about the data source. If I'm re-screening the same carrier 90 days later under continuous monitoring and the record has since populated fully in both systems, I note that too. The file should tell a complete story about what information was available at each decision point, not just the final answer.

If a carrier gave me an MC number in a format I didn't immediately recognize — eight-plus digits, non-sequential — that detail goes in the file with a note about which system resolved it.

The bottom line

FMCSA changed its registration system. Most lookup tools haven't caught up. If you're still relying on SAFER's MC search or any tool that only reads the legacy database, you're going to see carriers who exist come back as nothing — and you're going to make decisions based on that gap. Some of those decisions will be wrong, and some of them will land in your carrier file in discovery.

That's worth fixing before a claim makes it an exhibit.

— Mason Lavallet

Founder, DOTScreener.com