Your Carrier Packet Is Not Legal Protection

Ask a broker how they protect themselves from carrier-liability exposure and a huge number will say the same thing: *"We have a carrier packet on file for every carrier."* The W-9, the operating authority, the certificate of insurance, the signed broker-carrier agreement, the carrier's setup paperwork — all neatly stored in the TMS. It feels like diligence. It feels like protection.

It is neither. And the gap between how protective a carrier packet *feels* and how protective it actually *is* in a courtroom is exactly the gap that turns a routine load into a nuclear verdict. So let me say the uncomfortable thing plainly: **your carrier packet is not legal protection.** Here's why, and what actually is.

What a carrier packet actually proves

A carrier packet is an *onboarding* artifact. You collected it once, when you set the carrier up — which might have been three weeks ago, or eighteen months ago, or three years ago. It establishes a few facts **as they existed on that onboarding date:**

• The carrier was a real entity with a W-9.
• It held operating authority then.
• It had an insurance certificate then.
• It signed your agreement.

That's genuinely useful information — about the day you onboarded. But notice what it does *not* establish: it says nothing about whether the carrier was **safe**, and nothing about its condition on the day that actually matters in litigation — **the day you tendered the load.**

A packet is a photograph of a carrier's paperwork at one moment in the past. Litigation is about a different moment entirely.

The moment that matters is the tender, not the onboarding

After the Supreme Court's decision in *Montgomery v. Caribe Transport II*, the duty is settled: a broker (and the shipper behind it) owes a duty of **ordinary care in selecting a carrier**, and that duty is judged at the moment of **selection** — the tender — based on what was knowable *then.* Not at onboarding. At tender.

This is where the packet collapses, because carrier safety is not static. Between onboarding and the tender that crashed, any of the following can happen — invisibly, unless you look again:

• The carrier's **authority lapses or is revoked.**
• The **insurance gets cancelled** (the certificate in your packet is now worthless paper).
• The **BASIC scores cross into Alert** — Unsafe Driving, Hours-of-Service, Vehicle Maintenance.
• A **cluster of crashes** appears.
• The **safety rating** drops to Conditional.

Your packet captures *none* of this, because your packet stopped looking the day you filed it. The carrier that was clean at onboarding can be a documented hazard by the time you tendered — and the only thing your packet proves is that you didn't notice.

The deposition scene

Here's how this plays out in the room that decides the case. It's three years after a fatal crash. The plaintiff's attorney holds up your carrier packet.

*"This is your file for the carrier that killed my client?"*

"Yes."

*"And this is everything you checked before you trusted them with this load?"*

"We have a thorough onboarding process —"

*"I'm sure you do. This certificate of insurance — what's the date on it?"*

"...It's from when we set them up."

*"Which was nineteen months before this load. When did you last verify this carrier's safety record before you tendered?"*

"We... rely on the onboarding packet."

*"So the answer is you didn't. You never looked again. This carrier was flagged by the federal government for unsafe driving four months before the crash — it was free, it was public, and your file shows you never looked. You had a folder. You didn't have a process."*

That exchange is a loss, and it's a loss even if your onboarding was genuinely thorough — because in litigation, **a check you can't prove you performed at the relevant time is a check you didn't perform.** The packet is the wrong document, frozen at the wrong moment.

A packet is a folder. A screen is a process.

The distinction that matters — and it's worth burning into your operation — is **packet vs. screen:**

• A **carrier packet** is collected *once,* at onboarding, and sits in a file. It proves the carrier existed and had authority *then.*
• A **carrier screen** is performed *at tender, every time,* and captures the carrier's *current* safety profile — rating, BASICs, OOS rates, crash history, authority and insurance status — *as it exists on the day you're entrusting them with this load.*

Everyone has a packet. Almost no one, when pressed, can produce a *screen* — a dated, per-load record of the carrier's safety picture as of the tender. And the screen is the only thing that answers the question the law actually asks: *did you exercise reasonable care in selecting this carrier, on this load, on this day?*

A packet can't answer that question. It was never built to. It answers "did we onboard them properly," which is not the question a plaintiff's attorney — or a jury — is asking.

What actually protects you

Real protection isn't a fatter packet. It's a different *kind* of artifact:

1. **Screen at tender, not just at onboarding.** Capture the carrier's current FMCSA safety profile every time you tender, against a written standard.

2. **Timestamp it.** The record has to prove *when* you looked, so it can't be dismissed as reconstructed after the fact.

3. **Capture the carrier's attestation** tied to the load — its signed representations about insurance and safety — so that if the carrier lied, your reliance was documented and reasonable.

4. **Retain it for years.** Claims surface late; a record purged after 90 days is no record when the subpoena arrives at month 30.

5. **Do it consistently** — every load, so there's no undocumented tender for the plaintiff to find.

Keep your packet — it still has its uses for setup and contracting. Just stop mistaking it for the thing that defends you. The packet is the lobby. The screen is the vault.

Where DOTScreener fits

This is, bluntly, the entire reason DOTScreener exists: to produce the **screen**, not the packet. Every screening pulls the carrier's live FMCSA safety record at the moment of selection, evaluates it against your standard, flags the red flags, captures the carrier's risk-adaptive attestation, and freezes it into a **dated, retained, audit-logged record** — the per-load, timestamped proof of reasonable care that an onboarding folder can never be. It doesn't replace your carrier packet for setup; it replaces the *false belief* that the packet was protecting you.

When the plaintiff's attorney holds up your file three years from now, the difference between a folder and a defense is whether what comes out is an eighteen-month-old certificate — or a timestamped screen from the morning you tendered. Build the screen. The packet was never going to save you.

— Mason Lavallet

Founder, DOTScreener.com

---

Sources

• *Montgomery v. Caribe Transport II, LLC*, 608 U.S. ___ (2026) — duty of ordinary care judged at carrier selection
• [Restatement (Second) of Torts § 411 — Negligent Selection of an Independent Contractor](https://www.law.cornell.edu/wex/negligent_hiring)
• [FMCSA SAFER Company Snapshot](https://safer.fmcsa.dot.gov/CompanySnapshot.aspx) — the tender-date safety data a packet doesn't capture
• [FMCSA Safety Measurement System (CSA BASICs)](https://csa.fmcsa.dot.gov/) — Alert-status changes that occur after onboarding
• [FMCSA Licensing & Insurance (L&I)](https://li-public.fmcsa.dot.gov/LIVIEW/pkg_menu.prc_menu) — insurance status and cancellations that postdate a packet's certificate