Quality & InspectionFree templatePDF, Excel, Word exportAutomotive

IATF 16949 DFMEA Template with Nonconformance Report Examples

IATF 16949 expects design and process risk to be analyzed with FMEA and the results to flow into control plans and corrective action. This template gives you a DFMEA structure using Action Priority, example rows to copy the thinking from, and a nonconformance report example with a complete follow-up chain.

Fill in

Live preview
Download:

IATF 16949 DFMEA Template and Nonconformance Examples

Design FMEA

Organization: Acme Automotive Components Item: Brake caliper bracket, PN BR-4411 Customer / program: OEM X, Platform 24 Team: Design, Manufacturing, Quality, Supplier quality Date: 2026-10-21 Revision: B Method: AIAG and VDA FMEA approach with Action Priority (High, Medium, Low) instead of RPN thresholds.

DFMEA worksheet

Function / requirementFailure modeEffect (end user)SCausePrevention controlODetection controlDAPAction
Retain caliper under braking loadBracket fracturesLoss of braking, safety hazard10Insufficient section thickness at filletFEA to design standard, material spec3Fatigue test per validation plan3HAdd fillet radius study and extra test cycles
Locate caliper within toleranceBore out of positionBrake drag, noise6Datum scheme mismatch with machiningTolerance stack and GD&T review4CMM check at first article4MReview datum scheme with manufacturing
Resist corrosion for vehicle lifeCoating breaks downVisible rust, customer complaint4Coating spec too thinCoating spec per corporate standard3Salt spray test3LNone

Nonconformance report example

NCR number: NCR-2026-0187 Item: Brake caliper bracket, PN BR-4411 Description: Bore diameter measured 24.06 mm against requirement of 24.00 plus 0.03 mm on 12 of 200 sampled brackets from lot L2610. Containment: Lot quarantined; 100% sort at gauge station; shipped stock traced by lot and customer notified.

Nonconformance follow-up

StepExample entryOwnerDue
ContainmentQuarantine, sort 100%, notify customer, trace shipped lotsQuality engineer24 hours
Root causeTool wear on boring bar exceeded tool-change frequency; 5 Why and fishboneManufacturing engineer5 days
Corrective actionReduce tool-change interval, add in-process gauge every 50 partsManufacturing engineer10 days
VerificationCapability study Cpk of at least 1.67 on 30 partsQuality engineer15 days
Systemic actionUpdate PFMEA, control plan and tool-life standardQuality manager30 days
Design engineer / Date
Quality engineer / Date
Program manager / Date

Starting point, not a customer-approved form. Use the severity, occurrence and detection rating tables agreed with your customer, and check customer-specific requirements. Update the PFMEA and control plan when the DFMEA changes.

Search past failures before you write the FMEA

Learn how an on-prem AI layer can surface similar failure modes and NCRs from your own records.

Optional. The tool and every export work without this. No spam.

How to fill the DFMEA

Start from the function and its requirement, not from a part list. For each function ask how it could fail, what the effect is on the vehicle or end user, and rate severity. Then identify causes, rate occurrence against your prevention controls, and rate detection against the design verification you actually run. Action Priority combines the three ratings into High, Medium or Low, so a safety-related failure with severity 9 or 10 is always examined even if occurrence is low.

  • Severity is about the effect, not the cause
  • Prevention controls lower occurrence; detection controls lower D
  • High AP requires action or a documented rationale
  • Link to the PFMEA, special characteristics and control plan

Writing a useful nonconformance report

A good NCR identifies the part, lot, quantity checked and quantity failing, states the requirement and the measured value, and records containment before any root cause work. The follow-up chain moves from containment to root cause, corrective action, verification of effectiveness and systemic action. Customers expect an 8D-style structure for escapes, and IATF auditors check that the corrective action reaches the FMEA and control plan.

Common mistakes

Frequent errors include listing the failure cause as the failure mode, rating detection on the final end-of-line test instead of at design stage, using a prior RPN limit while the customer requires Action Priority, and never updating the DFMEA after field returns. Another is an NCR closed on containment alone. Keep a lessons learned loop so that every escape changes a standard, not only a lot.

Frequently Asked Questions

Is FMEA required by IATF 16949?

IATF 16949 requires risk analysis, and its core tools include design and process FMEAs for new product development and for process control planning. Customer-specific requirements often mandate the AIAG and VDA approach and customer review.

What is Action Priority in a DFMEA?

Action Priority replaces the RPN threshold. A table maps combinations of severity, occurrence and detection to High, Medium or Low priority for action, which prevents a high severity item hiding behind a low product of the three numbers.

How is a DFMEA different from a PFMEA?

A DFMEA analyzes failures that come from the design of the product, while a PFMEA analyzes failures that come from the manufacturing process. They are linked: design characteristics identified as special flow into the process analysis and control plan.

What does a good nonconformance example include?

Include the part and lot, requirement versus measured value, quantity affected, containment, root cause method, corrective action with owner and date, effectiveness check and any update to FMEA or control plan. Without those, the record will not satisfy an auditor.

Netray can build a private AI layer over your quality records and ERP so engineers can search past failure modes and NCRs before writing a new FMEA, hosted on your own servers.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Manufacturing hubs

Software