Too-Good-To-Be-True Rate Signals

How this comes up in practice

A load board posting offers $4.20 per mile for a lane where the carrier's usual rate runs closer to $2.80. The broker MC number is active in L&I. The posting has been up for two hours. When the carrier calls the contact number, they're told the shipper has urgent capacity needs and the load will be reposted if not confirmed within thirty minutes. The carrier signs the rate confirmation — which lists the shipper as a holding company name they don't recognize — and sends their packet. No pickup appointment is produced. When the carrier calls back two days later, the phone number in the posting routes to no one familiar with the load, and the MC number belongs to a company that denies posting that lane. The carrier's packet is now in someone else's possession. The above-market rate served its purpose: enough urgency to compress the verification steps that would have surfaced the mismatch before the packet went out. A rate that stands out from market context isn't a signal by itself — markets move and brokers post premium rates for difficult lanes and short-notice capacity. It becomes a concern when it arrives alongside time pressure that discourages the callback confirming whether the contact behind the posting is who the posting claims.

What an above-market rate signals versus what it establishes

An above-market rate by itself is not a fraud signal. Markets move, capacity tightens in specific lanes, and brokers do offer premium rates for short-notice capacity, difficult lanes, or high-value freight that requires extra verification steps. A carrier who declines every rate above market will miss legitimate loads. The issue is not the rate; it's the rate combined with the conditions attached to accepting it. For adjacent verification steps, compare this with Load Board Scam Red Flags, and Broker Payment History Red Flags.

The conditions that turn an above-market rate into a verification concern are specific: urgency that discourages standard verification steps, missing load details that would ordinarily be confirmed before booking, contact information reachable only through the current posting, or resistance to a callback to the broker's FMCSA-listed number. None of those conditions are incompatible with a legitimate load — but each makes independent verification harder, which is precisely why they appear together in fraudulent postings.

The verification workflow this guide describes is the same one that applies to any unfamiliar posting, regardless of rate. The above-market rate is a reason to apply the workflow, not to skip it. A broker posting a genuine high-rate load can confirm their identity through their FMCSA-listed number and provide missing load details without difficulty. The rate is a signal worth noting when something in the posting makes that confirmation harder to complete.

When an above-market rate is a reason for extra verification steps

An unusually high rate is not proof of fraud. Markets move, lanes tighten, and brokers do post loads above prevailing rates for difficult lane, high-value cargo, or short pickup windows. The concern is when the high rate arrives alongside other signals: urgency without explanation, minimal load details, a new or slightly different email domain, or resistance to standard verification steps.

The combination of signals matters, not the rate in isolation. A broker who posts a high rate and welcomes a call-back through their known office line is handling it transparently. A broker who posts a high rate, discourages call-backs, and asks for driver and equipment details before confirming basic load information is showing a different pattern.

Records to verify before responding to a post

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 save from the posting and thread

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 that verify the posting 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.

Assumptions that lead to packet exposure

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 the posting warrants a report

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