Freight Fraud Glossary

Why the gap between what a term proves and what it implies matters

A verification term like 'active broker authority' proves that a specific MC number is registered with active status in FMCSA's system. It does not prove that the person presenting it has any connection to the company that registered it, or that the company is the one behind the current communication. The gap between what a term formally proves and what a reader instinctively assumes is where many verification breakdowns start. For adjacent verification steps, compare this with What Is Freight Fraud?, FMCSA Broker and Carrier Fraud Guide, and SAFER Company Snapshot Guide.

Glossary terms in freight operations carry implicit assumptions that experienced operations staff stop noticing over time. 'Carrier packet' sounds like a complete document set; practitioners know it's only as complete as what was actually included and whether each item was checked against independent records. 'POD' is treated as final; who signed it and whether the receiver confirms delivery are separate questions the POD itself doesn't answer.

The definitions in this guide are written to surface those gaps rather than paper over them. Knowing what each term formally establishes — and what it leaves open — is more useful than a clean definition, because it tells you where the next check belongs.

Terms that matter most for verification and documentation workflows

Freight fraud prevention relies on a specific set of documents, authority designations, and official records. Using the same terms consistently across a team — and understanding what each term actually proves versus what it implies — reduces both miscommunication and the risk of acting on an unverified assumption.

This glossary supports document review and verification workflows, not legal analysis. Each definition notes the most common mistake associated with that term, because the misunderstandings tend to be more practically useful to know than the definitions themselves.

Records that reveal the pattern

Use the same identifiers across every record. Small differences can be clerical, but they should be resolved before pickup, dispatch, or payment.

If a detail is missing, ask for the missing record rather than filling the gap from memory, an old packet, or a search result.

What to preserve from the transaction

Save records in their original format when possible. Use one folder named with the load number, lane, date, and parties involved.

If a dispute, identity concern, or theft concern appears later, the timeline is easier to reconstruct when emails, PDFs, screenshots, call notes, and lookup results are grouped together.

Questions to ask when verifying identity

Questions should be specific and tied to records. That keeps the conversation professional and avoids unsupported accusations.

If an answer changes the transaction, document the person, date, time, and channel used to confirm it.

Common assumptions to avoid

One detail checking out is not the same as authorization confirmed. A correct number, a recognized company name, or a well-formatted document can each appear in a transaction where the communicating party has no connection to the registered entity.

A warning sign is a reason to document and verify, not a finding. Record what prompted the concern and what check it led to — that record determines whether the situation can be addressed if it escalates.

When to escalate the concern

When the file still has gaps, slow the transaction enough to preserve the record and move the question to the right channel.

That may mean a direct call-back, a shipper or receiver confirmation, an internal escalation, an insurer or claims contact, or an official complaint or reporting resource where appropriate.

Source Notes

FAQ