ISO 42001 readiness
ISO 42001 checklist: 20 points to check before you certify
This checklist follows the clauses of ISO/IEC 42001:2023, the standard for AI management systems. For each point you see what the standard asks for and what evidence a company usually already has. If most points are covered, you are ready for a self-assessment.
01: Overview
How the ISO 42001 checklist is organised
ISO 42001 follows the same high level structure as ISO 9001 and ISO 27001. Clauses 4 to 10 describe the management system itself. Annex A adds the controls that apply specifically to AI systems. The checklist below goes through the clauses in order, so you can tick off points with the person who owns each topic.
Most companies have more evidence than they expect. A policy in the intranet, a risk list kept by the IT lead, supplier contracts with data clauses: these count. What is usually missing is the link between them, meaning one scope, one owner and one review rhythm.
Settle three questions before you start the clauses.
- AI inventory
- A list of every AI system you build, provide or use, including tools bought from suppliers. Without it, scope and risk assessment have no basis.
- Your role
- The standard asks you to determine whether you act as AI provider, producer or user. Many firms are more than one at the same time.
- Scope
- Decide which AI systems, teams and locations the management system covers. A narrow, honest scope is better than a broad one you cannot maintain.
02: Clauses 4 and 5
Context and leadership: what management must have in place
These points are about direction. Auditors and assessors look here first, because a missing policy or an unnamed owner makes everything else hard to judge.
Internal and external issues are identified
Think of customer expectations, regulation, technology dependencies and your own AI ambitions. Evidence: workshop notes or a short context paper.
Interested parties and their requirements are listed
Customers, employees, regulators and the people affected by AI outputs. Evidence: a stakeholder list with the requirement of each party.
The scope is written down
Evidence: a scope statement that refers to the AI inventory.
An AI policy is approved by management
Evidence: a signed policy, communicated to staff, for example on the intranet.
Roles and responsibilities are assigned
Someone is accountable for AI governance, and someone owns each AI system. Evidence: role descriptions, an organisation chart or a responsibility matrix.
Management provides resources
Evidence: budget decisions, project approvals or meeting minutes that mention the AI management system.
03: Clauses 6 and 7
Planning and support: risks, impact and competence
Clause 6 is the core of ISO 42001. Besides the usual risk assessment, the standard requires an impact assessment for the people your AI systems affect. This is the part most companies have not done before.
An AI risk assessment method is defined
Criteria for likelihood and severity, and a rule for what is acceptable. Evidence: a method document of one or two pages.
Risks are recorded per AI system
Evidence: a risk register with owner, rating and status.
Risks are treated and a Statement of Applicability exists
For each Annex A control you state whether it applies and why. Evidence: the Statement of Applicability and a treatment plan.
Impact assessments are carried out
For each relevant AI system you assess effects on individuals and groups, such as unfair outcomes or loss of privacy. Evidence: completed assessment forms.
AI objectives are measurable
Evidence: a list of objectives with owner, target and date.
People who build or use AI are competent and aware
Evidence: training records, onboarding material, proof of qualifications.
Documented information is controlled
Evidence: a document register or a wiki with version history and approval.
04: Clauses 8 to 10
Operation, evaluation and improvement in practice
Here the standard checks whether the system runs in daily work and not only on paper. Evidence is mostly records that your teams create anyway.
Life cycle controls are applied
From design and training to release and retirement. Evidence: test reports, release approvals, change records.
Data for AI systems is managed
Origin, quality and permitted use of training and input data. Evidence: data descriptions, source records, licence or contract terms.
Third-party AI is assessed
Models, APIs and tools from suppliers are part of your risk picture. Evidence: supplier assessments and contract clauses.
Operation is monitored
Performance, errors and incidents are tracked. Evidence: a monitoring dashboard and an incident log.
An internal audit has been planned and held
Evidence: audit plan, findings, report.
Management reviews the system
Evidence: minutes that cover results, risks and decisions.
Nonconformities lead to corrective action
Evidence: a log of issues with cause, action and closing date.
05: Evidence
Which documents belong to which clause?
The table collects the typical evidence per clause and the person who usually holds it. A company of 20 to 50 people can cover all of it in a few documents and registers. A manual of hundreds of pages is not needed.
| Clause | Typical evidence | Usual owner |
|---|---|---|
| 4 Context | Scope statement, AI inventory, stakeholder list | Management, IT lead |
| 5 Leadership | Signed AI policy, role descriptions | Managing director |
| 6 Planning | Risk register, Statement of Applicability, impact assessments | Risk or quality manager |
| 7 Support | Training records, document register | HR, quality manager |
| 8 Operation | Test and release records, data descriptions, supplier assessments | Product and development lead |
| 9 Performance evaluation | Monitoring reports, internal audit report, review minutes | Quality manager, management |
| 10 Improvement | Nonconformity and corrective action log | Quality manager |
Gaps are normal at this stage. Close them in the order of the clauses, starting with scope and policy.
06: With Zertify
From checklist to ISO 42001 certificate
Once the points above are covered, the online self-assessment is the next step. It has 40 yes/no questions on ISO 42001. Thirteen of them are mandatory requirements of the standard and all must be answered yes. Among the other 27 you need at least 18 yes answers to pass.
There is no on-site audit. The certificate is issued by G6 Agency AG under licence from SICE, and SICE reviews every assessment before issue. After you pass and pay, the certificate arrives within 4 hours as a PDF with a number and a QR code. Your customers can check it on the public verification page.
The price is CHF 849 (€849) in the first year, then CHF 569 (€569) per year including the yearly online re-audit. The certificate is valid for 3 years. You can cancel in your customer account at any time to the end of the paid year.
07: FAQ
Questions about the ISO 42001 checklist
08: Guide
Related pages
Test your ISO 42001 readiness
Answer 40 yes/no questions online and see where you stand against the standard.
Free and without registration.