File DataQs challenges on inaccurate violations. Screen every hire with a PSP report. Check your SMS the same week FMCSA updates it, not at the end of the quarter.
Consistently doing these three things can help improve BASIC percentiles over time — especially when fleets reduce new violations and successfully correct inaccurate data through the proper FMCSA review processes.That's what the time-weighting math produces when you stop adding new violations and remove the bad data that doesn't belong.
The fastest lever you've got.
DataQs at dataqs.fmcsa.dot.gov handles formal reviews. Most carriers never file a single challenge — they look at their SMS, assume the data is accurate, and wait for violations to age out. That can mean missing opportunities to correct inaccurate data that may be affecting SMS calculations.
Wrong USDOT assignment is more common than you'd expect, especially with owner-operators and leased equipment. Incorrect violation codes happen when an inspector cites the wrong CFR section or the violation as described doesn't match conditions at the stop. Crash preventability cases — where your driver wasn't at fault — can be submitted through FMCSA's Crash Preventability Determination Program and may receive a “Not Preventable” designation through FMCSA’s Crash Preventability Determination Program, which can affect how the crash appears in SMS calculations and public display.
Review every inspection within 30 days. Get copies of reports from drivers as they come in, not six months later. Gather supporting evidence upfront: photos, ELD data, maintenance records, bills of lading. Include everything in the initial submission. Incomplete documentation can slow the review process and reduce the likelihood of a successful correction. Then file through DataQs and follow up at 60 days if you haven't heard back (response times run 30–120 days depending on the state agency).
| Challenge Type | Typical Outcome Potential | Impact on BASIC |
|---|---|---|
| Wrong carrier (USDOT error) | High | Removes entire inspection from your record |
| Incorrect violation code | Moderate | Removes or reduces severity points |
| Factual error | Moderate | Depends on the correction |
| Crash preventability | Moderate | Removes crash from Crash Indicator BASIC |
“A meaningful share of violations on a typical carrier's SMS record contain some type of challengeable error — wrong carrier, incorrect violation code, factual mistakes. Most carriers never file a single DataQs challenge because they don't know the system exists or don't have the time. That's leaving points on the table.”
Foley Compliance Team, FMCSA-Registered C/TPA
Vehicle Maintenance is where carriers accumulate the most violations. It's also the most controllable BASIC. The difference between fleets with a clean Vehicle Maintenance score and those above threshold usually isn't equipment quality — it's pre-trip inspection discipline.
DVIRs are required under 49 CFR §396.11 and §396.13. The question is whether drivers are catching defects or just checking boxes. Those 90-second walkarounds where every field gets marked clean before the driver's walked halfway around the truck? That's the program that misses brake adjustments and tire wear that get trucks placed OOS.
Use a checklist that mirrors FMCSA Level 1 inspection criteria, not just minimum DVIR fields. Focus on high-severity items: brake adjustment, brake components, tire condition and inflation, coupling devices. When a driver reports a defect, document the repair — date, description, mechanic name, parts used. You'll need this for audit defense.
Spot audits matter. Have a maintenance supervisor verify that drivers are actually completing thorough inspections. This is the first thing that slips during peak season.
Consistently clean inspections can help support stronger SMS performance over time by demonstrating better inspection outcomes without adding new violations. If you're running well-maintained equipment, scales aren't your enemy.
Hiring drivers with recent inspection or crash histories can increase operational risk and may contribute to future SMS issues if the same violation patterns continue after hire.
FMCSA's PSP reports show you exactly what you're getting before you make the hire. Three years of inspection history, five years of crash data, specific violation codes and severity weights. It costs about ten dollars. Skip it and hire someone with three high-severity violations from their last fleet? You'll spend significantly more cleaning up the mess on your SMS.
Many carriers establish internal hiring standards around recent violations, out-of-service history, and serious safety-related offenses based on their risk tolerance and operational needs.
Combine PSP with MVR and Clearinghouse queries. PSP shows federal inspection data. MVR shows the state driving record. Clearinghouse shows drug and alcohol history. Run all three.
FMCSA generally updates SMS data monthly, which is why many carriers review BASIC trends on a recurring basis rather than waiting until quarterly reviews.. Most fleets check quarterly. That's three months behind on problems that compound every week.
Check all 7 BASICs after each monthly update. Compare to the prior month — which BASICs moved and in which direction? A five-point jump in a single month warrants immediate investigation. Review the specific inspections added since the last snapshot. Track which violations are in the 3x, 2x, and 1x weighting windows and calculate when they age down.
Don't wait for FMCSA's thresholds to trigger action. Set internal alert thresholds 10–15 points below FMCSA's:
| BASIC | FMCSA Threshold | Recommended Internal Alert |
|---|---|---|
| Unsafe Driving | 65th percentile | 50th percentile |
| HOS Compliance | 65th percentile | 50th percentile |
| Crash Indicator | 65th percentile | 50th percentile |
| Vehicle Maintenance | 80th percentile | 65th percentile |
| Controlled Substances | 80th percentile | 65th percentile |
| Driver Fitness | 80th percentile | 65th percentile |
| HM Compliance | 80th percentile | 65th percentile |
When a BASIC crosses your internal threshold, act. Many shippers, brokers, and insurers monitor safety performance using standards that may be stricter than FMCSA intervention thresholds, making early action important.
Generic driver safety training is better than nothing. But targeting specific violations driving your worst BASICs is substantially more effective.
Sort violations by BASIC to find where you're bleeding the most points. Within that BASIC, find the highest-severity violation types. Then sort by driver. That's your training priority list — not a fleet-wide quarterly module, but specific drivers with specific coaching on the actual violations causing damage.
| BASIC | Training Focus | Delivery Method |
|---|---|---|
| Unsafe Driving | Speed management, following distance, distraction | Simulator + ride-along coaching |
| HOS Compliance | Trip planning, ELD operation, rest requirements | Classroom + dispatcher coordination |
| Vehicle Maintenance | Pre-trip inspection technique, defect identification | Hands-on yard training |
| Driver Fitness | Medical certificate management, CDL renewal | Administrative process + calendar alerts |
| Controlled Substances | Policy awareness, reasonable suspicion recognition | Annual policy review + supervisor training |
“The carriers we see achieve the best CSA results treat their score like a fleet KPI, reviewed monthly, with specific drivers assigned to specific improvement plans. It's not a compliance exercise. It's an operational discipline.”
Foley Compliance Team, FMCSA-Registered C/TPA
| Timeframe | Action | Expected Impact |
|---|---|---|
| Days 1–14 | Audit all violations from past 24 months; identify DataQs candidates | Immediate, removes inaccurate data |
| Days 1–14 | Pull PSP on all drivers; flag high-risk individuals | Foundational, prevents future violations |
| Days 15–30 | File DataQs challenges on all eligible violations | 30–120 days for resolution |
| Days 15–30 | Implement enhanced pre-trip inspection program | Reduces new Vehicle Maintenance violations |
| Days 30–60 | Launch targeted driver training for top violation types | Reduces Unsafe Driving and HOS violations |
| Days 30–60 | Establish monthly SMS monitoring cadence | Visibility into all 7 BASICs |
| Days 60–90 | Review first month of post-implementation inspection data | Measure violation rate change |
| Day 90 | Compare BASIC percentiles to baseline | Quantify improvement, adjust |
Foley supports carriers with CSA-related compliance workflows, including SMS monitoring support, PSP and Clearinghouse screening workflows, and visibility into violation trends across BASIC categories. See how it works. See how it works.
File DataQs challenges on inaccurate violations. A successful challenge immediately removes the violation's severity points from your BASIC calculation. Combined with clean inspections that dilute the weighted average, DataQs challenges can produce measurable improvement within 30 to 60 days.
Carriers that actively file DataQs challenges, improve pre-trip inspections, and accumulate clean roadside inspections see BASIC percentile reductions of 10 to 20 points within 3 to 6 months. The 3x time weighting on violations from the most recent 6 months means clean inspections have an outsized positive impact.
Yes. Clean inspections increase your inspection count without adding severity points, which dilutes your violation rate and lowers your BASIC percentile. Carriers that consistently pass inspections improve their scores faster than carriers that avoid inspections.
Yes. FMCSA's Pre-Employment Screening Program (PSP) shows a driver's 5-year crash history and 3-year inspection history. Carriers using PSP reports have 8% fewer crashes and 17% fewer out-of-service violations. Hiring drivers with clean PSP records prevents inherited violations from inflating your BASIC scores.
Yes. FMCSA's DataQs system at dataqs.fmcsa.dot.gov allows carriers to challenge inspection violations and crash records containing errors: wrong carrier assignment, incorrect violation code, or factual inaccuracies. Successful challenges remove or correct the violation in your SMS data.