ISO/IEC 42001:2023·Annex A A.8.2·medium·Component: Organizational controls

What this control requires

Documentation and user-facing information for AI systems shall be maintained to support safe, responsible, and intended usage.
— ISO/IEC 42001:2023, Annex A A.8.2

In plain English

Documentation and user-facing information for AI systems shall be maintained to support safe, responsible, and intended usage. In practice, this means you can prove you document ai systems-level controls on a defined cadence.

Why it matters

ISO 42001 is the first audited evidence regulators, customers and investors can ask for that you are managing AI risk. Each Annex A control is a check-box in that audit; it is also the management system enterprises are starting to require from AI vendors before an MSA can be signed.

What an auditor looks for

An ISO 42001 auditor verifies you have an AI policy, a risk-based system of impact assessments for each AI system, lifecycle controls from data acquisition through retirement, and third-party-AI controls that pierce the vendor's wrapper to underlying model behaviour.

Within Organizational controls, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.2) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

  • Document. Document the trigger, the owner and the cadence.
  • Use. Document the trigger, the owner and the cadence.
  • Scope: ai systems.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Approved documentation and communication policies should define what information is provided to users, while controlled records should demonstrate that user-facing documentation is maintained and made available. Focus: System documentation and information for users.

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in ISO/IEC 42001:2023

References

Topics: governance risktransparencydocumentation managementpolicy management