AI System Characterization Checker
ISO/IEC DIS 42102 Edition 1 Stage 40.60, close of voting 41 pages Planning date 16 Sep 2027, an estimate 26 clause pages, 7 defined terms

Home / The draft record / What changes

What this draft changes, and what you can do now

The draft adds a shared description language to an estate that already has an AI inventory, a risk process and an impact assessment. It does not replace any of them. The change is that a system description becomes comparable across teams, and that comparison exposes claims which were never evidenced.

The gap the draft fills

Most AI inventories record a model, a vendor and a use case. They rarely record how the system works or what it can do in terms another team can test. A model name is not a method, and a use case is not a capability. The draft separates the four: task, component, method and capability, and asks the organisation to relate them.

What changes in practice

  1. The inventory gains two axes. A system record needs a method position and a capability claim, not only a model and an owner.
  2. A capability claim becomes testable. The claim needs a population, a condition, a measure and an evidence item.
  3. Empty cells acquire meaning. Not applicable, not yet evidenced and outside scope are three different states and must be labelled.
  4. The description follows the system. A retrain, a model swap or a new tool changes the matrix, and the previous version is kept.
  5. The crosswalk becomes useful. A claimed cell lands in the 42001 verification plan, the 23894 risk file or the 42005 impact assessment, rather than in a separate document nobody reads.

What does not change

The draft creates no new legal duty, no certification and no transition period. It is voluntary. A firm that already runs ISO/IEC 42001 does not need a second management system; it needs the descriptor set to fit the one it has. A firm outside any management system can still use the public definitions and the matrix without buying anything from us.

Five moves to make before publication

  1. Put the system description under one owner. One person, a review date and a version for the matrix.
  2. Name the method families in the inventory. Add traditional, symbolic, machine learning and hybrid, including "none of these" for systems that are not AI.
  3. Rewrite three capability claims as tests. Population, condition, measure, evidence. Start with the claims a customer or a regulator would rely on.
  4. Add the empty-cell key. Not applicable, not yet evidenced, outside scope. It prevents the most common misreading.
  5. Map one cell to the 42001 evidence you already keep. One worked row is enough to prove the crosswalk is usable before you scale it.

What not to do

Do not wait for the published text to start the inventory work. Do not buy a template that claims to contain the draft. Do not turn the matrix into a maturity score. Do not treat the planning date as an ISO deadline.

Common questions

Does this replace ISO/IEC 42001?
No. 42001 is a management system standard with requirements. This draft is a descriptive framework. It is useful inside a 42001 system, and it does not amend or replace it.
Can we prepare without the full text?
Yes, at the level of the inventory, the defined terms and the matrix geometry. The exact descriptor wording can only be added when the draft or the published standard is available.
Is the framework mandatory?
No. It is a voluntary standard. It becomes binding only when a contract, a procurement schedule, a regulator or a management system adopts it.
Does it have Annex A controls?
No. The draft is not a requirements standard and the public preview does not publish annex titles. The introduction says informative annexes explain and illustrate the framework.

Source. ISO Online Browsing Platform, public preview, read on 22 October 2026. The scope, introduction and clause 3 entries are read here.

Claim level: public preview and public project record. No draft text is reproduced.

Last updated: