You Pulled the COI at Onboarding. Their Cargo Policy Expired Last Month.

A colleague of mine tendered a load last spring — flatbed, $85,000 machine tool, customer-owned piece of equipment that had no replacement value because the manufacturer stopped making it. He'd been running loads with this carrier for eight months. Onboarded them clean: MC-1247893, DOT-3567102, solid safety rating, no BASIC alerts, $1M BIPD and $100K cargo on file. Standard five-truck flatbed outfit.

The load went out. Something shifted during transit, hit a bridge abutment in a Michigan detour, and the machine tool was totaled.

The cargo claim was denied. The carrier's cargo policy had renewed four months earlier, and the renewal came back at $50,000 — half what the original certificate showed. Nobody noticed because nobody checked. The carrier's onboarding file still had the old ACORD 25. The claim check they eventually got covered about 59 cents on the dollar after the limit, and my colleague ate the rest to keep the customer.

That's not a paperwork error. That's a structural problem with how most brokers approach insurance verification.

The Onboarding Certificate Problem

Most carrier vetting workflows have a checkpoint at onboarding and then nothing. You collect the COI, confirm it meets your minimums, file it in the TMS, and move on. The carrier goes into the approved list. From that point forward, unless something triggers a re-vet — a BASIC alert, a CSA event, a complaint — nobody looks at the insurance again.

The problem is that carrier insurance is not a static fact. Policies renew. Limits change. Riders get added and removed. Cargo policies get amended when a carrier shifts from general freight to specialized equipment, or to hazmat, or back. The certificate you collected in October doesn't describe the policy that covers a load tendered in June.

49 CFR § 387.9 sets the federal minimums for most motor carriers: $750,000 BIPD for general freight hauled in vehicles over 10,001 lbs gross, $1 million for non-bulk oil and hazardous materials, $5 million for bulk hazmat Class A and B. That's the floor, not your number. If you're moving machine tools, construction equipment, temperature-sensitive pharma, or anything with a replacement cost above what the minimum covers, you have to check the cargo sublimit on the actual certificate — not just confirm the carrier is "insured."

49 CFR § 387.31 requires insurers to file a 30-day notice of cancellation with FMCSA before a policy can be terminated. That sounds like a safety net. It isn't. The 30-day clock runs from when the insurer files the notice, not from when the FMCSA database updates. By the time you check the L&I database, the carrier might be two weeks into operating under a renewed policy that looks completely different from what they showed you at onboarding — or operating with a gap. The FMCSA insurance check tells you whether coverage exists at the FMCSA-minimum level. It does not tell you the current limits, the expiration date, the cargo sublimit, or the named insured list.

Most brokers don't know this. They check L&I, see "Active," and call it done.

Every Broker Checks the Same Certificate Independently

Here's the other problem: if a carrier hauls for a dozen different brokers, every single one of those brokers is doing their own insurance check. Calling the same 1-800 number. Emailing the same carrier rep. Getting faxed the same ACORD 25 that may or may not be current. Twelve separate brokers, twelve separate tasks, one carrier file that nobody owns.

This is expensive and it doesn't actually improve the quality of the verification. If the certificate they're sending you is the same certificate they sent to the other eleven, and nobody is cross-checking the issue date against the policy expiration, then you've done twelve transactions and produced zero additional insight. You've just confirmed that the carrier has a PDF they're willing to share.

What would actually help is if the verification work got better over time as more brokers looked at it — and if the most recent certificate was always available without requiring a new document request. That's not how the industry works. Or didn't used to.

What Network-Shared Insurance Changes

DOTScreener started doing something different when we shipped network-shared carrier insurance verification a few weeks ago. The concept is simple: once any broker gets a carrier to upload their actual certificate of insurance, every broker who screens that carrier sees the current coverage — automatically.

Not a summary. The actual certificate, with coverage limits, expiration dates, the insured fleet decoded by VIN to year, make, and model, and the named insured information. When a carrier uploaded their COI to respond to one broker's request, the verified document becomes part of the carrier's profile for the whole network.

This changes the economics of verification. The broker who got the carrier to upload the document did the legwork. Every subsequent broker gets that work for free. And when the policy expires, the expiration date is visible on the certificate that's already on file — you don't need to make another call to find out.

The insured fleet piece matters more than it sounds. Carriers sometimes run equipment that isn't on their COI. A truck purchased after the policy was issued, a leased trailer that's not named, a new unit from a recent acquisition. When the COI lists specific VINs and we decode them against the FMCSA equipment database, you can see whether the truck actually picking up your load is covered by the policy on file. That's a check most brokers cannot do today because they don't have the tools to cross-reference the certificate against the registered fleet.

If the carrier hasn't had a certificate uploaded yet, you can request it in one click from the screening file. The carrier gets a direct upload link, not another email chain. When they upload it, it populates their profile and you get an in-app notification. The certificate doesn't sit in someone's inbox waiting to be forwarded.

What You Should Actually Check

The federal BIPD minimum is $750K. Most brokers set their internal minimum at $1M because the federal floor hasn't been updated since 1985 and $750K doesn't cover a serious crash in 2026. That's not my opinion — that's math.

Cargo limits are a different calculation. The federal minimum for cargo insurance isn't a single number; it's carrier-type specific and commodity-specific, and for many general freight operations there's no federally mandated cargo minimum at all. The burden is on you to match the cargo limit to the shipment value. A $100K cargo policy covers a $95K load. It doesn't cover a $150K load just because the carrier is otherwise clean.

Check the named insured. The policy covers entities named on the certificate, and in freight, that sometimes means a doing-business-as name doesn't match the legal entity that holds the MC number. If the carrier is operating as "Fast Midwest Freight" but the policy is issued to the owner's personal entity, "J. Ramirez Trucking LLC," you want to know that before there's a claim.

Check the policy expiration date. If a carrier's certificate expires in two weeks and you're setting up a regular lane with them, that's a trigger conversation before the tender goes out.

How I Document This

When I screen a carrier, my file now includes a note on:

• The cargo limit at the time of the load, not just at onboarding
• The policy expiration date — and a flag if it's within 60 days
• Whether the COI on file is the carrier's most recently uploaded version or an older document from a prior request
• The named insured and whether it matches the operating entity on the MC

If I'm pulling a certificate myself rather than relying on a network-shared upload, I note the date I pulled it and the issue date on the document. A COI issued 14 months ago isn't documentation of current coverage — it's documentation that coverage existed 14 months ago.

If a carrier's cargo policy doesn't cover the shipment value, I document that I either required additional coverage, changed to a carrier with sufficient limits, or (if the customer is insisting on this carrier) got written acknowledgment from the customer that they understand the coverage gap. That last option is rare and usually wrong, but at least it's documented.

Post-Montgomery v. Caribe Transport II, the plaintiff's lawyer is going to ask what you knew about the carrier's insurance at the time of the tender, not at the time of onboarding. If your answer is "we verified it at onboarding and assumed it hadn't changed," that answer isn't going to hold up well. Insurance is a live document. Treat it that way.

The carriers that upload their COI directly — and keep it current — are telling you something about how they run their operation. It's a small data point but it's a real one. A carrier who argues with you about providing a certificate of insurance, or who keeps sending you the same document from two years ago, is telling you something too.

---

— Mason Lavallet

Founder, DOTScreener.com