A Carrier Packet Isn't a Document. It's a Timestamp.

Imagine you're in a deposition two years after a bad accident. The plaintiff's lawyer slides a document across the table — your carrier's W-9. She asks when you received it.

You know you have it. It's in a folder somewhere. But the email thread it came from? You'd have to dig. And that email thread might have a date that's eight months before the load moved.

She asks the obvious question: "Did you verify this carrier's insurance was still current on the day of the loss?"

You collected the COI. You know you did. It's in the same folder. But it came from a different email, different date, and the certificate itself shows an effective date from the prior year. You never requested a fresh one for the load.

"What was the carrier's safety rating on the day you booked them?"

You don't actually know. You pulled it when you onboarded them. Whether it had changed since — you didn't check.

This is not a hypothetical. This is what happens when a broker's "carrier file" is a loose collection of documents assembled from different emails and different moments in time. After Montgomery v. Caribe Transport II, the U.S. Supreme Court confirmed brokers can be sued in state court for negligent carrier selection. The paper trail you've been treating as admin paperwork is now your legal defense. And the dates on that paperwork are as important as the documents themselves.

The difference between collecting documents and building a record

Most brokers go through some version of the same onboarding process: carrier emails a W-9, you request a COI, you pull an FMCSA authority print, maybe you get a signed carrier agreement. The problem isn't that you didn't collect the documents. The problem is that nothing in that process is timestamped to the day you evaluated this carrier for your load.

In discovery, a carrier packet that can't demonstrate recency looks identical to a carrier packet that was assembled after the fact. A plaintiff's attorney can't prove you backdated anything, but they can certainly point out that your COI was issued in January, your SAFER print is from March, the load moved in October, and you have no documentation of anything happening between March and October.

The law doesn't require a specific format for carrier selection documentation. 49 CFR Part 371 covers the general conduct rules for brokers — good faith and fair dealing — and Part 387 establishes the minimum insurance carriers must maintain. What neither regulation prescribes is how you prove that you verified those requirements were satisfied on the day in question. That's on you to figure out. And courts have not been sympathetic to brokers whose answer is "well, we had a W-9 from sometime earlier."

Four things a carrier packet actually needs to show

I'm not a lawyer. What I know is what I've heard from brokers who've been through litigation and talked about what held up and what didn't. Four things consistently come up as gaps.

1. A defined onboarding date. Not the date the carrier's authority was issued. Not the date you last used them. The date your company formally evaluated this carrier and decided they were approved. This is the stake in the ground everything else hangs off. If you can't produce a document that says "we evaluated MC-1247893 on this date and found the following," you don't have an onboarding record — you have a pile of papers.

2. Contemporaneous verification, not standing files. There's a difference between "we have this carrier's COI on file" and "we requested this COI and it was current on the date of this load." The carrier you onboarded in March might have let their cargo coverage lapse by October. If your policy is to pull the file you already have, the file is doing no protective work for loads moved after the original verification date. The FMCSA L&I system shows you current insurance filings — a timestamp from L&I at or near load date is meaningfully different from a certificate you collected at onboarding.

3. A carrier agreement with a verifiable signature. The carrier agreement establishes the terms under which you're tendering freight — including representations about their authority, insurance, and compliance. An agreement you emailed and got back unsigned, or that was signed by someone whose identity you never verified, is weaker than it looks. Who signed it? Were they authorized to bind the carrier? These are questions a plaintiff's attorney will ask.

4. Documentation that the carrier was within your selection policy. This one is easy to skip when there's no formal policy, which is part of why having a written carrier selection policy matters. If your policy is "satisfactory safety rating + at least 12 months authority + no active OOS order," then your onboarding record should show that you checked those three things and the carrier passed. Without that, you're relying on implied judgment, which is a lot harder to defend than documented judgment.

Why the timestamp is the point

I've worked with brokers who are genuinely diligent about vetting. They pull the SAFER snapshot. They check the BASIC scores. They request a COI and actually read it. But if all of that diligence lives in someone's head and a scattered email folder, it's nearly invisible in discovery.

The Montgomery decision didn't change what smart brokers already do. It changed the consequence of not being able to prove that you did it. Before the ruling, many circuits said the Federal Aviation Administration Authorization Act preempted state negligent-selection claims against brokers. That's gone now. You can be sued in any state court for putting a bad carrier on a load. And in that lawsuit, your carrier file — every document, every date, every gap — is Exhibit A.

A well-documented carrier onboarding record isn't proof you're a good broker. It's evidence you exercised reasonable care. Those are different things, and the second one is what you need.

What I actually do at onboarding

When I onboard a new carrier in DOTScreener, I use the built-in carrier onboarding packet — it sends the carrier a branded request for their carrier agreement (e-sign, verified), W-9, and COI in a single link. The link goes to the carrier's FMCSA-registered email, so the "who received this request" question has a clean answer. When they complete it, the agreement includes a verifiable identity step at /verify/agreement — the carrier attestation is timestamped and tied to the specific entity, not just a PDF that could have been signed by anyone.

The AI document review layer in DOTScreener cross-checks what the carrier submitted against what FMCSA has on file — insurance limits, carrier name, authority status, expiration dates. It flags mismatches. It's not a replacement for my read, but it catches the things I'd miss at 4 PM on a Friday: the COI that shows $750,000 BIPD but the carrier's BMC-91 on file with FMCSA shows a different insurer. The certificate says one thing. The federal filing says another. I want to know about that before the load moves, not after.

This matters because, for a carrier like DOT-3567102 / MC-1247893, a 14-month-old company with 8 trucks and a spotless SAFER snapshot, the onboarding packet is your only contemporaneous evidence. There's no inspection history to lean on. No years of relationship. You're betting on what you can document about this specific evaluation.

The 91X question at onboarding

One thing I always check at onboarding that most brokers skip: the BMC-91X vs. BMC-91 distinction on the carrier's insurance filing. 49 CFR § 387.11 requires carriers to maintain financial responsibility through specific filings. A BMC-91 is an endorsement from an admitted insurer. A BMC-91X is a financial responsibility filing from a surplus lines insurer — one that isn't licensed through the state's guarantee fund.

That matters because surplus lines carriers can exit the market, decline renewals, or become insolvent without the backstop you'd get from an admitted insurer. When I see a BMC-91X, I'm not saying don't use the carrier. I'm saying I want to know the insurer's paper and I want a current certificate that I can verify, not just the federal filing. That goes in the onboarding record.

If the carrier's coverage lapses and DOTScreener's continuous monitoring flags it, that flag — timestamped, linked to the original onboarding record — shows that my evaluation was dynamic, not a one-time checkbox. That's the paper trail holding up.

The whole thing lives on the screening record. It didn't take longer. It just happened through a structured process instead of scattered emails. And that structure is the only thing that makes it readable in discovery two years later.

Montgomery v. Caribe Transport II, LLC didn't change how to vet a carrier. It changed what happens when you can't prove you did it. The document collection you've been doing the same way for ten years might be fine. But if your evidence depends on someone reconstructing a timeline from email metadata and memory, you're in a worse position than you think.

The carrier packet is a timestamp. Every piece of it should be able to answer the same question: what did you know, and when did you know it?

How I document this

At onboarding:

• DOTScreener screen, timestamped (authority, insurance, BASIC scores, active BMC-91/91X filings)
• Carrier packet completion record via DOTScreener: e-signed agreement with verifiable identity check, COI, W-9 — all timestamped together
• AI document review output flagging any mismatches between submitted COI and FMCSA insurance filings
• Note on BMC-91 vs BMC-91X, insurer name and AM Best rating if the carrier is on surplus lines paper

Per-load (or per-quarter for regular carriers):

• Date of screening for this specific load, or a continuous monitoring confirmation that nothing material changed since onboarding
• Current insurance pull from FMCSA L&I, dated within 30 days of load
• Verifi™ truck/trailer verification if the load carries a double-broker signal or the carrier has under 18 months authority

This is what I can hand a lawyer and have it hold up. Not because it's elaborate. Because every date on every document answers the same question.

— Mason Lavallet

Founder, DOTScreener.com