IATF 16949 FMEA Requirements: What Auditors Actually Check

IATF 16949:2016 is the automotive quality management system standard that governs how suppliers design, manufacture, and control parts for OEMs. FMEA is not optional under IATF 16949 - it is a required output of multiple process stages. This guide explains exactly which clauses mandate FMEA, what format auditors expect, and the nonconformities that trip up experienced teams.

If you are preparing for a specific OEM audit, also see our Ford PPAP FMEA Requirements guide. For FMEA basics, see What Is FMEA.

IATF 16949 and FMEA: The Connection

IATF 16949 builds on ISO 9001:2015 and adds automotive-specific requirements. Where ISO 9001 broadly requires “risk-based thinking,” IATF 16949 explicitly names FMEA as the method. The standard references the AIAG-VDA FMEA Handbook as the recommended methodology (replacing the older AIAG 4th Edition and VDA Volume 4 as separate documents).

FMEA appears in IATF 16949 across the entire product lifecycle:

• Design phase: DFMEA as a design output
• Process planning: PFMEA as input to the control plan
• Production: FMEA updates in response to field issues and process changes
• Continual improvement: FMEA reviews as part of the living QMS

Key Clauses That Require FMEA

Clause	Title	FMEA Requirement
8.3.3.3	Special Characteristics	Special characteristics must be identified in the DFMEA. Product and process special characteristics flow from the DFMEA into the PFMEA and control plan.
8.3.5.1	Design and Development Output - supplemental	Design outputs shall include design FMEA (DFMEA) and reliability results. The DFMEA is a required PPAP deliverable.
8.3.5.2	Manufacturing Process Design Output	Process design outputs shall include process FMEA (PFMEA), process flow diagrams, control plans, and work instructions. These are linked: the PFD defines the operations, the PFMEA analyzes them, and the control plan specifies controls.
8.5.1.1	Control Plan	The control plan shall be based on the DFMEA and PFMEA output. Detection controls in the PFMEA map to control plan entries. Changes to the FMEA require control plan updates.
8.5.6.1.1	Temporary Change of Process Controls	When temporary controls replace permanent ones (e.g., during equipment maintenance), the PFMEA and control plan shall reflect the change and be reviewed.
8.7.1.4	Control of Reworked Product	Rework processes shall be assessed for risk using the PFMEA.
10.2.3	Problem Solving	Root cause analysis for customer complaints and nonconformities shall include FMEA update where applicable.
10.2.4	Error-Proofing	Error-proofing methods shall be determined using the PFMEA. Failure modes with S ≥ 9 shall have error-proofing controls.

DFMEA Requirements Under IATF 16949

The DFMEA must be completed during the product design phase (APQP Phase 2). Key expectations:

• Scope: All product failure modes that could affect safety, regulatory compliance, fit, function, durability, or manufacturing
• Structure: AIAG-VDA 7-step method with 3-level structure (system / subsystem / component)
• Special characteristics: Identified in the DFMEA and flagged per OEM symbol convention
• Interface analysis: Failure modes at component interfaces (mating parts, fluid/thermal connections)
• Lessons learned: Previous warranty data, 8D reports, and similar product FMEAs reviewed and incorporated
• Severity inheritance: DFMEA severity scores carry into the PFMEA for corresponding characteristics

For a complete DFMEA walkthrough, see our automotive DFMEA example.

PFMEA Requirements Under IATF 16949

The PFMEA must be completed during process design (APQP Phase 3), before the pre-launch control plan is finalized. Requirements:

• Every process step analyzed: Each operation on the process flow diagram requires a PFMEA entry
• Severity from DFMEA: Process steps that affect design characteristics inherit the DFMEA severity score
• 4M cause analysis: Man, Machine, Material, Method causes for each failure mode
• Control plan linkage: Every detection control in the PFMEA maps to a control plan entry with method, frequency, and reaction plan
• Special process controls: For failure modes with S ≥ 9 or OEM-designated special characteristics, error-proofing or enhanced detection required
• Lessons learned: Scrap/rework data, warranty returns, and similar process FMEAs incorporated

For a complete PFMEA walkthrough, see our PFMEA manufacturing example.

Reverse PFMEA: Supplemental Requirement

IATF 16949 Clause 8.5.1.1 (Control Plan) and related sanctioned interpretations (SIs) support the use of Reverse PFMEA as a verification tool. Reverse PFMEA is a floor-based exercise where the cross-functional team walks the production process and validates that every PFMEA control actually works on the shop floor.

Reverse PFMEA is increasingly expected by OEMs, particularly for high-severity failure modes and during process revalidation after changes. For a detailed guide, see our reverse FMEA guide.

What Auditors Actually Check: 15-Point Checklist

Certification body auditors (e.g., IATF-recognized CBs like DQS, BSI, SGS, TÜV) evaluate FMEAs against these criteria:

1. DFMEA exists as a design output for each product
2. PFMEA exists with entries for every PFD operation
3. Current revision - FMEA updated after last design or process change
4. Team composition documented (not just one engineer’s work)
5. Scoring consistency - S, O, D scores defensible against AIAG-VDA criteria tables
6. Severity inheritance - DFMEA severity carries into PFMEA for the same characteristic
7. Special characteristics flagged in FMEA and carried through to control plan and work instructions
8. Action Priority used (or RPN with justification) - AP tables preferred per latest handbook
9. High-AP items have actions with owner, target date, and evidence of completion
10. Revised scores documented after actions completed
11. Control plan traceability - every PFMEA detection control maps to a control plan entry
12. Error-proofing for S ≥ 9 failure modes - per Clause 10.2.4
13. Lessons learned from warranty, field returns, and 8D reports incorporated
14. Customer complaints - any recent complaint triggers FMEA review (Clause 10.2.3)
15. Living document evidence - revision history shows updates, not just the initial release

The most common audit approach is thread auditing: the auditor picks a specific product characteristic, then traces it from DFMEA → PFMEA → Control Plan → Work Instructions → Inspection Records. A break in the chain at any point is a finding.

Most Common FMEA Nonconformities

Finding	Clause	Root Cause
PFMEA not updated after process change	8.3.5.2	FMEA treated as PPAP deliverable, not living document. No change management trigger.
No DFMEA for a product line	8.3.5.1	Supplier inherited product from another site, DFMEA not transferred.
Control plan does not match PFMEA	8.5.1.1	PFMEA updated but control plan revision not triggered.
Severity inconsistent between DFMEA and PFMEA	8.3.3.3	PFMEA team scored severity independently without referencing DFMEA.
High-AP items with no action taken	8.3.5.2	Actions assigned but never completed, no follow-up process.
No error-proofing for S ≥ 9	10.2.4	S=9 or 10 failure modes rely on visual inspection only. No poka-yoke.
PFMEA missing operations from PFD	8.3.5.2	PFD added rework loop, PFMEA not updated to include it.
No lessons-learned evidence	10.2.3	8D report closed but FMEA not updated with new failure mode or revised scores.

IATF 16949 vs. OEM-Specific Requirements

IATF 16949 sets the baseline. Individual OEMs add customer-specific requirements (CSRs) on top:

OEM	Additional Requirement Beyond IATF 16949
Ford	FMEA must use Ford-specific severity/occurrence/detection tables. Critical characteristics use Ford “diamond” symbol. Enhanced PFMEA required for safety items.
GM	GM Biased PFMEA for high-risk items. GP-11 Subfolder requirements for FMEA documentation.
Stellantis (FCA)	PFMEA must include rework and repair operations explicitly. SQ.00007 quality system requirements layer on specific FMEA format expectations.
VW Group	Formel-Q requirements. VDA Volume 4 methodology (now aligned with AIAG-VDA). Product audit interfaces with FMEA.
BMW	Supplier quality manual requires FMEA scope to include logistics and packaging failure modes.
Toyota	FMEA expected to integrate with Toyota PDCA approach. Special characteristics per Toyota symbol convention.

For Ford-specific details, see our Ford PPAP FMEA Requirements guide.

FMEA as a Living Document

The most important IATF 16949 principle for FMEA is that it must be a living document. Triggers for FMEA review and update include:

• Design change (engineering change order)
• Process change (equipment, tooling, parameters, suppliers)
• Customer complaint or warranty return
• Internal nonconformity (scrap, rework, stop ship)
• New lessons learned from similar products or processes
• Regulatory or standard change
• Annual review (at minimum, during management review)

An FMEA last updated at PPAP and never touched again is a nonconformity waiting to happen. For how to maintain FMEAs efficiently at scale, see our FMEA software comparison.

How Tacit AI Approaches This

Tacit AI connects your FMEA to the data streams that should trigger updates - work orders, engineering changes, customer complaints - so the “living document” requirement is met by default.

Audit-ready traceability. Every FMEA row links to its source: design requirements, process flow steps, control plan entries, and work orders. Thread auditing becomes a clickable trace, not a paper chase.

Automatic update triggers. When a work order reveals a new failure mode, or an engineering change alters a process step, the FMEA flags the affected rows for review. You decide what changes. The system ensures nothing is missed.

Severity inheritance enforced. DFMEA severities flow into corresponding PFMEA rows. Inconsistencies are flagged before the auditor finds them.

OEM CSR formatting. Export FMEAs in formats that match OEM-specific requirements, including Ford, GM, Stellantis, and VW Group conventions.

Preparing for an IATF 16949 surveillance audit? Book a working session and see how your current FMEAs measure against the 15-point checklist above.