Freight Fraud Glossary

How this comes up in practice

A dispatcher, accounting lead, and claims contact review the same file after a load goes sideways. One person calls it double brokering, another calls it carrier identity theft, and a third calls it non-payment. Each label points to a different evidence path. Before anyone drafts a complaint or sends the file outside the company, the team rewrites the timeline using neutral terms: who sent the rate confirmation, which carrier appeared on the BOL, what the SAFER callback confirmed, when the POD was submitted, and which payment instruction changed. The glossary matters because it keeps the file from turning into a pile of conclusions. A shared vocabulary helps the team describe the pattern while the records are still being checked.

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

Start with the identity trail: the first message, the company name used there, and the MC or USDOT number that later appears in documents. In this guide, that starts with terms that appear in authority, insurance, bond, document, and incident records.

A pattern becomes easier to evaluate when each name, number, domain, and phone number is tied to the moment it entered the file. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Where the pattern becomes visible

For freight fraud glossary, the useful record is usually the one that shows where terms that appear in authority, insurance, bond, document, and incident records first entered the file.

That record is stronger when it sits beside the dated lookup, the original message, and a note from the party connected to the transaction. It is weaker when it has been renamed, cropped, forwarded without headers, or separated from the transaction timeline.

A practical stopping point

Hold the booking, dispatch, pickup, or payment decision when the file depends on a new contact path, revised document, missing official record, or mismatch that no one has explained.

The pause should be narrow and written down: the field that does not line up, the source used to check it, and the person or channel that must answer before the work continues.

What to preserve from the transaction

For basic fraud-pattern review, preserve the earliest version of each document before later corrections blur the timeline. In this guide, that starts with terms that appear in authority, insurance, bond, document, and incident records.

Keep the documents beside the message thread that introduced them, because the sequence often matters more than a single mismatch. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Questions to ask when verifying identity

Ask questions that separate an operational mistake from an identity concern without accusing a party too early. In this guide, that starts with terms that appear in authority, insurance, bond, document, and incident records.

Good answers point to a record, a known contact, or a dated confirmation rather than a general assurance. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Common assumptions to avoid

Fraud basics are most useful when they slow down conclusions. A familiar brand, correct MC number, or polished packet can still be used by an unauthorized sender. In this guide, that starts with terms that appear in authority, insurance, bond, document, and incident records.

The safer habit is to write down the gap and the check it triggered, then decide whether the records resolved it. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

When to escalate the concern

Escalation begins when the file still has an identity gap after ordinary confirmation steps. In this guide, that starts with terms that appear in authority, insurance, bond, document, and incident records.

Move the issue to an internal lead, known company contact, insurer, law-enforcement contact, or official reporting channel based on what the records show. Keep the question practical: what changed, who introduced it, and which dated record can be saved before anyone acts on it.

Source Notes

FAQ