Your Carrier Approval Expires. You Just Don't Know When.

A driver working for MC-982741 ran a red light outside Knoxville last February and hit a minivan. Two people went to the hospital. One came out with a spinal injury that required surgery and six months of physical therapy — about $340,000 in medical bills before the case settled.

The shipper's broker had a clean vetting file on that carrier. One pull date. One SAFER snapshot. One ACORD 25. That was it.

Sixteen months old.

What the plaintiff's expert found in discovery: MC-982741 had picked up two OOS orders in the nine months before the crash — brake and steering defects on separate units. Both cleared without a load loss or incident. But between those OOS orders and the date of the crash, the carrier's Vehicle Maintenance BASIC had climbed from the 61st percentile to the 84th percentile. The broker's approved-carrier file had none of this. It showed a carrier who looked fine in November 2024.

Nobody updated the file. Nobody was watching.

An Approval Is a Point-in-Time Snapshot

This is the thing nobody explains when you set up your carrier qualification process: approving a carrier doesn't cover you. It covers you on the date you ran those checks. Every load you tender after that date, you're operating on information that's going stale in real time — unless you've built something to catch what changes.

And things do change. Constantly.

OOS orders. FMCSA issues out-of-service orders under 49 CFR § 385.13 when an inspector or investigator finds an "imminent hazard" — a condition likely to cause serious injury or death if not immediately corrected. These aren't minor paperwork violations. An OOS order targeting a carrier's brake systems means FMCSA decided those trucks shouldn't move until it's fixed. The order clears from active status once the carrier addresses it, but the inspection records stay on SAFER. A broker who approved a carrier in January has no idea whether that carrier picked up an OOS order in April unless someone went and looked.

BASIC percentile movement. CSA scores update every month. A carrier at the 55th percentile on Vehicle Maintenance when you approved them can be sitting at the 80th percentile four months later after a rough inspection cycle. The FMCSA intervention thresholds under 49 CFR Part 385, Subpart F are one benchmark, but litigation doesn't wait for you to hit an alert. A steadily climbing BASIC trend reads poorly in discovery even if it never crossed a formal threshold, especially when the crash involved equipment failure.

Insurance filing changes. Carriers switch insurers, let policies lapse, and reinstate coverage regularly. Your ACORD 25 from onboarding reflects the insurer of record on that specific day. Between that day and your next load, the insurer may have changed, limits may have been renegotiated, or there may be a lapse-and-reinstatement gap sitting in the FMCSA L&I database that nobody caught. The L&I database logs every filing event — a gap is visible if you're looking.

MCS-150 amendments. Carriers amend their Motor Carrier Identification Report when their fleet size, operation type, or principal officers change. A carrier who reported 8 power units when you approved them and now operates 22 is running more miles, more drivers, more exposure. The MCS-150 amendment date will tell you when the fleet grew. If you never looked, you don't know.

Safety rating changes. A "Satisfactory" rating can flip to "Conditional" after a compliance review. The process is slow — FMCSA can take months to act even after a problematic investigation — but it does change. And it has direct legal significance: tendering loads to a carrier with a "Conditional" or "Unsatisfactory" rating is harder to defend than using a "Satisfactory" carrier, regardless of what the BASIC scores show.

The "What Did You Know and When" Problem

After Montgomery v. Caribe Transport II, the Supreme Court settled in May 2026 that the FAAAA does not preempt state-law negligent selection claims against freight brokers. Unanimous opinion. What that ruling means in practice is that the analysis plaintiffs' lawyers have always wanted to run — "what did this broker know, when did they know it, and was their selection reasonable given that knowledge" — can now happen in state courts without hitting a preemption wall.

That framing makes monitoring a legal question, not just a process question.

If your carrier selection duty is ongoing — and the negligence standard says it is — then satisfying it once at onboarding and never looking again is thin. A plaintiff's attorney who finds a 16-month-old vetting file with zero activity between approval and crash has an easy argument: "Did you know what this carrier's profile looked like at the time of the crash? No. Did you have the tools and the means to check? Yes. Did you check? No."

That's a difficult place to sit in deposition.

49 CFR § 371.3 requires brokers to keep transaction records for three years. It doesn't say how often you have to re-vet. But silence on frequency is not freedom to ignore what changes. Courts look at what a reasonably careful broker would have done — and a reasonably careful broker, operating in 2026 with access to SAFER, the L&I database, and monitoring tools, would have known that MC-982741 had a climbing BASIC and two cleared OOS orders before they tendered that load.

The standard is what you should have known, not just what you did know.

What Actually Triggers a Re-File

Not every change in a carrier's profile needs a response. Carriers pick up minor violations. BASIC scores fluctuate. The question is which changes should send you back to the file to make a documented, dated decision.

An active OOS order is a hard stop. Before the next load moves, you should know it's cleared, and you should have the OOS order number, the cleared date, and a note about what the violation was. A carrier operating under an active OOS order is a carrier FMCSA has said shouldn't be moving freight. Tendering to them anyway creates a whole different level of exposure.

A BASIC percentile crossing your review threshold — wherever you set it — should trigger a pull and a written decision. The decision doesn't have to be "no." It can be "Vehicle Maintenance at 71st percentile, above our 65-point review trigger; 28 total inspections over 18 months, most recent four inspections clean, decision to continue with confirmation call before next tender." That's a defensible record. "I didn't notice" is not.

Any change in the L&I insurance history — new insurer, a shorter coverage period than expected, a filing gap — should trigger a fresh ACORD 25 request and a call to the insurer to confirm current limits. This takes 20 minutes. The alternative is discovering at claim time that the policy the carrier had during your load isn't the policy you thought they had.

An MCS-150 amendment showing a significant fleet size increase is worth a second look, especially on shorter-tenure carriers. A carrier who went from 6 trucks to 19 in eight months is operating a fundamentally different business than the one you approved.

How DOTScreener Handles This

The reason I built Continuous Monitoring into DOTScreener is that I watched good brokers get surprised by changes they had no system to catch. Running manual re-pulls on every carrier in your approved list isn't realistic at scale. You end up doing it for nobody.

DOTScreener watches every carrier in your approved list and flags when something changes — an OOS order issued, a BASIC percentile spike past your configured threshold, an insurance status shift in the L&I data, an authority status change. When a flag fires, it kicks off a re-file: a new dated Carrier Selection Record that captures the current snapshot and your decision on whether to continue tendering loads.

That re-filed record is what changes your litigation posture. Instead of a file that shows one check from 16 months ago, you have a file that shows sustained attention — monitoring active, flag received, carrier reviewed, decision documented. That's how you answer the "did you look" question.

The record doesn't need to show the carrier was perfect. It needs to show that you were paying attention and that every decision to use them was deliberate, dated, and based on current information.

How I Document This

When a monitoring flag fires, my re-file record captures:

• Date of the flag and what triggered it — specific BASIC that moved, OOS order number, or insurance change
• Current SAFER snapshot with the relevant data at that moment
• My decision: continue, hold pending review, or remove from approved list
• If continuing: a written rationale — "Vehicle Maintenance BASIC at 68th percentile, above review threshold; 31 total inspections over 22 months with no brake violations in the most recent five; decision to continue with confirmation call before next tender"
• If it was an OOS order: the order number, what the violation was, and the cleared date before any loads moved
• Who ran the review and when — timestamped

DOTScreener's Carrier Selection Record captures this automatically when you act on a flag. The timestamp, the SAFER data pull, the decision text — all in the file. I built it that way because I know from experience that documentation discipline collapses when you're running at capacity. The system has to make it easy or the habit doesn't stick.

The Bottom Line

Your approved carrier list is a list of carriers who were acceptable at a specific point in time. Every load you tender to a carrier you haven't looked at since onboarding is a load you're booking without fully knowing who you're dealing with today.

Post-Montgomery, that gap has real consequences. Not every broker who runs a stale approved list will get sued — most won't. But if a crash happens and you end up in front of a jury, the question of whether you maintained a monitoring practice and re-filed when conditions changed will matter. And "we approved them 18 months ago and assumed nothing changed" is a hard position.

The re-file isn't paperwork. It's proof that you did your job continuously, not just once.

— Mason Lavallet

Founder, DOTScreener.com