Seeing a Carrier's Insurance Isn't the Same as Verifying It

A carrier I'd been using last winter had their COI right there when I screened them. MC-1349821. Another broker in the DOTScreener network had already collected it 47 days earlier. Policy limits matched what my load required. $1M cargo, admitted carrier, limits looked right. Everything seemed fine.

I didn't request a fresh one. I booked three loads with them over six weeks. No problems, smooth pickups, customers were happy.

On the fourth load — a $420,000 pharmaceutical pallet from Erlanger to a DC in Reno — I found out after the fact that the carrier had switched insurers during week five of our relationship. The old policy had cancelled on a Friday. The new policy filed with FMCSA the following Wednesday. Nine days where nothing was on file. The carrier didn't tell me. The shared COI still showed the old policy, which looked perfectly fine, because it was fine — 47 days ago.

Nothing happened on that load. The freight moved clean, no claim, no incident. I was lucky.

But I spent a week thinking about what the deposition would have looked like if something had happened on day seven of that nine-day gap. "Did you verify the carrier's insurance before booking?" "Yes, I could see it in our platform." "Was that verification current as of the booking date?" "I... believed so." "Did you check the FMCSA L&I database before booking?" Silence.

That's a bad silence to have.

---

What Network-Shared Insurance Actually Is

One of the things DOTScreener does that I find genuinely useful is surface carrier insurance data that other brokers in the network have already collected. When a broker requests a carrier's COI through the platform and it's verified, that COI becomes visible to other DOTScreener users who screen the same carrier. Carrier insurance you can see even when you didn't request it.

The logic is sound. If another broker collected a COI three days ago, verified the limits, confirmed the insurer, and attached it to the carrier profile — why should you spend 20 minutes requesting and waiting for another copy of the same document? That's a reasonable efficiency argument.

And it works, up to a point. Network-shared insurance is real intelligence. It tells you something about the carrier: they've been vetting-ready enough to provide a COI recently, their coverage structure is visible, you can see the limits and the insurer and whether anything looks structurally wrong before you've made a single phone call. That's useful context when you're doing an initial screen on an unfamiliar carrier.

But intelligence and verification are different things. Intelligence tells you what was true at a point in time. Verification tells you what's true right now.

---

The Gap the COI Doesn't Cover

A certificate of insurance is a snapshot. It reflects the policy as it existed when the producing agent printed it. There's even a disclaimer on the ACORD 25 that tells you this explicitly: the certificate is for informational purposes only and confers no rights on the certificate holder. Most brokers read past that line because it looks like boilerplate. It isn't.

The FMCSA L&I database — the Licensing and Insurance page — updates in near real-time when insurance filings change. A carrier who cancels a policy on Monday has that cancellation reflected in L&I within hours to a day or two, depending on how efficiently their insurer files the notice. A new policy filing can take same-day or up to several business days. During the gap between cancellation and replacement, the L&I database shows the lapse. The old COI still exists and still looks fine.

This is what 49 CFR § 387.3 actually requires: financial responsibility must be on file and in effect as a condition of operating. "In effect" means the policy is active right now, not that it was active when the last certificate was printed. If you rely on a shared COI to satisfy yourself on the insurance question, you're relying on a document that doesn't speak to today. The L&I database does.

The L&I check takes 45 seconds. Pull the carrier's MC number on the FMCSA licensing and insurance page, confirm active insurance is on file, note the effective date. That's it.

---

When Shared Insurance Is Worth More, When It's Worth Less

The age of the shared COI changes how much weight it carries.

A COI collected three days ago, for a carrier with a long relationship with the same insurer, where L&I shows that policy has been continuously active — that shared COI is reinforced by a current L&I check and it means something. You're not just relying on someone else's 72-hour-old document; you're using it as a starting point and confirming it with current data.

A COI collected 90 days ago for a carrier who renewed their policy since then — that's a snapshot of a policy that no longer exists. L&I might still show active insurance under the new policy, but the document in the network is describing something that's already been replaced. You'd want a fresh COI to confirm the current limits and carrier, even if L&I confirms something is active.

There's also a carrier behavior pattern worth noting. Carriers who switch insurers frequently — or who have had policies non-renewed and had to shop coverage — are worth more scrutiny. It's not automatically disqualifying, but a carrier who's on their third insurer in 18 months is telling you something about their claims history or their premium situation. You won't see that from a single COI. You see it from the history of what L&I shows over time and from asking the right questions when you call the insurer to confirm.

---

What Verifying Insurance Actually Requires

Here's the process I use for every load booking where insurance is a question:

First, look at whatever's in the carrier profile — shared COI, prior verification, whatever's there. That's your starting point. Note the insurer, the limits, the coverage structure. If the limits are wrong for your freight, you already have your answer.

Second, go to the L&I database. Pull their MC. Confirm active insurance is showing. Note the effective date. If the policy on file and the COI match — same carrier, same policy period — you're in good shape. If there's a discrepancy, stop and find out why before you book.

Third, for first-time bookings or carriers I haven't moved freight with in more than 30 days, I'll often call the insurer directly to confirm the policy is active and there haven't been any claims that might affect coverage. Takes five minutes. On a $200K+ load with a carrier I don't know well, it's five minutes I don't skip.

None of this replaces the shared COI — it supplements it. The COI tells me the structure; L&I tells me it's still standing; the direct confirm tells me nothing's changed on the insurer's side that isn't reflected in the database yet.

---

The Deposition Question That Gets Brokers

After Montgomery v. Caribe Transport II (U.S. Supreme Court, May 2026), brokers can be sued in state court for negligent carrier selection. In that framework, what matters isn't just whether you did something — it's whether you can document what you did and why it was reasonable.

A plaintiff's attorney asking about insurance verification is going to want to know: when did you verify it, how did you verify it, and can you show me the record? "I saw a COI in our platform" is a start. "When was that COI dated?" is the follow-up. If the COI was collected 47 days ago by another broker and you have no record of checking L&I on the date you booked, you've got a gap.

That gap isn't hard to close. A 45-second L&I check with a timestamp in your carrier file closes it completely. "We reviewed the network-shared COI showing policy limits of [X] with [insurer], and confirmed active insurance via FMCSA L&I on [date]." That's a defensible answer.

The version where you saw the COI in the platform, figured it looked fine, and moved on — that's the version that costs you.

---

The Broader Principle

I've said this about other tools and I'll say it about network-shared insurance too: intelligence is not a substitute for verification. Intelligence speeds up your process. It gives you context. It tells you where to look and what questions to ask. But the final confirmation that a policy is active, that insurance is in effect, that § 387.3 is being met for this load on this day — that's yours to do. Nobody else's timestamp makes it yours.

The network-shared COI is one of the things that makes DOTScreener faster than doing this by hand. You're not starting from zero on carriers who've been vetted before. That's real. But faster-to-start isn't the same as already-done. You're a couple of clicks and 45 seconds from confirming what the shared data shows. Don't skip those clicks.

On a $420,000 pharmaceutical load, I'm not sure what I was thinking when I skipped them. I probably figured the shared COI was close enough. It was. That time.

---

How I Document This

For every load involving a carrier where I'm relying partly on network-shared insurance:

• Note in the carrier record that a network-shared COI was reviewed, with the date it was collected.
• Separate note: L&I database confirmed active insurance on today's date. Policy [number if visible], effective [date].
• Screenshot of the L&I page saved to the carrier's screening record.

That's three lines and a screenshot. It's the difference between "I saw insurance in a platform" and "I verified insurance was active on the date I booked this load." The first is intelligence. The second is documentation. Post-Montgomery, you need the second.

If you're running a carrier through DOTScreener and you can see their insurance from a prior request — great, that's a head start. Then go confirm it's still standing. Every time.

---

— Mason Lavallet

Founder, DOTScreener.com