Locate the applicable automotive requirements

Locate the applicable automotive requirements

Begin by identifying the organization, product, customer and certification scope. IATF16949:2016 replaced the historical ISO/TS16949:2009 reference; certification Rules sixth edition are a separate document effective January2025. A July2026 IATF communiqué plans the second standard edition for mid2027 and explicitly treats timing as indicative. Do not treat that future edition as already published. Check current interpretations and customer-specific requirements alongside the applicable standard. Map responsibilities and evidence without claiming that a lesson, internal checklist or completed template establishes conformity. Certification status and scope depend on the authorized process; they cannot be inferred from familiarity with the terminology.

Follow the method

1. Scope + customer
2. Current standard
3. Scheme Rules + interpretations
4. Required evidence
5. Authorized certification

Keep the standard, scheme Rules and revision plan separate

Fictional case: an automotive supplier receives a purchasing note saying “ISO/TS 16949 certified” and an internal slide titled “IATF sixth edition”. Quality lead Ren must correct the references and identify the actual requirements applicable to a defined site/customer scope. Primary IATF pages were checked on 20 September 2026 for this lesson.

Follow the method

1. ISO/TS 16949:2009?
2. IATF sixth edition?
3. Second edition available?
4. Certified site?

Rules 6 is not a sixth edition of the standard

Identify the current automotive requirement authorities and distinguish the standard edition, certification Rules, interpretations, customer requirements and historical references.

Fictional case: an automotive supplier receives a purchasing note saying “ISO/TS 16949 certified” and an internal slide titled “IATF sixth edition”. Quality lead Ren must correct the references and identify the actual requirements applicable to a defined site/customer scope. Primary IATF pages were checked on 20 September 2026 for this lesson.

Role: Automotive quality-system lead and customer interface

Normal condition

The requirement register identifies source, edition/revision, applicability, owner and review date. Certification status is confirmed through authorized evidence, not inferred from training.

The gap

Historical ISO/TS wording and scheme Rules numbering are being treated as interchangeable current standard names.

• IATF 16949:2016 first edition replaced ISO/TS 16949:2009.
• Rules 6 became effective 1 January 2025; July 2026 planning places the second standard edition at mid-2027 with explicitly indicative timing.

1. Define the organization and customer scope

   Ren identifies the site, activities, customer relationship and decision being made. He distinguishes a requirement lookup from a claim that the organization is certified.

   Why: Applicability depends on scope and the relevant contractual/certification framework. A generic training title cannot establish those facts.

   Evidence: The register names the scope and the person responsible for confirmation.

2. Correct historical terminology

   He marks ISO/TS 16949:2009 as historical and points to IATF 16949:2016 as the published first-edition standard at the check date. He retains the old reference as a traceable source of the question.

   Why: Historical wording may appear in old records or informal requests. Correcting the reference should not silently alter the meaning of a retained historical document.

   Evidence: The current register distinguishes historical and current authorities.

3. Separate Rules from the standard

   Ren records Rules 6 as the certification-scheme Rules effective 1 January 2025, not a sixth edition of IATF 16949. He identifies applicable scheme responsibilities through the official authority.

   Why: Edition numbers belong to different documents. Combining them produces a nonexistent standard label and can send the team to the wrong requirements.

   Evidence: The register has separate rows for standard and scheme Rules.

4. Check supplements and customer conditions

   He reviews current official interpretations/FAQs and applicable customer-specific requirements, recording revision and relevance rather than copying protected clauses into the training pack.

   Why: The base standard title alone may not capture applicable current obligations. The organization needs access to the authorized documents and a controlled applicability process.

   Evidence: Each additional requirement has a source, applicability decision and accountable owner.

5. Treat revision plans as plans

   Ren records the July 2026 communiqué’s mid-2027 publication plan as indicative and schedules source monitoring. He does not claim the second edition is published or invent a transition deadline.

   Why: A planned date is not an effective requirement. Current work follows applicable published authorities while preparing for verified future changes.

   Evidence: The register separates published status, planned change and next review date.

A customer request uses an ambiguous document name

The customer asks for “latest automotive certification rules” without specifying the intended deliverable.

Clarify the required authority and scope through the customer interface, provide the verified current references and avoid promising certification evidence that has not been checked.

Ambiguity should be resolved before turning a phrase into a compliance claim or internal requirement.

The clarification record identifies the customer’s actual requirement and retained decision.

Run a practice session

Materials

• Authority-name cards
• Official-source links
• Blank applicability register

1. Sort the document types · 5 minutes

   Which edition number belongs to which document?

2. Review the current register · 8 minutes

   What is published and what is planned?

3. Repair the launch slide · 10 minutes

   Which claim requires evidence beyond a source lookup?

4. Debrief updates · 5 minutes

   Who monitors a change and what triggers review?

Debrief

• Do not turn the register exercise into clause reproduction.
• Require explicit dates for time-sensitive status statements.

Create separate rows for standard, Rules, supplements and customer requirements before writing a status summary.

Transfer into the work

Owner: Automotive QMS owner and customer interface

Record: Controlled authority/applicability register and scoped status evidence

Review: At official updates, customer changes and planned periodic review

Evidence: Current authoritative references with documented applicability

Clarify ambiguous requirements and assess published changes before updating operational commitments.