Our process: how our data is compiled and verified

1. Compile from the right sources

Our team compiles every record from official US registries of transportation businesses and from business sources such as company websites and business listings. We do not buy contact lists and we do not scrape social networks. The source categories are described on the data sources and verification page.

2. Cross-check across multiple sources

A record reaches a file only after it passes checks against separate sources:

Check	What it guarantees in the file
Operating authority	Authority is active today, not only a USDOT registration. New-authority rows also need a recent authority grant.
Revocation pending	Carriers with a revocation pending are removed from the active feeds. They appear only in the dedicated revocation-pending feed.
Registration	The USDOT registration was active when we last checked.
Operation type	The carrier is authorized for hire.
Insurance on file	Liability insurance on file is compared with the federal minimum. New-authority rows must meet it.
Phone	The phone number is validated.
Contacts	Phone numbers and emails that belong to filing services, or are shared by several unrelated businesses, are removed, so the contact that remains looks owner-direct.
Removal list	Anyone who asked to be removed is excluded from every file, dashboard view and API response.
Freshness	The status check is recent enough for the feed (see step 4).

A row in the Active Small Carriers feed passes 8 of these checks, and a row in the New Authority Feed passes 9.

Status comes from current status, never from old events. An authority history is a log of past events: a revocation in it can be old and already cured. We never read that log as today's status.

Pending is not active. A carrier whose authority is still pending does not count as active.

3. Automated verification, specialist spot-checks

Every new build passes automated verification before release, and every continuously updated feed is checked again every day. The verification takes a random sample of rows, spread across states, plus the rows our checks flag, and checks each one: contact validity (phone number format, email format and a mail server for the email domain), authority status and revocation pending, agent and shared contacts, duplicates across unrelated businesses, the removal list and freshness. It also compares the number of rows with the last approved check. A serious failure stops the build and customers keep the previous one; smaller issues above a set rate hold the build for a data specialist. Our data specialists also spot-check samples. The table below shows the date of the last verification of each feed, and whether it was automated or by a specialist.

When a check finds a row that should not have passed, we fix the rule itself and add a regression test, so the same mistake cannot come back in a later build.

The checks in step 2 run on every row; automated verification checks samples and flagged rows, and specialists spot-check samples. We do not claim that each individual row was checked by hand.

4. Refresh on a schedule

Every row carries a last_verified date. A feed is not built or served when its status checks are older than the feed allows: 7 days for the carrier status feeds, 8 days for the weekly new-authority feed and 35 days for the monthly broker feed. When that happens you see "refresh pending" on the site and the API returns a stale_source error instead of old data. The current state of each feed is shown below.

5. Deliver

Download a CSV from your dashboard, pull JSON from the API, or receive events by webhook. Every channel applies the same rules and the same removal list, and every file carries your licence reference.

What we do not claim

• We do not claim the data is free of errors. Records reflect what businesses registered, verified on the date shown.
• We do not check numbers against the National Do Not Call Registry. That is the buyer's responsibility (see CAN-SPAM and TCPA responsibilities).
• Shared subscriptions are not exclusive: other customers can receive the same records.
• When we publish the result of an audit of a sample of records, we state the sample size, the result and the date, and nothing more.