MOTUS, two weeks in.
Strip the press releases off MOTUS and you find a federal IT project that shipped on a deadline its software couldn't meet. The platform replaced FMCSA's decades-old registration network on May 14 at 8:00 PM Eastern — Login.gov–backed, fraud-resistant, single sign-in for every interaction with the agency. The Secretary's launch statement framed it as the end of "loose, fraud-prone applications." 2.2 million launch letters went out. 400,000 came back undeliverable.
Week one: spinning wheels, "unauthorized access" JSON errors on routine MCS-150 updates, login failures during the exact window the filings were due. Design consultancy Don Norman Associates stood up motusbugs.com as a public bug board within two weeks of launch — a six-column Kanban (Reported → Confirmed → Working → Fixed → Open → Submitted to FMCSA), structured issue cards, upvotes — — it's collecting submissions faster than FMCSA's published response cadence. FreightWaves' May 30 piece carried the line that defined the week: "It is one of the worst software releases I've ever witnessed."
The tell that the agency knows is in a different doorway. On April 11, FMCSA quietly issued a 180-day exemption letting CDL holders and carriers use paper medical certs for up to 60 days after issuance — because the parallel NRII (National Registry II) rollout, which is supposed to electronically transmit medical certifications from examiners to state DL agencies, isn't ready either. The exemption runs through October 11. FMCSA has stated it does not plan to grant additional nationwide waivers after that. Translation: the parallel system needed for the registration overhaul to work won't be functional for at least five more months, and the agency is pre-committing to no extensions.
What this means for an operator this week: the gap between FMCSA's enforcement posture and its own system reliability is widening. The agency is withholding $73M from New York while its login flow drops your MCS-150 mid-submission. The hedge is documentation — timestamp every failed attempt, save screenshots, version-stamp your paper backups, and file through a compliance service provider with API access if you have one (most are bypassing the public web form's failures).
Read the full deep dive →
|