Motus is a 20 year experiment of trying to fix trucking's front door
FMCSA's new registration system has had a rough launch. The complaints are real. So is the history of how we got here, and the reason the system has to work despite the pain of getting there.
30ish years ago, we went from the closed doors of the ICC to the FHWA and then the FMCSA in 2000. We opened a door controlled by the industry and the market through deregulation, and we went from 17,000 to 750,000 trucking companies. We’re still trying to fix the front door. That’s your legislature in action, so before you jump on that pro-trucking Senator or Congressman's wagon, dig in and take a look at how long they’ve had their hands in this very muddy industry and process; odds are some of these dinosaurs helped break it. I personally am looking forward to these folks questioning leadership about why trucking is in its current state. Most of the time, the question can be answered by installing mirrors in the House and Senate office buildings, where some of these antiques have become fixtures of bureaucratic failure so long that they’ve molded to their chairs while becoming extremely wealthy as career consumer politicians. That’s much of our issue. We’ve passed this Motus “buck” so long that the chickens had to come home to roost. Those same legislators are hoping you forgot how Motus got here.
The Motus registration system went live on May 14, 2026, and the rollout has not been smooth. Carriers are locked out. Compliance professionals are filing bug reports faster than FMCSA can process them. Insurers and their clients are struggling. Social media is not being kind. None of that changes the fact that the system Motus replaced was a patchwork of platforms built decades ago that could not verify who was registering, could not prevent a revoked carrier from walking back in under a new name, and could not fulfill a statutory mandate passed by Congress in 2012. The problems with the launch are real. The problems with the old system were worse, and the administration that finally pulled the trigger on the transition inherited a project that two previous administrations had started but neither had finished. Keep in mind, Administrator Derek Barrs has barely been on the job 247 days. Motus was being piloted 60 days later to the day. Point being, this didn’t start today. Let’s break down when it started, how we got here, and where we go from here.
On May 14, 2026, at 8:00 p.m. Eastern, the Federal Motor Carrier Safety Administration retired the Unified Registration System, the Licensing and Insurance public filing system, and the registration functions of the FMCSA Portal. In their place, the agency launched Motus, a single centralized platform tied to Login.gov identity verification, designed to replace a fragmented collection of aging systems with one dashboard for USDOT number applications, operating authority, biennial updates, insurance filings, and carrier record management.
Within days, carriers began reporting login failures, unauthorized access errors, screens returning raw JSON instead of a usable interface, and processes hanging mid-transaction. Compliance professionals who earn a living doing FMCSA registration work found themselves unable to complete basic tasks. One carrier posted a screenshot showing the system returning a raw error. So… when are we fixing Motus, and how do we comply with the rules when the system won’t work for us? Garrett Allen at SearchCarriers called it one of the worst software releases he had ever witnessed. The frustration is real.
FMCSA responded with two separate statements. The first acknowledged the issues in the measured language of a government agency aware that its system is not working: the agency recognized the challenges, called resolution an absolute priority, and committed to working through the problems. The second, from Administrator Derek Barrs personally, carried a different tone, more direct, more accountable, and more aligned with the posture this administration has taken on enforcement. Neither statement pretended the rollout was going well. Both are committed to fixing it.
I am not going to pretend the launch has been acceptable. It has not. People who need to register, update their records, file insurance, and maintain their authority cannot reliably do so right now, and that is a problem that affects the livelihoods of every carrier and compliance professional in the country. I am also not going to pretend that the system Motus replaced was working, because it was not, and the history of how we got here matters if you want to understand why this administration made the decision to launch despite the risk, and why the end result, when it arrives, is going to be worth it.
Twenty years of trying
The statutory mandate for a unified registration system dates to the ICC Termination Act of 1995. Congress told FMCSA to consolidate its registration processes into a single electronic system. The agency didn’t do it. The Safe, Accountable, Flexible, Efficient Transportation Equity Act of 2005, known as SAFETEA-LU, repeated the requirement and added specifics. The agency still didn’t do it. The Moving Ahead for Progress in the 21st Century Act of 2012, known as MAP-21, mandated it again with additional requirements for fraud prevention, identity verification, and stronger vetting of new applicants. That was 14 years ago.
In 2005, FMCSA published a Notice of Proposed Rulemaking for the Unified Registration System. In 2011, it published a supplemental notice incorporating the new congressional mandates. In August 2013, it published a final rule establishing URS and laying out a phased implementation. Phase 1, covering new applicants for USDOT numbers and operating authority, went live in December 2015. It worked. It screened 100 percent of authority applications for disqualified carriers, issued more than 100,000 new DOT numbers, and removed more than 360,000 dormant records.
Phases 2 and 3 never happened. Phase 2 was supposed to migrate existing carriers to the new system for biennial updates and record management. Phase 3 was supposed to consolidate the USDOT and MC dockets into a single identifier. In January 2017, the final week of the Obama administration, FMCSA published a rule indefinitely suspending the remaining URS phases because the IT infrastructure was not ready and the state partner systems had not been tested for compatibility. That suspension remained in place throughout Trump’s first term and Biden’s entire term. For nine years, the industry operated on Phase 1 of a three-phase system, with everything else frozen in place.
During that nine-year gap, the registration system sat on infrastructure built in the 1990s and early 2000s. Identity verification was minimal. A carrier could register with an email address and a self-reported name. The system could not reliably detect that a revoked carrier’s officer was filing a new application under a different LLC at the same address with the same phone number. The chameleon carrier problem that has dominated enforcement headlines for the past two years grew in the shadow of a registration system that was not built to stop it and had not been upgraded to try.
Why this administration pulled the trigger
When Secretary Duffy took office in early 2025, he inherited a registration system that had been in partial implementation for a decade, a chameleon carrier problem that had become a national news story, a statutory mandate that remained unfulfilled 13 years after Congress passed it, and an agency workforce that had never been resourced to process the volume of new registrations the system was generating. Administrator Barrs arrived in October 2025, 10 months later. The decision to build and launch Motus was made because the alternative, continuing to run on a system that everyone knew was broken, was no longer defensible.
Motus was designed to do what the old system could not. Tie every registration action to a verified identity through Login.gov. Validate business information at the point of submission. Provide role-based access so that only authorized individuals can modify carrier records. Integrate with the fraud detection tools that ARCHI pioneered but could not fully execute on the old infrastructure. Consolidate the half-dozen disconnected systems that carriers, insurers, registered agents, and compliance professionals had been navigating for years into a single platform and to finally fulfill the statutory requirement that Congress passed in 2012 and that three administrations had failed to deliver.
The scope of the replacement is part of why the launch has been difficult. Motus did not replace one system. It replaced several: URS for new applications, the FMCSA Portal for record management, the Licensing and Insurance system for financial responsibility filings, and the various interfaces that supporting companies used to file BOC-3 designations, insurance policies, and other documents on behalf of carriers. Each of those systems had its own user base, workflows, and data structures. Merging them into a single platform while migrating millions of records and maintaining regulatory continuity is, to put it plainly, one of the hardest things a federal agency can attempt in the IT space.
Systems break on launch
I say this as someone who has built systems from scratch, not even knowing what I was doing at first. After all, I’m a farm kid turned truck driver turned risk guy. Unless it's harvest season in VA, then I’m back to being a trucking farm guy. But my site started with no code and no users in February 2026. Four months later, it serves nearly 1000 users across federal investigators, law firms, insurers, and carriers, with more than 30 API integrations and millions of records. Every single one of those integrations broke at least once. They still bug out and break right now. Data sources changed formats without notice. Edge functions returned errors that took hours to diagnose. Updates to one component broke three others. That is what building software looks like. It is not pretty. It is iterative. Anyone who tells you they have launched a complex system without post-launch issues is either lying or has not launched anything complex. Samsung even struggles to roll out updates, and then we get the patch. It happens. The issue here is that this failure is affecting livelihoods, but the failure isn’t new in 2026. The failure started decades ago as a bureaucratic process that Duffy and Barrs are fighting to actually bring into compliance with the law. I think that’s worth noting.
Samsung pushes firmware updates that brick phones. Apple has released iOS versions that killed battery life and cell reception. Microsoft’s Windows updates have caused blue screens across enterprise deployments. Google has shipped Chrome updates that broke major websites. These are companies with tens of thousands of engineers and budgets measured in billions. FMCSA is a federal agency with constrained procurement processes, a fraction of the technical staff, and the additional burden of complying with government IT security standards that private companies do not face. That does not excuse the bugs. It provides them with context from people who have been playing in this industry and its messy systems for decades.
The end state
When Motus is working as designed, a carrier applying for a new USDOT number must verify their identity through Login.gov before the application is accepted. That single change eliminates the ability to register anonymously, the first step in every chameleon carrier’s book. The system will validate business information at submission, checking that the address is real, the entity exists, and the people behind it are who they say they are. That eliminates the mailbox suites and virtual office addresses that ghost carriers have used as their principal place of business for years.
When an existing carrier’s authority is revoked, and the same officer files a new application at the same address with the same phone number under a different LLC name, the system will have the data integration to flag that application at the point of entry rather than relying on a downstream investigator to catch it during a manual review that may not happen for months. Motus provides the infrastructure to do it at the front door, rather than after the carrier is already on the road.
For insurers, the system provides a verified filing environment in which policy filings are tied to a verified entity rather than to a self-reported name and DOT number. For registered agents, it provides a single portal for BOC-3 filings, replacing the fragmented process they have been using. For compliance professionals, it provides one login, one dashboard, and one place to manage everything that currently requires navigating four or five separate systems with different credentials and different interfaces.
For enforcement, which is ultimately the point, Motus provides the data infrastructure that the current registration system lacks. A system that can verify identity, validate business legitimacy, flag related applications, and integrate with inspection and violation databases in real time can catch the next ghost fleet before it accumulates 7,505 inspections across 46 states under 32 nominally separate authorities. That is the end state. It is not here yet. It is coming.
Where we go from here
The bugs need to be fixed, and they need to be fixed fast. Carriers that cannot access the system cannot comply with the law, and carriers should not be penalized for a system failure that is not their fault. FMCSA has already indicated that it will not cite carriers for compliance issues caused by Motus access problems, and the agency needs to make that commitment explicit, public, and enforceable for as long as the transition issues persist.
As an industry, we should also give this administration credit for doing what the two previous administrations did not. The Obama administration started URS and stalled it. The Biden administration inherited the stall and let it sit. The current administration, under Barrs and Duffy, decided to build, fund, staff, and launch a new system, knowing the transition would be painful and that the political cost of a rough rollout would fall on them. They launched it anyway because the old system was failing in ways that were getting people killed, and because a statutory mandate that Congress passed in 2012 has not been fulfilled.
Administrator Barrs has said the agency bit off more than it could chew and would keep chewing anyway. That was about the chameleon carrier crackdown, but it applies here too. Motus is the infrastructure that makes the crackdown stick. Without a registration system that can verify identity and validate business legitimacy at the point of entry, every carrier the agency shuts down can walk back in under a new name within days. We documented exactly that pattern in the hotshot ghost fleet investigation. Thirty-two carriers, 6,082 VINs, and every time the agency killed one authority, the trucks were running under a new one within 48 hours. The FMCSA shut them down just as fast. The fraudsters are on the run. The issue is, they're like roaches, so the work must continue both at the front door and within the nest. That is what a registration system without identity verification allows. Motus is built to stop it. It is not there yet. It will be, and when it is, the industry will look back on this launch the way it looks back on the ELD mandate, a painful transition that nobody enjoyed going through and nobody wants to go through again.