The COI That Looked Real (And What Nobody Checked)

I know a broker who spent eighteen months thinking she'd done everything right with MC-1489203. The carrier ran dry van on three steady lanes. Never missed a pickup. When she onboarded them, she reviewed the certificate of insurance: names matched, BIPD was listed at $1 million, effective date was three months prior, expiration was next April. She checked the box and put the carrier on her approved list.

What she hadn't noticed: the original policy had expired the previous October. Six weeks before she approved the carrier. Someone had changed the year in the expiration date field — one digit, in a PDF editor. The FMCSA's L&I filing showed a cancellation notice. She hadn't checked L&I at onboarding; she'd checked the certificate the carrier sent her.

The load that ended badly wasn't on her carrier. It was a different broker, a different run. But the carrier had multiple broker relationships and she got subpoenaed anyway. Discovery surfaced her onboarding file. The effective dates on her certificate didn't match what the insurer's records showed. Her attorney spent six hours explaining what "valid COI on file" actually meant.

That's what document fraud in carrier onboarding costs. Not always a direct hit — sometimes just six hours of attorney time and a year of anxiety. Sometimes more.

What a COI Is Actually Supposed to Prove

The ACORD 25 — the standard certificate of insurance — is a snapshot produced by the carrier's insurance agent. Not FMCSA. Not the insurer directly. The carrier requests it; the agent issues it; the carrier sends it to you. Nobody in that chain is verifying that you received an unaltered copy.

Under 49 CFR § 387.7, motor carriers must file evidence of insurance directly with FMCSA as a condition of their operating authority. That filing creates a government record — the L&I database — that shows active coverage, coverage amounts, and cancellation history. That's the filing that matters legally. The ACORD 25 is the carrier's representation to you. When they conflict, believe the government record.

So when you're looking at a COI in a carrier's onboarding packet, you're looking at a document that tells you what the carrier says their coverage is. It's a starting point. It is not an ending point. A competent review uses the certificate as a reference and then checks it against something the carrier didn't produce themselves.

Most brokers don't do this. They look at the PDF, the numbers look right, the dates look right, and they move on. That's enough to satisfy a box-checking workflow. It's not enough to satisfy a deposition question that starts with "and did you independently verify whether this certificate was accurate?"

Four Ways COIs Get Manipulated

I've tracked four patterns in carrier document fraud that come up more often than they should:

Date manipulation. The simplest and most common. Change the expiration year — a "3" to a "5," an "April 2025" to an "April 2027." A good PDF editor makes this a five-minute job. The rest of the certificate looks fine. The coverage amounts match. The named insured matches. Nothing trips the eye during a quick review.

Coverage amount padding. Inflating the BIPD or cargo limit to meet a contract minimum the carrier's actual policy doesn't support. This shows up on high-value freight lanes where shippers require $1 million cargo coverage but the carrier's underlying policy only writes to $100,000. The certificate says a million. The policy says a hundred thousand. A claim surfaces this gap in a way nobody wants.

Named insured mismatches. The operating authority is held by "Jordan Express LLC." The certificate names "Jordan Transport Inc." — a related entity, different legal structure, different policy. Sometimes this is intentional fraud. Sometimes it's carrier sloppiness where they have two LLCs and sent you the wrong certificate. Either way, your policy defense is that you verified their COI — and the entity on it doesn't match the MC holder you dispatched.

Policy number substitutions. Using a valid-format policy number from a lapsed period or from a different carrier. Harder to catch without calling the insurer directly, but the FMCSA L&I filing will show what policy number is on file. If the number on the certificate doesn't match the number FMCSA has, that's worth a phone call before dispatch.

None of these are theoretical. All four have shown up in discovery on carrier-selection litigation. The fact that you "checked the COI" doesn't end the inquiry when the COI was wrong.

What Part 387 Says — and What It Leaves to You

Your regulatory obligation as a broker under 49 CFR Part 371 is to have a written broker-carrier agreement and to use carriers with proper operating authority. Part 387 governs the carrier's minimum financial responsibility — it's their obligation to maintain and file insurance, not yours to verify it exists.

The problem is that Montgomery v. Caribe Transport II moved the goalposts. The Supreme Court's May 2026 ruling — unanimous opinion by Justice Barrett — held that the FAAAA does not preempt state-law negligent-selection claims against brokers. Your exposure is now defined by the common-law standard of care in every state where a carrier you selected causes a crash. That standard is not what the regulations require. It's what a reasonably careful professional in your position would have done.

A jury in 2026 is going to hear that COI fraud is known and documented. They're going to hear that the FMCSA L&I database exists and is publicly accessible. They're going to hear that you could have checked it. "I looked at the PDF the carrier sent me" is not a compelling answer in that room.

What the AI Review in the Carrier Onboarding Packet Catches

DOTScreener's Carrier Onboarding packet runs an automated document review when a carrier uploads their COI. Three things get flagged:

Expiring insurance. Coverage that's within a defined window of lapsing — whether or not the carrier disclosed it — surfaces as a flag before you approve them for dispatch. You'd be surprised how often a carrier submits a certificate with two weeks of coverage left and genuinely doesn't think it's a problem because they "plan to renew."

Named-insured mismatches. The name on the certificate gets compared to the carrier's registered entity in FMCSA records. When they don't match, the packet flags it. This catches both the sloppy-LLC-structure cases and the intentional substitution cases. The review doesn't auto-reject — it flags for a human decision. Sometimes the explanation is fine. But now you have a record showing you looked.

Low coverage. If the certificate amounts fall below the Part 387 minimums or below your configured thresholds, it's flagged. This catches the padding cases in reverse — a carrier whose actual certificate shows inadequate coverage that a quick PDF scan might miss because the numbers still look like numbers.

These are informational flags, not automatic failures. The system surfaces the anomaly; a human makes the call. That distinction matters operationally — sometimes there's a legitimate explanation — but it matters even more legally. Because "the AI review flagged a named-insured discrepancy and our reviewer confirmed the carrier's entity structure via FMCSA records before approving" is a very different deposition answer than "I looked at the PDF."

The Carrier Onboarding packet also generates a timestamped activity log — Sent, Opened, Documents Uploaded, Review Flagged, Resolved — so the sequence is on record. Discovery can ask what you checked. The answer is documented.

What You Still Have to Do Yourself

The AI review doesn't replace the FMCSA insurance tab check. It works alongside it. When a carrier submits their COI, the right sequence is: run the automated document review, then pull their L&I filing in SAFER and compare policy numbers and coverage amounts against what the certificate shows. If anything doesn't match, call the insurer. Get a confirmation number.

On a high-value lane — $500K equipment, electronics, pharmaceuticals — go further: ask for a Certificate of Liability naming your brokerage as a certificate holder. Insurers can issue these. It's not a guarantee, but it's another point of verification that generates another record.

For carriers with brand-new authority, or carriers you haven't used in over six months, treat the COI review as if you'd never seen them before. An approved carrier whose coverage lapsed quietly while you weren't dispatching them is a loaded gun. The FMCSA L&I database will show the gap. Better you find it than a plaintiff's expert.

How I Document This

The carrier file gets the uploaded COI, timestamped on receipt. The AI review flags go in with the disposition — what was flagged, what the reviewer did about it, and when. If the L&I check matched the certificate, log that it ran, log the date, log what it showed. If you called the insurer to confirm an active policy, log the agent's name, the call date, and the reference number they gave you.

The pattern is what matters. A carrier file that shows: COI received → AI review flagged expiring coverage → L&I query ran and showed coverage lapsing in 11 days → broker emailed carrier requesting updated certificate before dispatch is a sequence a defense attorney can work with. A carrier file that's a PDF with no other record is a folder.

Document fraud in carrier onboarding is underreported because it usually doesn't become a problem until a crash surfaces it. By then, the file is evidence. Build it that way from the start.

— Mason Lavallet

Founder, DOTScreener.com