A monthly change in a carrier's Safety Measurement System (SMS) percentile is hard to investigate when the inspection report, driver vehicle inspection report (DVIR), repair order, and driver record sit in different systems. Fleets call these percentiles CSA scores, but CSA is FMCSA's safety compliance and enforcement program, and the What Is CSA? factsheet explains how SMS produces the percentile ranks behind that shorthand.
SMS analyzes inspection, violation, and crash data across seven Behavior Analysis and Safety Improvement Categories, or BASICs. Percentiles run from 0 to 100; a higher percentile means worse relative performance, and reaching the applicable intervention threshold can flag a carrier for FMCSA's attention, though the percentile itself is not a formal safety-fitness rating. A percentile change usually traces back to a specific inspection, violation, or crash record.
That tracing matters beyond conventional trucking fleets. Heavy-civil contractors, ready-mix producers, and aggregate suppliers running dump trucks or equipment haulers may operate regulated commercial vehicles, and their inspections reach the same profile. The sections below cover what the scores measure, how FMCSA calculates them, how to check a carrier profile, and how to work the records behind a rising percentile, including the driver qualification files behind Driver Fitness.
What CSA Scores Measure
Use BASIC-level results to identify which safety areas require review. The CSA program combines the Safety Measurement System with interventions and a Safety Fitness Determination system. SMS is a workload-prioritization system. SMS identifies carriers that may warrant warning letters or investigations, including targeted roadside inspections.
The Seven BASICs
SMS evaluates safety data from the preceding 24 months. It organizes that data into seven BASICs:
Unsafe Driving: Speeding, reckless driving, improper lane changes, texting while operating a commercial motor vehicle, and seat-belt violations.
Crash Indicator: The frequency and severity of qualifying state-reported crashes.
Hours-of-Service Compliance: Violations involving records of duty status, driving limits, ELD use, and driver alertness requirements.
Vehicle Maintenance: Defects and failures involving brakes, tires, lights, inspections, repairs, and other vehicle systems.
Controlled Substances/Alcohol: Prohibited possession or use and related regulatory violations.
Hazardous Materials Compliance: Problems such as leaking containers, improper packaging, or incorrect placarding.
Driver Fitness: Invalid licenses, missing qualifications, and medical-certification issues.
The categories connect roadside findings to specific areas of fleet operation.
Where Built World Fleets See Risk
For built world fleets, these categories provide practical review points. Vehicle Maintenance can expose recurring brake, tire, or lighting failures on dump trucks and lowboys, the same units where a bad load plan shows up later as an axle-weight violation at the scale. Driver Fitness can reveal gaps in CDL and medical records. HOS Compliance becomes a concern when drivers exceed an applicable short-haul exception or when time records don't show they qualified for it.
How FMCSA Calculates CSA Scores
Review the calculation method when a BASIC percentile changes unexpectedly or when prioritizing corrective action. Under the current Safety Measurement System methodology, FMCSA calculates a separate measure within each BASIC. It may assign a percentile after comparing the carrier with peers that have similar numbers of relevant safety events.
How Events Become BASIC Measures
FMCSA's SMS Methodology document describes the current calculation in several stages:
Assign a severity weight: Each violation receives a BASIC-specific weight from 1 to 10. A weight in one BASIC is not directly comparable with the same weight in another.
Add out-of-service weight: An out-of-service violation receives 2 additional points.
Apply the inspection cap: Violation severity weights from one inspection are capped at 30 within each BASIC before time weighting.
Apply time weighting: Events from the most recent 6 months receive a 3× multiplier. Events older than 6 months but no more than 12 months old receive a 2× multiplier. Events older than 12 months but within the 24-month window receive a 1× multiplier.
Calculate the BASIC measure: SMS normalizes the carrier's weighted violations using the applicable exposure measure.
Compare peer carriers: SMS groups carriers with sufficient data by relevant inspections, crashes, or violations and ranks them from 0 to 100.
Why Percentiles Move
A higher percentile means worse relative performance. Because the percentile depends on peer performance, a carrier's percentile can rise even when its underlying measure improves if comparable carriers improve more, as the National Academies motor carrier report explains. That is why the source measure and peer comparison matter more than the headline percentile alone.
This also explains the limited meaning of "7 CSA points." Seven may describe a violation's severity weight within one BASIC. The carrier's BASIC percentile depends on the violation, time weight, out-of-service status, and peer group.
What Is a Good CSA Score?
Check the applicable intervention threshold when a BASIC percentile rises month over month. FMCSA publishes these thresholds by carrier type, and the operational goal is staying below the applicable one while continuing to reduce preventable violations.
Table 2-2 of that SMS Methodology document lists the following current intervention thresholds.
BASIC | General carrier | Hazmat carrier | Passenger carrier |
|---|---|---|---|
Unsafe Driving | 65% | 60% | 50% |
HOS Compliance | 65% | 60% | 50% |
Crash Indicator | 65% | 60% | 50% |
Vehicle Maintenance | 80% | 75% | 65% |
Controlled Substances/Alcohol | 80% | 75% | 65% |
Driver Fitness | 80% | 75% | 65% |
HM Compliance | 80% | 80% | 80% |
Crossing one of these thresholds may contribute to FMCSA's intervention prioritization, but it leaves the carrier's official safety rating unchanged, consistent with the distinction FMCSA draws between an SMS percentile and a formal safety-fitness rating. Treat movement toward a threshold as an early trigger and act before the percentile crosses it.
How to Check Your CSA Scores
Use the SMS carrier portal to review roadside inspections, violations, crashes, BASIC measures, and other available safety information by USDOT number.
Check the Complete SMS Profile
Property carriers need authorized access to view their complete SMS results. Public visitors can see absolute measures for five BASICs. Viewing property-carrier percentiles requires authorized profile access. The Seven BASICs visor shows that Crash Indicator and Hazardous Materials Compliance information also require authorized profile access. A carrier must log in through the FMCSA Portal to view its complete SMS results.
Use SAFER for Official Records
Use the SAFER Company Snapshot when you need registration information, out-of-service inspection summaries, crash history, and the carrier's official safety rating, if one exists. Search SAFER using a USDOT or MC/MX number. You can also search by company name.
Run the Monthly Review
A sound monthly SMS review should compare the latest profile with the previous update and identify new inspections or crashes. It should trace each finding to the relevant driver and vehicle and collect supporting records. For a construction fleet, those records may include inspection reports, DVIRs, maintenance histories, time records or electronic logging device (ELD) logs, CDL qualification records, dispatch records, photographs, and dashcam footage, which is why document control decides how long the monthly review takes.
CSA Scores Versus Official FMCSA Safety Ratings
How SMS Differs From a Rating
CSA/SMS percentiles and official safety ratings answer different questions. BASIC percentiles are monthly prioritization metrics based primarily on recent on-road performance, and they do not directly change a carrier's safety rating.
What Each Official Rating Means
FMCSA issues an official rating through a rated investigation under 49 CFR § 385.3:
Satisfactory: Adequate safety-management controls are in place and functioning.
Conditional: Adequate controls are not in place to ensure compliance with the safety-fitness standard.
Unsatisfactory: The carrier lacks adequate controls and may be prohibited from operating in interstate commerce when the rating becomes final.
SMS tracks performance and intervention priority. SAFER tracks the official rating.
Check Both Systems
A carrier can have a Satisfactory rating while exceeding a BASIC intervention threshold. It can also have no official rating because it has not undergone a rated investigation. Check SMS for performance and intervention data; check SAFER for the official rating.
What Is DOT Compliance?
Check the operation's DOT compliance obligations whenever the fleet adds vehicles, drivers, routes, or new hauling types. DOT compliance means following the federal and state requirements that apply to a carrier, its drivers, and its commercial motor vehicles.
Federal and State Obligations
Depending on the operation, these obligations include registration, driver qualification, drug and alcohol testing, hours of service, inspections, repair and maintenance, crash reporting, and recordkeeping.
CSA is one part of DOT compliance. SMS measures selected on-road indicators and investigation findings. A carrier can have no percentile in a BASIC because it lacks sufficient data and still have significant compliance obligations.
Carrier Registration Requirements
The gap between a CSA percentile and a compliance obligation matters most for contractors hauling their own equipment and materials, including spoils. A private motor carrier may require a USDOT number even though it does not need for-hire operating authority. Interstate operations generally trigger federal requirements, while states may also require USDOT registration or similar compliance for intrastate fleets.
Short-Haul Recordkeeping
Local fleets should also document their use of the short-haul exception. Qualifying drivers may be exempt from records-of-duty-status and ELD requirements when they meet short-haul limits. They must remain within a 150-air-mile radius of the normal reporting location and not exceed a 14-hour duty period. That exception does not remove driver-qualification, inspection, or vehicle-maintenance duties.
How Contractors Can Improve CSA Scores
Start with the inspection or crash record behind the measure. Review the headline percentile in that context. Prioritize recent, high-severity, and out-of-service findings because time weighting gives newer events more influence.
Verify the Source Record
Review every new inspection: Match violations to the inspection report, driver, vehicle, dispatch record, and maintenance history, the same records a project document management workflow keeps aligned. Determine whether the record is accurate before designing corrective action.
Challenge inaccurate data: File a Request for Data Review when evidence shows an incorrect violation, crash attribution, out-of-service designation, or other eligible data problem. DataQs reviews accuracy. Eligible requests address data problems; objections based solely on a carrier's view that a valid rule is unfair fall outside that scope.
Evaluate eligible crashes: Submit qualifying crashes through the crash preventability program with the police report and available evidence. Dashcam video, photographs, GPS or ELD data, weather records, and witness statements can establish the sequence of events.
These checks establish whether the source data is accurate and complete. Use that verified record to identify operational gaps.
Close Operational Gaps
Correct recurring vehicle failures: Cross-check roadside findings against DVIRs, preventive-maintenance schedules, repair orders, and vendor invoices. Treat repeated brake, tire, or lighting violations as a trigger to review the inspection workflow, repair verification, and release-to-service decision.
Validate driver records: Compare the active-driver roster with CDL status, medical certification, qualification files, Clearinghouse queries, and required training records. Do not rely on a spreadsheet that is disconnected from dispatch assignments.
Audit HOS and short-haul records: Check ELD exceptions, unidentified driving, edits, personal-conveyance use, supporting records, reporting locations, radius limits, and duty-period limits.
Track corrective actions to closure: Assign an owner, due date, required evidence, and validation step. A policy update alone does not prove that the field workflow changed.
The completed record should document the finding and its resolution. Use that record to confirm that the corrective action changed the field workflow.
How Datagrid Executes CSA Monitoring Workflows
Use Datagrid's AI agents when a monthly review requires comparing the same inspection against records held in multiple approved systems. Construction fleet records may sit across connected systems and project files. This distribution makes the monthly SMS review difficult to reproduce. AI agents can execute the cross-checking so safety managers can focus on record conflicts, driver interviews, and corrective-action decisions.
Define Sources and Review Rules
Datagrid's agentic AI platform executes defined review workflows across connected systems. A documented monitoring workflow should identify approved sources such as Procore, SharePoint, Microsoft Excel, Google Drive, and Autodesk Construction Cloud, all of which Datagrid supports as integrations. It should define how records are compared and specify which SOPs apply. It should also establish how the team handles possible gaps and review materials.
Cross-Check Records and Route Exceptions
Use exception routing when an inspection report and the available maintenance history disagree. After a new inspection violation, the review should compare the inspection report with available maintenance histories, DVIRs, driver records, and internal procedures. Route conflicts to the fleet safety manager to determine the correct source.
Prepare and Validate Investigation Evidence
Before an investigation, project teams should check available project files against a defined evidence list and identify missing or inconsistent material. They should also review written procedures for gaps and compare record sets or policy versions for relevant differences. Datagrid's Audit Agent can verify project files against defined audit requirements and flag compliance gaps. The SOP Agent can review written procedures to surface gaps, compliance risks, and improvement recommendations.
These workflows still require FMCSA Portal access, legal interpretation, mechanic judgment, driver interviews, and management approval of corrective actions. Project teams must validate findings, resolve false positives, and confirm that assembled records are complete before relying on agent output.
Run CSA Monitoring With Datagrid’s Agentic AI
Datagrid's AI agents work the record side of a monthly CSA review across your connected inspection, maintenance, and driver systems, so safety managers spend their time on conflicts and corrective action:
Inspection-to-record cross-checks: Compare each new roadside violation against the DVIR, maintenance history, repair order, and dispatch record for that unit and date.
Driver file verification: Check the active-driver roster against CDL status, medical certification, qualification files, and Clearinghouse query records, and flag gaps before they reach Driver Fitness.
Evidence assembly for DataQs and preventability submissions: Pull the police report, photographs, GPS or ELD extracts, and witness statements into one package for the safety manager to review.
Written-procedure gap review: Compare the fleet's SOPs with the workflow the records actually show, and surface where they diverge.
Corrective-action tracking: Hold each finding with its owner, due date, required evidence, and validation step until someone closes it.
Fleet safety managers still decide which source record is correct, whether a violation is challengeable, and when a corrective action has genuinely changed the field workflow.
Get started with Datagrid and run your most recent month of inspections through the Audit Agent alongside your usual review to see which record conflicts it surfaces first.
Frequently Asked Questions About CSA Scores
These are the questions safety managers ask when they're interpreting CSA scores and deciding what a percentile change means for their DOT obligations.
Is 7 CSA Points Bad?
Seven points may be a violation severity weight rather than a carrier percentile.
Why Can a CSA Percentile Rise When a Carrier's Measure Improves?
Percentiles reflect performance relative to comparable carriers.
Can a Carrier Have No CSA Percentile and Still Have DOT Obligations?
Yes, insufficient SMS data does not remove applicable DOT obligations.
What Records Should Contractors Review After a Roadside Inspection?
Review the source record and violation-specific evidence before assigning corrective action.
How Long Do Violations Affect a CSA Score?
Up to 24 months. SMS weights events from the most recent 6 months at 3×, events 6 to 12 months old at 2×, and events 12 to 24 months old at 1×, then drops them from the calculation once they age past 24 months.
Can a Carrier Dispute a CSA Violation?
Yes, through a Request for Data Review in FMCSA's DataQs system, but DataQs corrects data errors rather than disputes on the grounds that a valid rule feels unfair.
