FMCSA Says Active, Your Vetting Tool Says Inactive? The Motus Transition, Explained

If a carrier's FMCSA record says one thing and your load board or vetting platform says another, you are probably looking at the Motus transition — not at a carrier who quietly lost authority or insurance. FMCSA moved carrier registration onto a new system (Motus) in mid-May 2026, and during the migration the government's own data surfaces have disagreed with each other about authority statuses and insurance filings. FMCSA has temporarily suspended USDOT inactivations while the system stabilizes — the agency's own acknowledgment that statuses in flight may not reflect reality.

The practical rule for brokers until this settles: treat any single-source 'inactive' or 'filing disappeared' reading as a signal to VERIFY, not a verdict to act on. The carriers being wrongly rejected right now are someone's good, insured, long-time partners — and the brokers rejecting them are losing capacity over a database migration.

Motus is FMCSA's replacement for its legacy registration infrastructure — the system of record behind USDOT numbers, operating authority, and the insurance filings insurers submit (the BMC-91/91X liability filings, cargo filings, and broker surety bonds). Every vetting product in the industry, whatever its brand, is downstream of this one federal source; there is no parallel database of operating authority or federal insurance filings anywhere.

During a migration like this, different surfaces of the same record — the public web lookups, the QCMobile API, the open-data extracts — can serve different answers for the same carrier while records move and caches lag. That's how you get the pattern brokers and carriers are reporting: FMCSA's own site shows a carrier active and insured, while a platform reading a different surface shows the same carrier inactive or lapsed. Neither the carrier nor the broker did anything wrong; the plumbing is mid-swap.

First: don't auto-reject on one reading. A tool that hard-declines carriers off a single federal surface will, during this window, decline carriers whose coverage and authority are fine. If your process (or your platform) does that automatically, add a human check before any rejection that cites authority or insurance status.

Second: corroborate across surfaces. If one source says inactive, check another — FMCSA's own SAFER lookup is the quickest second read. Agreement across two federal surfaces is meaningful; disagreement means transition artifact until proven otherwise.

Third: for insurance specifically, the ground truth is one phone call away — the issuing agent on the carrier's COI can confirm in minutes whether a policy is in force. A federal filing status is a pointer to coverage, not the coverage itself.

Fourth: document what you saw. If you tender to a carrier whose record looked conflicted — or decline one — a dated note of which sources said what protects you either way. 'Both federal surfaces agreed' and 'sources conflicted, verified with agent before tendering' are both defensible; 'the tool said so' is not.

Two months after the Motus cutover, the problems have shifted rather than cleared. The pattern being reported now is access, not just status: carriers trying to claim their USDOT record in Motus are finding themselves accidentally registered as Transportation Service Providers (TSPs), which blocks access to their own carrier profile. FMCSA's guidance for affected users is to close the mistaken TSP account through Motus settings, log back in, and look for the prompt to claim the USDOT number — and if that fails, to submit a support ticket with ownership documents and account information.

FMCSA has also extended its pause on USDOT inactivations to cover carriers who have missed required biennial updates since June 1 — an acknowledgment that carriers shouldn't lose authority because the system won't let them complete the filing. No end date has been announced.

For brokers, the vetting takeaway is unchanged but worth restating with two more months of evidence behind it: a carrier whose record looks wrong, stale, or unclaimable right now may simply be stuck in the transition. Corroborate across surfaces, verify insurance with the issuing agent, and document what you saw — the carriers being wrongly rejected over migration artifacts are still someone's good partners.

Draylo reads two federal surfaces — the QCMobile API and FMCSA's L&I insurance-filing data — and compares them before alarming anyone. A filing that vanishes from one surface while the other still shows the policy is reported as exactly that: a source conflict, likely a transition artifact, verify with the issuing agent. A drop both sources agree on still waits for a second consecutive daily check before the critical alert goes out — real cancellations are announced by insurers ~30 days ahead in the filing data, so confirmation costs nothing.

The system also watches its own data feeds: when conflicts or flapping statuses spike across carriers — the fingerprint of a federal data event rather than real simultaneous cancellations — alert severities soften automatically until the feeds stabilize. And Draylo never auto-blocks a carrier on any status reading — every decision stays with you, on a dated record.

You can see the two-source read on any carrier right now with the free insurance lapse check — enter a USDOT and it shows the live filings, any pending cancellations insurers have filed, and calls out source conflicts instead of hiding them. No signup.