The COI You Got at Onboarding Isn't the One That Matters When the Freight Goes Missing

The month I actually understood insurance verification wasn't from a class or a trade publication. It was from a phone call with another broker after a $218,000 pharmaceutical load vanished somewhere between Chicago and Atlanta.

His carrier file had a clean ACORD 25 — $250,000 cargo limit, no gaps, properly formatted. He'd onboarded the carrier in February. The load moved in September. By September, the carrier had switched insurers. The new policy had a $100,000 cargo limit. Nobody had asked for a fresh certificate since February, and nobody had noticed the L&I filing change in the FMCSA database.

The insurer paid $100K. The broker was on the hook for the remaining $118,000, or at least in the middle of a two-year argument about who was. That's not a carrier fraud story. The carrier had insurance. The documentation was real. What the broker missed wasn't a red flag — he missed a window. The certificate he had showed the world as it looked seven months before the load moved.

Insurance changes. Your carrier file doesn't update itself.

Carriers switch insurers. Policies get repriced. Cargo limits get amended at renewal. An endorsement that was in place in February might not be on the policy in September. None of this triggers an automatic update to the certificate of insurance you have on file. The carrier's insurer follows whatever their policy says; your file just sits there holding the old document.

The regulatory framework doesn't solve this problem for you. Under 49 CFR § 387.9, FMCSA requires for-hire property carriers to maintain at least $750,000 in BIPD (bodily injury and property damage) liability for non-hazmat freight moving in vehicles over 10,001 lbs GVWR — that's the federal floor for the liability side of the house. What Part 387 does not mandate is a minimum cargo liability limit for general freight. Cargo coverage is contractual: whatever the carrier bought, and whatever you required in your carrier agreement.

That distinction matters. Your carrier agreement might require $250,000 in cargo coverage. Whether the carrier is actually maintaining it right now is between them and their insurer — and you won't know it changed unless you look.

What the ACORD 25 actually shows — and where it stops

The certificate of insurance is a snapshot. It shows the insurer, the policy number, the effective and expiration dates, and the stated limits at the moment the certificate was issued. There's language on most ACORD 25s that makes this explicit: "This certificate is issued as a matter of information only and confers no rights upon the certificate holder." It's not a guarantee. It's documentation of what existed on a specific date.

After that date, the world keeps moving. The carrier can switch insurers mid-policy period. They can reduce cargo limits at renewal without violating any federal regulation, as long as they still meet the BIPD minimums. A refrigeration endorsement that covered your reefer loads might not be on the renewal policy. An exclusion for high-value electronics might have been added. None of that shows up in the certificate you have on file.

The FMCSA L&I database is more current than your on-file COI. It shows the filing insurer as of today, the effective date of the current filing, and the coverage form. When those fields change, that's your signal — not an automatic notification to you, just a change in the database you either catch or you don't. If you're monitoring, you catch it. If you're relying on the original onboarding certificate, you're flying on data that might be a year old.

The three moments when you should pull a fresh COI

Most brokers pull a certificate of insurance exactly once: at carrier onboarding. Some programs require annual re-verification. That's better than nothing, but it's still a calendar trigger rather than a risk trigger.

There are three situations where I pull a fresh COI before tendering, regardless of what's already in the file.

The first is time-based, but with a shorter window than annual: if I haven't tendered a load to a carrier in 90 days, I verify current insurance before booking the next one. Policies renew annually. Ninety days is long enough for a carrier to have switched insurers, had a policy amended, or let something lapse and reinstate. I'm not assuming a 90-day-old carrier relationship is still in the same coverage situation it was.

The second is load-specific. When I'm tendering something where cargo value approaches the limits I have on file — pharmaceutical, electronics, high-value commodity, anything where $100K vs. $250K actually matters — I want current proof before I confirm. If my carrier agreement requires $250K cargo and the carrier is now writing $150K with their new insurer, I need to know that before the load, not after.

The third is triggered by a monitoring alert. DOTScreener's continuous monitoring watches the FMCSA L&I database for every carrier I've screened. When the filing status changes — new insurer, a lapse and reinstatement, a new coverage form — that alert is my cue. Something changed. I need to understand what it changed to before the next load tender.

Why this matters more after Montgomery

Before May 14, 2026, a broker in the right circuit could argue that the FAAAA preempted state-law negligent selection claims. The Supreme Court's unanimous decision in Montgomery v. Caribe Transport II, LLC closed that door. State-court suits against brokers for negligent carrier selection now proceed regardless of federal preemption arguments.

Insurance adequacy is directly in scope. If your carrier's cargo coverage was inadequate for the load you tendered — either because they never had the limits you thought they had, or because those limits changed after onboarding and you didn't verify — plaintiff's counsel will ask about it at deposition. They'll want to see the certificate you relied on. They'll want to know when you got it, whether you checked current FMCSA filings before tendering, and whether you requested a fresh certificate for this particular load.

"We had a COI from eight months ago" is not a strong answer. "We ran a fresh screen the day of tender, noticed the insurance filing had changed, requested a current certificate, and received it before booking" is a much better one. The difference between those two answers isn't just administrative. It's the difference between a documented due-diligence process and a static file that nobody updated.

The commodity gap you might be overlooking

Here's one that catches brokers off guard: cargo policies often have commodity-specific limits or exclusions that the standard ACORD 25 doesn't spell out. The certificate shows the cargo limit. It doesn't show you whether electronics are excluded, whether there's a per-unit cap on pharmaceuticals, or whether the policy has an "unattended vehicle" exclusion that kicks in any time the driver leaves the cab.

If you're hauling high-value commodity on a regular basis, it's worth asking your carrier for the actual declarations page or endorsement schedule, not just the certificate. The certificate is the summary. The declarations page is the policy. They don't always say the same thing.

This isn't something you need to do for every load. But for specialized freight — pharmaceutical, electronics, jewelry, high-value machinery — the COI is a starting point, not an ending point. Verify that the limit applies to your commodity and that there are no exclusions that would void coverage for the specific scenario you're running.

What I do now

My process runs inside the existing carrier vetting workflow rather than as a separate step.

For any carrier I haven't used in 90 days, I run a fresh screen in DOTScreener before booking. If continuous monitoring has already flagged a change in their insurance filing, I respond to that alert before tendering. If I'm tendering something where cargo value is close to the limits I have on file, I request a fresh COI regardless of what the screen shows.

DOTScreener's Text-to-Screen workflow includes a COI request. When I'm in the same text thread where I'm arranging the load, I can send a COI request from that thread and route the response to whatever email I specify. The carrier gets a text, they send the certificate to the email I designated, and the request and response are timestamped in the screening record. That timestamp matters: it shows I asked for current proof before tendering, which is a different story than "we had a COI on file."

For carriers I'm using regularly, continuous monitoring catches insurance changes between loads. When something changes, I respond before the next tender — not reactively, not after the freight is on the road. Before.

How I document this

For every load where I verify current insurance, the file shows:

• The DOTScreener screening record, timestamped, showing the FMCSA L&I filing status at the time of tender (insurer, effective date, coverage form)
• Whether I requested a fresh COI for that load, when I requested it, and where the response was delivered
• The certificate I received, with the date of receipt, the insurer, the limits, and the effective/expiration dates
• If I didn't pull a fresh certificate (because the carrier was recently screened and no changes had been flagged), a note in the record showing that the current L&I filing matched my on-file certificate

If continuous monitoring flagged a change before the load, that alert is in the record. If I responded to the alert by requesting a fresh certificate, the request is there too. The sequence — screen, flag, request, receive, tender — is the documented defense.

The certificate your carrier emailed in February proves nothing about September. A dated request, a dated response, and a dated screen record tell a story that actually holds up.

— Mason Lavallet

Founder, DOTScreener.com