Background

Harmon spent several years in U.S. freight brokerage operations as a carrier compliance coordinator at a regional brokerage handling dry van, flatbed, and temperature-controlled loads across the Midwest and Southeast. Day-to-day work involved reviewing carrier packets — legal name, USDOT number, MC number, insurance certificates, W-9, and dispatcher contact — against FMCSA SAFER and Licensing & Insurance records before any carrier was approved for dispatch.

A consistent problem in that role was the gap between document receipt and actual authorization verification. Packets could look complete and still belong to an impersonated carrier; dispatchers could present genuine credentials for a company they had no relationship with. That desk-level exposure to verification breakdowns drives the editorial standard here: identify which record to pull, compare it to an independently established source, and preserve the original before acting.

After brokerage compliance work, Harmon moved into freight fraud documentation — reviewing transaction files where identity misuse, double brokering, or cargo diversion was suspected, and helping organize records for escalation to FMCSA, bond contacts, or law enforcement. That workflow is the basis for the escalation sequences and document-preservation steps throughout this site.

Editorial Focus

  • FMCSA SAFER Company Snapshot and Licensing & Insurance record comparison
  • Carrier packet review: legal name, USDOT, MC number, insurance issuer, W-9, and dispatcher contact verification
  • Broker authority status and financial responsibility (BMC-84 / BMC-85) cross-checks
  • Dispatch authorization gaps between documented carrier identity and the communicating party
  • Documentation structure for suspected fraud, identity misuse, double brokering, and cargo theft

Review Scope

  • Reviews high-risk wording for unsupported accusations or claims that exceed what official records can establish.
  • Checks that verification steps trace back to FMCSA, FBI, FTC, IC3, CISA, or DOT OIG source material.
  • Keeps legal, financial, insurance, and law-enforcement scope boundaries explicit in every guide.
  • Flags guides where a claimed red flag or escalation step cannot be supported by an official or independently known source.

Review Standards

  • A red flag must be worded as a verification prompt unless a dated official record or transaction document supports a stronger conclusion.
  • Each operational step in a guide should name the document, database, or official source behind it.
  • Checklists should reach the point of preserving the original record before recommending any escalation.
  • Scenario examples should reflect patterns consistent with FMCSA fraud guidance and FBI IC3 reporting without identifying private parties.

Source Handling

  • FMCSA, SAFER, L&I, NCCDB, FBI IC3, FTC, CISA, and DOT OIG sources are checked directly from official domains before publication and on update review.
  • Time-sensitive records — FMCSA registration status, SAFER company snapshots, identity verification processes — are described as current only at the time they are checked.
  • Source notes explain what each record can establish in a verification workflow and where its evidentiary scope ends.

What This Profile Does Not Provide

  • Legal advice about fraud findings, broker contracts, bond or trust claim rights, or liability questions.
  • Insurance coverage opinions, claim strategy, or guidance on what insurers are required to pay.
  • Real-time certification that any broker, carrier, driver, load, document, or payment instruction is verified or safe.

Scope note: This profile explains editorial experience and review scope. It does not create legal, financial, insurance, compliance, or law-enforcement authority.