Design & development changes
Plain-language summary
Once designed, change carefully: identify and review every change, control it to prevent harm to conformity, and record changes, reviews, authorisations and actions.
What the clause is really asking
Changes during or after design get identified, reviewed and controlled so they do not adversely affect conformity. Records retained of the changes, the review results, who authorised, and actions taken.
What auditors look for
Auditors sample design changes: review evidence before implementation, authorisation, impact on related documents (FMEA, control plan, instructions) and on already-produced/fielded product.
Typical evidence
Engineering change records; impact assessments; authorisation evidence; document update trails.
How to comply — recommendations
One ECN form: what changes, why, impact (documents/tooling/stock/customer), approvals. No change without the form — including 'small' ones; small changes cause big recalls.
Common nonconformities
Changes implemented before review; affected documents updated late or never; impact on existing stock not considered.
Related clauses
IATF 16949: extended by 8.3.6.1; links 8.5.6
In the book
Chapter 8 — Operation — Where the Product Is Won or Lost treats this clause family in full: what it is really asking, what auditors look for, the evidence that satisfies, how to make it work on a real floor, and where companies stumble.
Get the free ISO 9001:2026 Readiness Scorecard
Free, instant download. We'll only email you the occasional practical quality update — no spam, unsubscribe anytime.
Qlause provides interpretive guidance only and is not a substitute for the standard. Refer to your licensed copy of the relevant standard for the authoritative text.