Determining the scope of the QMS
Plain-language summary
Draw the boundary honestly: which products, sites and processes your QMS covers — and justify anything you claim does not apply to you.
What the clause is really asking
Scope is a truth-telling exercise. It must reflect your context, your interested parties and your actual products — not a convenient subset that hides the messy corners. Any requirement you treat as not applicable must be justified, and the justification must not compromise product conformity or customer satisfaction.
What auditors look for
Auditors compare three things: the written scope, the certificate, and what they see on site. Warehouses, labs, support offices doing QMS-relevant work must fall inside. Non-applicability claims get probed hard — 'we don't design' while engineering changes process settings is a classic trap.
Typical evidence
Documented scope statement; certificate wording; site/process list; justification for non-applicable requirements.
How to comply — recommendations
One honest paragraph: what we make, where, for whom, and what is excluded with the reason why. Revisit whenever a product line, site or service is added. Make sure the certificate and the statement never drift apart.
Common nonconformities
Support functions operating outside the claimed scope; exclusions claimed for requirements that clearly apply; scope statement contradicting the certification body's certificate.
Related clauses
IATF 16949: tightened by 4.3.1 & 4.3.2; ISO 14001 4.3; ISO 45001 4.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.