The score you pulled at quote is not the score at tender
Most brokers and shippers run an SMS check once — at booking, when the carrier is being vetted for the first time. The score is good, the thresholds are clear, and the load is tendered.
What gets missed is the second check. The FMCSA's Safety Measurement System is not a static lookup. A carrier that passed every threshold at booking can have a new violation, an open investigation, a driver disqualification, or a Crash Indicator BASIC tick by the time the load actually moves. Hours or days may have passed. The carrier's data has not stood still.
If the post-tender SMS check shows the carrier has crossed into a red threshold, the broker is now tendering freight to a carrier the FMCSA is actively flagging. That is the part that turns a normal load into a liability event.
What the SMS actually measures
The Safety Measurement System evaluates carriers across seven Behavior Analysis and Safety Improvement Categories (BASICs):
- Unsafe Driving — hours-of-service, speeding, reckless driving violations
- Hours of Service Compliance — log violations, fatigue-related issues
- Driver Fitness — licensing, medical certificate, qualification violations
- Controlled Substances/Alcohol — failed tests, use or possession violations
- Vehicle Maintenance — out-of-service rate on inspections
- Hazardous Materials Compliance — placarding, shipping paper, packaging violations
- Crash Indicator — pattern of crash involvement relative to fleet size
Each BASIC is scored 0–100, with percentiles against peer carriers. A percentile above 80 in any single BASIC triggers an Intervention Threshold. Two or more BASICs above 90 triggers an Investigation Threshold. The thresholds are not a one-time event either — they re-evaluate monthly as new data comes in.
What changed: the Montgomery ruling
For years, brokers relied on the Federal Aviation Administration Authorization Act preemption to argue that state-law negligence claims related to carrier selection were preempted. The June 2025 SCOTUS ruling in Montgomery v. CSX narrowed that preemption significantly. Brokers can no longer assume FAAAA shields them from state-law claims about how they vetted the carrier they tendered to.
The practical translation: documented SMS review at the time of tender is no longer optional. A broker who booked a carrier with a clean score three days ago and tendered without re-checking is exposed if that carrier's score crossed a threshold in the interim and something went wrong on the load.
The four practical steps
Here is what a defensible carrier vetting workflow looks like:
- Initial SMS pull at quote or onboarding — record the score, percentile per BASIC, and the date you pulled it. This becomes part of the carrier's file.
- Re-pull SMS within 48 hours of tender — same metrics, fresh timestamp. If anything has moved, you make a documented decision before tendering.
- Flag changes since last haul — if you have worked with this carrier before, compare the new pull to the prior pull. A jump of 10+ percentile points in any BASIC is a conversation, not an automatic disqualification, but it is on the record.
- Document the decision — even when the call is "proceed with tender, here is why," that note is your defense if the load goes sideways. Timestamp, score, who reviewed it, what the threshold comparison showed.
What this is not
An SMS pull is not a substitute for insurance verification, authority status, or operating history. It is one input in a layered vetting process. But it is the input that has gotten the most legal attention recently, and the input that is most likely to be checked after an incident.
The straight-shooter takeaway
Pulling SMS once at booking was acceptable when the legal environment was simpler. After Montgomery, a single pull is not enough. The data moves, the legal standard moved with it, and the broker who documents a fresh pre-tender check is the broker who does not have to explain themselves after the fact.
BKE pulls SMS at quote and again at tender, every time, on every load. It is not glamorous work and it adds a step to the workflow. It also keeps the company off the wrong end of a liability claim. That trade is worth it.
