🇷🇺 Эта статья есть на русском: читать по-русски →  |  Russian & English support: (315) 871-0833
🟢 We work 7 DAYS A WEEK — Saturdays & Sundays included. Call (315) 871-0833 or message us on WhatsApp
English & Русский | (315) 871-0833 | WhatsApp | truckernavi.com

🌐 English | Русский

Claiming Your Existing Authority in FMCSA Motus: Timeline and Verification Steps

Published August 14, 2026 | TruckerNavi Inc | 9 min read

The short answer: claiming an existing USDOT/MC record in FMCSA Motus takes about 30–60 minutes of active work and finishes the same day — when your documents are clean. A failed Login.gov identity scan stretches it to 2–5 days of retries and manual review, and a record already claimed by someone else means a support case measured in weeks. Claiming carries no FMCSA fee: you are not filing anything new, you are proving to the new system that you are the human behind an authority it already knows.

Since May 14, 2026 — the day Motus went live and URS with the FMCSA Portal went dark (official notice: Federal Register 2026-08334, published April 29, 2026) — this claim is mandatory homework for hundreds of thousands of existing registrants. What Motus is and how it changed new applications, we covered in the general Motus guide. This article is only about the claim: how long it takes, where it breaks, and what an unclaimed record eventually costs you.

What is "claiming your authority" — and why is it not re-registration?

Your authority did not move, expire, or reset on May 14. The MC number, the USDOT number, the insurance filings your carrier submitted on Form BMC-91/BMC-91X, the BOC-3 your process agent has on file — all of it stands. What died is the door: the old Portal login and the MCS-150 PIN no longer open anything. Motus only lets a verified human touch a company record, and "claiming" is the one-time procedure that ties your verified Login.gov identity to your existing USDOT/MC record. Until it happens, the record floats: visible to the public in SAFER and L&I, editable by no one.

How long does claiming your authority in Motus actually take?

ScenarioWhat happensTypical time to a claimed record
Clean documents, name matches FMCSA recordLogin.gov setup → ID photos → selfie scan → find company by USDOT/MC → claim30–60 min of work, same day
ID scan fails on glare or dim lightRetake photos: no flash, matte surface, daylight, another phoneSame day to 2 days
Name spelled differently on ID vs FMCSA recordAutomated match fails; manual review or record correction firstTypically 2–5 days
Stale contacts on file (old email, dead phone)Extra ownership checks before the claim goes throughSeveral business days
Record already claimed by a third partyThat person adds you as a user — or an FMCSA support case with proof of ownershipWeeks, depending on the queue
Never claimed at allNext MCS-150 biennial update physically cannot be filedUSDOT deactivation risk + $80 reinstatement fee

These are practical ranges from the 2026 transition, not official service levels — FMCSA publishes no claim-processing SLA. The pattern is consistent though: the technology is fast; the mismatches between your documents and your 2019-era record are slow.

What do you need ready before you open Motus?

Step by step: from Login.gov to a claimed record

  1. Create the Login.gov account and turn on two-factor authentication;
  2. Pass identity verification: photograph the ID both sides, then complete the live selfie scan — the system matches your face against the document photo;
  3. Sign in to Motus with the verified account — there is no separate Motus password;
  4. Find your company by USDOT or MC number and start the claim; expect confirmation questions tied to the record's data;
  5. After the claim: same day, add a second verified user and confirm the MCS-150, address, and contacts are current — stale contacts are exactly what MC hijackers hunt for.

Why does identity verification fail? The four boring blockers

Almost nobody fails the selfie scan for dramatic reasons. The list is dull: glare on the ID (shoot without flash, on a matte surface), a dim room during the live scan, an expired document, and the classic of immigrant paperwork — transliteration drift. If your license says Aleksandr and your 2018 MC application says Alexander, the machine sees two strangers. First fix: another phone, daylight, patience. Second fix: manual review. What you should not do is start the whole exercise the week your biennial update is due — Iakinf below tried exactly that.

The "one verified person" trap: whose Login.gov owns your company?

Verification belongs to a person, not to the company. Whoever passed the selfie scan and claimed the record is the only human who can edit it. If that person is your spouse, your bookkeeper, your former dispatcher, or a filing service — your own Login.gov account opens nothing. Decide up front whose identity holds the keys, and always add a second verified user the same day you claim.

This is the single most expensive surprise of the Motus era for existing companies. The old world ran on a shareable PIN; the new one runs on a face. A face cannot be emailed to whoever happens to be doing the paperwork this month.

What happens if you never claim your record?

Nothing — right up until the day something needs to change. Then everything at once:

"Ten minutes" vs the full story: why the answers online contradict each other

Ask an AI assistant how to update your MCS-150 and you may still get a confident walkthrough of the FMCSA Portal and its PIN — a system that stopped existing on May 14, 2026. Anything written before spring 2026 describes a door that is no longer there. The opposite distortion is newer marketing: "verification takes minutes." Both are true and both mislead. The scan itself takes minutes; the claim as a project — Login.gov, documents, the name your record carries from years ago, the question of who verified — takes an evening when it goes well and weeks when it does not. Plan for the project, not the scan.

Typical scenario (composite) — Dorofey, owner-operator, 3 trucks, Chicago: read about the transition in July, picked a quiet Tuesday evening, pulled his SAFER record first and checked every spelling against his license. Login.gov account — 10 minutes; ID photos on the kitchen table without flash — one retake; selfie scan — passed. Found his company by USDOT, answered the confirmation questions, claimed the record: about 40 minutes total. Next morning he added his wife as a second verified user and corrected a dead phone number on the MCS-150. His biennial update, due in November, is now a ten-minute task.
Typical scenario (composite) — Iakinf, 2 trucks, Jacksonville: postponed the claim until the week his biennial update was due. His license reads Iakinf; the 2019 application, typed by a filing service, says Yakinf — the automated match failed twice, and manual review ate the better part of two weeks. The MCS-150 went in late: USDOT number deactivated, the $80 reinstatement fee, and several days of downtime while two brokers' systems still showed a dead company in SAFER. Total cost of "I'll do it later": about two weeks of nerves and lost loads that the claim itself — 40 minutes for Dorofey — never required.

Don't want to fight Motus on your own?

TruckerNavi walks existing carriers through the claim, the verification, and the MCS-150 cleanup as part of Safety Compliance from $189/mo. Starting a company from scratch? The Authority Bundle — $499: LLC, EIN, MC, DOT, BOC-3, UCR, Clearinghouse, filed through Motus by verified specialists. Russian, English & Ukrainian support.

Authority Bundle — $499 →

Or just call: (315) 871-0833 · WhatsApp

FAQ

Do existing carriers have to re-register in Motus?

No. Authority stands. But you must claim the record via Login.gov before you can manage it. Claiming has no FMCSA fee.

How long does the claim take?

30–60 minutes same day with clean documents; typically 2–5 days after verification failures; weeks if the record is claimed by someone else.

What do I need?

Login.gov with two-factor, an unexpired photo ID, USDOT/MC numbers, EIN, and company details matching the FMCSA record.

Why does the selfie scan fail?

Glare, dim light, expired ID, or name-spelling mismatch between the ID and the record. Retry with another phone in daylight first.

My dispatcher claimed my record — now what?

They add you as a user from their verified account, then you pass your own verification. If they are unreachable — FMCSA support case, weeks.

What if I never claim?

The next MCS-150 biennial update cannot be filed → USDOT deactivation risk, an $80 reinstatement fee, and an easier target for MC hijacking.

Is there a claim deadline?

No published date. Your real deadline is your next mandatory filing — claim well before it.

Can two people be verified for one company?

Yes — and they should be. Each passes their own ID + selfie. Two verified users means no single point of failure.

Related articles