The Carrier's Insurance Lapsed for Eleven Days. Your Load Ran on Day Nine.

A broker I know got deposed last spring on a fatality case out of Tennessee. The crash happened three months after he'd done a full packet on the carrier — checked SAFER, pulled the COI, ran the BASIC scores, the whole routine. His file was actually pretty solid. Then the plaintiff's attorney asked him one question: what was the carrier's insurance status on the day of the crash?

He didn't know. He'd checked at onboarding and never again.

The attorney produced a printout from the FMCSA L&I database. The carrier's primary liability policy had lapsed for nineteen days — a payment processing issue, reinstated quietly, no service interruption anyone noticed. The crash happened on day fourteen. The COI in the broker's file was dated forty-three days before the lapse began.

The broker's carrier file, which he'd been proud of, suddenly looked like evidence that he knew how to vet carriers and then stopped.

Why Insurance Lapses Happen and Why You Don't See Them

Insurance lapses in trucking are more common than most people realize. Carriers manage tight cash flow, premiums are high, and payment processing on large commercial policies can have timing issues. A policy doesn't always cancel because the carrier is unsafe — sometimes it's a billing dispute, a banking hiccup, a policy renewal that got delayed at the insurer's end.

But "it was just an administrative glitch" is not a defense you want to be making after a fatality.

When a carrier's insurance lapses, the insurer files a notice with FMCSA. The L&I database — the FMCSA's Licensing & Insurance system — reflects the lapse, usually within a few days. SAFER may or may not update quickly. The COI the carrier sent you at onboarding is just a snapshot. It says nothing about what happened after the date on the form.

The gap is structural. A COI is a document produced at a point in time. Insurance is a continuous obligation under 49 CFR Part 387, which requires carriers to maintain financial responsibility — specifically, minimum liability coverage of $750,000 for most general freight under § 387.9, higher for hazmat under § 387.7. The regulation doesn't care about your COI date. It cares about whether coverage was in force when the incident occurred.

Plaintiff's counsel cares about the same thing, and they have access to the same database you do.

What Discovery Looks Like on a Lapse Case

The L&I database stores insurance filing history. That means not just current status — past lapses, reinstatements, the dates they were reported. A plaintiff's attorney who knows what they're doing will pull that history for every carrier on a fatality case. It takes maybe twenty minutes with FMCSA's systems.

What they're looking for is any period of lapsed coverage that overlaps with the load date. If they find it, they build a simple timeline: your vetting record shows you checked insurance at onboarding (if they're generous, they'll give you that); the lapse occurred after that; your load ran during the lapse; you had no record of verifying insurance status at tender. That's negligent selection, because a reasonable broker exercising ordinary care would have known that a months-old COI isn't confirmation of current coverage.

The argument practically writes itself.

And here's the compounding factor. If you're a broker post-Montgomery v. Caribe Transport II — which the Supreme Court decided this past May, holding unanimously that the FAAAA doesn't preempt state negligent-selection claims — a plaintiff doesn't need to prove you knew about the lapse. They need to prove you should have known. In a world where the FMCSA L&I database is publicly accessible and shows real-time insurance status, "I checked the COI six weeks ago" is not going to impress a jury.

The standard they'll argue is what a reasonably careful broker does. Reasonably careful brokers verify insurance status close to load tender. Not just at onboarding.

The COI Problem Nobody Talks About

A certificate of insurance is issued by the carrier's agent or broker. It's accurate as of the date it was produced. After that, the underlying policy can change — it can be canceled, lapsed, reduced, or modified — and the COI sitting in your file has no mechanism to reflect any of that.

I've seen brokers operate as if a COI is a warranty. It isn't. It's a receipt. What it tells you is "as of this date, this carrier had coverage." It tells you nothing about tomorrow.

The right source is the L&I database, queried close to the time you're booking the load. For high-frequency carriers you work with regularly, you need a system that watches for insurance status changes and alerts you when something changes. Not because carriers are malicious — most lapses are exactly the administrative issues I described — but because the gap between a lapse and reinstatement is real exposure, and you can't manage exposure you can't see.

MC-2184633 is a carrier I pulled as an example recently — small flatbed operation, been in business seven years, solid inspection history, no real BASIC issues. About eight months ago their insurance lapsed for twelve days while their insurer processed a mid-term endorsement change. Reinstated, fully current, nothing going on. But if a load had run during those twelve days and something had gone wrong, the broker on that load would have been explaining a months-old COI to a jury.

The exposure isn't about bad carriers. It's about the time gap between when you looked and when something happened.

The DOTScreener Approach: Watch, Don't Just Check

This is one of the core problems DOTScreener's Continuous Monitoring is built to catch. When you screen a carrier through DOTScreener and put them on your approved list, the system monitors their insurance status against the FMCSA L&I database on an ongoing basis. If coverage lapses, it flags — and your Carrier Selection Record gets an alert notation rather than a clean re-file.

That matters for a few reasons. First, obvious one: you don't book an uninsured load. But second, and maybe more important in the current legal environment: when something does go wrong and your file gets subpoenaed, you can show monitoring activity, not just a point-in-time check. You have a record that says "we were watching" rather than "we checked once and assumed."

The re-filed Carrier Selection Record on every load adds a timestamp — not just a static vetting date. That timestamp is dated to the load, reflects the monitoring state at the time, and is the document structure a court can actually follow. That's a different answer to the "what was coverage status on the date of the crash" question than a forty-day-old COI.

I'm not saying the monitoring record makes you bulletproof. But there's a material difference between "I checked insurance at onboarding" and "the carrier was on continuous monitoring and the insurance field showed active at the time of tender." One of those answers survives cross-examination. The other one doesn't.

Reading the L&I Database Yourself

If you're not using a monitoring tool, you can check L&I status manually at safer.fmcsa.dot.gov under the carrier's snapshot — look for the "Operating Authority" section and then the "Insurance" tab. The FMCSA also has a direct L&I query at li-public.fmcsa.dot.gov.

What you want to see: an active Form BMC-91 or BMC-91X filing under the carrier's DOT number, with no pending cancellation notice and a policy effective date that covers today. A BMC-91X is a surplus lines form — not inherently bad, but worth a note in your file because surplus lines carriers sometimes have less regulatory oversight than admitted carriers on the BMC-91.

Check the cancellation history too. Not just current status — whether there's a pattern of lapses and reinstatements. A carrier that's lapsed twice in eighteen months has a payment history problem. That's a risk factor, and it belongs in your evaluation.

Do this at tender, not just at onboarding. The five minutes it takes to pull current L&I status before you book is the cheapest insurance you'll ever buy.

The Practical Question at Load Tender

Here's how I think about it. Before you send a rate confirmation or book a carrier, you should be able to answer three questions:

Is their authority currently active? (SAFER snapshot, "Operating Status" field.)

Is their insurance currently in force? (L&I check, today's date.)

Has anything material changed since the last time I looked? (Monitoring alert, or manual re-check if it's been more than a week.)

If you can't answer all three, you haven't finished vetting.

The third one is the one most brokers skip. They check once at onboarding, and then the carrier goes into an approved list and lives there until something goes wrong. The approved list becomes a false confidence — a feeling that these carriers are cleared, when what's actually true is that they were cleared as of some earlier date.

The broker who got deposed in Tennessee had done good work at onboarding. The gap wasn't in his initial diligence. It was in the absence of any follow-up mechanism. Nineteen days was long enough for a policy to lapse, a load to move, and a crash to happen — all without a single alert in his system.

That's the gap. That's what "the silent killer" actually means.

How I Document This

For every carrier on my approved list, the file should reflect ongoing insurance monitoring, not just initial verification. Here's what the documentation looks like:

At onboarding: COI received, L&I query date and result, BMC filing type (91 or 91X), insurer name and policy number noted.

At each load tender: Either a monitoring system alert showing no change in insurance status, or a fresh L&I query with the query date recorded. I timestamp this entry to match the load date. If it's a carrier I book frequently, the monitoring system handles this automatically and the log is built into the carrier record.

If an alert fires: Note the lapse date, reinstatement date (once confirmed), and hold on booking until coverage is confirmed active. Log the hold decision.

That's it. It doesn't take long. But it produces a paper trail that shows continuous attention to insurance status rather than a one-time check. When counsel asks "what was coverage status on the date of the crash" — that's the file that lets you answer the question.

The broker in Tennessee couldn't answer it. Don't be him.

— Mason Lavallet

Founder, DOTScreener.com