Loading…
A fraud flag on your carrier profile is one of the most actionable problems you can have — brokers reading it are filtering on the flag, not on the underlying nuance. The good news is that almost every flag has a deterministic cause and a deterministic correction path. This guide walks the flag types that appear on KnowHaul, what evidence clears each one, and the step-by-step correction workflow if the flag is wrong about you.
Almost every fraud flag on a carrier profile is computed from public federal data: authority history, insurance filings, address records, and inspection patterns. Disputing a flag means correcting the underlying data — either at the federal regulator (the source) or on the carrier profile (the surface) — and then re-running the rules. KnowHaul's 'Report something wrong' dialog on every carrier page lets you submit a correction request that goes to the admin review queue. The fastest path: identify which flag is firing, gather the document that proves the federal record is current (insurance certificate, BOC-3 update, ownership-change filing), submit through the correction dialog, and follow up by phone if the issue is time-sensitive.
A fraud flag is a rules-engine output, not a regulator verdict. KnowHaul's rules engine runs the federal carrier record against a set of fraud patterns — multi-year dormancy followed by recent reactivation, address that resolves to a residential property, freshly issued MC with an established-business carrier name, insurance lapse inside the cancellation window — and surfaces a flag when the pattern fires. The flag is a high-confidence signal that brokers should ask additional questions; it is not a claim that the carrier is necessarily fraudulent.
The distinction matters because it controls the correction path. If a flag is firing because the federal record contains the pattern (and the pattern is correct), the correction is to update the federal record — not the rules engine. If a flag is firing because the federal record is stale or wrong (and the rules engine is reading correct-as-of-yesterday data), the correction can be either a federal-record update or a profile correction submitted through the KnowHaul dispute workflow.
KnowHaul does not hand-curate fraud flags. The rules engine reads the federal carrier record (authority, insurance, BOC-3, addresses, inspections) and computes flags from that data. A flag that feels unfair is almost always reading something specific from the federal record — identifying which field and correcting it is the path.
Four flag types account for the majority of disputes. Each has a specific trigger in the federal data and a specific correction path.
There are other flag types — BOC-3 termination, fresh MC + established-name mismatch, very low inspection volume on an old MC, equipment-vs-cargo-classification mismatch — but the four above cover most of the disputes carriers actually file.
Open your own carrier profile (search by your DOT or MC at /c) and read the fraud-signal section. Each flag has a name and a one-sentence explanation of what triggered it. Copy the exact flag wording — you will reference it in the correction submission.
If the flag is firing because the underlying federal data is correct (you did just reactivate your authority after 3 years dormant; your physical address really is a virtual office), the correction path is operational, not corrective. Update the actual federal data — file a BOC-3 update, update your MCS-150 to reflect a real physical address, file proof of operational continuity — and the rules engine will re-read the federal record on its next refresh cycle.
Every flag has a deterministic 'what would clear this' answer. Bringing the right document on the first submission cuts the review cycle from days to hours.
If the flag is reading a stale or wrong field on the federal record (FMCSA), filing a DataQs Request for Data Review at the federal level is often the fastest path. The rules engine re-reads the federal record on its next refresh and the flag clears automatically — no separate KnowHaul intervention needed.
Every carrier page on KnowHaul has a "Report something wrong" button. Click it, sign in (corrections require an authenticated account to prevent spam), and submit the correction request. The form asks for: the field being disputed, the reason (outdated / incorrect / no longer operating / merged or acquired / typo / other), the value currently shown, the value it should be, and any supporting notes or source URL.
For fraud-flag disputes specifically, the most useful submission lists the flag wording in the "notes" field, references the supporting evidence (with URLs if available — a DataQs case number, a state corporate-records lookup, a license-plate-on-trailer photo), and explains the operational context. Submissions that include both the data correction and the human context resolve fastest.
Corrections go to an admin review queue, where they are evaluated against the federal record and the submitted evidence. Three outcomes are possible: accepted (the correction is applied to the carrier profile and the rules engine re-runs), rejected (the federal record stands and no change is made; you receive an explanation), or duplicate (a similar correction is already in flight; both submissions are linked).
Review timing varies with the queue depth and the complexity of the dispute. Simple field corrections (typo, outdated phone number) typically resolve within 24-48 hours. Fraud-flag disputes that require evaluating supporting documents typically resolve within 3-5 business days. Disputes that hinge on the federal record itself being wrong — where the right path is a DataQs filing — may take longer because the federal regulator's own review can take 30-60 days.
When the federal record is wrong (and the rules engine is correctly reading it), no amount of KnowHaul-side correction will keep the flag from re-firing on the next data refresh. The durable fix is to correct the federal record. File a DataQs Request for Data Review at the federal level, and the rules engine will re-read the corrected data automatically.
Two common mistakes that slow the dispute process down. First: do not submit the same correction request multiple times in rapid succession. The queue is FIFO and duplicates are linked, not prioritized. If the original submission is taking longer than expected, follow up by email rather than re-submitting.
Second: do not try to dispute the rules engine itself. The rules are public-data-driven and apply uniformly to every carrier in the system. The dispute path is the data underneath the rules, not the rules. Submissions that say 'the flag is wrong, you should not be checking dormancy patterns' will not move the queue — submissions that say 'the dormancy flag is firing because the federal record shows my authority was revoked in 2019, but here is the DataQs case where the regulator confirmed the revocation was an error' will.
Every carrier profile page on KnowHaul (at /c/[your-DOT]) has a 'Report something wrong' button near the top of the page, in the carrier-identity section. You need to be signed in to submit a correction — anonymous submissions would be too easy to spam. If you do not have a KnowHaul account, sign up first (free) and then submit the correction.
Most simple field corrections (typo, outdated phone, address change) resolve within 24-48 hours. Fraud-flag disputes that require evaluating supporting documents typically take 3-5 business days. Disputes that depend on the federal record being wrong may take longer because the FMCSA DataQs review process can run 30-60 days; in those cases, KnowHaul will note that the dispute is pending federal review and the flag will clear automatically once the federal data refreshes.
The correction dialog accepts submissions from any authenticated user — you do not have to be the carrier of record to submit. In practice, most fraud-flag disputes come from the carrier themselves (or their dispatch/back-office) because they have the supporting documents. Third-party submissions are accepted and evaluated against the same evidence standard.
Rejected submissions come with a written explanation of which field was disputed and why the federal record (or the rules engine logic) stands. If the rejection is because the federal record contains the disputed pattern (and the carrier's evidence does not overturn it), the path forward is to correct the federal record through DataQs. Resubmitting the same evidence will produce the same outcome — the new submission needs new evidence.
Yes. KnowHaul re-reads the federal carrier record on a daily refresh cycle. Once the federal data corrects (DataQs ruling, MCS-150 update, new BMC-91 filing, BOC-3 update), the rules engine re-evaluates on the next refresh and any flag that was reading the stale data will clear. There is no separate KnowHaul action needed.
Yes — and this is the operational lesson worth taking from the rules engine. The patterns the engine flags (multi-year dormancy + reactivation, virtual-address physical locations, insurance cancellation windows, BOC-3 lapses, identity-flip multi-field changes) are the same patterns that cause real-world broker friction. Operating with the federal record in good order — current insurance, current BOC-3, real commercial address, stable contact info, regular MCS-150 updates — keeps the rules engine quiet and keeps brokers comfortable tendering to you.
Search your DOT or MC, read the joined federal record and fraud signals the way brokers see them, and start a correction from the 'Report something wrong' dialog.
Free, no signup. Paste a DOT, MC, or VIN — verify right away.
Step-by-step checklist for vetting any motor carrier before tendering a load — operating authority, insurance, safety scores, inspection history, and identity flags.
Authority types in plain English — Common, Contract, Broker, and Freight Forwarder. What each allows, when carriers hold more than one, and what 'revoked' actually means.
Decoder ring for the free public carrier lookups every broker can reach — what each field means, what is missing, and how to read authority and inspection data without misinterpreting it.
How double brokering works in 2026, recent fraud patterns, and a prevention checklist for freight brokers and shippers who want to stop the bleed.
Open one of these profiles in a new tab to see how the checklist applies to a live carrier record.
Search your DOT or MC, read the joined federal record and fraud signals, and open the 'Report something wrong' dialog right from the page.