The MC Number That Doesn't Show Up Anywhere — FMCSA's Motus Rollout and the Vetting Blind Spot Nobody Warned You About

I had a broker call me in late May with a situation that took me a minute to untangle. He'd gotten a carrier lead — strong reputation on a lane he runs frequently, clean phone call, the dispatcher knew the load requirements cold. He entered the MC number into his screening tool. Nothing. Blank. Carrier not found.

He ran it through SAFER. Nothing there either.

His assumption: fake MC. He walked away from the carrier.

I asked him for the number. It was ten digits long. That was the clue.

That wasn't a fake MC. That was a real carrier registered through FMCSA's new Motus system — and most screening tools have no idea it exists.

What FMCSA Changed, and Why It Matters

FMCSA moved its carrier registration to a new platform called Motus in May 2026. The shift was overdue — the old unified registration system was built in a different era — but the timing and implementation created a problem for anyone doing carrier vetting the way brokers and shippers have always done it.

The old system issued sequential MC and DOT numbers. You could roughly gauge a carrier's vintage from the number alone. A carrier with MC-900000 had been around for a while. MC-1200000 was newer. The numbers told you something.

Motus doesn't work that way. New MC and DOT numbers are randomized. No sequential logic. And they can be long — 8 digits or more. A carrier who got their authority after the May cutover might have MC-10284731 or DOT-4198204. Legitimate authority. Real operating history starting to build. And completely invisible to any tool that reads SAFER's legacy MC search, because SAFER hasn't backfilled that data.

The Two Problems This Creates

The first is carrier identification. A broker enters an MC into their usual tool and gets "not found." They assume fraud. The carrier is real. They either refuse the load (opportunity cost) or accept it without any screening (liability cost). Both outcomes are bad, just in different ways.

The second problem is worse: insurance.

When a carrier is registered through Motus, their insurance filings — BMC-91 for auto liability, BMC-91X for cargo, and broker bonds — are also filed through Motus. The legacy FMCSA L&I feed that most insurance verification tools read doesn't capture those Motus-filed policies. So you run an insurance check on MC-10284731. You get back "no insurance on file." The carrier has a valid policy. Your tool just can't see it.

That creates a specific trap. You think the carrier doesn't have coverage. You require them to upload a certificate. They send you one. Now you're doing manual COI verification — which comes with its own failure modes around blanket additional-insured endorsements, policy limits, and effective dates — instead of pulling the actual filing from FMCSA's records where the insurer has directly attested to the coverage.

I've written before about why the FMCSA L&I database is more reliable than a certificate for verification purposes. That advantage disappears when your tool can't read the Motus side of that database.

Who Gets Hurt by This

New authority carriers are already operating with limited runway. They can't always get on load boards, brokers apply the 18-month rule liberally, and building a load history takes time. The Motus registration issue piles on. A legitimately-authorized, insured carrier who started operations after May 2026 looks invisible to brokers running standard vetting — not because anything is wrong, but because the data pipeline the industry relied on hasn't caught up to the registration change.

That's a problem for carriers trying to build a book of business. It's also a problem for brokers who need capacity.

But the bigger problem is for the brokers and shippers who end up accepting Motus-registered carriers without any screening at all — because their tools returned nothing and they didn't know why.

The Montgomery Angle

Post-Montgomery v. Caribe Transport II, you can be sued in state court for negligent carrier selection. The Supreme Court settled that in May. The standard the plaintiff's bar uses is whether you exercised reasonable care in selecting the carrier.

"My tool said they didn't exist" is not reasonable care. It's a description of a broken process.

In discovery, the question isn't whether your screening tool was glitchy. It's whether you took reasonable steps to verify that the carrier you hired was authorized, insured, and not disqualified from operating. A plaintiff's attorney who knows about the Motus transition will ask whether you knew about it, whether you checked additional sources, and whether you had a written policy for handling carriers whose MC numbers don't resolve through your standard tool.

If the answer is "we just didn't screen them," that's a problem. If the answer is "we had no idea this registration change happened," that's also a problem — arguably a worse one, because it suggests your vetting process has no connection to what FMCSA is actually doing.

A one-sentence policy that says "carriers whose MC does not resolve through our primary screening tool require a supervisor review before tender" is better than nothing. But better than that policy is a tool that reads both the legacy SAFER data and the Motus registration data, so you're not creating exceptions in the first place.

What to Check on a Long-Format MC Number

If you get an MC number you don't recognize the format of — eight digits, ten digits, doesn't fit the typical sequential range — here's the manual path while you're waiting for your tools to catch up:

Go to safer.fmcsa.dot.gov and try the DOT number if you have it, not just the MC. Motus-registered carriers exist in SAFER's DOT lookup even when the MC search doesn't surface them. The DOT number tends to be the more stable cross-reference in Motus records.

Also check the FMCSA registration and licensing portal directly. This isn't SAFER — it's the system that holds actual operating authority status, and it's been updated to include Motus-issued authorities. The interface is worse than SAFER, but the data is more current on newly-issued authority.

For insurance, if FMCSA L&I shows nothing on a carrier you believe is real, ask the carrier which insurer holds their policy and file number, then call the insurer directly and ask them to confirm the filing. Slow, but it's the right backup when your tool is coming up blank on a legitimate carrier.

Document that call. Date, time, who you spoke with, what they confirmed. That documentation is your paper trail if this load ever ends up in discovery.

The Authority Age Issue

There's an additional wrinkle worth noting. One of the signals I use on new-authority carriers is authority age — specifically, the FMCSA grant date. An authority issued two weeks ago tells me something different than one issued fourteen months ago.

For Motus-issued authorities, some legacy tools were pulling incorrect authority ages because they couldn't read the Motus grant date. They'd either return null, or pull a fallback date that didn't reflect the actual authorization. A carrier who'd been operating for six months looked brand-new, which triggered unnecessary scrutiny — or worse, caused brokers to miscalculate their risk tolerance.

The correct grant date is in the Motus registration record. If your tool can read it, the authority age signal is accurate. If it can't, you're guessing — and guessing in a direction that could either cause you to turn away a carrier you should have been comfortable with, or misjudge the tenure of one you should have scrutinized more carefully.

How I Document This

When a carrier's MC resolves through Motus rather than the legacy SAFER data, I'm documenting the following in the carrier file:

Carrier authority verification: Confirmed active operating authority for MC-10284731 / DOT-4198204 via FMCSA Motus registration system. Authority granted [date]. Registration system: Motus (post-May 2026 cutover).

Insurance verification: BMC-91 cargo liability confirmed via FMCSA Motus insurance filing, policy [policy number], insurer [insurer name], $1,000,000 limit, effective [date], no lapse history in Motus filing record. Secondary confirmation: called [insurer name] on [date] at [time], spoke with [rep name], confirmed policy is active and the MC is a named insured.

Data source notation: Standard SAFER MC search returned no results for this carrier — consistent with Motus-issued MC. Carrier identity confirmed via DOT number cross-reference in SAFER and full authority/insurance confirmation via Motus data directly.

That notation matters. It shows you knew why your standard tool returned nothing, you understood the registration environment, and you took extra steps to close the gap. That's the kind of paper trail that holds up when a plaintiff's attorney is trying to argue you skipped the process.

What DOTScreener Does Now

I want to be direct about why I'm writing this post and not just venting into the void.

DOTScreener now reads both the legacy SAFER data and FMCSA's Motus registration records. If a carrier exists in Motus — whether the MC is old format or new, whether their insurance was filed through the legacy system or through Motus after the cutover — DOTScreener surfaces it. The screening page, Text-to-Screen, and continuous monitoring all read both data families automatically.

For new-authority carriers who registered after May 2026, DOTScreener pulls the correct authority grant date from Motus so the tenure signal is accurate. For carriers whose insurance was filed through Motus, those policies show up on the screening record instead of returning "no insurance on file." You're not managing a list of carriers your tool can't find. You're just screening carriers.

I don't say this because I want to run an ad. I say it because the Motus rollout is real, the data gap is real, and brokers who don't know about it are making vetting decisions based on a blank screen that doesn't mean what they think it means. Whether you use DOTScreener or another tool that's solved this problem, check with whoever you use that Motus-registered carriers resolve properly before you assume a blank is a fraud.

The carrier who looks like they don't exist might be the safest one on your board.

One More Thing Worth Knowing

The FMCSA's enforcement posture hasn't changed to match the registration transition. OOS orders, authority revocations, and insurance lapses for Motus-registered carriers still show up in the enforcement data. If a Motus carrier gets their authority revoked, that revocation exists in the system. If they get placed OOS, it's there.

The data gap is specifically about discovery and verification of newly-issued authorities — not about enforcement against carriers who've already been found non-compliant. That matters because it means the risk profile on a Motus-issued carrier isn't necessarily higher than any other new-authority carrier. The risk is in not knowing what you're looking at.

Know what you're looking at.

— Mason Lavallet

Founder, DOTScreener.com