Your Carrier's Insurance Was Lapsed on the Day of the Crash. You Had No Idea.

The crash happened on a Tuesday in March. Dry van, 53-footer, electronics load worth $280,000. The driver ran a red light at a controlled intersection outside Memphis, hit a sedan, and two people ended up in the hospital. Neither died, thank God, but both had injuries that took months to recover from and a plaintiff's firm that knew exactly what it was doing.

MC-1247893 had been in my carrier approval database for fourteen months. Clean authority, no fatal crashes, Unsafe Driving BASIC in the 30th percentile. I'd onboarded them properly — ran the SAFER snapshot, pulled the L&I, noted the insurance, put the ACORD 25 on file. Standard stuff.

What I didn't know — what no one on my team knew until the subpoena landed — was that MC-1247893 had switched insurance carriers four weeks before that Tuesday. The new policy started on a Thursday. The old policy ended the Sunday before. That left a four-day gap, and the crash happened on day three of it.

The ACORD 25 I had on file was fourteen months old.

The ACORD 25 Is a Snapshot, Not a History

I'm going to be direct about something the insurance industry doesn't exactly go out of its way to advertise: a certificate of insurance proves the carrier had coverage on the date the cert was issued. That's it. It doesn't prove they have coverage today, it doesn't show whether the policy was renewed, and it absolutely doesn't tell you whether there was a lapse between the last cert you have and right now.

Most brokers treat the ACORD 25 like a permanent document. Carrier comes through, you pull their cert, you check the BIPD minimum ($750K for dry van under 49 CFR § 387.9, $1M for hazmat, and yes the cargo side is a separate question), you put it in the file, and you move on. You tender 80 loads to that carrier over the next year and never request another cert because nothing has changed — as far as you can see.

The problem is what you can't see from where you're sitting.

What the L&I Database Actually Contains

The FMCSA Licensing and Insurance database records every insurance filing a carrier's insurer submits. When a carrier gets a new policy, their insurer files a Form BMC-91 (or BMC-91X for the excess/surplus lines). When that policy cancels, the insurer files a cancellation with FMCSA — and under 49 CFR § 387.313, insurers are required to give FMCSA 30 days' notice before the cancellation is effective.

That's the mechanism that protects FMCSA from authorizing freight on a carrier that's flying without coverage. The cancellation notice goes in, 30 days tick, and if no new filing appears in that window, theoretically the authority goes suspended.

What actually happens in practice is messier. Carriers switch insurers all the time — program markets, risk pools, hard markets pushing premiums up, a carrier that got a single bad inspection hitting the ceiling on their current policy. The transition usually goes fine. Old policy ends, new policy starts, the filings overlap, no gap appears.

Usually.

When there's a gap — even four days, even two days — it shows up in the L&I filing history. Every filing and every cancellation has a date. Line them up chronologically and you can see exactly when coverage existed and when it didn't. You can look up any carrier's filing history right now on FMCSA's L&I database for free.

Plaintiff's attorneys discovered this a long time before most brokers did.

How a Plaintiff's Lawyer Uses the L&I History

After the Memphis crash, the first subpoena to us was for our carrier file on MC-1247893. That's standard. They got the onboarding packet, the fourteen-month-old ACORD 25, the load confirmations, the rate cons.

The second thing their expert did was pull the L&I filing history for the carrier and lay it out against a timeline of every load we'd tendered in the prior six months. It took about forty minutes.

The gap was right there. Old policy cancelled. New filing effective four days later. Load tendered on day three.

Their theory wasn't that we caused the crash. Their theory was that a broker exercising reasonable care would have known the carrier's insurance status at the time of tender — or at minimum, would have had a system that would have caught a lapse before a load went out on a carrier with no active coverage. Post-Montgomery v. Caribe Transport II, that "reasonable care" standard is the entire ball game. The Supreme Court was unanimous: the FAAAA doesn't preempt state negligent-selection claims, and state courts get to define what "reasonably careful" looks like. Right now, "reasonably careful" is being defined in courtrooms across the country in real time.

Standing pat with a fourteen-month-old ACORD 25 on file is not going to meet that standard in 2026.

The 30-Day Notice Rule Means You Have a Window — If You're Watching

Here's the one piece of good news in all of this. Because 49 CFR § 387.313 requires insurers to give 30 days' notice before an effective cancellation, the filing that kills your coverage appears in the L&I database up to 30 days before anything actually lapses. The information is available. You just have to be watching.

That's not easy to do manually. You'd need someone checking the L&I filing page for every carrier in your network, every day, and comparing effective dates. Nobody does that. If you have 150 approved carriers and you're hauling 30+ loads a day, that's not a realistic ask.

What that means practically is that the carriers with gaps usually aren't getting caught until after something bad happens. The broker's file gets subpoenaed, the L&I history goes into evidence, and the question "why didn't you know about this?" becomes very uncomfortable.

What Continuous Monitoring Changes

The reason I've moved to continuous monitoring isn't primarily the BASIC scores. BASIC scores change slowly. A carrier doesn't go from 30th percentile to 95th percentile between loads. Those changes unfold over quarters, not days.

But insurance changes happen overnight. A cancellation notice gets filed on a Monday. If you're monitoring, you can know by Tuesday. If you're not, you might not know until a plaintiff's expert pulls the L&I timeline eighteen months later and asks why you didn't catch it.

DOTScreener's Continuous Monitoring watches L&I filings across the carrier network in real time — and when a cancellation notice appears, it flags that carrier and logs it against your file. If you've tendered to them recently, you get the alert. You can contact the carrier, ask about the transition, get an updated cert if they've already bound the new policy, or pull them from the active queue until the new filing appears. Most of the time it's a routine transition that resolves in a day or two. Occasionally it's not routine at all — a carrier whose policy got dropped for cause is a very different conversation than one that shopped markets and picked a new program.

The network-shared insurance data means that if another org in the DOTScreener network has already flagged a lapse or received an updated cert from that same carrier, you can see that the coverage history was clean on the loads they ran. That shared intelligence doesn't replace your own file, but it adds context and sometimes surfaces carriers that are playing games with their coverage that a single organization wouldn't catch on their own.

The Carrier That's "Fine"

I want to be specific about what a coverage gap doesn't tell you. A carrier that lapses for four days between policies isn't automatically a bad carrier. Transitions happen. What a gap does tell you is that for those four days, there was no insurer backing their operation, and if something happened in that window, you'd be looking at a coverage fight on top of a liability fight.

The bad actors aren't the carriers that transition policies smoothly but one filing shows up a day late. The bad actors are the carriers who cycle through policies because they can't get coverage renewed — or who use the gap to shed a claims history before binding a new policy with a fresh slate. The L&I history shows you both, but they look different. A carrier with twenty clean years and one gap during a market transition looks very different from a carrier with three different insurers in eighteen months and two gaps along the way.

You have to read the whole timeline, not just flag any gap.

The BIPD Minimum Isn't the Only Number

When brokers think about insurance verification, they usually think about whether the carrier meets the 49 CFR § 387.9 BIPD minimum. $750K for property freight, $1M for hazmat. Most carriers meet those minimums — and many shippers are now requiring $1M across the board regardless of commodity, which is a reasonable ask given where jury verdicts have been trending.

But the minimum is just the floor. The gap problem isn't about whether the carrier's policy has the right dollar amount. It's about whether a policy exists at all on the day you tender. A $5M policy that's been cancelled is worth zero.

Same goes for cargo coverage. If you're tendering a $280,000 electronics load to a carrier whose cargo coverage was cancelled three weeks ago and they haven't told you, your contingent cargo is going to work harder than you want it to. That's not a fight you want to be in when you could have caught the lapse before the truck left the dock.

How I Document This

For every carrier in my active queue, the file now includes:

• The onboarding ACORD 25 with the date it was received.
• A log of every L&I status check since onboarding, with timestamps. Even if I ran the check and everything looked current, that check gets logged.
• Any insurance alerts generated by Continuous Monitoring — the alert date, the filing date, what the filing was, and how we resolved it (got an updated cert, contacted carrier, etc.).
• If a carrier switches insurers, I get an updated ACORD 25 from the new policy before the next load goes out. That cert goes into the file with the date I received it.

It takes maybe five minutes per event. The alternative is trying to explain in a deposition why your file has a fourteen-month-old ACORD 25 on a carrier that had a four-day lapse on the day of the crash.

I know which conversation I'd rather have.

---

— Mason Lavallet

Founder, DOTScreener.com