What the REVOKE Act Adds to MOTUS - Registration enforcement and the fight against chameleon carriers
By Eli’sha E. Petite Sr., TRS, CPIA President & CEO, ASE Insurance Agency LLC DBA TheTruckersInsurance.com
Legislative analysis and opinion | September 21, 2026
A trucking company can change its name without changing the people making its safety decisions. When an operator uses a new business identity to escape an enforcement order or conceal a troubled compliance history, the public may encounter the same unsafe operation under a different name.
That is the concern behind chameleon carriers. It also raises a fair question about the proposed REVOKE Act: if FMCSA’s MOTUS registration system is supposed to make fraudulent identities harder to use, why does Congress need to act?
My view is that the proposal can reinforce registration enforcement, but its value depends on how it works with existing law. Better identity verification, sound eligibility decisions, and effective enforcement serve different purposes. A new registration platform cannot substitute for all three.
H.R. 10237, the Registration Enforcement for Vehicle Operations of Known Evaders Act, was introduced by Representative David Taylor with Representative Shomari Figures on September 2, 2026. The official record reviewed for this article lists referral to the House Transportation and Infrastructure Committee as its latest action. This article analyzes the introduced proposal, not an enacted requirement. H.R. 10237 bill record.
What MOTUS contributes
MOTUS is FMCSA’s modernized registration system. Its purpose extends beyond chameleon carriers: it consolidates registration functions, supports transactions and filings, and introduces stronger verification and validation. FMCSA’s rollout notice describes access to existing agency information and safety data, alongside tools for managing registration records. FMCSA notice on MOTUS.
FMCSA’s modernization guidance describes individual identity proofing and business verification. These controls can make it harder for someone to impersonate a legitimate carrier or submit a registration using an invented identity. The guidance also distinguishes a USDOT identifier from safety registration and explains that some policy changes require later implementation. FMCSA modernization FAQs.
But verifying that a person exists and a company is legally formed does not establish that the people controlling that company are eligible to operate it. A real person can submit accurate identification while concealing an important relationship with a prior carrier. A valid business filing can coexist with an undisclosed manager, an unsafe maintenance program, or a misleading account of who actually directs the trucks.
That distinction explains the remaining work. Investigators and registration personnel need usable evidence of control and continuity, not merely a successful identity check. Technology can help organize and flag information; someone must still determine what the information proves.
FMCSA already has tools to address evasion
The agency does not have to wait for REVOKE to confront reincarnated operations. Existing federal law establishes registration eligibility and provides grounds and procedures for suspension or revocation. Another provision addresses related businesses used to evade requirements or hide noncompliance, including arrangements involving common ownership, management, control, or family relationships. 49 USC 31134; 49 USC 31135.
Under 49 CFR 386.73, FMCSA can order qualifying reincarnated or affiliated carriers out of service and consolidate their records when a new identity or affiliate is used for specified forms of evasion. The rule considers operational continuity and relationships involving management, vehicles, drivers, facilities, and other evidence. It also provides administrative review procedures. 49 CFR 386.73.
For operating authority applications covered by 49 USC 13902, the statute requires disclosure of specified relationships with other carriers, brokers, freight forwarders, or applicants during the preceding three years. That is an existing disclosure obligation, not a new invention of this bill. 49 USC 13902.
These authorities matter to the policy debate. Saying that FMCSA currently lacks any power to stop a chameleon carrier would overstate the gap. The more useful question is whether the registration process consistently identifies disqualifying circumstances, connects related records, and produces timely, supportable decisions.
What the proposed bill changes
REVOKE would amend 49 USC 31134 to expressly require an active USDOT number for operations requiring registration under that section or chapter 139. It would condition issuance of an active number on a determination that the applicant satisfies registration requirements. It would also direct immediate inactivation if the registrant has no valid registration under either statutory route, or fails to make a required periodic update. REVOKE Act introduced text.
The proposed reinforcement is a more explicit statutory connection between registration eligibility and an active identifier. FMCSA already warns that failure to complete a biennial update can lead to deactivation, so REVOKE should not be described as inventing that consequence. FMCSA biennial update guidance.
Component | Contribution | Practical limit |
MOTUS | Registration transactions, identity checks, and more consistent information. | Verified identity alone does not establish safe operations or reveal every concealed controller. |
Existing law | Eligibility review, action against evasion, and consolidation of related records. | Investigators still need evidence and a defensible determination. |
REVOKE proposal | A clearer statutory link between active USDOT status and registration requirements. | It does not supply a new carrier matching algorithm or guarantee that evasion will be detected. |
The distinction also protects against another misunderstanding: an active USDOT number is not a substitute for whatever operating authority a particular business must hold. Registration categories differ. Some private or exempt operations do not require the same operating authority as regulated for-hire transportation. Status must be evaluated against the actual operation. FMCSA notice on MOTUS.
How a change of identity can conceal the same operation
Consider a hypothetical carrier with repeated safety failures and an enforcement order. Its owner closes the company. A new company appears under a relative’s name, using many of the same trucks and drivers. The former owner continues selecting loads, directing dispatch, and deciding which repairs to postpone.
The relative may pass an identity check. The new company may appear in a state business registry. Neither fact answers the central question: who controls the operation, and is the new identity being used to evade the consequences imposed on the old one?
A meaningful review would examine the arrangement as a whole. Who purchased or leased the equipment? Who hires and pays the drivers? Who controls the accounts and dispatch decisions? What explains the timing of the closure and the new application? What corrective action actually changed the safety practices?
Existing anti-evasion authority supplies the framework for evaluating that evidence. My assessment is that REVOKE could reinforce the resulting registration decision through clearer active-status requirements. It would not eliminate the need to uncover the relationship in the first place.
Shared equipment, a family connection, or a common address can warrant questions without proving evasion. A legitimate sale or succession may have a straightforward explanation. The objective should be to establish responsibility accurately, with a fair opportunity to address adverse findings, rather than treat every connection as wrongdoing.
Why trucking insurance has a stake in the outcome
For insurance underwriting, the practical concern is continuity of risk. A new company name does not by itself establish that maintenance improved, unsafe dispatch practices ended, or the people responsible for recurring losses left the operation. When the risk continues, the history remains relevant to evaluating it.
That is why I believe the industry should support reliable disclosure and meaningful scrutiny of prior operations. A carrier with a difficult history should be able to demonstrate corrective action. It should not gain an advantage simply because a fresh application makes that history less visible.
For a newly formed or reorganized trucking business, an insurance review should address the people exercising control, their prior transportation businesses, relevant loss information, the equipment and drivers transferring into the operation, and the reasons for the change. Those are underwriting questions; they are not a claim that REVOKE creates a universal insurance application or a new mandatory insurer database.
I would also distinguish formation of a new entity from correction of the underlying exposure. Evidence of correction could include completed maintenance repairs, documented driver qualification reviews, changed management responsibilities, and sustained oversight. Paperwork should describe the real operation, and the real operation should support the account given to the insurer.
Better information can support more informed risk selection and help compliant carriers compete on fairer terms. It cannot promise an individual premium reduction, eliminate crash losses, or establish the outcome of a coverage dispute. Underwriting and claim decisions still depend on the relevant facts, policy terms, and applicable law.
Strong enforcement requires accurate records
There is a second side to active-status enforcement: the records used to make the decision must be reliable. A company experiencing a system problem is not automatically an evader.
FMCSA’s posted MOTUS transition notice supplies a concrete example. Following the May 19 launch, the agency temporarily suspended USDOT inactivation for entities missing required biennial updates since June 1, citing transition-related access and system issues. The notice was last updated June 22, 2026. FMCSA MOTUS transition relief.
That experience makes the proposed immediate-inactivation language an implementation issue worth examining. Lawmakers and FMCSA should explain how verified filing failures, system outages, correction requests, and disputes over the underlying record would be handled. A missed obligation and an unsuccessful attempt to comply because of an agency system failure deserve careful factual treatment.
I support consequences for evasion alongside clear notice, workable correction channels, and review of mistaken identity or affiliation findings. A credible enforcement program should be capable of stopping an unsafe reincarnation and protecting a legitimate carrier from an inaccurate match.
What responsible carriers can do now
A carrier does not need to wait for a new statute to make its own history understandable. These practices support cleaner registration and insurance discussions today.
1. Keep a clear record of control. Maintain accurate ownership and management information, including who actually directs dispatch, hiring, maintenance, and finances. Explain changes in those responsibilities.
2. Disclose prior operations accurately. Answer registration and insurance questions completely. Identify relevant prior entities, affiliations, and histories within the scope of the question. Do not assume a new name makes an earlier operation irrelevant.
3. Document legitimate business changes. Retain purchase agreements, equipment transfers, leases, and management records that explain an acquisition, reorganization, or closure. The documents should match what happened in practice.
4. Verify the status required for the work. Check the registration and authority applicable to the actual operation, together with required filings. Resolve inconsistent records and retain evidence of submissions and support requests.
5. Show the safety correction. If the earlier operation had deficiencies, document what changed, who is accountable, and how the business confirms that the change continues. A renamed company is not evidence of improved performance.
Judge success by the carriers the system actually stops
The meaningful test is whether an unsafe operator can still return under a concealed identity after adverse action. Counting registrations processed or identities verified will not answer that question by itself.
I would want to see evidence that suspicious relationships are reviewed promptly, supported findings lead to effective action, relevant histories remain visible, and incorrect matches are corrected. These are measures I recommend for evaluating the program, not reporting requirements stated in REVOKE.
A separate technology-focused proposal, the SAFE Act, addresses another part of this problem. Its sponsors describe development of an automated tool to flag suspicious registration applications while retaining human review. That proposal should not be confused with the narrower statutory changes in REVOKE. Senators Young and Kim on the SAFE Act.
My position is that REVOKE can be a useful addition to the registration system. MOTUS can provide better information and stronger verification; existing law supplies substantial enforcement authority. The proposed legislation would reinforce the connection between eligibility and active registration status. The public benefit will depend on how reliably those parts work together.
A responsible trucking business should be able to grow, change ownership, or correct past problems. What it should have to carry forward is an honest account of the people, operations, and safety decisions behind it.
For a review of how a business change affects the information your trucking insurance program needs, contact ASE Insurance Agency LLC DBA TheTruckersInsurance.com. Bring the ownership, operations, equipment, and loss-history records that describe the business as it actually operates.
Frequently asked questions
Is REVOKE already law
The official record reviewed as of September 10, 2026 identifies H.R. 10237 as introduced and referred to committee. The analysis above concerns the introduced bill. Legislative text and status should be checked again before relying on a future version. H.R. 10237 bill record.
Does MOTUS verification prove a carrier is safe
Identity and business checks establish different facts from a safety review. In my assessment, a verified registration profile should prompt accurate due diligence, not substitute for evaluating the carrier’s operations and compliance history.
Is voluntary revocation evidence of a chameleon carrier
No. FMCSA provides a legitimate process for voluntarily revoking operating authority. The concern is whether a new identity or related business is used for evasion. Closing, selling, or reorganizing a business does not establish that by itself. FMCSA voluntary revocation guidance; 49 CFR 386.73.
Would the bill automatically ban an owner with prior crashes
The introduced text does not establish a crash-count threshold or an automatic lifetime owner ban. Eligibility and enforcement still require application of the relevant law to the facts. REVOKE Act introduced text.
Sources and legislative record
Primary authorities reviewed September 10, 2026. Statutes, agency guidance, and proposed legislation serve different roles; the article identifies those distinctions where they affect the analysis.
1. H.R. 10237 bill recordIntroduced bill, sponsors, referral, and latest action listed in the official record.
2. REVOKE Act introduced textProposed amendments to 49 USC 31134 concerning active USDOT numbers.
3. FMCSA notice on MOTUSApril 29, 2026 notice describing the registration platform, phased rollout, and existing statutory framework.
4. FMCSA modernization FAQsAgency explanations of identity and business verification and modernization implementation.
5. 49 USC 31134Current registration eligibility, suspension, revocation, and updating provisions.
6. 49 USC 31135Safety registration and related-business provisions addressing evasion and concealment.
7. 49 USC 13902Operating authority registration and specified three-year relationship disclosures.
8. 49 CFR 386.73Agency authority and procedures concerning reincarnated or affiliated carriers and record consolidation.
9. FMCSA biennial update guidanceExisting agency guidance connecting biennial update failures with deactivation.
10. FMCSA MOTUS transition reliefPosted transition relief for specified biennial updates; last updated June 22, 2026.
11. FMCSA voluntary revocation guidanceAgency procedure demonstrating that voluntary revocation is an established registration action.
12. Senators Young and Kim on the SAFE ActJuly 28, 2026 sponsor announcement describing a separate suspicious-application screening proposal.
