Issue 3 · Compliance Tech · Jun 2, 2026

MOTUS, two weeks in: the federal registration system that's failing in real time

Two weeks in, MOTUS is still broken and FMCSA quietly admitted it. The launch, the bugs, the NRII tell, and what to do this week if you're stuck.

On May 14, 2026 at 8:00 PM Eastern, FMCSA flipped the switch on MOTUS — a single Login.gov–backed platform that replaced the loose constellation of legacy systems carriers had used for two decades to register, update, and prove themselves to the agency. The Secretary’s launch statement framed it as the end of “loose, fraud-prone applications.” 2.2 million carriers received launch letters. By the morning of May 15, the most useful resource for working with the new system was not on .gov.

Two weeks later, that’s still true.

The launch the press releases promised

MOTUS — the Motor Carrier Operations and Technology Unified System — was the agency’s first ground-up rebuild of carrier registration since URS (Unified Registration System) consolidated the previous patchwork in the early 2010s. The promise was structural: one identity, verified through Login.gov; one platform for MCS-150 updates, authority filings, insurance changes, and lookups; one set of fraud controls layered into the registration process itself instead of bolted on after the fact. For an agency whose own oversight reports have spent a decade flagging carrier-identity theft and “chameleon carrier” reuse of revoked DOT numbers, the modernization was overdue. The framing was sound. The execution is where it has unraveled.

What actually happened in week one

The first reports came from carriers trying to complete routine MCS-150 biennial updates — the standard registration refresh that operators are legally required to file. Instead of the new flow promised in the agency’s launch materials, users hit spinning wheels, invalid login messages, and JSON error screens reading “unauthorized access.” Twitter screenshots of error states started circulating within 48 hours of launch. By May 22, the first hard number landed: FMCSA had mailed 2.2 million launch notification letters to every motor carrier address in the country, and roughly 400,000 came back undeliverable — a return rate the agency has not publicly explained.

The signal that mattered most wasn’t a single bug; it was that no one knew which bugs were known. With FMCSA’s published response cadence stretched thin and no public status page, carriers found themselves unable to tell whether the error they hit was a five-minute outage, a misconfiguration on their end, or a system-wide failure that wouldn’t resolve before their filing deadline.

So an operator built the missing page.

motusbugs.com: the bug board the federal government didn’t ship

Within two weeks of launch, design consultancy Don Norman Associates stood up motusbugs.com — a public crowdsourced board where carriers and compliance officers report MOTUS bugs, document workarounds, and track what’s been fixed. It is unaffiliated with FMCSA. It is well-designed: a six-column Kanban workflow (Reported → Confirmed → Working → Fixed → Open → Submitted to FMCSA), structured issue cards with category tags, status badges, and an upvote system to surface the bugs hitting carriers hardest. As of this writing, it is the canonical reference for what the federal system is and isn’t doing — built and shipped by a private design firm in the time the agency hasn’t published a status page.

The site’s stated intent is collaborative: report bugs publicly so the queue is visible, while feeding submissions to FMCSA to help the agency triage. That a private operator had to build it at all is the story.

FreightWaves’ May 30 retrospective carried the line that defined the week. A user posted on X: “The motus rollout has been unacceptable. It is one of the worst software releases I’ve ever witnessed.” The post wasn’t from a marketing firm or a competitor — it was from a working carrier with no incentive to overstate. Land Line covered the same week as “Hello MOTUS” — a more measured framing, same underlying story.

The tell: NRII’s quiet exemption

The most analytically interesting piece of evidence didn’t come from the bug reports or the trade press. It came from a notice the agency published a month before MOTUS even launched, and never publicly connected to the rollout.

On April 11, 2026, FMCSA issued a 180-day temporary exemption allowing interstate CDL holders, CLP holders, and motor carriers to continue using paper copies of the medical examiner’s certificate (Form MCSA-5876) for up to 60 days after issuance. The exemption expires October 11, 2026.

The reason given: State Driver’s Licensing Agencies and certified medical examiners are still transitioning to the electronic transmission of medical certification data required under the National Registry II (NRII) final rule. NRII and MOTUS are parallel modernizations — NRII handles the medical-cert pipeline from examiners to state DL agencies, MOTUS handles registration and identity at the federal level. Both were supposed to be running by mid-spring. Neither is.

The agency’s own forward-looking language is the smoking gun. FMCSA stated it does not anticipate granting additional nationwide NRII waivers or exemptions after the six-month duration. Translation: the parallel system needed for the registration overhaul to fully work won’t be functional for at least five more months, and the agency is already pre-committing — in writing — to no further extensions. That’s not the posture of a project running smoothly.

The enforcement gap (and why it’s getting wider)

The deeper problem isn’t that MOTUS is buggy. New systems are buggy. The problem is that the same week MOTUS rolled out broken, FMCSA’s enforcement posture got materially more aggressive.

On May 18, the Department of Transportation announced strengthened identity verification for the Drug & Alcohol Clearinghouse — adding friction to pre-employment queries that motor carriers and brokers are legally required to run before dispatching a new hire. On May 20, FMCSA revoked 12 more ELDs from the Registered Devices list (888 ELD, DRAGON, ACTION, Mondo HOS, FIRST, FIRST V2.0, MTL, USPower, Sam Freight, DSGELOGS, COBRA, and GT USA ELOGS), with a July 20 replacement deadline — two weeks after the Safe ELD and MYLOGS revocations announced May 7. Cumulative ELD revocations since January 2025: 67 devices, per FreightWaves’ tally. Same week, the Secretary withheld $73 million in federal funds from New York State for failing to revoke illegally-issued trucking licenses.

The pattern is consistent: enforcement is sharpening on every surface — states, carriers, devices, drivers — while the agency’s own primary registration tool is failing to function. For an operator with a clean record, that gap is where penalties accumulate. The MCS-150 update that timed out on Wednesday becomes a missed-filing flag by the following audit cycle. The Clearinghouse query that hung becomes a hiring violation if the driver was dispatched in the interim. The MOTUS error message is not, today, a defense.

What to do this week if you’re stuck

Five concrete moves, sourced from operator reports and compliance counsel posting publicly:

Document every failure. Screenshot the error, timestamp the attempt, save the URL. Maintain a simple log. This is the first piece of evidence in any future audit defense, and it’s the only thing the agency or your insurer can act on.
File through a compliance service provider with API access if you have one. Most established providers — Foley, J.J. Keller, Consultran, etc. — have direct API integration with FMCSA’s backend and are bypassing the public web form’s failures. If your service provider isn’t reporting issues, your filing is probably going through.
Use the NRII paper exemption proactively. If your medical certificate is within the 60-day window of issuance, carry the paper MCSA-5876 in the truck. Don’t assume electronic transmission from your examiner has reached your state DL agency.
Check motusbugs.com before spending an hour on a MOTUS error. If a workaround exists, it’s posted. If your bug isn’t listed, submit it — the queue is the queue.
If you’re hiring from a state in transition, confirm a clean Clearinghouse pre-employment query came back before dispatch. The strengthened ID verification rollout adds friction without warning; a hung query is not a clean query.

What’s next

The five-month forward window through October 11 is the period to watch. Three things to track:

Whether FMCSA stands up a public status page for MOTUS. As long as motusbugs.com remains the canonical bug reference, the agency is operating below standard for any modern public service.
Whether the NRII rollout actually reaches functional state by October 11. FMCSA’s pre-commitment to no further nationwide waivers means a missed date forces either a quiet policy reversal or an enforcement posture against medical-cert filings that aren’t electronically transmitted — neither option is operationally clean.
Whether the ELD revocation pace continues. 67 devices since January 2025, 14 in May alone, with two more deadlines (July 7 and July 20) about to land. The carriers most exposed are small-fleet operators who selected low-cost ELDs without compliance-vetting infrastructure — exactly the segment that least afford OOS time.

The thing operators keep saying — and what no FMCSA press release will admit — is that the gap between regulatory enforcement and system reliability is widening, not closing. The hedge for this quarter is documentation, redundancy, and the assumption that the primary system will fail at the worst possible moment.

That’s not a posture anyone wanted to take toward a federal modernization that was supposed to make compliance easier. It’s the posture the rollout has earned.

Sources

Read this in full each Tuesday