Scope · 1
Scope
The document sets out the vocabulary of AI and explains the ideas behind it. It is meant to serve the people who write other standards and anyone who needs a shared language for AI, and it applies to every kind of organisation.
What this clause settles
The clause matters because it decides how the rest of the vocabulary is read. The page keeps the claim level visible: a concept clause is not a requirement clause, and a definition is not a control. For Scope, the page keeps the claim level "scope statement" visible and says where the public text stops.
Who it binds
The organisation that adopts the vocabulary. The clause is not a shall requirement; the claim level states what it is.
What to do in your practice
Put the clause title and the citation in the policy map, then test the policy against the terms it covers. The test is a reading of the firm's own documents, not a certification. Start with the artefacts that cite Scope and work outwards.
Evidence an auditor or regulator asks for
- A policy map that names Scope and the clause it comes from.Shows that Scope was read and placed, not merely cited.
- A controlled vocabulary register for the entries in Scope, with an owner and a review date.An auditor asks who keeps the Scope entries current, not only whether they exist.
- One live artefact that uses a term from Scope correctly, with the date it was checked.Connects Scope to the work rather than to a shelf document.
Common gaps this page catches
- Scope is cited without the entries behind it, so the citation cannot be tested.
- A team has built a local vocabulary beside the standard and the two are now reconciled by memory rather than by a register.
What to prepare before the amendment lands
Take Scope into the next review, list the artefacts that rely on it and give each a named owner. The Scope list is the plan; the owner is the control.
How to test it here
Take one live artefact rather than a template, find the sentence or field where Scope is used, and put this page beside it. Record the answer, the artefact and the date, because that record is the evidence and a glossary entry on its own is only an intention.
What this page does not claim
The page does not reproduce the standard, certify the firm or predict the wording the amendment will use; it states Scope at the claim level "scope statement" and stops where the public record stops.
Common questions
- What does Scope mean in ISO 22989?
- The document sets out the vocabulary of AI and explains the ideas behind it. It is meant to serve the people who write other standards and anyone who needs a shared language for AI, and it applies to every kind of organisation.
- What evidence should we keep for 1?
- A policy map that names Scope and the clause it comes from. A controlled vocabulary register for the entries in Scope, with an owner and a review date.
- Is Scope a requirement?
- No: Scope is a definition or clause of a terminology standard, and it becomes binding only when a firm writes it into a policy, a contract or a procedure, or when another standard incorporates it.
Related units
Source. ISO/IEC 22989:2022, Clause 1. Open the ISO public entry. Retrieved 21 October 2026.
https://www.iso.org/obp/ui/en/#iso:std:iso-iec:22989:ed-1:v1:en
ISO catalogue record 88145, the amendment status, stage and dates. Catalogue record 74296, the base standard.
Claim level: scope statement. The clause is in the public preview.
Last updated: 2026-10-21 · Markdown version · Check your vocabulary