The Insurance Lapse Your SAFER Pull Won't Show You

The discovery request came back 127 pages thick. Driver logs, HOS records, dash-cam files. Standard stuff in a fatality case. But six pages near the back changed the calculus on everything: a printout from FMCSA's insurance database showing the carrier's policy had lapsed for eleven days in October — eight weeks before the December accident that put us in that conference room.

We'd run SAFER the morning we booked them. Authority active. OOS rate well below the intervention threshold. Nothing flagged. What we didn't see was October, because SAFER doesn't show you October. It shows you today.

That's the problem with a one-time pull. It's a photograph. It tells you what FMCSA's database reflected at 9 a.m. on the day you checked. It tells you nothing about what happened in the five months between that day and the load. And in post-Montgomery v. Caribe Transport II litigation, a plaintiff's attorney who knows what they're doing won't stop at what SAFER shows today.

What a lapse actually looks like

I want to be specific about the mechanics because most brokers have a vague sense that "insurance can lapse" without understanding what that means in the database.

When a motor carrier files for operating authority, their insurer files a BMC-91 or BMC-91X with FMCSA — these are the standard certificates of insurance that tie the carrier's operating authority to their coverage. The filing includes an agreement that the insurer will give FMCSA at least 35 days' advance written notice before canceling. That 35-day window exists so FMCSA has time to suspend the carrier's authority before they're out there running uncovered.

Here's the gap: that notification flows to FMCSA. Not to you. Not to any broker who previously checked that carrier. There's no email to your inbox when the carrier's insurer files a cancellation notice. You'd have to be watching FMCSA's database in real time to catch it.

And carriers — especially smaller ones operating close to the financial edge — sometimes let policies lapse and reinstate them. The insurer files a cancellation notice with FMCSA, the carrier gets current on premiums or finds a replacement policy, and the insurer files a new BMC-91. Authority may never get formally suspended if the reinstatement happens fast enough. But the history is there. The database records it. The eleven-day window sits in the file, quiet and damning, until someone subpoenas it three years later.

Take MC-1247893 / DOT-3567102 as a hypothetical. Carrier with solid compliance numbers, five years of authority, no OOS orders. Their cargo policy lapses October 3rd through October 14th — insurer filed the cancellation notice, carrier came current before FMCSA suspended authority. You pull SAFER on November 28th. Active. Nothing unusual. You book them for a $340,000 electronics shipment. December 12th, there's a serious accident. The plaintiff's attorney requests FMCSA insurance history as a matter of course. Now you're explaining why you used a carrier with a recent lapse in their record.

Did you know about October? You couldn't have from a November pull. But "I didn't check continuously" is exactly the kind of answer that costs money at settlement.

What the regulation actually requires

49 CFR § 387.7 is the core rule. It requires motor carriers operating in interstate commerce to maintain financial responsibility — meaning continuous coverage at or above the minimum levels set in § 387.9. For a standard property-carrying vehicle over 10,001 GVWR, that's $750,000 BIPD minimum. If they're hauling hazmat, it's $1,000,000 or $5,000,000 depending on the commodity.

The key word is maintain. Not "have at time of hire." Continuous. The regulation doesn't contemplate gaps. The carrier's authority is conditioned on uninterrupted coverage. A lapse, even one that's been remedied, is a violation of § 387.7 for the period it was open.

At load-tender time, what this means practically: the coverage you verified on your screen date is the coverage as of your screen date. It is not a guarantee of coverage for the day of the load, the week of the load, or the month the freight is in transit. A broker who screens once and moves on has met none of the due diligence standard that plaintiffs will argue Montgomery now demands.

What form MCS-90 doesn't protect you from

This trips people up. There's a common piece of bad logic that goes: "the carrier has an MCS-90 endorsement, so we're covered." No. You're confusing two different protections.

The MCS-90 endorsement is a statutory liability endorsement that prevents the insurer from denying a claim on coverage defenses it might otherwise use — policy exclusions, violations, late notice, whatever. It exists to protect the public, not brokers. The MCS-90 means an injured third party can collect from the insurer even if the policy technically had a defense. That's meaningful for crash victims. It doesn't protect the broker from a negligent-selection lawsuit.

What the plaintiff is arguing against the broker in a Montgomery case isn't "who pays the injured party." The insurer is often on the hook regardless of MCS-90. What they're arguing is that the broker was negligent in selecting an unsafe carrier, and that the broker's negligence contributed to the damages. The broker's liability is separate from the carrier's insurance coverage. MCS-90 is irrelevant to that analysis.

The only thing that protects a broker from that claim is a documented, reasonable selection process. Which means proving you did more than a one-time SAFER pull.

The deposition question you don't want to answer

Here's how it goes in discovery. Plaintiff's attorney has the FMCSA insurance history. They know about October. They ask:

"Did your company have any process for monitoring the insurance status of carriers after the initial screening?"

If the honest answer is "no, we checked at booking and that was it" — that answer is now in the record. Every broker in that brokerage's peer group who ever used that carrier is at risk. The broker's coverage decisions, their vetting procedures, their written policies (if any exist): all of it becomes relevant.

Post-Montgomery, that question has teeth. Before the Supreme Court's ruling last May, the 7th and 11th Circuits had given brokers an FAAAA preemption shield against state-law negligent-selection claims. That shield is gone. State courts can now hear these cases, which means plaintiff attorneys in every jurisdiction in the country are building this playbook. Insurance history queries are not a specialty move anymore. They're going to be routine.

What "continuous monitoring" means in practice

I want to be clear about what continuous monitoring actually catches versus what it doesn't.

FMCSA's insurance database is not a live data feed from the insurer's policy management system. There's inherent lag — a policy that lapses today may not reflect in SAFER for days or weeks, depending on when the insurer's agent files the cancellation. A perfect monitoring system running against FMCSA data will catch lapses that have been filed and haven't been reinstated. It won't always catch a lapse that was remedied in the same billing cycle before any FMCSA filing was triggered.

That's a real limitation and I'm not going to oversell around it.

What continuous monitoring does catch: the October scenario. The carrier whose insurer filed a formal cancellation notice, where authority was at risk of suspension, where the lapse is now in the database. It also catches authority revocations, new OOS orders, safety rating changes, MCS-150 updates that change the operational picture. The point is that you're watching the carrier's regulatory posture continuously — not just on the day you decided to use them.

DOTScreener's continuous monitoring runs against the carriers you've screened. When something changes — authority status, insurance filings, safety rating, OOS activity — your Carrier Selection Record gets updated and you get an alert. That re-filed record matters because it creates a timestamped evidence trail: you checked at booking, you were watching after booking, and you acted on what you saw. That's a fundamentally different paper trail than "I ran SAFER once in November."

The carriers that are worth worrying about are often the ones who look clean at one point in time. No one's going to hand you a carrier with authority that's already suspended and insurance already cancelled. The risk is in the gap between your initial check and when something changes. Continuous monitoring is the only way to close that gap.

How I document this

This is what goes in the carrier file when continuous monitoring flags a status change:

• The original screen record with the date and what it showed
• The alert: timestamp, what changed, the specific field that triggered it
• A note on what I did in response — did I contact the carrier? Require a new COI? Pull them from a pending load?
• If I kept using the carrier after the flag: the reason, documented. New certificate received? Insurer confirmed reinstatement? FMCSA records updated clean? Put it in writing.

If the flag is an insurance issue, I want a new ACORD 25 from the carrier's broker before I move any more freight. I note that request and its outcome in the file. If the carrier can't produce it, they're out until they can.

The goal of the document trail isn't to prove you're perfect. It's to prove you were paying attention. A broker who noticed a change, asked questions, got answers, and made a documented decision is in a completely different legal position than a broker who checked once and moved on.

"I didn't know" is a liability. "I was watching and here's what I did" is a defense.

---

— Mason Lavallet

Founder, DOTScreener.com