Reading inspection and OOS history

roadside inspections are not a safety rating

A roadside inspection is an event. A safety rating under 49 CFR Part 385 is an FMCSA determination: Satisfactory, Conditional, Unsatisfactory, or Unrated. Unrated means FMCSA has not assigned a rating. It is not a hidden Unsatisfactory. Most small carriers are unrated.

Inspection reports produce violations and, sometimes, out-of-service orders. Those reports feed SMS / CSA. A percentile in Vehicle Maintenance is still not a rating. Do not tell a shipper “they have a 40 score” as if that were 49 CFR 385.

Use the rating as a gate. Use inspections as questions. Unsatisfactory is a hard stop until it changes. Conditional means FMCSA found problems and the carrier is still operating. Read the date. Then read recent inspections.

what OOS actually means

Out of service means the driver or the vehicle was not allowed to proceed until the condition was corrected. It is a roadside order, not a revocation of operating authority. Authority revocation is a different process on L&I.

A single OOS for a light two years ago is a data point. Repeat OOS for the same brake or tire defect in the last year is a pattern. Write the defect, not “they have OOS.” The next person on the desk needs the fact.

An OOS order that is still in effect on the census snapshot — allowed-to-operate N, or an FMCSA OOS order listed on SAFER — is not historical. That is current. Do not cover.

sample size versus fleet size

Compare inspection count to power units. A two-truck carrier with forty inspections in two years is being looked at constantly. A two-hundred-truck fleet with forty inspections is barely sampled. The same raw OOS count does not mean the same thing.

Small samples swing. One bad inspection on a one-truck carrier can dominate the file. That does not make the inspection imaginary. It means you ask about that truck and that date instead of citing a percentile as destiny.

Do not invent a national average and score them against it. You do not have a dated census ingest on this page that would support that. You have this carrier’s inspections, this fleet size, and this date. Stay inside that.

SMS Vehicle Maintenance as a question, not a score

The Vehicle Maintenance BASIC summarizes inspection defects relative to a peer group. A high percentile on a tiny fleet is noisy. A high percentile plus three recent lighting or brake OOS events is a conversation.

Ask: why are the last inspections lighting. Ask: is the unit on this load the unit that was OOS. SMS will not name your trailer. The carrier’s shop record might. If they cannot talk about the last OOS, you are not talking to operations.

Do not recite a BASIC number to a shipper as a safety rating. If you need to explain Vehicle Maintenance, say you saw repeat equipment defects on roadside reports and you asked the carrier. That is the true statement.

SMS Hours-of-Service as a question, not a score

The HOS BASIC summarizes hours-of-service and related violations relative to peers. It is not proof the driver on your load will run legal tonight. It is a reason to ask how they dispatch and whether the pickup appointment is realistic.

A clean HOS BASIC with a driver who cannot produce logs at the dock is still a problem. A noisy HOS BASIC on a new-entrant with three inspections is a small sample. Read the actual violations: form-and-manner versus driving over hours are different operational facts.

For a long lane, the appointment math is part of the inspection read. If the only way to make pickup and delivery is a 19-hour drive day, you are booking the violation. That is on you as well as them.

new authority and thin files

New-entrant carriers under 49 CFR Part 385 Subpart D often have few or no inspections. A clean SMS display can mean no data. It does not mean a clean history. Pair a thin inspection file with identity and insurance checks, not with a shrug.

Do not treat “no inspections” as a plus without noting the authority grant date. A three-week-old MC with zero inspections is expected. A five-year-old MC with zero inspections and twenty power units is odd. Ask how they avoid roadside contact. Write the answer.

Chameleon patterns sometimes reset the inspection file by reincarnating the DOT. If officer, phone, or address overlap an OOS carrier, the new snapshot’s empty inspection tab is not comfort. See the chameleon check before you celebrate a clean BASIC.

how to write inspections in the load file

Record last inspection date, last OOS date, power units, and the official safety rating with its date. Separate those four fields. Mixing them into “looks fine” is how a Conditional rating gets forgotten.

If you pass a carrier with recent OOS, write why: defect corrected, different unit, shipper accepted Conditional, extra cargo limit. The reason belongs next to the snapshot. The next dispatcher should not have to reverse-engineer your yes.

Re-check on the next dispatch if you have not used them in a while. Inspection files grow. Ratings change. A PDF from onboarding is a timestamp, not a live status.

when inspections change the booking, and when they do not

A Conditional rating plus recent brake OOS on a small fleet is a reason to pass, or to book only after the carrier names the unit and the repair. A Satisfactory rating with one lighting ticket last year is not a reason to skip identity and insurance. Inspections sit beside those checks. They do not replace them.

Shippers sometimes ask for “no OOS in 12 months.” That is their contract, not 49 CFR 385. If you agree to it, apply it as written and record the last OOS date. Do not relabel an SMS percentile as that promise. You will not be able to defend the relabel.

If the only inspections on file are clean walk-arounds at a scale the carrier never misses, you still have a sample-size problem. Note it. For high-value or hazmat, thin files push you back to identity, insurance amount, and permits — the parts that do not need a large inspection history to be true or false.

desk checklist

• Official 49 CFR 385 safety rating and date recorded separately from SMS.
• Last inspection date and last OOS date noted.
• Inspection count compared to census power units — no peer-average invented.
• Vehicle Maintenance used as a question about recent equipment defects, not a recited score.
• HOS used as a question about this lane’s hours, not a recited score.
• Unrated + new authority triggers identity/insurance extras, not a free pass.
• Current OOS order or allowed-to-operate N is a stop.

what belongs in the load file

• SAFER / SMS snapshot with rating, inspection dates, and check timestamp.
• Power-unit count from the census record.
• Note of any OOS in the window you reviewed, with defect type.
• Questions asked (VM/HOS) and the carrier’s answers, if you still covered.

fail closed

• Unsatisfactory rating still in effect.
• FMCSA out-of-service order in effect or allowed-to-operate = N.
• Repeat OOS on the same defect class in the recent file and no operational explanation.
• You cannot separate the rating from an SMS percentile and the shipper is being told a “score” as if it were 385.
• Thin inspection file plus failed identity or insurance check.