The standard: ordinary care, proven
Negligent selection is not about being right. It is about being reasonable, and being able to show it. The law asks a narrow question: did you take the steps a careful broker or shipper would have taken before you selected this carrier for this load? You are not the insurer of the carrier's safety. But you are responsible for your own selection process — and after Montgomery v. Caribe removed the FAAAA preemption defense, that process is what gets examined in discovery instead of the case being dismissed at the threshold.
Anatomy of a defensible selection file
A file that demonstrates ordinary care has six parts. Each one answers a question a plaintiff's expert will raise.
- Live FMCSA snapshot at selection. Authority, insurance, safety rating, SMS BASIC alert status, 24-month crash history, and out-of-service rates — captured with a timestamp, not recalled later.
- A written carrier-acceptance policy. The thresholds you apply, in writing, so the decision is a policy applied consistently rather than an ad-hoc judgment call.
- Recorded checklist results. Which checks passed, which flagged, and how each flag was handled for this load.
- Documented reasoning on exceptions. Where anything needed justification, a contemporaneous note of why the load was tendered anyway — signed by the person who made the call.
- Broker-vetting evidence (for shippers). If you used a broker, proof that you reasonably vetted the broker too.
- A tamper-evident audit trail. A hash-linked record so the file is verifiably unchanged at any future point.
The gap plaintiffs exploit
Most operations do some of this. They pull a snapshot, or they have an informal rule, or a rep remembers checking. What they rarely have is all of it, captured contemporaneously, applied consistently, and preserved so it cannot be second-guessed. That gap — the difference between "we usually check" and "here is the timestamped record of what we checked on this load" — is precisely where a negligent- selection case is won or lost.
How DOTScreener produces the file
DOTScreener runs the checks against live FMCSA data, applies your written acceptance policy automatically, records the decision and any exception reasoning, collects the carrier's attestation through a cross-device portal, and seals it all in a timestamped, hash-linked Carrier Selection Record — generated as a side effect of the screening workflow, on every load, without anyone having to remember to build a file. It does not guarantee any litigation outcome; it produces the evidence that ordinary care requires.