Terms related to trustworthiness · 3.5.17
verification
confirming, with objective evidence, that stated requirements have been met
What this term settles
This is the sense the standard gives verification. A firm is free to use another sense, but then the difference belongs in its own glossary rather than in an assumed shared language.
Who it binds
The entry has no shall in it, and the force of verification comes from use: once it appears in a procedure or a supplier term, this is the meaning the reader may rely on.
What to do in your practice
Add verification to the vocabulary register and to the onboarding pack. A term that is only in a PDF is not controlled; it is controlled when a new joiner can find it and a reviewer can test it.
Evidence an auditor or regulator asks for
- A controlled vocabulary entry for verification with the citation 3.5.17, an owner and a review date.An auditor can check that verification is controlled rather than assumed.
- An assurance argument that links the property to the test, the review or the incident record behind it. The row names verification.Shows verification in use in the artefact the firm relies on, not only in a glossary.
- A register row with the owner, the date and the evidence reference for the claim. The record carries the verification entry and its date.The assurance case asserts the property without naming the test, review or incident record that supports it. The gap is tested against verification.
Common gaps this page catches
- verification is used in the assurance argument without a written definition, so two teams can mean different things.
- verification appears in a template with no citation, so the reader cannot tell which sense was intended.
What to prepare before the amendment lands
Add the entry to the register, give it an owner and a review date, and test it against one live artefact this week. The test is the evidence; the register row alone is not.
How to test it here
Take one live artefact rather than a template, find the sentence or field where verification 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 verification at the claim level "definition" and stops where the public record stops.
Common questions
- What does verification mean in ISO 22989?
- confirming, with objective evidence, that stated requirements have been met
- What evidence should we keep for 3.5.17?
- A controlled vocabulary entry for verification with the citation 3.5.17, an owner and a review date. An assurance argument that links the property to the test, the review or the incident record behind it. The row names verification.
- Is verification a requirement?
- No: verification 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 3.5.17, Terms and definitions. 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: definition. The definition is in the public preview. This page states it in our own words and does not reproduce the text.
Last updated: 2026-10-21 · Markdown version · Check your vocabulary