Your Carrier Approval Isn't a Document. It's a Timestamp.

A broker I know spent three years approving carriers the same way most of us do: pull SAFER, check insurance, confirm operating status, add them to the approved list. That list had maybe 400 carriers on it. He treated it like a bank account — once a carrier was in, they were in.

Then a carrier on his list had a fatal accident. Driver ran a red light, T-boned a minivan. Five people in the hospital, one dead. His attorney asked for the carrier file.

The "approval" was dated fourteen months earlier. In the intervening time, the carrier's Unsafe Driving BASIC had crossed into the 88th percentile, they'd picked up two OOS violations for brake defects, and their insurance had lapsed twice and been reinstated. None of that was in his file. His documentation showed he'd vetted the carrier once — before any of that happened — and then used them repeatedly without re-screening.

That approval didn't protect him. It buried him. It showed a jury that he knew vetting was his job, did it once, and then forgot about it for over a year.

What a Carrier Selection Record Actually Is

A lot of people in this industry use "carrier approval" and "Carrier Selection Record" interchangeably, and they're wrong. An approval is the status you give a carrier. The CSR is the document that explains why you gave it, what you looked at, and when.

The distinction matters because an approval in a spreadsheet is a conclusion. A Carrier Selection Record is evidence. It shows what data you reviewed, what the data said at the moment you reviewed it, and that you made a conscious judgment before putting freight on that truck.

What the record needs to capture:

The when. Not just the date — the timestamp. Plaintiff's attorneys sequence everything. If your FMCSA pull happened at 2:47 PM and the BOL was signed at 1:30 PM, the carrier was already dispatched when you ran the check. That's not documentation of diligence. It's documentation of a process that ran backward.

The specific data points you reviewed. Operating authority status, yes. Safety rating. BASIC scores with actual percentile numbers, not just "checked." Insurance filing type and carrier name, with the policy number. If you looked at crash history, how many crashes in what window. If you reviewed inspection history, what the OOS rate was and how many inspections it was based on. "Reviewed FMCSA" tells a jury nothing. "Carrier showed Satisfactory rating, Unsafe Driving BASIC at 47th percentile, 0 crashes in 24 months, cargo insurance through Canal Insurance, policy #CI-8843-21, verified active via FMCSA L&I at 2:47 PM CT" is a record.

Your judgment call and why. If anything was out of the ordinary — authority under 12 months, a BASIC score you decided was acceptable, a gap in inspection history — note it and note why you proceeded. The absence of a note is worse than a note that explains a decision. Silence looks like you didn't notice.

The specific load context. Dry van lane, hazmat, oversize permit, reefer — these have different risk profiles and different due diligence requirements. A CSR for a standard dry van load is different from a CSR for a 12-axle oversize move through three states.

The Problem With the Approved List

Here's where most brokers go wrong: they conflate carrier approval with load-tender vetting.

An approved list solves for "is this carrier generally acceptable to work with." It doesn't answer "should I put this load on this carrier today." Those are different questions with different answers, and the gap between them is where negligent selection exposure lives.

A carrier can be on your approved list and be in the middle of an FMCSA intervention. They can have picked up a new OOS pattern since your last review. Their insurance carrier might have left the market and the new policy might have lower coverage. If your only defense is "they were on our approved list," the next question is when you last verified what you approved.

49 CFR Part 371 doesn't actually spell out a specific CSR format or re-verification schedule for brokers — that's both a gap and a trap. The gap is that nobody's forcing you to document anything specific. The trap is that courts, post-Montgomery v. Caribe Transport II, are increasingly asking what a "reasonable broker" would do, and reasonable brokers don't approve a carrier once and coast on that for 14 months while the carrier's safety record deteriorates.

When the Record Expires

There's no official shelf life on a CSR. FMCSA doesn't say "re-vet every 90 days." But here's the practical reality: your CSR expires the moment any material fact in it changes.

If a carrier's BASIC score crosses an alert threshold, the record you filed when it was below that threshold is now stale. If their OOS rate spikes after an FMCSA blitz, your pre-blitz data is a snapshot of a different carrier. If their insurance lapses and reinstates, the policy you verified is gone and a new one is in its place — and you don't know whether the new policy has the same limits.

The carriers I get most worried about aren't the ones with clean safety records that suddenly go bad. It's the ones with mediocre records that you approved as "acceptable" on a good month, and then used again six months later when that month was the exception, not the rule.

Take MC-1247893, DOT-3567102 — a 3-truck flatbed carrier out of Berea, KY. On the day you approved them: Satisfactory rating, Vehicle Maintenance BASIC at 52nd percentile, cargo OOS rate of 18%. Acceptable. Six months later: same Satisfactory rating (those don't update automatically), Vehicle Maintenance BASIC now at 79th percentile, cargo OOS rate up to 31%, one brake defect OOS violation in the last 90 days. Your approval said they were fine. Your new pull would say proceed with caution. But if you never pulled again, you're still operating off the old record.

That's what a plaintiff's attorney calls "constructive notice" — you had the ability to check, you had reason to check, and you didn't.

The Re-Filing Concept

The way I think about it: every time you run a carrier through a meaningful re-screen, you're filing a new CSR. Not updating the old one — filing a new record for that moment in time. The old record stays; it shows what you saw when you first approved them. The new record shows what you saw before this specific load.

This matters because a load-by-load re-check — even a quick one — is the difference between "we ran this carrier once and used them repeatedly" and "we check before each tender." The first is defensible only if nothing changed. The second is defensible almost unconditionally, because it shows you were actually watching.

The mechanics of re-filing don't need to be complicated. A timestamped pull of operating status, BASIC scores, and insurance verification takes 90 seconds in DOTScreener. The record generates automatically with the carrier's data at that moment, attached to the load context. If something's changed since the last pull, the system flags it before you dispatch.

That's what Continuous Monitoring does — it's not just watching the carrier's profile between loads, it's giving you the trigger to re-file the record when something changes. An alert on a BASIC threshold crossing or an insurance status change isn't just a notification. It's a re-screening prompt that lets you generate an updated CSR before the next tender. The re-filed record becomes proof that you responded to the change instead of ignoring it.

The Deposition Question You Don't Want to Answer

Plaintiff's attorneys have gotten very good at one specific question. They'll ask: "When was the last time you verified this carrier's safety status before the load date?"

If the answer is "I checked them when I first approved them," the follow-up is: "And how long ago was that?"

If the answer is "I ran them through our system before each tender," the follow-up is: "And what system is that? What data does it pull? And you have a record of the pull on [date of load]?"

You want to answer the second version. The second version has a document attached to it. The first version has a spreadsheet cell with a date that's over a year old.

Post-Montgomery, that question isn't hypothetical. The Supreme Court's decision in May 2026 confirmed that state-law negligent-selection claims against brokers survive FAAAA preemption. State courts can now hear those claims. State juries can now decide what a "reasonable" broker would have done. And state courts don't have the institutional knowledge of the federal court system when it comes to the freight industry. You want your documentation to be so clear that no one has to explain it.

A CSR that shows a load-level re-check — with current data, a timestamp, and specific numbers — is that clarity.

How I Document This

Here's what a defensible load-level CSR looks like for a standard dry-van tender:

Carrier: [Legal name, MC#, DOT#]

Screened: [Date and time — to the minute, in local or UTC, whichever you're consistent about]

Operating authority: Active, for-hire motor carrier authority

Safety rating: Satisfactory (or Not Rated — note the date of last compliance review if available)

BASICs reviewed: List the ones you actually looked at, with the percentile. If the BASIC is "insufficient data," note that — it's a fact, not a pass.

Insurance: [Policy type, carrier, policy number, effective/expiration date, verified via FMCSA L&I]

Flags: Any OOS violations in the last 90 days, any carrier-level flags from your network, any open interventions

Load context: Lane, commodity, trailer type, estimated value

Disposition: Approved / Approved with conditions / Declined

Reviewer: Your name

If you're using DOTScreener, the screen generates most of this automatically and attaches it to the carrier's record. The re-file is triggered when continuous monitoring shows a material change. If you're not, you're building this in a spreadsheet and hoping your timestamps are granular enough to matter.

Either way — the document is the record. The timestamp is the spine. And the file either holds up under deposition, or it doesn't.

Most don't. Yours should be the exception.

— Mason Lavallet

Founder, DOTScreener.com