The full AIAG-VDA Severity scale, from minor cosmetic defects through hazardous failures. Use this as the team reference during rating workshops.
Severity of effect on the customer or downstream process
Minor annoyance, cosmetic, no functional impact
Degraded performance, customer complaint, rework
Loss of primary function, regulatory or warranty exposure
Safety or compliance failure, with or without warning
Severity is the rating that measures how serious the consequence of a failure would be if the failure reached the customer, user, next manufacturing operation or regulatory authority.
Severity does not measure how often something happens. It does not measure how likely a control is to detect a defect. It only measures the impact of the failure effect.
Within the AIAG-VDA methodology, Severity is one of the three ratings used during Risk Analysis together with Occurrence and Detection. Because Severity reflects the consequence of failure, it often remains unchanged unless the design, process or resulting effect itself changes.
Many organizations spend most of their workshop time debating Occurrence and Detection ratings while treating Severity as a quick estimate. This is a mistake.
Severity drives customer impact, safety concerns, warranty exposure, regulatory compliance and Action Priority decisions. An incorrect Severity rating can distort the entire FMEA.
High-Severity failure modes deserve deeper engineering discussion because they represent the greatest potential business and customer risk.
| Severity | General Meaning | Typical Impact |
|---|---|---|
| 10 | Hazardous | Safety or regulatory issue |
| 9 | Very High | Loss of primary function |
| 8 | High | Major customer dissatisfaction |
| 7 | Significant | Reduced product performance |
| 6 | Moderate | Partial degradation |
| 5 | Low-Moderate | Noticeable inconvenience |
| 4 | Low | Minor customer annoyance |
| 3 | Very Low | Small effect |
| 2 | Minimal | Barely noticeable |
| 1 | None | No customer impact |
AIAG-VDA evaluates Severity based on the effect of the failure mode rather than the cause of the failure.
This distinction is critical. Teams frequently lower Severity because they believe a failure is unlikely. That logic belongs in Occurrence, not Severity.
Maintaining this separation improves consistency across projects and ensures that Action Priority decisions remain objective.
When assigning Severity ratings, ask the following questions in order:
Using a structured framework reduces subjectivity and prevents rating inflation during workshops.
| Failure Mode | Effect | Severity |
|---|---|---|
| Brake failure | Loss of vehicle braking | 10 |
| Battery thermal event | Safety risk | 10 |
| Water ingress | Product malfunction | 8 |
| Loose fastener | Noise and vibration | 6 |
| Cosmetic scratch | Appearance issue | 3 |
| Packaging defect | Minor inconvenience | 2 |
One of the most difficult tasks during FMEA workshops is distinguishing between the highest Severity levels.
Teams should document their reasoning when assigning Severity 8, 9 or 10 because these ratings often receive increased scrutiny during audits and customer reviews.
| Industry | Failure Example | Severity |
|---|---|---|
| Automotive | Brake system failure | 10 |
| Automotive | Interior trim scratch | 3 |
| Medical Device | Incorrect dosage delivery | 10 |
| Electronics | Power supply failure | 9 |
| Machining | Critical bore out of tolerance | 8 |
| Injection Molding | Minor flash on hidden feature | 2 |
| Consumer Products | Packaging tear | 2 |
This is one of the most misunderstood concepts in FMEA.
Detection controls may reduce risk exposure but they do not change the consequence experienced by the customer if the failure escapes.
Severity can only be reduced by changing the design, process or resulting effect itself.
| Action | Changes Severity? | Changes Detection? |
|---|---|---|
| Add camera inspection | No | Yes |
| Increase sampling frequency | No | Yes |
| Add poka-yoke detection | No | Yes |
| Redesign component | Yes | Possibly |
| Add fail-safe feature | Yes | Possibly |
Severity is only one component of overall risk assessment. AIAG-VDA combines Severity, Occurrence and Detection to determine Action Priority.
Severity has a disproportionate influence on Action Priority decisions.
High Severity values frequently produce High Action Priority outcomes even when Occurrence remains relatively low.
Learn more in the Action Priority Guide.
The goal is not perfect precision. The goal is consistent risk evaluation across all FMEAs.
During IATF 16949 and customer audits, reviewers frequently examine high-Severity rows first.
Weak justification for Severity ratings is a common source of audit findings.
How Severity connects to other FMEA concepts, standards, examples and software.
Three tiers, automatically derived from the Qhubio knowledge graph. The tier containing this guide is highlighted.
Curated next steps — methodology guides, worked examples, and the relevant tool.
Move from theory to a working FMEA. Same methodology, three entry points depending on how you want to start.
Qhubio applies the AIAG-VDA methodology automatically — no Excel formulas, no inconsistent rating scales, no scattered spreadsheets.
Generate your first FMEAHelp us improve Qhubio. Analytics help us understand which FMEA features are useful, which pages need improvement, and where users encounter problems. No advertising. No selling personal data. See our Cookie Policy.