Most audit findings are not caused by incorrect Severity, Occurrence, or Detection ratings. Findings usually result from weak traceability, poor maintenance, outdated assumptions, and disconnects between PFMEA and Control Plan.
| Area | Typical Finding |
|---|---|
| Scope | Process scope unclear |
| Failure Modes | Generic or vague descriptions |
| Controls | Prevention and Detection mixed together |
| Ratings | No rationale for S/O/D values |
| Action Priority | AP ignored or incorrectly applied |
| Control Plan | Characteristics do not match PFMEA |
| Traceability | Missing revision history |
| Maintenance | PFMEA not updated after process changes |
Verify that the organization follows the actual AIAG-VDA methodology, not simply a modified spreadsheet version.
| Element | Audit Question |
|---|---|
| Function | Is it measurable and specific? |
| Failure Mode | Can it actually occur? |
| Failure Effect | Does it describe customer impact? |
| Failure Cause | Is root cause actionable? |
| Prevention Control | Does it reduce occurrence? |
| Detection Control | Does it detect the issue? |
One of the most common AIAG-VDA findings is organizations using Action Priority incorrectly.
This is one of the highest-value audit sections because many organizations fail here.
| PFMEA | Control Plan |
|---|---|
| Process Step | Process Step |
| Special Characteristic | Characteristic |
| Detection Control | Inspection Method |
| Inspection Frequency | Sampling Frequency |
| Reaction Action | Reaction Plan |
Auditors increasingly verify whether the PFMEA is maintained rather than simply created.
| Finding | Risk |
|---|---|
| Generic failure modes | Weak risk analysis |
| Missing functions | Broken failure chain |
| Optimistic detection ratings | False confidence |
| No AP follow-up | Uncontrolled risk |
| No residual rating | No effectiveness verification |
| PFMEA-Control Plan mismatch | Audit finding |
| Outdated PFMEA | Obsolete controls |
| No reviewer evidence | Weak governance |
| Missing ownership | Actions not completed |
| Copy-paste FMEA | Poor process representation |
Audits are won by evidence, not by argument. Bring this exact stack to the opening meeting and most PFMEA findings disappear before they get written.
| Evidence | Purpose |
|---|---|
| Current PFMEA (signed, dated) | Proves revision control |
| Process Flow Diagram | Step-by-step alignment with PFMEA |
| Control Plan | Characteristic, control, frequency, reaction |
| MSA / GR&R studies | Backs Detection ratings |
| Cpk / Ppk reports | Backs Occurrence ratings |
| Warranty / 0-km ppm | Backs Severity and Occurrence with field data |
| 8D and complaint log | Proves feedback loop into PFMEA |
| Action log with residuals | Proves AP follow-up |
| Revision history | Proves PFMEA is maintained, not frozen |
| Calibration set | Proves rating consistency across teams |
| Audit | Focus area | Most common finding |
|---|---|---|
| IATF 16949 (cert body) | AIAG-VDA methodology, action follow-up | AP exists but no residual rating |
| Customer SQA (OEM) | Special characteristics, PFMEA→CP linkage | Characteristic IDs do not match |
| VDA 6.3 process audit | Process risk vs current controls | Detection rating not justified by GR&R |
| Internal layered audit | Live process vs PFMEA controls | Operator runs a control not in the PFMEA |
| PPAP submission review | PFMEA, Control Plan, Process Flow set | Revision dates not aligned across the set |
| Auditor question | Strong answer |
|---|---|
| Why is this Detection a 3? | Automated vision, 100% inspection, GR&R 8%, MSA validated 2024-Q1 |
| Show me the action for this High AP. | Action #14, owner J. Müller, closed 2024-09-12, residual AP Low, Cpk now 1.55 |
| When was this PFMEA last reviewed? | Last revision 2024-10, triggered by 8D-2024-031 |
| Why doesn't this characteristic appear on the Control Plan? | It does — characteristic ID CH-014, page 3, frequency 100% |
| Who approved this PFMEA? | Cross-functional team, signed 2024-10, list attached |
How FMEA Audit Checklist 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.