When a state trooper or FMCSA inspector walks around your truck and finds the same problem in two places, your first thought might be: "That's twice the violation. Our SMS score is going to take a bigger hit." That's the natural assumption. But SMS—the Safety Management System that scores your company—doesn't work that way.
Here's the rule: if an inspector cites the same violation code twice during a single inspection, SMS counts it only once. Not twice. That's one citation against your record.
I've watched this confusion cost fleets unnecessary stress and bad decisions. Drivers worry. Dispatchers make calls to yank trucks unnecessarily. Safety managers panic about scores. But if you understand how the counting actually works, you can keep your response proportional to what actually happened.
How SMS Violation Counting Works
SMS is built on what the FMCSA calls the Safety Event Submission system. When an inspection is conducted, violations are documented and submitted. The critical point: the FMCSA's architecture counts each unique violation code only once per inspection, regardless of how many times an inspector noted that same problem.
This matters because inspections are thorough. An inspector might spot the same defective equipment, improper maintenance, or documentation issue in multiple locations on your vehicle. They'll write it up each time they see it—that's good inspection work. But when the violation is submitted to SMS, it becomes one data point, one weight in your BASIC category score.
This is different from five different violations cited in the same inspection. Those five codes count as five separate violations. But if one code appears five times in that inspection, it counts as one.
See the VioCodes calculator if you want to model how violations score in real time—enter an inspection and watch what numbers actually move.
The 30-Point Severity Cap Per Basic
Here's where the single-count rule ties into another important constraint: SMS applies a ceiling of 30 points per BASIC category per inspection. That's the maximum severity weight any single inspection can contribute to a BASIC score, no matter how bad the inspection was.
This cap includes all violations cited during that inspection, whether they're different codes or the same code cited multiple times. So even if an inspector found that same defect in four places and wrote it four ways, the total impact on that BASIC can't exceed 30 points from that one inspection.
That means two things for you:
- Multiple instances of the same violation code don't multiply the penalty—they count as one violation.
- Even that one violation, combined with other violations in the same BASIC during that inspection, won't exceed 30 points of impact.
Why This Design Exists
The rule exists because SMS is designed to measure patterns, not to stack penalties for circumstances. An inspector might legitimately document the same problem in three locations on a truck. That's three instances of the same root issue, not three independent failures. SMS treats it that way.
The single-count rule also prevents a perverse incentive where inspectors might be tempted to list the same defect multiple times to drive up severity artificially. The system doesn't reward that. One violation code equals one count.
Similarly, the 30-point cap per BASIC per inspection keeps a single bad day from permanently wrecking your score. If you get hit with a rough inspection, your SMS hit is bounded. That gives fleets a real path to recovery through better operations.
What This Means for Your Fleet
When you receive inspection results, your first step is to identify the actual unique violations. Don't count the same code twice just because it appeared twice on the report. It counts once.
This is also why understanding violation codes matters. Two different codes that describe similar problems—say, improper maintenance of air brakes versus improper maintenance of air supply—are different violations and will count separately. But the exact same violation code appearing multiple times is just one count.
Check the VioCodes glossary if you need to parse violation codes and what each one really captures.
Avoiding the Real Damage
The single-count rule doesn't mean the violation doesn't matter. It still counts, it still affects your BASIC score, and it still gets weighted by age. A violation from this week carries a weight of 3. One from six months ago carries a weight of 2. And so on.
What the rule does mean is you don't get double-penalized for a single underlying problem found in multiple places. That's fair. Your job is to fix the problem—the root cause—not to obsess over the citation count.
If you're seeing the same violation code repeated across multiple inspections over time, that's different. Those are separate citations on separate occasions, and they all count independently. That pattern suggests a systemic issue you need to address.
Review the SMS scoring guide for the full picture of how violations, timing, and inspection frequency all combine.
The Bottom Line
When you get an inspection with the same violation code listed multiple times, take a breath. You're getting hit once on that code, not once per appearance. The SMS system is designed to measure fleet safety patterns, not to punish the documentation of legitimate observations.
Your focus should be on fixing the underlying issue and tracking whether it shows up again in future inspections. That's where real BASIC score movement happens—patterns over time, not multiple counts of the same problem on one day.
If you want to model how specific violations and inspection scenarios actually affect your SMS scores, use the VioCodes calculator. Input the violations, the BASIC, the timing, and watch your numbers in real time. That's the best way to move from confusion to clarity.