Double brokering is the risk that ends brokerages. Every gate here exists for one sequence — this one.
A carrier answers your posting. The MC is real, the paperwork ordinary, the rate a little better than everyone else’s.
It never meant to run the load. It re-brokers it cheaper — under your rate confirmation, on your load number.
A real trucking company hauls the box and invoices the party that tendered it. Nobody answers the phone.
He comes to you, because your name is on the paperwork. He holds the freight, or files a lien, or a cargo claim.
You pay twice, or you eat the cargo. Neither is covered by the margin on that load.
Your customer hears it from the trucker outside their dock. That is the part you do not get back.
Every brokerage has a policy that would have stopped this. Almost none enforce it at six on a Friday, when the box has to move and the only carrier answering is cheap and unknown.

✓ AUTHORITY MATCH · VERIFIED 08-SEP-26
Source: FMCSA QCMobile. Re-check due 08-OCT-26.
The check
It runs server-side and fills the carrier record from what the registry returns — not from a retyped copy of whatever the carrier chose to send.
Verification is a decision, not a checkbox: verified only on a positive authority match, never because a lookup completed.
Legal name and DBA against the number you typed. A mismatch is what a re-brokered load looks like first.
Legal name · DBA
Active, inactive or revoked. A broker authority answering as a carrier is the whole fraud in one line.
Status · type · granted
The federally registered address — the one a fraudulent party cannot quietly change.
FMCSA email
Rating, out-of-service rate, power units, drivers. A fleet of two running four boxes a day is odd.
Rating · OOS · fleet
Liability and cargo cover, with the expiry as a watched date rather than a number read once.
BIPD · cargo · expiry
The gate
All four on file, and a reviewer approving in writing. Not three of the four. Not “we’ll get the W9 on Monday”.
Matched to the legal name the registry returns, not the PDF the carrier emailed.
Checked at lookup and again when the freshness clock runs out. A duplicate surfaces early.
Liability and cargo, with the expiry entered as a date, not remembered.
On file before the carrier is usable — so, before the first payment.
The comment, the reviewer, the timestamp and the source live on the record, so an auditor can be shown the decision rather than told about it.
Carriers created in a hurry start pending. No path to approved skips a human, so the back door is shut too.
Dispatch documents refuse to generate
✕ NOT USABLE FOR DISPATCH
Attempts are refused and recorded with the user who tried.
Carrier paperwork sends only to the FMCSA-registered email. There is no manual override.
The email lock
Rate cons, carrier confirmations and dispatch sheets go only to the registered address. With none on file, the send is blocked.
The moment a person can type a destination the control is worth nothing — the fraud is a domain one character different.
✕ SEND BLOCKED
There is no override on this control, for any role.
Two clocks
Both are jobs on the server. Closing the tab does not cancel them, and a deploy in the middle does not either.
15
Minutes, then somebody is told
After a carrier is created and left pending
Create it now, approve it later, dispatch in between is how a gate gets worked around. Still pending after fifteen minutes, and compliance is told. It unblocks nothing — dispatch still refuses.
30
Days, then the check is stale
Verification carries its date and its source
Authority gets revoked on ordinary Tuesdays. Past thirty days the carrier reads stale everywhere it appears — in colour and in a word.
Stale check
Nothing auto-rejects a carrier. A report that cried fraud at every new small fleet would be ignored inside a week — including the once it mattered.
Forty minutes, no slides. Bring one live container and one messy invoice.
What happens on the call