Broker guides

FMCSA Motus Says Your Broker Authority Is Pending: A 7-Check Diagnostic

broker authority pending Motus

An MC docket number is not the same thing as permission to begin brokering freight. In 2026, a new-authority broker should treat the reason shown on the operating-authority card in Motus as the starting point, then reconcile that reason against the financial-responsibility filing, process-agent filing, legal business identity, FMCSA notices, and the public record.

That distinction matters during the Motus transition. FMCSA says its legacy Licensing & Insurance (L&I) system has been historical-only since May 14, 2026, and that Motus filings are not reflected there. An L&I screen can therefore be useful history without being reliable evidence of a current Motus filing.

This guide provides an evidence-first diagnostic for freight brokerage owners and new-authority teams. It is operational guidance, not legal advice, and it does not replace instructions or a decision from FMCSA.

Quick answer: what should you check first?

Open the company account in Motus and locate the operating-authority registration. Confirm the authority type and docket number, then copy the exact status and the specific reason displayed beneath it into a dated worksheet. FMCSA says Motus keeps the familiar authority status names but adds the reason behind a status; its company-account guidance says a pending application can identify missing insurance or process-agent filings.

Do not start with an old L&I result, a provider’s invoice, a submitted-form PDF, or the fact that a docket number exists. Those may be supporting evidence. The current application card and the final FMCSA grant are the decision evidence.

The 7-check pending-authority diagnostic

1. Confirm that you are reading the right authority

Write down the legal business name, USDOT number if assigned, docket number, authority type, and application date shown in the company account. Motus assigns one unique docket number to each newly granted authority, even when multiple authorities were requested in one application. Existing authorities can still share a docket number.

This prevents a common desk error: attaching a filing or notice to the company but not to the authority actually under review.

2. Preserve the exact status reason

Record the status and reason verbatim, along with the date and the authorized user who checked it. Do not rewrite “pending” as “almost active.” Do not infer that a missing item has cleared because a vendor says it was submitted.

Use four worksheet columns:

| Motus observation | Supporting evidence | Owner | Next check | |---|---|---|---| | Exact authority status and reason | Dated Motus capture or downloaded notice | Company official | Date and trigger for recheck |

The worksheet is an internal control, not an FMCSA form.

3. Reconcile the legal identity before chasing timing

Compare the legal name and business address on the authority application with the records used by the surety or financial institution and the process-agent filer. FMCSA warns that deviations between pre-registration records and the operating-authority application delay a grant.

Check punctuation, entity suffixes, former names, assumed names, suite numbers, and address changes. If a mismatch exists, determine which source record is wrong and follow the official correction path. Repeatedly resubmitting the same mismatched information creates more artifacts, not better evidence.

4. Verify the BMC-84 or BMC-85 as a filing—not merely a purchase

FMCSA requires a property or household-goods broker to maintain $75,000 in financial responsibility through a BMC-84 surety bond or BMC-85 trust fund agreement. The financial-responsibility provider makes the filing on the applicant’s behalf.

Ask the provider for a confirmation that identifies:

  • the exact legal entity;
  • the correct docket number;
  • the form type;
  • the filing date or submission reference; and
  • whether the filing was accepted, rejected, or still processing.

A quote, payment receipt, executed agreement, or certificate may prove a commercial transaction. It does not by itself prove that FMCSA associated an accepted filing with the pending authority.

5. Verify the process-agent filing separately

BOC-3 is a separate authority prerequisite. Preserve the filer confirmation and compare its entity name and docket number with the application. In Motus, the operating-authority record should ultimately show the relevant process-agent detail for a granted authority.

Do not merge the bond/trust and BOC-3 rows into one “compliance complete” checkbox. Different parties may submit them, and either can be the unresolved item.

6. Read the FMCSA notice and calendar from the official event

FMCSA’s current insurance-filing page says that, after an authority application, the financial-responsibility provider must file the appropriate form. If the entity has not complied within 20 days of publication in the FMCSA Register, FMCSA serves a decision saying the application will be dismissed unless compliance occurs within 60 days.

Use the actual publication date and the actual notice—not the day someone bought a bond—as the source for any deadline worksheet. If a notice and the Motus reason appear inconsistent, submit an FMCSA Contact Center ticket or call 800-832-5660 rather than inventing a deadline.

7. Separate private application status from public operating proof

Use Motus to diagnose the private application. Use SAFER and current FMCSA-issued authority documents as public/final cross-checks. FMCSA defines SAFER’s “AUTHORIZED FOR” display as listing the specific operating authorities the broker or carrier may exercise; “NOT AUTHORIZED” means the entity has no operating authority and/or is not authorized for interstate, for-hire operations.

Do not use the legacy L&I system to verify a new Motus filing. FMCSA’s May 21, 2026 update says L&I is available only for historical motor-carrier records and does not reflect Motus filings.

A practical go-live rule for a new brokerage

Create three internal states:

  1. Application work: application submitted; prerequisites and identity being reconciled.
  2. Grant verification: Motus and FMCSA-issued evidence show the authority was granted; public evidence is cross-checked.
  3. Operations release: a named company official has reviewed the grant evidence and separately confirmed that any other applicable business, contractual, and compliance prerequisites are ready.

The framework is intentionally conservative. A provider submission confirmation resolves an evidence question; it does not substitute for FMCSA’s authority decision. A docket number identifies a matter; it does not prove permission to operate.

The evidence packet to keep

Keep one dated folder for the authority containing:

  • the Motus authority card status and reason;
  • application confirmation and docket number;
  • BMC-84 or BMC-85 provider filing confirmation;
  • BOC-3 filing confirmation;
  • legal-name/address reconciliation notes;
  • FMCSA Register publication and subsequent notices;
  • grant letter or certificate when issued;
  • public SAFER cross-check; and
  • owner, date, and rationale for the internal operations-release decision.

Redact personal information before sharing the packet outside authorized staff. Use official `.gov` destinations and access Motus from FMCSA’s Registration Modernization Resources Hub rather than from unsolicited email links.

Public facts versus ServeOps functionality

The Motus, authority, filing, and SAFER statements in this guide are public facts attributed to FMCSA. The seven-check method, worksheet, and three-state release rule are original editorial frameworks; they are not FMCSA requirements.

This guide makes no claim that ServeOps applies for authority, submits or validates BMC-84/BMC-85 or BOC-3 filings, monitors Motus, changes an FMCSA status, or guarantees a grant. Any TMS capability needed by your brokerage should be demonstrated with current product evidence.

Verified ServeOps offer only: 60-day free trial; card collected upfront; no charge for 60 days; cancel anytime; then $49 per seat/month or $490 per seat/year.

After the authority evidence is under control, you can use a trial to test your brokerage’s operating workflow with synthetic or properly authorized data.

Start a 60-day ServeOps trial

Sources