From Database to Enforcement: How Aggregated Complaint Data Is Reaching the Agencies That Need It

When Trunk scraped complaint records for 23,789 registered movers from FMCSA's Protect Your Move database and aggregated them nationally, the goal was to answer questions FMCSA wouldn't: What is the most common complaint category? Which companies are worst? Where are the shell company networks?

The data answered those questions. But what happened next was more significant than the answers themselves. Consumer advocates, legal professionals, and investigative journalists started using the aggregated data in enforcement filings, attorney general referrals, and news investigations. The data that FMCSA collects but won't publish in aggregate is now reaching the agencies and newsrooms that can act on it.

The pipeline works like this:

1. FMCSA collects consumer complaints through the NCCDB. The data is available one company at a time, with no aggregation.

2. Trunk scrapes every registered mover's complaint history from FMCSA's Protect Your Move site, extracts 14 complaint categories by year, and stores everything in a database with normalized addresses and phone numbers for cross-referencing.

3. The database automatically detects shell company signals: companies sharing addresses, phone numbers, or ownership. It identifies chameleon carriers (new companies replacing revoked ones with the same people). It aggregates complaints by state, region, company type, and category.

4. The results are published as interactive dashboards, exportable PDFs, and investigative articles with rendered evidence documents.

5. Consumer advocates and legal professionals download the PDFs and submit them to enforcement agencies, state attorneys general, and the DOT Office of Inspector General as supporting documentation.

The critical step is #5. Data in a database is potential energy. Data in an enforcement filing is kinetic energy. The aggregation makes it possible, but the advocates make it happen.

In July 2026 alone, Trunk's aggregated complaint data and fraud investigations have been submitted to or cited by:

- FMCSA regional enforcement divisions (Georgia and Florida Division Administrators, Southern Regional Enforcement, Compliance Enforcement and Investigations unit, PRISM reincarnation tracking unit) - A state attorney general's consumer protection division investigating a broker with 290 complaints - The DOT Office of Inspector General - An FBI referral from local police investigating a carrier whose customers tracked stolen goods to a warehouse shared by four other companies - An investigative journalism series at a major market TV station - Facebook consumer advocacy groups with thousands of members - A university professor and newspaper columnist covering moving fraud

In each case, the data that made the filing or the story possible was publicly available in FMCSA's own systems. It just wasn't aggregated. A state attorney general investigating a broker with 290 complaints could have found those complaints on FMCSA's website, one at a time, if they knew where to look and had the staff to compile them. Trunk's contribution is making the compilation automatic and the patterns visible.

The fact that aggregated complaint data is useful to enforcement agencies proves that the gap is real. If FMCSA published aggregated complaint data by category, company, and region, the advocates and agencies receiving Trunk's PDFs would not need them. The demand for the data is the evidence of the gap.

FMCSA's own Operation Protect Your Move initiative acknowledged this implicitly: the agency cited rising complaint volumes as the catalyst for its 2023 and 2024 enforcement sweeps. But it did not publish the aggregated data that would allow consumers, advocates, or state agencies to independently identify the worst actors. The complaint data went in. Nothing came out.

Trunk is not a replacement for FMCSA enforcement. A database cannot revoke a carrier's authority, impose civil penalties, or refer a case to the Department of Justice. But it can make the case for doing so visible to the people and agencies that have that authority.

The most important development is not any single filing or investigation. It is the feedback loop that is forming.

Consumers report fraud to Facebook groups. Advocates in those groups share Trunk data with enforcement agencies. Enforcement filings generate public records. Public records generate news coverage. News coverage reaches more consumers. More consumers report to Trunk.

This loop did not exist six months ago. The data existed in silos: FMCSA complaints in one system, BBB complaints in another, court filings in a third, Facebook posts in a fourth. The aggregation connects them. The advocacy puts them in motion.

Trunk maintains a running log of these efforts at trunk.lorea.ai/insights/trunk-advocacy-timeline. If you have information about enforcement actions, investigations, or media coverage related to companies or patterns documented by Trunk, report it at trunk.lorea.ai/report-mover.