Qhubio
    Detection Rating

    FMEA Detection Rating Guide

    6 min read Last updated
    Detection rates the ability of current controls to detect the cause or the failure mode before the product leaves the process. Detection is the most frequently over-rated value in FMEA — and the easiest place for an auditor to challenge a team.

    Detection 1–10 scale at a glance

    The full AIAG-VDA Detection scale calibrated by control type. Use this as the team reference during rating workshops.

    Detection (D) — 1 to 10

    Strength of current controls to detect the cause or failure mode

    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    1–2Almost Certain

    Error-proofed, 100% automated detection, validated

    3–4High

    Automated in-line measurement, capable gauge

    5–6Moderate

    Periodic SPC, sampling inspection, end-of-line test

    7–8Low

    Visual / manual inspection, subjective check

    9–10Very Low / None

    No control, or control cannot detect this cause

    What Detection actually measures

    Detection rates the existing control system, not the control system you wish you had. Detection looks only at what is in place today, in production, reliably, every shift.

    If the control is performed only "when the operator remembers" — it is not a real Detection control.

    AIAG-VDA Detection scale (summary)

    RatingDetection capabilityTypical control
    10No control or cannot detectNo inspection
    9Very remote chance of detectionRandom visual check
    7–8Low — manual inspection of high-volume partsSample visual / dimensional check
    5–6Moderate — variable measurement with SPCSample measurement with gauges
    3–4High — 100% automated inspection with feedbackIn-line gauge, vision system
    2Very high — error proofing detects defectPoka-yoke detection
    1Cannot pass defective partError-proofing prevention (defect impossible)

    Prevention vs Detection controls

    Prevention controls reduce Occurrence. Detection controls reduce Detection. They are not the same and must not be mixed in the same column.

    • Tool-life counter → prevention (reduces Occurrence).
    • In-line vision system → detection (reduces Detection).
    • Poka-yoke that makes the defect impossible → prevention, rating Detection = 1.

    Worked examples

    Process stepControlDetection
    Bore drillingSample bore gauge every 25 parts6
    Bore drillingIn-line air gauge with auto-reject3
    Bore drilling100% vision + automatic reject + alarm2
    Visual finish checkOperator visual at end of line8
    Torque applicationTorque tool with data logging and alarm3

    Common Detection mistakes

    • Rating Detection optimistically to bring AP down — auditors look for exactly this pattern.
    • Counting visual operator checks as low Detection. Manual visual is rarely better than 7.
    • Crediting a control that exists in the Control Plan but is not actually performed.
    • Mixing prevention and detection in the same rating.

    How Detection feeds Action Priority

    With high Severity, Detection can still keep AP High even when Occurrence is low. See the full logic in the Action Priority Guide and the complete ranking tables.

    Detection by control type — definitive reference

    Use this table to anchor team debates. Anything below 5 must be defended with control evidence.
    Control typeRealistic Detection rangeWhy
    No inspection / no control10Defect escapes with certainty if it occurs
    Operator visual at the workstation7–8Human eyes miss 10–30% of defects in repetitive work; fatigue, lighting and pace degrade it further
    Sampling visual or attribute check7Most defects between samples go undetected
    Sample variable gauge (e.g. caliper every n parts)5–6Catches drift, not single defects; depends on sample size and frequency
    Sample SPC with control chart5Detects shifts after the fact; not individual escapes
    100% manual gauging without feedback4Every part checked but operator decisions vary; no closed loop
    100% automated in-line gauge with auto-reject + alarm3Closed loop; small risk from gauge drift or false-pass
    Automated vision system with verified GR&R and auto-reject2–3Excellent for visible features; rate 2 only when capability is proven and alarms are actioned
    Poka-yoke detection (defect is detected and part stopped)2Mechanism physically halts a bad part; very small residual risk
    Poka-yoke prevention (defect cannot be produced)1Belongs in Occurrence reduction; Detection collapses to 1 because the failure mode cannot occur

    Automated vision systems — what Detection they really earn

    Vision systems are the most over-rated control in modern PFMEAs. Teams default to Detection 2 because the system is "automated", then auditors find lighting drift, missing reference images, or alarms that nobody actions. A vision system earns its rating from evidence, not from its existence.

    Evidence in placeDetection earned
    Vision installed, no GR&R, no alarm response procedure5–6
    GR&R passed, auto-reject, alarm acknowledged but no escalation4
    GR&R passed, auto-reject, alarm with mandatory containment3
    All of the above plus reference-image control and daily challenge parts2

    The same logic applies to torque transducers with data logging, laser micrometers, and barcode-verified assembly. Closed-loop alarm response is the dividing line between Detection 4 and Detection 2.

    SPC, gauges and layered process audits

    SPC is primarily a Prevention control. A capable, in-control process reduces Occurrence. SPC only earns Detection credit when the chart is reviewed in time to stop product before escape — typically Detection 5 with frequent sampling and timely reaction rules.

    Gauges earn Detection based on coverage (sample vs 100%) and feedback (open loop vs auto- reject). A go/no-go gauge used 100% with documented reaction earns 4; the same gauge used as a sample check earns 6.

    Layered process audits (LPAs) verify that controls exist and are followed. They do not themselves detect defective product, so they do not appear in the Detection column. They protect the Detection ratings you have already claimed — auditors expect to see LPA evidence supporting any Detection below 5.

    Mistake-proofing vs detection — the rating boundary

    Mistake-proofing (poka-yoke) splits into two AIAG-VDA categories:

    • Prevention poka-yoke — the defect physically cannot be produced (fixture only accepts the correct orientation). Reduce Occurrence; Detection collapses to 1.
    • Detection poka-yoke — the defect can occur but is detected and the part stopped before the next operation (presence sensor + interlock). Detection 2.

    Mis-classifying a detection poka-yoke as prevention is the single most common reason an auditor rejects an FMEA's Detection ratings.

    Why auditors challenge Detection ratings

    Detection is where teams lower AP without changing the process. IATF auditors and customer SQE teams know this and target it specifically. Expect challenges when:

    • Detection 3 or lower is claimed without GR&R and alarm-response evidence.
    • The Control Plan reaction plan is missing, generic, or names a role nobody owns.
    • The control in the FMEA is not the control actually listed on the Control Plan.
    • Layered audit records do not confirm the control is performed every shift.
    • Detection ratings stayed flat after a known escape — the FMEA was not updated.

    Treat any Detection below 5 as a claim that must be defended with evidence. See the FMEA audit checklist for the exact evidence customers ask for.

    False confidence in inspection

    Inspection feels safe, so teams over-credit it. Three patterns to watch for:

    • Inspection theatre. A check exists on paper but adds no real detection capability (visual check of a feature the operator cannot actually see).
    • Detection inflation after an escape. Adding a second inspection rarely justifies more than one rating-point improvement; the root cause is usually upstream.
    • Substituting Detection for Prevention. Teams add a final check instead of fixing Occurrence. AP often stays High; the audit finding lands on the Prevention column.
    Rule of thumb: if reducing Detection is your only action, you have not reduced risk — you have moved it.

    How to calibrate Detection during a workshop

    1. Walk the line before the workshop. Confirm the control exists and is performed every shift.
    2. For every Detection ≤ 4, demand evidence: GR&R, alarm log, reaction plan, audit record.
    3. Default operator visual inspection to 7 unless the team can prove otherwise.
    4. Force a re-rating any time a control is removed or replaced.
    5. Re-rate Detection only after the action is verified in production, not when the work order is closed.

    Key takeaways

    • Occurrence rates how often the cause occurs, not how often the customer sees the failure.
    • Strong prevention controls (poka-yoke, validated SPC, qualified tooling) move Occurrence down.
    • Visual inspection and operator training are not prevention controls — they are detection.
    • Use the same Occurrence anchors across products to keep the FMEA library calibrated.
    • Document the data behind any Occurrence ≤ 3 (history, capability, lessons-learned).

    Detection in the Qhubio knowledge graph

    How Detection connects to other FMEA concepts, standards, examples and software.

    Frequently asked questions

    Learning path

    Three tiers, automatically derived from the Qhubio knowledge graph. The tier containing this guide is highlighted.

    Further reading

    Curated next steps — methodology guides, worked examples, and the relevant tool.

    Generate a structured FMEA in minutes

    Qhubio applies the AIAG-VDA methodology automatically — no Excel formulas, no inconsistent rating scales, no scattered spreadsheets.

    Generate your first FMEA