Motus and your USDOT MCS-150 update: what changed

If you last did your USDOT MCS-150 update on the old FMCSA Portal, you will not recognise the process. On 19 May 2026 FMCSA's new registration system, Motus, took over the Portal's registration functions. The sign-in changed, the account rules changed, and the first few months were bumpy enough that FMCSA paused deactivations. Here is what is different, what is the same, and how to avoid the problems carriers have reported.

What replaced the FMCSA Portal?

Motus is FMCSA's registration system. It handles new USDOT numbers, updates, reactivations and related changes that used to run through the Portal. Fraud was part of the backdrop. CCJ reported that FMCSA said Motus had blocked "thousands" of bad actors, even as carriers complained of glitches.

For the honest carrier, the main change is more identity checking up front. That is the price of a system built to keep fakes out.

How do I file an MCS-150 update in Motus?

The broad steps for a USDOT MCS-150 update are these.

1. Create or sign in to a Login.gov account. It is the government's single sign-in.
2. Claim your company. A company official, such as an owner or officer, does this the first time.
3. Open the company record and start the update.
4. Work through each section, confirm the details and certify.
5. Submit and keep the confirmation.

We go through the form in detail in our MCS-150 walkthrough, and the rule behind it is in our deep dive on the biennial update.

FMCSA's own data notes show the change under the hood. The Motus carrier dataset warns:

The legacy registration system allowed multiple OAs per docket number

In plain terms, the data behind Motus records operating authorities differently from the system carriers were used to.

Who can sign in for a carrier?

This is the part that tripped people. Under the old Portal, many offices shared a single PIN. Under Motus, the account belongs to a person. A company official owns it. A service provider, such as a compliance firm or a trusted employee, can be connected to it with the official's approval.

The point of that is accountability. If your bookkeeper filed your last update, check that they are connected to the new account. Otherwise they will be locked out on the day it matters.

What the rollout looked like

The rollout was rough. Overdrive reported mounting problems, and FMCSA responded by suspending USDOT deactivations for missed biennial updates. The pause covers updates due on or after 1 June 2026. It has no end date, and we cover the details here.

Here are the problems carriers reported most, with our suggested workaround:

A short story

Let us invent a carrier, Greystone Transport. Its owner, Dev, always let his bookkeeper handle the MCS-150. In June the bookkeeper tried to sign in with the old Portal PIN and could not. The USDOT number ended in 57, so the update was due in July of odd years, 31 July 2027. No panic. But Dev took the hint, set up Login.gov, claimed the company, and connected the bookkeeper as a provider. It took him twenty minutes in an evening. The next time it will take two minutes.

What stays the same

The rule has not moved. 49 CFR 390.19 still sets a 24-month cycle, and your due month still comes from the last digit of your USDOT number. If you want to check your date, our MCS-150 due date guide shows how. The filing is still free.

What we would do now

Create the Login.gov account and claim the company before you need to. Then run your number through the free check to see what FMCSA currently has on file, and update anything that is out of date. The MCS-150 guide covers the rest.

A checklist for your first Motus sign-in

Do this when nothing is urgent, not on the day an update is due.

1. Create a Login.gov account if you do not have one. It asks for a second step when you sign in, so keep your phone or key nearby.
2. Sign in to Motus as the person who owns the company.
3. Claim the company by its USDOT number, and follow the identity checks.
4. Look at your record. Is anything out of date?
5. Connect any bookkeeper or filing service that acts for you.

What this means for service providers

If you run a small dispatch or compliance shop, Motus changes your daily work. You cannot use a shared PIN. Each carrier has to approve you before you can act. That is slower the first time and safer every time after. Keep a written record of each approval, the date, and the person who gave it. Those records protect you if a carrier later disputes who filed what.

Why this matters for the MCS-150 itself

The sign-in is a means to an end. The end is a correct record, because the data you enter in your USDOT MCS-150 update is what brokers, insurers and the UCR Plan's Auto-Renew read. If you want to see what it says today, use the free check. If it looks stale, our MCS-150 guide shows what to correct.

A word on security

Login.gov is built around personal accounts and a second step at sign-in. That is good for the system and slightly annoying for a small office that used to share one login. Resist the urge to share. If two people need access, each should have their own Login.gov account, and the company official connects the second person. When someone leaves, the official can remove them. A shared password cannot do that.

For a small carrier the practical rule is simple: one owner, one named backup, and a note of who has access. Then your USDOT MCS-150 update never depends on one person's phone being charged.