What NCCDB accepts, what it doesn't, and what a complaint actually produces

NCCDB — the National Consumer Complaint Database — is FMCSA's complaint and tracking system for eligible complaints against motor carriers, brokers, and related entities. Filing creates an official record FMCSA can review. It is not a payment enforcement mechanism, not an arbitration service, and not a guarantee of regulatory action. What it does is contribute to FMCSA's visibility into patterns of conduct across the regulated community. For adjacent verification steps, compare this with How to Report Freight Fraud, FMCSA Broker and Carrier Fraud Guide, and What to Do If a Broker Does Not Pay.

The eligible complaint categories are specific: NCCDB handles complaints within FMCSA's jurisdiction — broker and carrier conduct in regulated freight transactions. It doesn't handle every payment dispute or commercial disagreement between freight parties. Understanding which complaints are eligible before filing determines whether NCCDB is the right channel, or whether IC3, FTC, DOT OIG, or legal counsel applies more directly to the specific situation.

Preparing the complaint file before opening the NCCDB form produces a more complete submission. The records that give a complaint substance — rate confirmation, carrier packet, official lookup screenshots with dates, communications showing what happened and when — are the same records every other process depends on. Building the file once, before any process begins, is more efficient than assembling different documents for each channel in sequence.

Key Takeaways

  • Use the official domain directly when checking records or filing reports.
  • Save the source page URL and access date with your case notes.
  • Check the official FMCSA page for current status before relying on a record.
  • Keep copies of complaint confirmations, report numbers, and supporting documents.

Preparing a complaint file before filing through NCCDB

The NCCDB is FMCSA's official portal for complaints involving motor carrier safety, broker conduct, and registration-related issues. Before filing, the eligible complaint categories are worth reviewing — the NCCDB is not a general fraud reporting system, and complaints outside its defined scope won't be processed through the same review pathway.

A filed NCCDB complaint is not a collection mechanism and doesn't guarantee regulatory action. It creates a record that FMCSA can review, and that record may appear in the complaint search tool — subject to the significant non-endorsement limitations NCCDB itself states on that page. What the complaint does provide is an official documentation channel for eligible issues.

Preparing a complaint file before filing through NCCDB checklist

  • Whether the complaint type falls within FMCSA's eligible complaint categories
  • Whether documentation for the complaint is organized before filing — the form asks for specific records
  • Whether the MC or USDOT number has been confirmed in official records before entry
  • Whether the complaint search results page and its stated limitations have been reviewed
  • Whether a copy of the completed complaint and any confirmation number has been saved

Records to organize before submitting an NCCDB complaint

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.

Records to organize before submitting an NCCDB complaint checklist

  • Use the official domain directly when checking records or filing reports.
  • Save the source page URL and access date with your case notes.
  • Check the official FMCSA page for current status before relying on a record.
  • Keep copies of complaint confirmations, report numbers, and supporting documents.

What to preserve from the complaint submission process

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.

What to preserve from the complaint submission process checklist

  • Original rate confirmation and every revised version.
  • Broker or carrier packet documents, including W-9, insurance, authority, and agreement records.
  • BOL, POD, seal records, pickup number, delivery confirmation, accessorial approvals, and invoices.
  • Screenshots or saved PDFs of official lookup results with the date checked.
  • Messages showing who requested, approved, or disputed a change.

Questions that establish whether NCCDB is the right channel

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.

Questions that establish whether NCCDB is the right channel checklist

  • Which legal entity is tendering, carrying, paying, or receiving the freight?
  • Which official record supports the MC number, USDOT number, authority, insurance, bond, or trust detail?
  • Who is authorized to approve pickup, rerouting, revised documents, or changed payment instructions?
  • What document proves the current instruction, and who should receive a copy?

What an NCCDB complaint doesn't substitute for in a private dispute

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.

What an NCCDB complaint doesn't substitute for in a private dispute checklist

  • Do not assume a public lookup proves the sender is authorized.
  • Do not assume a document is current because it appears complete.
  • Do not assume a red flag proves wrongdoing by itself.
  • Do not assume a missing detail can wait until after pickup or payment.

When the documentation and incident type qualify for NCCDB filing

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.

When the documentation and incident type qualify for NCCDB filing checklist

  • Record the unresolved mismatch in plain language.
  • Save the official lookup result with the access date.
  • Keep the original communication that created the concern.
  • Use official reporting channels for eligible complaints or cyber-enabled incidents.

Source Notes

Source use for FMCSA NCCDB Complaint Guide

These sources are used as verification and documentation references. They should be checked directly for current status, and they do not certify any private party, document, load, or payment instruction.

FAQ

What happens after I file an NCCDB complaint?

FMCSA reviews eligible complaints and may take regulatory action, but NCCDB is not a direct dispute resolution service and does not guarantee a specific outcome for private payment or cargo disputes. Save the confirmation and any case number with your load documentation.

Can I search for complaints filed against a specific broker before working with them?

The NCCDB search tool at ai.fmcsa.dot.gov/nccdb allows searching by MC or USDOT number. The search results come with significant limitations stated on the NCCDB page itself — results are not an endorsement or certification of any company, and not all complaints produce visible public records.

What if my situation doesn't fit neatly into the NCCDB eligible complaint categories?

File with the channel most closely matching your situation, or contact FMCSA directly to ask about the right process. If there's a cyber-enabled element — email spoofing, account takeover — IC3 may be the more appropriate primary channel regardless of NCCDB eligibility. FMCSA's eligible complaint page describes the types of matters NCCDB is designed to handle.

Source References

  • National Consumer Complaint Database Federal Motor Carrier Safety Administration. primary source. Last checked 2026-05-28. Official FMCSA complaint portal for eligible motor carrier, broker, safety, and registration-related issues.
  • Eligible Complaints Federal Motor Carrier Safety Administration. primary source. Last checked 2026-05-28. Explains eligible FMCSA complaint categories and jurisdiction boundaries.