Engineering specifications (IATF only)
Plain-language summary
When a customer engineering standard or spec changes, you must have a documented process to review, distribute and implement it fast — within the timeframe the customer sets, or two weeks if they set none — including updating your own documents and records of the change.
What the clause is really asking
Customer engineering changes cannot sit in inboxes: documented review and implementation process, timing per customer schedule (default: as soon as possible, not later than 10 working days per common interpretation — confirm against the actual customer requirement), records of implementation date, and updates flowing into PPAP/control plans/instructions where affected.
What auditors look for
Auditors trace a recent customer spec revision: when received, when reviewed, when implemented, which documents changed, was PPAP impact assessed? Gaps between receipt date and floor implementation are measured in findings.
Typical evidence
Spec change log (received/reviewed/implemented dates); document update evidence; PPAP impact assessments; communication to affected stations.
How to comply — recommendations
Run a one-line-per-change log with four dates: received, reviewed, implemented, verified. Make someone own the customer portals (link to 5.3.1) so changes enter the log the day they land.
Common nonconformities
Spec revisions found unopened in portals; implementation months after receipt with no record; affected control plans never updated; no PPAP impact considered.
Related clauses
Builds on ISO 9001 7.5.3 / links to IATF 4.3.2, 5.3.1
Qlause provides interpretive guidance only and is not a substitute for the standard. Refer to your licensed copy of ISO 9001 / IATF 16949 for the authoritative text.