How Carrier Verification Works

These get used interchangeably and they are not the same thing. A USDOT number identifies a company in the federal system — it is how FMCSA tracks safety, inspections and crash data for that entity. Plenty of operations have one and are perfectly entitled to it without being allowed to haul another company's freight for money across state lines.

Interstate for-hire operating authority is the separate permission to do that, and it is what an MC number refers to. An entity can hold a USDOT number while its authority is pending, inactive, or revoked, and the number itself will look entirely normal quoted in an email.

This is why a lookup checks authority status rather than the existence of a number. Passing means active authority, not merely a technical flag indicating the entity is allowed to operate with no authority standing behind it.

The check queries FMCSA's QCMobile service by MC or DOT number and reads back the record as it stands at that moment: authority status, whether the carrier is under an out-of-service order, insurance on file, safety rating, and crash history.

An out-of-service order is the one that admits no interpretation. It means a federal or state enforcement action has prohibited the carrier — or a specific vehicle or driver — from operating. It is not a warning or a score; it is a prohibition, and it is checked on every verification.

Safety rating and crash history are context rather than a pass or fail line by themselves. A rating of satisfactory, conditional, or unrated each means something specific, and unrated is common for newer carriers simply because a compliance review has not happened yet, not because anything went wrong.

The insurance element deserves its own explanation because it is the single easiest thing to fake elsewhere. A certificate of insurance is a PDF. PDFs get edited, and a certificate that was accurate when it was issued says nothing about whether the policy is still in force.

What FMCSA holds is a filing made by the insurer itself — for public liability, the form filed under 49 CFR part 387, and cargo coverage filed separately where it applies. The insurer files it, the insurer cancels it, and the federal record reflects the cancellation. That makes it evidence of current coverage in a way an emailed certificate is not.

It also means a lapse shows up without anyone having to notice. Coverage that ends gets recorded against the authority, and a subsequent lookup returns the changed state rather than the state somebody screenshotted last quarter.

Authority is revoked. Insurance lapses. Out-of-service orders get issued. All three happen to carriers who were entirely legitimate the last time anyone looked, and none of them send a notification to the platforms that checked earlier.

So verification here has a shelf life: it goes stale after 90 days and has to be re-run, and a carrier cannot get paid on a booking with an expired or missing check. The alternative — verify once at signup, treat it as permanent — is what makes a lapsed or revoked authority invisible for as long as the account stays open.

Practically, the thing to avoid is discovering the expiry at the worst moment. Re-running the check is quick, and doing it before a load is booked rather than when payment is due keeps a stale record from holding up money that is otherwise ready to move.

FMCSA verification establishes that an authority exists, is active, and is insured. It does not establish that the person typing into the account is connected to it. Those are separate claims and they fail separately.

MC and DOT numbers are public information — that is the point of a public register. Anyone can read a real, active, well-insured carrier's details and repeat them. What they cannot do is produce that carrier's identity on demand, which is why identity verification here is its own check against a real name, date of birth and government ID.

Both are required, and independently, to book a load or post publicly on the board. A stolen MC number does not get an account past the second check, and an identity with no active authority behind it does not get past the first.

The Government Contracts board requires both checks together rather than either one alone. It is the same pair of checks used everywhere else on the platform, with both made mandatory at once for that board.

If an authority check fails, read what actually failed before assuming the worst. Pending authority on a new entity, an insurance filing that has not posted yet, and a genuine revocation look different in the record and have completely different fixes — the first two resolve on their own timeline, the third does not.

Where the federal record is wrong, the correction has to happen at the source: FMCSA's record is what gets read, so a platform cannot override it, and would not be worth much if it could. Once the record updates, re-running the lookup picks up the change.