Skip to content
Qualityforeveryone
Lesson 2 of 5≈ 3 min read
View All Lessons →

Scoring Severity, Occurrence, and Detection on a 1-10 Scale

Audio Narration (Voxtral)Voxtral♀ Female Voice

Scoring Severity, Occurrence, and Detection on a 1-10 Scale

Each FMEA row gets three scores from 1 to 10. Severity (S) rates how bad the effect is if it reaches the user. A 1 means the effect is barely noticeable; a 10 means it could harm the patient or user with no warning. Severity is about consequence only. It does not care how often the failure happens or whether you can catch it.

Occurrence (O) rates how often the cause is expected to produce the failure mode with the current process. A 1 means it practically never happens; a 10 means it happens very frequently or almost every time. Base this on real data where you have it: scrap records, complaint logs, test results. Where you have no data, score conservatively and note the assumption.

Detection (D) rates how likely your current controls are to catch the failure mode or its cause before the product leaves the step or the plant. Here the scale runs the opposite way to what people expect: a 1 means your controls almost certainly catch it; a 10 means there is no control or it cannot be detected. A high detection score is bad news.

Key Concept
Severity, occurrence, and detection each run 1 to 10, and a higher number always means higher risk, including for detection, where 10 means you will not catch it.
Practical Example
For the unseated luer connector from Lesson 1, the team scores severity 8 because a leak during infusion can interrupt therapy and is a serious effect, though with some warning signs. They score occurrence 4 because in-process checks over the last six months found short insertions on about 1 in 500 assemblies. They score detection 6 because the only current control is a visual check against a pencil mark, which catches obvious shorts but misses depths between 7 mm and 9 mm. The row reads S 8, O 4, D 6.

Standard Procedure

  1. 1Agree on written one-line descriptions for each score level in your own words before scoring anything.
  2. 2Score severity first, based on the worst credible effect on the end user.
  3. 3Score occurrence from actual failure data for the cause; if none exists, estimate and flag it.
  4. 4Score detection by asking how reliably the current control catches the problem, remembering that 10 means it will not.

Lesson Summary

  • ✓Severity describes consequence, occurrence describes frequency, detection describes catch probability.
  • ✓Detection is scored so that a strong control gets a low number.

Progress Tracking

Sign in to save your lesson completion markers.