Tomorrow night, 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. The 14 ELDs revoked on March 4 — including the May 4 enforcement deadline that already passed. And a preflight checklist you can run on your phone before the lockout.
Free. Primary sources cited. No vendor pitches. Reply with anything that breaks for you — those replies become Issue #1.
01 · Claim flow
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".
02 · Identity proofing
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:
1.Motus shows you a QR code. Scan it with your phone or tablet — that opens an IDEMIA verification session in your mobile browser. |
2.Pick language, document country, and document type. Accepted: identity card, U.S. driver's license, passport, or resident card. |
3.Photograph the document. |
4.Photograph yourself. IDEMIA does a face scan and matches it against the document photo. |
5.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. |
›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.
"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." Sean Garney, Scopelitis Transportation Consulting · via FreightWaves |
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.
03 · Who can log in
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.
04 · ELD enforcement
The 14 ELDs FMCSA revoked on March 4. Sorted by what to do.
⚠ Deadline passed The May 4 enforcement deadline has already passed. If you're still running one of the 14 devices below, you are non-compliant today. Drivers will be cited under 49 CFR 395.8(a)(1) and placed out-of-service. Discontinue use immediately; revert to paper logs while a replacement ships. |
Per FMCSA Administrator Derek D. Barrs: "Meeting federal requirements isn't optional. If a device falls short, it will be removed." (FMCSA Newsroom)
The list:
# | Vendor | Device | Model |
1 | Club ELD | Club ELD / Android | PT30 |
2 | Club ELD | Club ELD / iOS | PT30 |
3 | DENDRA INC | SAFERLOGS | PT30 |
4 | Egreen ELD | EGREEN ELD | EGREENELD1 |
5 | Gorilla Fleet Safety | Patriot ELD | PE0001 |
6 | Gorilla Fleet Safety | ClearPath ELD | TP-Pro |
7 | Gorilla Fleet Safety | SimpleX 2 Go | SIM2GO |
8 | Gorilla Fleet Safety | LB tech FleetTrack | LBFTELD |
9 | Gorilla Fleet Safety | HCSS Pro | HCSSPR |
10 | Gorilla Fleet Safety | ELDX Pro | ELDXP |
11 | Gorilla Fleet Safety | AllwaysTrack ELD | ALLTRE |
12 | Gorilla Fleet Safety | Gorilla Safety Express | WF-ANDP |
13 | Gorilla Fleet Safety | Command Alkon (Gorilla) | CAGPST |
14 | Gorilla Fleet Safety | Canada & US (Gorilla) | CUSGEOAN |
Reason cited: "failure to meet the minimum requirements established in Title 49 CFR Appendix A to Subpart B of Part 395." (FMCSA Newsroom)
The pattern worth noticing. Ten of the fourteen are Gorilla Fleet Safety devices sold under different brand names. If your dispatch screen says Patriot, ClearPath, SimpleX, AllwaysTrack, HCSS Pro, ELDX Pro, Gorilla Safety Express, Command Alkon Powered by Gorilla Safety, LB FleetTrack, or Canada & US by Gorilla Safety, you're running Gorilla firmware regardless of what the marketing says. Check.
Replacement candidates. FMCSA does not endorse vendors; we're not going to either. The published guidance is one sentence: replace the revoked device with a compliant one from the Registered Devices list. Practical filter to apply:
›Same form factor as what you swapped from (BT-OBD dongle vs. hard-wired vs. tablet-mount). Cuts installation time roughly in half. |
›Same telematics tier (basic HOS vs. integrated DVIR vs. full fleet management). Don't pay for features you weren't using. |
›Vendor on the registered list ≥2 years. Newly-registered vendors carry a higher revocation risk; let someone else stress-test the new entrants. |
›Verify the model number on the ELD list before purchase, not after. Vendors sell variants. Some variants are registered, some aren't. |
Cost-to-comply ballpark (anecdotal — carrier forums, not FMCSA): $200–$600 per truck for hardware, $20–$45 per truck per month for service. Cancellation fees on the revoked vendor's contract are usually waived if you cite the FMCSA revocation in writing — make them say no in writing.
The grace-period question. FMCSA published no extended grace beyond May 4. A driver inspection today is an OOS event. Don't roll the dice.
05 · Run this today
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 + 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 previous step is done |
☐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 |
☐Address matches your insurance certificate of liability and your state DOT registration. 5 min |
ELD compliance · Section 4
☐None of your trucks are running one of the 14 revoked devices. 5 min cross-check vs. Section 4 table |
☐If any are: revert to paper logs today; order replacements; schedule installations. |
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 |
Tuesday May 19 — Issue 1.
The 14 revoked ELDs, deeper. What each vendor's customers are actually swapping to, what the replacements cost, which vendors are honoring cancellation under the FMCSA revocation and which aren't. The Three Signals carry the post-MOTUS launch data — IDEMIA rejection rates, the four-day cutover, where carriers got locked out — so if something breaks for you this week, reply to this piece. Those replies become the issue.
The next two locked in:
›#1 (May 19) — The 14 revoked ELDs: replacements carriers are actually swapping to, real costs, and which vendors are honoring cancellation contracts. |
›#2 (May 26) — What AI dispatch agents actually do: three real fleets, the prompts they ship to drivers, the monthly costs, what broke. |
Subscribe at freightsignal.ai — Tuesdays, 6:00 AM Central. Reply directly. I read everything.
// Off the Dock — Aman Aman Singh Editor · Freight/Signal Hit reply with what broke for you this week. Those replies become Issue 1. |
Sources cited |
FreightWaves, "Motus steps up" (secondary, quoted for the Garney statement) |
Corrections Spot an error? Reply to this email or write [email protected]. Every correction runs in the next issue. | Role preferences Filter the archive by role — Carrier · Broker · Driver · Fleet · Compliance · Executive — at freightsignal.ai/me. | Tip the editor Story tip, source intro, or a tool worth reviewing? [email protected]. Anonymity respected. |
Disclosure
Written by Aman Singh. FreightSignal is published by Logixtecs. Aman builds Freight Passport (carrier identity / KYC), Rigsy (driver recruiting), and Trucker's Routine (driver wellness). MOTUS overlaps with Freight Passport's category — disclosed.