MOTUS Phase II: The Operator's Field Guide
What changes at 8 PM ET on May 14, where carriers get stuck, and what to do this week.
Five days from now, at 8:00 PM Eastern, FMCSA flips the switch on MOTUS Phase II — the largest carrier-facing federal tech change in a decade. Your USDOT PIN stops working. The Portal stops accepting registration changes for ~4 days. About 800,000 existing registrants have to identity-proof through IDEMIA before they can do anything in the new system.
FMCSA has documented this rollout accurately, in the Federal Register and across a half-dozen FAQ pages. Most owner-operators won't read any of it until they're locked out.
This is the guide that should have come from FMCSA but didn't. The Login.gov → Portal → Motus claim flow with the points where carriers will get stuck. What IDEMIA is and which failure modes will hit you. The Company Official rule that quietly kills the consultant-files-on-my-behalf model. And a preflight checklist you can run on your phone before the lockout.
Free. Primary sources cited. No vendor pitches. Three sections have a companion video on YouTube — screen-recordings of the actual flows with failure modes recreated, not just described. Links inline. Reply with anything that breaks for you — those replies become Issue #1.
1. Login.gov → Portal → Motus.
The claim flow has three stages. Two of them happen before May 14 8:00 PM ET. The third can't happen until after.
Stage one — confirm your FMCSA Portal account is active. Log in to portal.fmcsa.dot.gov. Accounts dormant 90+ days are disabled; 12+ months, archived. Both require a call to 1-800-832-5660 to restore. New users create an account with the USDOT PIN from safer.fmcsa.dot.gov; PIN reissues arrive by USPS — don't start this on May 13.
Stage two — verify the Company Official email. Inside the Portal, under "Registration" → "Biennial Update (MCS-150)", confirm the Company Official's name and email are correct. Two things will bite you. (1) The Login.gov email you'll use to sign into Motus has to exactly match the Portal Company Official email. (2) If a third-party consultant is listed as the Company Official because they did your last filing, they cannot claim your Motus account on May 14 — only the actual Company Official with a matching Login.gov email can. Reclaim ownership now.
Stage three — claim the Motus account, after launch. On or after May 14 8 PM ET, the Company Official goes to motus.dot.gov, signs in with Login.gov using the matching email, and links it to the existing USDOT Number (which doesn't change). Identity and business verification happen on first claim — that's the IDEMIA step in the next section.
Three places this breaks:
- Email mismatch. Portal Company Official email ≠ Login.gov email = lockout. Fix it in the Portal before 8 PM ET May 14. After that you're on hold with 1-800-832-5660.
- Dormant Portal account. Haven't logged in in 90+ days? Locked today. PIN reissue arrives by USPS.
- Consultant-held credentials. If your Portal account is in your filing consultant's name, transfer ownership to a real officer or employee before May 14.
Three things FMCSA documented but operators routinely ignore: the four-day registration outage during cutover, sub-account holders must be invited by the Company Official, and PIN-based auth ends entirely on May 14 — no PIN fallback. Sources: FMCSA Modernization FAQs, FMCSA "Important Steps to Prepare".
2. IDEMIA identity verification.
IDEMIA is the federal contractor FMCSA hired in April 2025 to run identity-document capture and biometric verification. About 800,000 existing registrants will hit it on first sign-in.
The flow inside Motus, per the FMCSA URS Identity Verification Fact Sheet:
- Motus shows you a QR code. Scan it with your phone or tablet — that opens an IDEMIA verification session in your mobile browser.
- Pick language, document country, and document type. Accepted: identity card, U.S. driver's license, passport, or resident card.
- Photograph the document.
- Photograph yourself. IDEMIA does a face scan and matches it against the document photo.
- Return to Motus. Verification result populates and you continue.
What you need in hand: a smartphone or tablet with a working camera, good lighting, the actual physical document (not a photo of it on another phone), and your Social Security Number. Login.gov needs the SSN separately, before IDEMIA runs.
The most common failure modes, and what to do at each:
- Glare on the document photo. Use natural light. Tilt the document 30°. Don't shoot through plastic sleeves. If IDEMIA rejects three times, you're routed to in-person verification.
- Selfie rejection. Hat, sunglasses, beard change since the ID photo, low light. Same fix sequence; same fallback to in-person.
- Address mismatch on Login.gov. Login.gov verifies your phone or your address by mail before IDEMIA runs. If your phone isn't in your name, address-by-mail adds 5–10 business days. Start now if your phone is in a spouse's or company's name.
- In-person fallback. Login.gov uses participating USPS post offices for in-person identity proofing — find one through the link on Login.gov's identity verification help page. Bring exactly the documents Login.gov tells you to bring; don't improvise.
The gap nobody is talking about. Login.gov, IDEMIA, and FMCSA have published nothing specific to non-U.S.-citizen carriers, B2-visa holders, foreign passports, recently-changed names with mismatched IDs, or DBAs. (Login.gov "How to verify your identity" — confirmed silent.) If any of those apply to you, call 1-800-832-5660 before you start the verification — failed verifications go on a record and get harder to clear, not easier.
Processing time: FMCSA hasn't published an SLA. Clean cases finish in under an hour. In-person fallback takes whatever USPS appointment availability looks like in your area — plan for a week, not a day. As Scopelitis Transportation Consulting's Sean Garney put it on FreightWaves: "Just the realness of the photo to verify that's a real person, I think that's huge." The flip side: when the photo doesn't verify, a real person also has to fix it. (FreightWaves, "Motus steps up")
3. The Company Official rule.
This is the rule that quietly kills the third-party-consultant model — and most carriers won't realize until they try to log in and can't.
What it says: the Company Official must be the company owner or an internal, direct employee who oversees registration. Not a third-party transportation service provider, not a freight broker, not an outside consultant. (FMCSA Modernization FAQs)
What it kills: the historical model where a small carrier paid $200–$400 to a filing consultant who handled MCS-150, biennial updates, MC authority renewals, and rule-change responses — using the consultant's own login. That worked under the FMCSA Portal because the Portal didn't strongly bind the human to the registration. MOTUS does. The Company Official has to actually log in, identity-proof through IDEMIA, and click the buttons.
What you can still do: consultants can still advise. They can sit next to you while you file. They can prepare the documents. They cannot be you in the system.
Why FMCSA built this in: the April 29, 2026 Federal Register notice describes Motus as designed to "incorporate enhanced verification tools" and reduce fraudulent activity. (FR Doc 2026-08334) Translation: chameleon carriers — operators who shut down a DOT number after a bad safety record and reopen under a new one — have historically used third-party filers to obscure the operator-entity link. Forcing the officer to identity-proof through IDEMIA breaks the easiest version. (GAO-12-364 put chameleon-attribute carriers at 18% severe-crash rate vs. 6% for clean applicants.)
What to do this week if you've been using a consultant:
- Confirm whose name and email are on your FMCSA Portal account. If it's the consultant's, get the Portal updated to reflect a real Company Official from your company before May 14.
- Get the Company Official a Login.gov account using the same email that's now on the Portal. (See Section 1.)
- Block 60 minutes for the Company Official's IDEMIA verification on a day before May 14, not on May 14 itself.
- Keep the consultant — they can still own the work. They cannot own the login.
The exception nobody has clarified: whether a Power of Attorney or designated agent can stand in for the Company Official under any circumstance. FMCSA's published guidance is silent. Assume no until they say otherwise.
4. The preflight checklist.
Run through this on your phone before May 14 8:00 PM ET. Each item maps back to a section above.
Identity (Sections 1 + 2)
- Login.gov account exists for the Company Official, using the email that matches the FMCSA Portal record. 15 min
- Login.gov MFA configured (text + authenticator app — pick two). 5 min
- SSN on file with Login.gov verifies cleanly. 5 min
- Phone in your name verifies at Login.gov, OR you've requested address-by-mail (allow 5–10 business days). 5 min, plus mail wait
- Government-issued physical ID in hand for IDEMIA (license, passport, ID card, or resident card). 0 min — it's in your wallet
- If you're foreign-born, B2-visa, recently changed your name, or operate as a DBA: call 1-800-832-5660 before attempting verification. 15 min on hold
Authority (Sections 1 + 3)
- FMCSA Portal account is active (not 90+ days dormant). 2 min
- FMCSA Portal Company Official is a real officer / owner / employee — not your filing consultant. 15 min if you have to update
- Company Official email on the Portal exactly matches the Login.gov account email. 0 min if the previous step is done right
- USDOT Number, MC Number (if applicable), EIN, MCS-150 last update date — all known and ready to enter. 5 min
Address
- Principal place of business is a physical street address, not a P.O. Box, not a CMRA. 0 min if it's already true; biennial-update flow if not
- Address matches your insurance certificate of liability and your state DOT registration. 5 min
If you can't complete this list before May 14 8:00 PM ET: the four-day registration outage means anything you don't do this week, you also can't do May 14–18. Plan for May 19 at the earliest. If you have a registration deadline (biennial update, authority renewal, insurance filing) inside that window, get it in by May 13.
What we'll cover next.
Issue #1 of FreightSignal Weekly ships Tuesday May 22 — what MOTUS actually does to fraud and what it doesn't fix. By then we'll have ten days of real data: IDEMIA rejection rates, where carriers got stuck, which failure modes FMCSA didn't anticipate. If something breaks for you, reply to this piece — those replies become the issue.
Locked in the next four issues:
- #1 (May 22): What MOTUS does to fraud — and what it doesn't.
- #2 (Jun 2): The 14 revoked ELDs, deeper — what each vendor said, what each costs to replace, what carriers are actually swapping to.
- #3 (Jun 9): Building an n8n workflow that flags MOTUS-related changes for your fleet.
- #4 (Jun 16): What carrier insurance underwriters are doing with the new MOTUS data.
Subscribe at freightsignal.ai — Tuesdays, 6:00 AM Central. Reply directly. I read everything.
Companion videos on the FreightSignal YouTube channel — same voice, same primary-source rule. Pattern from Issue #1 on: text Tuesday, screen-record companions the same week.
Sources cited in this piece
- Federal Register, "Availability of Motus, FMCSA's New Registration System" (FR Doc 2026-08334, Apr 29, 2026)
- FMCSA, "Registration Modernization FAQs"
- FMCSA Newsroom, "Important Steps You Must Take to Prepare for FMCSA's New Registration System"
- FMCSA URS Identity Verification Fact Sheet (PDF, Mar 2025)
- Login.gov, "How to verify your identity"
- GAO-12-364, "Motor Carrier Safety: New Applicant Reviews Should Expand to Identify Freight Carriers Evading Detection"
- FreightWaves, "Motus steps up: what carriers need to know about new FMCSA system" (secondary, quoted for the Garney/Scopelitis statement)