Where Our Data Comes From

The sources

We mirror FMCSA's public datasets published on data.transportation.gov: the carrier census (registrations and company details), authority histories (applications, grants, revocations, reinstatements), and insurance histories (filings, replacements and cancellation notices). Nothing is scraped, purchased from data brokers, or taken from private systems — these are the same records anyone can download from the government, refreshed at their source every morning.

The refresh schedule

FMCSA republishes the authority and insurance files early each morning (typically committed by 9:30 AM ET) and the census by midday. Our pipeline checks every 15 minutes from 6 AM, ingests the moment new files land, derives lead stages, and delivers digests from 10:30 AM ET. If a federal holiday delays publication, digests say so rather than repeating stale rows, and the next morning's run fills any gap automatically.

From filings to lead stages

Raw filings are events, not leads. We resolve each day's events into nine lifecycle stages — new USDOT registration, MC applied, insurance filed, authority granted, 30 days in, insurance-cancellation pending, suspended (insurance), suspended (BOC-3), and reinstated — and attach the carrier's census record: legal name, location, fleet size, cargo, and the contact details on file. The glossary defines every stage.

Owner contacts and the filing-agent problem

The phone and email on a registration are whatever was filed — and when a registration service filed the paperwork, that's the service's switchboard, not the owner's cell. We detect agent contacts two ways: addresses and numbers that recur across many unrelated carriers, and actors that appear in withdrawal records. Flagged contacts are labeled filing-agent contact in the app and digests, and can be hidden per feed, so your reps spend their dials on owners.

Limits, honestly stated

We publish what FMCSA publishes. If a carrier filed no phone or email, the lead says so. Contact details age as companies move. Cancellation notices are sometimes rescinded when a carrier cures coverage. Census details for the newest registrations can lag their first appearance by a day or two. The daily refresh corrects the record continuously, but no FMCSA-derived dataset is ever perfect — anyone who tells you otherwise is selling the same records with more confidence.

Carrier removal

Carriers who don't want their public record surfaced here can use the removal page; removals apply to all future digests, exports and API responses. Use of contact data is subject to our terms — calls and texts are subject to the TCPA, and subscribers are responsible for how they use the data.