The Safety and Accountability in Freight Enforcement (SAFE) Act requires two parallel responses to operators who try to evade motor‑carrier enforcement. First, it orders the Comptroller General to produce a study of so‑called “chameleon carriers,” their prevalence, the harms they cause, and gaps in DOT enforcement.
Second, it directs the Federal Motor Carrier Safety Administration to plan, develop, test, and implement an automated decision‑support tool to flag registration applications that display indicators of chameleon behavior.
The bill stitches together operational steps — interagency memoranda of understanding for data sharing, a set of technical detection requirements, an appeals pathway for applicants, and a post‑implementation inspector‑general audit — to move the FMCSA from paper rules toward automated screening. For transportation compliance teams, insurers, and state regulators, the Act signals tighter scrutiny of ownership continuity, insurance lapses, and other data points that signal regulatory evasion.
At a Glance
What It Does
The Act requires the Comptroller General to report on chameleon carriers and directs FMCSA to develop, test, and implement an advanced automation tool to flag risky registration applications for Department of Transportation (DOT) numbers. The tool must support interagency data sharing, compile evidence of continuity between entities, detect insurance lapses, and provide decision‑support without making a final automated denial.
Who It Affects
FMCSA registration staff and enforcement units, DOT operating administrations, federal agencies listed for data‑sharing MOUs (Treasury, Justice, DHS, USPS, Commerce, State), State motor‑vehicle and insurance regulators, freight carriers and brokers applying for DOT numbers, and insurers underwriting commercial motor‑vehicle policies.
Why It Matters
If implemented as written, the bill changes how FMCSA screens applicants for DOT numbers — from largely manual checks to automated, data‑driven flagging — and requires interagency information flows and an IG audit that will produce measurable outcome data (flagged/rejected applications, redeterminations, crash impacts). That combination can shift enforcement upstream and alter risk and underwriting decisions in the freight market.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Act contains two distinct but complementary tracks. The first directs the Comptroller General to produce a comprehensive study of chameleon carriers — operators that try to avoid enforcement by reorganizing, renaming, or otherwise masking continuity with a prior noncompliant entity.
The study’s scope reaches beyond anecdote: it must estimate prevalence, map fatalities and serious injuries back to states, quantify property damage, analyze evasion tactics, and identify DOT registration and information‑system gaps. The Comptroller General may work with other federal and non‑federal partners to assemble the necessary data.
On the operational side, FMCSA must design and deploy an “advanced automation tool” for the DOT number registration pipeline. The bill lists concrete analytic signals the tool must consider (ownership and management commonalities, prior DOT numbers, insurance continuity, shared addresses or equipment, advertising and public identity, and other continuity markers).
FMCSA can enter MOUs with a specified set of federal agencies and with relevant state agencies to obtain verification and data feeds needed to power the tool. The statute expressly prevents the tool from issuing a final automated denial; it must instead provide decision support to human reviewers.The bill builds procedural safeguards around flags: applicants denied on the basis of a tool flag must receive notice of the specific factors and get 30 days to correct the application; FMCSA then must redetermine any amended application within 30 days.
The Administrator must also brief congressional committees quickly after enactment and the Department of Transportation Inspector General must audit the tool’s effectiveness two years after implementation, reporting metrics such as counts of flagged and rejected applications, error rates, redeterminations, and any measurable impact on severe crashes.Finally, the Act defines “chameleon carrier” in detail — including operators who reincorporate to avoid FMCSA orders, evade penalties, misrepresent ownership to secure insurance, or reconstitute after insurance cancellation. That statutory definition anchors what signals the automated tool targets and frames potential enforcement and legislative responses that may follow from the Comptroller General’s recommendations.
The Five Things You Need to Know
The Comptroller General must deliver a study to Congress within 1 year of enactment that estimates prevalence, fatalities, injuries, property damage, and methods used by chameleon carriers since a 2012 GAO report and identifies DOT registration and software shortcomings.
FMCSA has 1 year after enactment to develop, test, and implement an advanced automation tool that compiles evidence of substantial continuity between entities, including ownership, management, addresses, equipment, liability insurance continuity, prior DOT numbers, and advertising or public identity.
The tool must include an appeals pathway: applicants flagged and denied due to the tool receive a notice listing flagged factors, have 30 days to correct the application, and FMCSA must redetermine the amended application within 30 days.
The statute forbids using the tool’s automated output as a final, standalone decision; human employees retain responsibility for final determinations, and the Inspector General must audit effectiveness 2 years after implementation, supplying empirical data on flags, rejections, redeterminations, errors, and crash reductions.
FMCSA must enter MOUs with Federal agencies (Treasury, Justice, USPS, DHS, Commerce, State, and relevant DOT operating administrations) and with relevant State agencies to obtain information needed to detect continuity, insurance lapses, or other signals of evasion.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Identifies the Act as the “Safety and Accountability in Freight Enforcement Act” (SAFE Act). This is purely stylistic but indicates Congressional intent to focus the Act on enforcement and accountability in freight operations.
Comptroller General study on chameleon carriers
Mandates a one‑year report from the Comptroller General that is quantitative and diagnostic: prevalence estimates, state‑level counts of fatalities and serious injuries since the 2012 GAO study, property damage estimates, methods used by evaders, and a critical evaluation of DOT registration processes, existing software capabilities, recommended Motor Carrier Management Information System (MCMIS) data‑field improvements, and statutory/regulatory penalties. The Comptroller General may collaborate with federal, state, academic, and private parties to compile data, which matters because meaningful prevalence and harm metrics will shape legislative and regulatory follow‑on actions.
FMCSA must build and coordinate the automation tool; MOUs required
Requires FMCSA to plan, develop, test, and implement the automated decision‑support tool within a one‑year horizon and authorizes collaboration with federal, state, academic, and private partners. The Administrator must execute memoranda of understanding with specified federal agencies (Treasury, Justice, USPS, DHS, Commerce, State, and DOT operating administrations) and with relevant state agencies to secure data feeds. Practically, those MOUs set the terms for interagency data access, retention, and operational responsibility — a prerequisite for the tool’s analytical value and a potential chokepoint for implementation if agencies are reluctant or if data quality is uneven.
Tool detection requirements and scope
Enumerates the analytic signals the tool must evaluate as evidence of ‘‘substantial continuity’’ between entities: evidence the entity was formed to evade rules, prior safety history, reused or inactive DOT numbers, asset purchase considerations, formation/dissolution dates, common ownership or officers, shared contact details, shared equipment or drivers, continuity of insurance coverage, ongoing facilities and operations, and public advertising or corporate identity. It must also detect insurance lapses and aggregate evidentiary elements to present a package for human review. These prescriptive inputs define the tool’s architecture and narrow the universe of allowable signals the FMCSA must track.
Appeals, briefings, limits on automation, data privacy, and IG audit
Sets procedural protections: any denial based on a tool flag must trigger notice that lists the flagged factors and gives applicants 30 days to correct; FMCSA must redetermine amended applications within 30 days. The Administrator must brief congressional committees within 30 days of enactment. The statute explicitly prohibits using the tool’s automated output as a final decision — human reviewers retain final authority — and requires safeguards limiting data disclosure to purposes described in the Act. Two years after the tool is implemented, the DOT Inspector General must audit and report on effectiveness and provide empirical outcome data and improvement recommendations.
Statutory definition of "chameleon carrier"
Provides a detailed statutory definition covering carriers, brokers, freight forwarders, and affiliated parties who reorganize or rebrand to evade FMCSA orders, regulatory requirements, civil penalties, enforcement actions, negative compliance histories, or adverse insurance outcomes; it also covers misrepresentations to insurers and reincorporations after policy cancellations. Embedding that definition in statute focuses both the Comptroller General’s study and the tool’s detection logic on concrete, enumerated behaviors rather than broader, ambiguous notions of misconduct.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Motor‑vehicle safety advocates and road users — better upstream screening aims to reduce operations by operators with poor safety histories, which could lower severe crashes and save lives.
- Compliant motor carriers and brokers — automated screening can level the competitive field by making it harder for noncompliant operators to reenter the market under new identities and undercut safety‑conscious firms.
- FMCSA and enforcement units — decision‑support tools and interagency data feeds should improve efficiency by prioritizing high‑risk registrations for scrutiny and reducing manual detective work.
- Insurers and underwriters — clearer detection of prior continuity and insurance lapses helps underwriters price risk more accurately and avoid underwriting entities that misrepresent history.
- State regulators and law enforcement — MOUs and centralized detection reduce blind spots and provide standardized evidence packages for follow‑up investigations.
Who Bears the Cost
- FMCSA — must allocate staff, procure technology, manage cross‑agency MOUs, and maintain the tool; development and ongoing maintenance are likely to be resource‑intensive.
- Other federal and state agencies — agencies named in MOUs must provide data, coordinate releases, and manage privacy and legal compliance burdens without dedicated funding in the text.
- Legitimate new entrants and small carriers — applicants flagged in error risk application delays and administrative burdens to prove distinctiveness, which can be costly for startups.
- Carriers and brokers with complex corporate structures — increased scrutiny of ownership, insurance history, and common management may raise underwriting costs and require additional documentation.
- Insurers and brokers — expected to respond to information requests and reconcile disparate data sources, which increases administrative overhead and may trigger contract changes.
Key Issues
The Core Tension
The Bill’s central dilemma is balancing stronger, faster detection of repeat bad actors (protecting public safety and honest carriers) against the risk that algorithmic screening and expanded data sharing will slow legitimate market entry, mis‑flag innocent applicants, and funnel scarce agency attention into appeals and remediation rather than frontline enforcement. The Act mandates aggressive detection but leaves the delicate tradeoffs — thresholds, data governance, funding, and due process for new entrants — largely to implementation.
The Act pushes FMCSA toward automated, data‑driven screening but leaves several implementation gaps. The legislation is prescriptive about the tool’s inputs yet silent on funding, data quality standards, model validation methods, and the technical threshold (how many and what weight of signals) that constitutes a ‘flag.’ That ambiguity creates operational risk: agencies must translate lists of signals into scoring, thresholds, and workflow rules — choices that affect false positive and false negative rates and have real consequences for applicants and road safety.
Data sharing and privacy are central practical constraints. The Act requires MOUs with multiple federal and state entities but does not resolve legal or technical barriers to data exchange (e.g., matching algorithms for identities, protected information, or differing retention rules).
The statute prohibits using the tool as a final automated decision, which reduces some legal exposure, but flagged applicants still face potential harm from erroneous flags and administrative delays. Finally, measuring success will depend on baseline data and causal attribution: the IG’s audit must show whether the tool actually reduced severe crashes and not merely increased administrative rejections or paperwork.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.