Determining, reviewing & changing requirements
Plain-language summary
Before you promise, know what you are promising: capture all requirements (stated, unstated-but-necessary, statutory), review that you can actually meet them, and manage changes so everyone works to the same requirement.
What the clause is really asking
Classic contract review: requirements defined including legal ones and those the customer did not state but the application needs; review before commitment (orders, tenders, changes) confirming you can deliver and resolving differences; records kept; and when requirements change, documents amended and people informed.
What auditors look for
Auditors sample orders and quotes: where is the review evidence? Differences between quote and order resolved? Statutory requirements identified? Then a change: who updated the documents and told the floor? Verbal orders get special attention — confirmation required before acceptance.
Typical evidence
Contract/order review records (even a signed checklist or ERP status); requirement registers; change amendments and communication evidence.
How to comply — recommendations
Build review into the order entry step: a short checklist (spec available? capacity? special requirements? legal?) signed before acceptance. For changes, one rule: no production to an unconfirmed change.
Common nonconformities
Orders accepted with no review trail; quote-vs-order differences discovered in production; changes actioned on the line before documents caught up.
Related clauses
IATF 16949: extended by 8.2.2.1, 8.2.3.1.1-8.2.3.1.3
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.