Study guide

11.1 Initiating the Audit & Feasibility

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

11.1 Initiating the Audit & Feasibility

Key Takeaways Explain This Topic AI

Audit initiation under ISO 19011 establishes contact with the auditee, confirms authority and roles (client, auditee, audit team leader), and gathers enough information to decide whether an ISO/IEC 42001 engagement can succeed.

Feasibility rests on three practical pillars: adequate AIMS information available in advance, cooperation and access (people, systems, sites, suppliers), and sufficient time and competent resources for the agreed objectives.

An AIMS-specific information request typically covers AI system inventory and scope, AI policy, risk and impact assessment methods/results, Statement of Applicability (SoA), prior internal/external audit reports, and multi-site or third-party AI arrangements.

Proceeding when feasibility fails wastes resources and risks invalid conclusions; a professional decision can be to postpone, reduce scope formally, or decline until readiness gaps close.

Certification audits (ISO/IEC 17021-1 thinking) add application review, contract/agreement steps, and Stage 1 readiness signals that go beyond a simple calendar booking.

Last updated: August 2026

11.1 Initiating the Audit & Feasibility

Quick Answer: Before you write an audit plan or open a Stage 1 checklist, initiate the engagement: contact the auditee, confirm who is the audit client, and decide feasibility . For an Artificial Intelligence Management System (AIMS) under ISO/IEC 42001:2023 , feasibility fails when critical documented information is missing, access to AI systems or third parties is blocked, or the team lacks time and AI-domain competence. ISO 19011 guides the process; certification bodies also apply ISO/IEC 17021-1 application and Stage 1 logic.

Domain 4 ( Preparing an ISO/IEC 42001 audit ) starts here. Poor initiation causes rushed Stage 2 work, mid-audit scope fights, and findings challenged as out of scope. Treat it as a professional gate.

Why Initiation Matters for AIMS Audits

AI estates are fragmented across product, data science, legal, procurement, and security. Auditing only the “AI governance office” without confirming system boundaries misses material risk. Initiation tests whether the organization can even locate the AIMS and the systems it claims to manage. AUDIT CLIENT / CB AUDIT TEAM LEADER AUDITEE

  • (who wants the audit) (plans & leads) (AIMS owner)
  • | | |
  • | engagement / | contact, |
  • | application | info request, |
  • +------------------------->| feasibility |
  • +------------------------>|
  • |<----- cooperation ------|
  • | PROCEED / POSTPONE / |
  • | DECLINE |
  • Roles to pin down early

Role Typical party in AIMS certification Why it matters

Audit client Organization requesting certification, or CB’s client under contract Defines commercial objectives and who may change scope

Auditee Legal entity operating the AIMS Must provide access and evidence

Audit team leader Lead Auditor assigned by CB or internal program Owns feasibility decision inputs and plan quality

Guides / technical experts AI engineers, data scientists (as guides, not decision-makers) Explain systems; must not dilute independence

Contact With the Auditee

ISO 19011 expects the team leader (or audit program manager) to establish communication with the auditee’s management. For AIMS work, that first contact should achieve more than a polite introduction:

Confirm purpose and type — initial certification (Stage 1 + Stage 2), surveillance, recertification, internal audit, or supplier (second-party) audit.

Confirm authority — named management representative for the AIMS; who can authorize access to production model environments, data platforms, and third-party portals.

Clarify language, channels, and confidentiality — model weights, training data, and customer prompts may be highly sensitive; agree NDA/security handling before document transfer.

Identify multi-site and remote work — cloud regions, outsourced MLOps, offshore annotation vendors, and “shadow AI” business units.

Set a provisional information-request list (see below) with realistic due dates.

If the auditee refuses any discussion of AI system inventory “for IP reasons,” treat that as a feasibility risk . You can often audit process evidence without exfiltrating weights, but total opacity on which systems exist usually means scope cannot be defined. Confirm legal entity names vs. product brands, AI hosting locations, AIMS–ISMS integration, interview windows, and remote-access constraints during the same contact cycle.

Determining Feasibility

Feasibility answers: Can this audit achieve its objectives under agreed constraints? ISO 19011 frames feasibility around availability of information, adequate cooperation, and adequate time and resources. Map those pillars to AIMS reality:

Feasibility pillar AIMS red flags Professional response

Information available No documented AI scope; SoA draft missing; no impact-assessment method Postpone Stage 2; may still run limited Stage 1 to confirm gaps

Cooperation No access to model owners; third-party LLM vendor bans all evidence Renegotiate scope, use alternative evidence paths, or decline

Time & resources 1 auditor-day for a multi-model high-risk estate; team has zero AI competence Increase duration/team competence or reduce scope formally

Information available

You need enough documented information to plan sampling—not perfection. Typical certification signals: defined AIMS scope , AI policy , risk and impact assessment approaches, SoA with justified inclusions/exclusions, process descriptions for claimed lifecycle/data/transparency/use/third-party controls, and internal audit / management review records (critical before Stage 2).

Cooperation

Cooperation covers people, facilities, and systems: interviews with owners who can explain experiment-to-production paths; observation of human-oversight workflows; access to logs, tickets, change records, and monitoring; supplier liaison for outsourced AI. Endless reschedules of the only model-registry expert are a feasibility problem.

Time and resources

AIMS audits often need more specialist time than document-only MS audits of similar headcount. Weigh auditor-days against system count and risk, technical-expert needs, remote-access logistics, and translation.

Scenario: A healthcare provider lists “all AI systems” for certification, but the inventory is empty and no impact assessments exist. Stage 2 feasibility is not met—document concerns, use Stage 1 for readiness if contracted, and postpone Stage 2 until basic planning records exist.

Initial Information Request for AIMS

Send a structured request early. Tailor depth to audit type, but cover these families:

Scope of AI systems — inventory IDs, purpose, autonomy level, lifecycle stage, owners, data categories, high-level architecture, deployment environments.

AIMS documented information — scope statement, AI policy, objectives, risk/opportunity and impact methodologies and recent results, operational procedures, competence matrices.

Statement of Applicability — control status, implementation status, exclusions with justification.

Prior reports — internal AIMS audits, integrated ISMS/AIMS audits, previous CB reports, major incidents related to AI (bias complaints, safety events, regulatory inquiries).

External context — relevant legal/regulatory obligations the organization claims to address through the AIMS (without turning the audit into a legal compliance opinion).

Third parties — critical AI suppliers, APIs, foundation-model providers, annotation vendors, and contractual audit rights.

Treat received files as confidential; do not paste proprietary prompts or personal data into unsecured tools.

Deciding to Proceed—or Not

Document the feasibility conclusion in engagement notes or the Stage 1 report path:

  • Decision When it is appropriate
  • Proceed as planned Information, access, and resources support objectives; residual risks accepted
  • Proceed with conditions Scope narrowed; extra technical expert added; remote access secured; extra days
  • Postpone Critical AIMS elements incomplete (e.g., no internal audit cycle before Stage 2)
  • Decline / withdraw No cooperation, unethical constraints, or conflict of interest that cannot be mitigated

Proceeding when feasibility fails is not “being flexible”—it undermines integrity and due professional care (ISO 19011 principles). For certification bodies, application review and contract review formalize this gate; for internal audits, the audit program manager should still refuse impossible mandates.

Once feasibility is confirmed, refine objectives/scope/criteria, complete Stage 1 document review, and issue the plan, team assignments, and working documents. Initiation decides whether those steps are worth doing now.