Study guide

7.4 A.5 Assessing Impacts of AI Systems

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

7.4 A.5 Assessing Impacts of AI Systems

Key Takeaways Explain This Topic AI

A.5 provides four controls: impact assessment process (A.5.2), documentation of assessments (A.5.3), impacts on individuals or groups (A.5.4), and societal impacts (A.5.5).

Clause 6.1.4 requires AI system impact assessment as a management-system planning requirement; A.5 supplies reference controls that operationalize assessing and documenting impacts on people and society.

Impact assessment focuses on effects on individuals, groups, and society (and related external consequences), which is complementary to—not identical with—enterprise AI risk assessment under Clause 6.1.2.

Auditors evaluate process completeness, documentation quality, coverage of individual/group and societal dimensions, and lifecycle timing (before deployment and after material change).

Typical NCs: no process; template never completed for high-impact systems; assessments only internal brand risk; one-time go-live assessment never updated after major model or use-context change.

Last updated: August 2026

7.4 A.5 Assessing Impacts of AI Systems

Auditor focus: A.5 is where ISO/IEC 42001 most clearly differs from a pure information-security standard. You are checking whether the organization systematically assesses who can be harmed or affected —individuals, groups, and society—and whether that work is documented and refreshed across the AI life cycle.

Control objective (intent): Identify and assess potential consequences of AI systems for individuals, groups, and society so that impacts can be addressed through the AIMS.

A.5 Control Map

  • Control Name Auditor essence
  • A.5.2 AI system impact assessment process Defined, repeatable process for performing assessments
  • A.5.3 Documentation of AI system impact assessments Results retained as documented information
  • A.5.4 Assessing impact on individuals or groups of individuals Explicit analysis of effects on people/groups
  • A.5.5 Assessing societal impacts of AI systems Explicit analysis of broader societal effects
  • Linkage to Clause 6.1.4

Clause 6.1.4 requires the organization to assess the potential consequences of AI systems for individuals and societies (AI system impact assessment) as part of planning. Annex A.5 provides the detailed control set for process, documentation, and the individual/group vs societal dimensions.

  • Element Clause 6.1.4 (planning requirement) Annex A.5 (controls)
  • Mandate to assess impacts Management system shall perform AISIA as specified A.5.2–A.5.5 structure how

Scope of effects Individuals and societies (and related consequences per the clause text) A.5.4 people/groups; A.5.5 society

Records Documented information as required by the clause A.5.3 documentation control

Audit citation Use when planning process missing at AIMS level Use when control design/implementation of impact assessment fails

In practice, Stage 1/2 findings often cite 6.1.4 and A.5 together when no credible impact assessments exist for in-scope high-impact systems.

Impact assessment vs risk assessment

AI risk assessment (6.1.2 family) AI system impact assessment (6.1.4 / A.5)

Primary focus Risks to organizational objectives (operations, finance, compliance, reputation, security of the org) Effects on external parties —individuals, groups, society

  • Example Model outage causes revenue loss Model bias denies credit to a protected group
  • Example IP leakage of model weights Mass profiling chills free expression
  • Relationship Inputs treatment and SoA Inputs treatment, controls, human oversight, transparency

Trap: A risk register that only lists “regulatory fine” and “brand damage” without analyzing harms to affected persons is not a complete impact assessment—even if enterprise risk scores are sophisticated.

A.5.2 — Impact Assessment Process

Expect a defined process covering at least:

Triggers — new system, new intended use, major model/data/context change, periodic review, incident-driven reassessment

  • Roles — who drafts, who reviews, who accepts residual impact
  • Method — steps to identify stakeholders, impacts, severity/likelihood or qualitative scales, mitigations

Inputs — system description, intended use, reasonably foreseeable misuse, data categories, automation level, human oversight design

  • Outputs — decisions feeding risk treatment, design controls, deployment gates, monitoring
  • Integration — link to SoA, life-cycle gates (A.6), transparency (A.8), use controls (A.9)

Interview probes:

When is an assessment mandatory before production?

Who can waive an assessment, and is waiver allowed for high-impact systems?

How is “significant change” defined for re-assessment?

Weak process signs: one-page “ethics checklist” with yes/no boxes and no stakeholder analysis; process owned solely by marketing; no deployment gate dependency.

A.5.3 — Documentation

Documented impact assessments should be retrievable, complete enough to reconstruct reasoning, and controlled .

Typical content auditors look for (scaled to risk):

  • Content element Why it matters
  • System identity & version / date Traceability to deployed model
  • Intended purpose & users Bounds analysis
  • Affected individuals/groups A.5.4 completeness
  • Societal considerations A.5.5 completeness
  • Positive and adverse impacts Balanced analysis
  • Foreseeable misuse Abuse cases
  • Measures to address impacts Link to treatment
  • Residual concerns & acceptance Accountability
  • Approvals Authority

NC example: Process document exists (A.5.2 appears designed) but zero completed assessments for three production high-impact systems → A.5.3 / 6.1.4 implementation failure .

A.5.4 — Individuals or Groups of Individuals

Assess impacts on people , including groups who may be differentially affected:

  • Impact theme Examples
  • Rights & dignity Privacy intrusion, unjust automated decisions, lack of contestability
  • Discrimination / fairness Disparate error rates across demographic groups
  • Safety & wellbeing Incorrect medical triage, unsafe recommendations
  • Economic Unfair denial of jobs, credit, insurance
  • Vulnerable groups Children, elderly, disabled users, marginalized communities

Sampling: For a hiring model, expect analysis of candidates as affected individuals, subgroup performance considerations, and human review pathways—not only “improves HR efficiency.”

A.5.5 — Societal Impacts

Societal lens looks beyond single-transaction harm:

  • Theme Examples
  • Labor & economy Large-scale workforce displacement patterns
  • Public discourse Amplification of misinformation via generative systems
  • Environment Material energy/water impacts of large-scale training where relevant to context
  • Public services & trust Erosion of trust in institutions from opaque public-sector AI
  • Collective rights Community-level surveillance effects

Not every system has dramatic societal effects—but the assessment should consider the dimension and document why effects are limited when that is the conclusion. Blank silence on society for a city-wide camera analytics platform is a red flag.

Lifecycle Timing and Completeness Evaluation

Lead auditors test when assessments occur relative to decisions that can harm people:

  • Lifecycle point Expectation
  • Concept / design Early impact framing informs requirements
  • Pre-deployment Completed assessment before high-impact go-live
  • Material change Re-assessment after major model, data, or use-context change
  • Periodic Planned refresh for long-lived high-impact systems
  • Post-incident Update after harms or near-misses

Completeness scorecard:

Process defined and known (A.5.2)?

Records exist for sampled systems (A.5.3)?

Individual/group analysis substantive (A.5.4)?

Societal analysis considered (A.5.5)?

Timing correct relative to deployment/change?

Outputs visible in treatment, monitoring, and oversight design?

Alignment with Clause 6.1.2 risks without collapsing into pure enterprise risk?

Scenario — InsurTech claims automation

System auto-denies low-value claims with optional human appeal. Impact assessment from two years ago covers “customer satisfaction” only. Model and fraud features changed three times; denial rates rose for a regional language minority. No re-assessment. Findings: A.5.2 trigger failure; A.5.3 stale/incomplete docs; A.5.4 inadequate group analysis; possible 6.1.4 and monitoring (9.1) gaps.

Scenario — Internal code assistant

Low external individual impact if scoped to internal developers with IP controls. Assessment may be lighter but should still exist if the AIMS/SoA applies A.5; document limited external impact with rationale . Do not accept “internal = never assess” if the tool can leak personal data or generate unsafe operational scripts affecting third parties.

Evidence Pack and NC Patterns

  • Evidence / NC pattern Notes
  • Procedure + completed AISIA reports A.5.2 design; A.5.3–A.5.5 substance
  • Deployment gates & change-linked re-assessment Lifecycle timing
  • Treatment/SoA/management-review linkage Process effectiveness
  • No process / no records 6.1.4 + A.5.2 / A.5.3
  • Only enterprise risk language A.5.4/A.5.5 substance missing
  • One-time ethics essay; blanket product waivers Timing and integrity failures

Bottom line: A.5 forces the organization to look outward at human and societal consequences, document that look, and repeat it when systems change. With A.2–A.5, governance policy, organization, resources, and impact foundations are in place for the life-cycle and data controls that follow.