Study guide
3.1 Annex SL High-Level Structure & Clauses Overview
PECB ISO/IEC 42001 Lead Auditor AI Management
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation & AI Landscape
1.1 Current Exam Facts & PECB Credential Path 1.2 AI Concepts & ISO/IEC 22989 Terminology 1.3 AI Lifecycle & Trustworthiness Characteristics
2 Chapter 2: ISO AI Family & AIMS Purpose
2.1 ISO/IEC AI Standards Family 2.2 AIMS Purpose, PDCA & Management System Thinking 2.3 Global AI Governance Landscape for Auditors
3 Chapter 3: AIMS Requirements — Context & Leadership
3.1 Annex SL High-Level Structure & Clauses Overview 3.2 Clause 4 Context of the Organization 3.3 Clause 5 Leadership & AI Policy
4 Chapter 4: AIMS Requirements — Planning
4.1 Clause 6.1 Risks, Opportunities & AI Risk Assessment 4.2 Clause 6.1.4 AI System Impact Assessment 4.3 Clause 6.2 AI Objectives & Planning to Achieve Them 4.4 Clause 6.3 Planning of Changes
5 Chapter 5: AIMS Requirements — Support & Operation
5.1 Clause 7 Support 5.2 Clause 8 Operation & Operational Planning and Control 5.3 Clause 8 AI System Lifecycle Controls in Operation
6 Chapter 6: AIMS Requirements — Evaluation & Improvement
6.1 Clause 9 Performance Evaluation 6.2 Clause 10 Improvement 6.3 Integrated AIMS–ISMS Thinking for Auditors
7 Chapter 7: Annex A Controls — Governance & Resources
7.1 Annex A Architecture: 38 Controls Across A.2–A.10 7.2 A.2 Policies Related to AI & A.3 Internal Organization 7.3 A.4 Resources for AI Systems 7.4 A.5 Assessing Impacts of AI Systems
8 Chapter 8: Annex A Controls — Lifecycle & Data
8.1 A.6 AI System Life Cycle — Design, Development, Verification 8.2 A.6 Deployment, Operation, Monitoring & Documentation 8.3 A.7 Data for AI Systems 8.4 Bias, Fairness & Data Quality Audit Focus
9 Chapter 9: Annex A Controls — Transparency, Use & Third Parties
9.1 A.8 Information for Interested Parties 9.2 A.9 Use of AI Systems 9.3 A.10 Third-Party and Customer Relationships
10 Chapter 10: Fundamental Audit Concepts (ISO 19011)
10.1 Seven Audit Principles 10.2 Audit Types, Objectives, Criteria & Scope 10.3 Evidence-Based & Risk-Based Audit Approaches 10.4 Auditor Competence, Ethics & Impartiality
11 Chapter 11: Preparing an ISO/IEC 42001 Audit
11.1 Initiating the Audit & Feasibility 11.2 Determining Audit Objectives, Scope & Criteria 11.3 Document Review & Stage 1 Readiness 11.4 Audit Plan, Team & Working Documents
12 Chapter 12: Conducting an ISO/IEC 42001 Audit
12.1 Opening Meeting & On-Site Kickoff 12.2 Collecting Evidence: Interviews, Observation, Documents 12.3 AI-Specific Evidence: Model Cards, Lineage, Logs, Impact Assessments 12.4 Sampling Strategies & Generating Findings
13 Chapter 13: Closing an ISO/IEC 42001 Audit
13.1 Classifying Nonconformities & Observations 13.2 Audit Conclusions & Closing Meeting 13.3 Writing the Audit Report 13.4 Corrective Action Follow-Up & Verification
14 Chapter 14: Managing the AIMS Audit Program
14.1 Establishing & Implementing an Audit Program 14.2 Program Resources, Risks & Opportunities 14.3 Monitoring, Reviewing & Improving the Program 14.4 Certification Cycle: Surveillance, Recertification & Multi-Standard Audits
3.1 Annex SL High-Level Structure & Clauses Overview
Key Takeaways Explain This Topic AI
ISO/IEC 42001:2023 uses the ISO Harmonized Structure (formerly Annex SL), sharing clause titles and core text patterns with ISO 9001, ISO/IEC 27001, and ISO 14001 for Clauses 4–10.
Clauses 4–10 are mandatory normative requirements expressed with “shall”; organizations cannot exclude body clauses the way they may justify Annex A control exclusions.
Annex A provides a reference set of AI-related controls; the Statement of Applicability links risk and context decisions to which controls are implemented or excluded.
Lead auditors use the HLS as a common map for integrated AIMS–ISMS–QMS audits, reducing duplicated interviews while still testing AI-specific requirements.
PDCA maps roughly as Plan (4–7), Do (8), Check (9), and Act (10), but auditors still evaluate each clause against objective evidence, not only the PDCA label.
Last updated: August 2026
3.1 Annex SL High-Level Structure & Clauses Overview
Auditor focus: ISO/IEC 42001 is built on the same high-level structure as ISO 9001, ISO/IEC 27001, and ISO 14001. That structure is your audit roadmap—not optional scaffolding. Clauses 4–10 are mandatory; Annex A is a reference control catalogue linked through applicability decisions.
ISO/IEC 42001:2023 specifies requirements for an Artificial Intelligence Management System (AIMS) . Like other modern ISO management system standards, it follows the ISO Harmonized Structure (historically called Annex SL ). For a Lead Auditor, HLS knowledge is practical: it tells you which clause owns which evidence, how multi-standard integrated audits can share interviews, and why a missing “shall” in the body is never “N/A because we are a small team.”
What Annex SL / HLS Gives Auditors
The Harmonized Structure standardizes:
Clause numbers and titles for Clauses 4–10
Core definitions shared across management system standards (organization, top management, documented information, process, risk, etc.)
Common normative phrasing so leadership, planning, support, operation, evaluation, and improvement work the same way across disciplines
Organizations with an ISMS (ISO/IEC 27001) , QMS (ISO 9001) , or EMS (ISO 14001) can align AIMS governance with shared management review, internal audit, and documented-information controls—when the IMS is real, not three disconnected binders. Nuance: shared structure does not mean shared evidence. An ISMS context analysis that never mentions foundation-model suppliers, model drift, or AI regulation does not satisfy AIMS Clause 4.1.
Clauses 4–10 Overview Table
Clause Title Core question for the auditor Typical evidence
4 Context of the organization Why this AIMS exists here, for whom, and within which boundaries? Context analysis, interested-party register, scope statement, process overview
5 Leadership Does top management own AI governance, policy, and role clarity? AI policy, RACI/role charters, management interviews, resource decisions
6 Planning Are AI risks, opportunities, impact assessments, and objectives planned? Risk methodology, AI risk assessments, impact assessments, AI objectives, change plans
7 Support Are competence, awareness, communication, and documented information sufficient? Training records, competence matrices, AI communication plans, controlled documents/records
8 Operation Are planned AI lifecycle and operational controls actually executed? Operational procedures, lifecycle gates, vendor controls, runbooks, change tickets
9 Performance evaluation Is the AIMS monitored, audited, and reviewed with data? Metrics/KPIs, internal audit reports, management review minutes, monitoring of AI systems
10 Improvement Are nonconformities, incidents, and improvements handled systematically? Corrective actions, improvement logs, post-incident reviews, trend analysis
PDCA mapping (useful, not a substitute for clause tests)
PDCA stage Primary clauses Auditor caution
Plan 4 Context, 5 Leadership, 6 Planning, 7 Support “We planned it” is not enough if operations ignore the plan
Do 8 Operation Watch for shadow AI projects outside operational control
Check 9 Performance evaluation Metrics must include AI-relevant performance and conformity, not only generic IT uptime
- Act 10 Improvement Recurring model failures without systemic action signal weak Act
- Mandatory “Shall” Language
Normative body requirements use “shall.” That language creates audit criteria you can raise nonconformities against. Soft guidance, examples, and Annex notes may use “should,” “can,” or “may”—those are not automatic nonconformity hooks unless the organization made them binding (for example through its own AI policy or customer contracts).
Body vs Annex A (critical for classification):
Layer Nature Can the auditee exclude it? Audit implication
Clauses 4–10 Mandatory AIMS requirements No exclusion of body requirements Missing process = nonconformity against the clause
Annex A controls Reference control set for AI management Yes, with justified exclusion in the Statement of Applicability (SoA) Unjustified exclusion or claimed implementation without evidence = nonconformity against planning/operation/SoA linkage
Annex B / related guidance Implementation guidance (where provided by the standard family) Not a free pass to ignore Annex A where applicable Use for interview probes; do not treat guidance text as silent mandatory requirements
Phrase findings against the requirement that failed (e.g., missing continual-improvement commitment in the AI policy under 5.2), not against “ISO in general.”
Relationship of Body Requirements to Annex A
Clauses 4–10 are the management system engine ; Annex A is the AI control catalogue that engine selects and operates. Context and parties (4) surface issues; leadership/policy (5) set direction; planning (6) assesses risk/impact and drives which Annex A controls apply; support and operation (7–8) implement them across the lifecycle; evaluation and improvement (9–10) check and fix. The Statement of Applicability bridges risk/context decisions to Annex A. Trace: context issue → risk/impact → SoA decision → operational evidence . Broken chains are classic Stage 1/Stage 2 findings.
Using HLS for Integrated Audits
Many certification programs allow combined or integrated audits when an organization claims multiple management systems. HLS makes this efficient:
Shared interviews: top management, internal audit, management review, document control, competence
Shared samples: management review minutes can show ISMS and AIMS agenda items—if AI topics are actually present
Distinct deep dives: AI system inventory, model risk, bias/fairness evidence, human oversight, third-party model APIs, impact assessments
Scenario: Integrated AIMS–ISMS Stage 2
You audit a fintech that holds ISO/IEC 27001 and is seeking ISO/IEC 42001. The CISO presents one management review pack. Security metrics and incident KPIs are excellent, but there is no agenda item on AI objectives, model performance drift, or AI-related nonconformities. The organization claims “AI is covered under information security.” As Lead Auditor you accept the integrated meeting structure, but you still raise a performance-evaluation / leadership gap if AI management outcomes are not reviewed as required for the AIMS. Integration reduces travel time; it does not collapse AI requirements into CIA-only thinking.
Practical Audit Use of the Clause Map
When you build an audit plan (ISO 19011 style), map processes to clauses: product ML teams primarily to 6–8 and lifecycle/data controls; legal/compliance to 4.1–4.2 and 5.2/6.1; HR to competence and awareness; executives to 5.1–5.2 and management review; internal audit to 9.2 with independence from AIMS ownership.
Common trap: Auditing only Annex A checklists while skimming Clauses 4–5. Without context and leadership, control samples lack criteria for “appropriate to the organization,” and findings become technical nits without system-level significance. Remember four field distinctions: HLS shared is not identical AIMS content; body “shall” differs from SoA exclusions; integrated efficiency is not evidence substitution; PDCA labels never replace clause-by-clause objective evidence.