# Sparse Carrier Inspection History: What Brokers Can Check Canonical: https://usdotdata.com/blog/sparse-carrier-inspection-history Author: John Hauler Published: 2026-10-01T07:13:04.874Z Updated: 2026-10-01T07:13:04.874Z --- Few or no recorded roadside inspections leave a broker or shipper with limited inspection evidence. They do not establish that a carrier is safe, unsafe, fraudulent or inactive. Record exactly which inspections are visible, the period they cover and the number behind any percentage. Then resolve the shipment questions that the public record cannot answer. This resource answers a specific question: **How should you evaluate a carrier when its public inspection history is sparse?** The output is a documented follow-up decision, not a home-made safety score. *Reviewed October 1, 2026. By John Hauler, USDOTData's editorial persona. This is independent analysis of public records and a suggested research workflow, not an FMCSA determination.* ## First distinguish zero, missing and unavailable Start with the exact USDOT number. Use [USDOTData's carrier lookup](https://www.usdotdata.com/) to locate the business, then open its official record. A similar company name is not sufficient identity evidence. Record the state you actually see: - **Zero inspections in a stated category and period:** the displayed count is zero. This does not describe every inspection the business has ever received. - **A small positive count:** there is some recorded evidence, but a percentage can change substantially with one additional event. - **A blank field or failed page:** the value was not obtained. Do not enter zero in your worksheet. - **Information not publicly displayed:** access is limited. This is different from an empty history. The [FMCSA Safety Measurement System](https://ai.fmcsa.dot.gov/sms) public notice explains that some property-carrier information is withheld. Public inspection and crash data remain available, while the Crash Indicator and Hazardous Materials Compliance BASICs are hidden from public view. A hidden category is not a favorable or unfavorable result. Do not ask for a carrier's login credentials to fill the gap. ## Attach a date and a scope to every number SAFER's [Company Snapshot](https://safer.fmcsa.dot.gov/CompanySnapshot.aspx) presents roadside inspection results for a stated 24-month period. Capture the endpoint printed on the page; your retrieval date does not redefine that window. The [SMS Help Center](https://ai.fmcsa.dot.gov/SMS/HelpCenter/Index.aspx) explains that SMS takes a monthly snapshot from FMCSA's Motor Carrier Management Information System and uses the preceding 24 months of roadside inspection data. Therefore, a report dated after the current snapshot may not yet be represented in that release. Keep three dates separate: the inspection event, the source's data cutoff, and the day you checked it. If SAFER and SMS differ, compare those dates and the selected categories before declaring either record wrong. A carrier-supplied recent report may help explain a difference; it still needs to match the entity and inspection. Avoid dividing a two-year inspection count by today's reported truck count and calling the result an inspection frequency. The numerator and denominator may cover different fleets and periods. Sparse results could reflect limited operations, different operating exposure, an event outside the window or a reporting discrepancy. These are hypotheses to investigate, not explanations established by the count. ## Driver and vehicle counts answer different questions FMCSA's [enforcement glossary](https://ai.fmcsa.dot.gov/EnforcementPrograms/Glossary) defines driver inspections as Levels I, II, III and VI, and vehicle inspections as Levels I, II, V and VI. Some events contribute to both categories. Adding the category counts can therefore count the same event twice. A driver-only inspection does not establish that the vehicle underwent a mechanical examination. A vehicle-only inspection does not supply the same driver evidence. Hazardous-material and intermodal-equipment entries also need their own definitions; do not substitute their counts for vehicle inspections generally. The [inspection-level guide](https://www.usdotdata.com/blog/dot-inspection-levels-roadside-checklist) explains the scope differences in detail. For an out-of-service (OOS) rate, retain the relevant inspection count and the number of inspections with an OOS finding. Do not use the number of individual violations as the numerator. One inspection can record several violations, and violations do not all produce an OOS finding. ## A worked example: small denominators magnify one event **Hypothetical example — these are invented worksheet entries, not real carriers.** A shipper reviews three candidates for one dry-van shipment. All counts below concern vehicle inspections in the same stated 24-month window: - Candidate A: zero vehicle inspections. There is no observed vehicle-inspection denominator from which to assess an OOS frequency. - Candidate B: one vehicle inspection, with one OOS result. The arithmetic is 1 ÷ 1 = 100%. - Candidate C: ten vehicle inspections, with one OOS result. The arithmetic is 1 ÷ 10 = 10%. The percentages alone do not rank these carriers' overall safety. Candidate A has an evidence gap. Candidate B has one consequential observation whose scope, date and documented response need review. Candidate C has more recorded observations, but the same number of OOS events in this example. None of these summaries authenticates the proposed driver or establishes the condition of the truck arriving today. Now suppose B has another vehicle inspection without an OOS result. Its arithmetic rate falls to 50%. That change is not proof that its safety management improved by half; the denominator changed from one to two. The shipper's useful next step is specific. For A, identify what current equipment and operating evidence its selection procedure requires. For B, examine the cited issue and evidence addressing it. For C, review the actual event instead of accepting a lower percentage as clearance. All three still require shipment fit, identity, applicable authority and insurance checks. ## Keep a safety rating separate from inspection history FMCSA's [Motor Carrier Safety Planner](https://csa.fmcsa.dot.gov/SafetyPlanner/MyFiles/Sections.aspx?ch=20&eta=84282&sec=58) distinguishes Satisfactory, Conditional and Unsatisfactory safety ratings. Unrated means FMCSA has not assigned a safety rating. It does not mean Satisfactory, and it is not a fourth adverse rating. Record the displayed rating and its date separately from inspection counts. Do not manufacture a rating from an OOS percentage or treat a lack of inspection data as an explanation for why a rating is absent. The [safety-rating guide](https://www.usdotdata.com/fmcsa-safety-rating) provides additional context. Crash counts also need a separate record. [SAFER's crash summary](https://safer.fmcsa.dot.gov/CompanySnapshot.aspx) identifies involvement in reportable crashes, without deciding responsibility. FMCSA's [Crash Preventability Determination Program](https://www.fmcsa.dot.gov/crash-preventability-determination-program) provides a separate review process for eligible events. An event can remain listed after a Not Preventable determination. A sparse inspection history plus a crash count is not evidence of fault. ## Turn uncertainty into a bounded follow-up Our suggested workflow is to assign each unresolved question an owner and a piece of evidence that could answer it: 1. **Observed fact:** record the source, cutoff, category, count and result. Preserve the original labels. 2. **Fit hypothesis:** explain why the carrier may suit the move, such as a claimed equipment type or service area. Attribute unverified claims to the carrier. 3. **Verification task:** specify what is missing, such as the proposed equipment identity or documentation addressing a particular inspection finding. 4. **Decision:** apply the organization's selection procedure and customer requirements. Record the reviewer, unresolved conditions and recheck trigger. For a broker, this may mean assigning an equipment-identity question to carrier onboarding before tender. For a shipper, it may mean confirming loading requirements and escalating a documented inspection concern to the person responsible for carrier selection. Neither task can be completed by relabeling “no data” as “passed.” Keep inspection follow-up separate from the [carrier insurance-check evidence record](https://www.usdotdata.com/blog/carrier-insurance-check-evidence). A maintenance document cannot establish shipment insurance coverage. Equally, a service seller should not turn sparse inspection data into a claim that a carrier needs repairs, compliance software or consulting. A confirmed buying need requires independent business confirmation. ## Copyable review checklist - Exact USDOT number and legal name matched. - Source URL, retrieval time and displayed data cutoff saved. - Observation window and inspection category recorded. - Missing, zero and restricted information kept distinct. - Inspection count and OOS-event count retained together. - Underlying event details reviewed when relevant and available. - Rating, rating date and crash information recorded separately. - Carrier explanations labeled as claims until corroborated. - Shipment-specific identity, equipment, authority and insurance questions assigned. - Reviewer, decision conditions and next check documented. The next check should follow the unresolved issue: a new source release, a promised report or a changed shipment. Waiting for the next monthly snapshot does not resolve an immediate mismatch before pickup. ## Frequently asked questions ### Does no inspection history mean a carrier is new? No. A zero count in a particular window does not establish a founding date, registration date or authority date. Check those separately and ask the carrier about its operating history without treating its explanation as independently verified. ### Is a 0% out-of-service rate enough to approve a carrier? No. First determine whether there were relevant inspections at all. Zero OOS results among observed inspections answers a narrower question than whether the carrier fits a shipment or meets your selection requirements. ### Can an annual inspection document fill an empty roadside history? It can provide different evidence about a particular vehicle, but it does not create a roadside event. [FMCSA's periodic-inspection guidance](https://www.fmcsa.dot.gov/safety/question-1-can-violation-free-cvsa-level-i-or-level-v-inspection-be-used-satisfy-periodic) also states that a CVSA Level I or V inspection is not equivalent to the federal periodic-inspection requirement. Preserve each document's purpose. ### How many inspections make a carrier safe? This workflow establishes no such threshold. A larger count provides more observations, but counts alone do not establish overall safety. Review event scope, timing and findings alongside the other evidence your selection process requires. ### What if the carrier supplies a report absent from SMS? Compare its event date with the SMS cutoff and match the USDOT number and report details. Label the document's source. An explained timing difference is different from a verified correction to the official dataset. ### Should a missing SMS category be treated as a clean result? No. First determine whether the category is publicly available and whether a value was actually obtained. Preserve “not available” in the record; do not convert it to zero or infer a federal safety rating.