ISO/IEC FDIS 42105 · stage 50.20 FDIS ballot closes 21 October 2026 Planning date 16 Feb 2027, our estimate Official record
OHISO 42105 Revision CheckerHuman oversight of AI systems, before publication

Home / Register / OH-25

ISO/IEC 42001:2023, A.6.2.6

Operation and monitoring

Unit OH-25 in the Life cycle theme. The held citation is ISO/IEC 42001:2023, A.6.2.6, and the row asks for 3 pieces of evidence.

At a glance

Ref
OH-25
Theme
Life cycle
Held source
ISO/IEC 42001:2023
Citation
ISO/IEC 42001:2023, A.6.2.6
Evidence
3 items
Gaps
3 common

Evidence to keep

  • Operation and monitoringOperating procedures for monitoring, repair, update and support
  • Operation and monitoringProduction performance monitoring including drift
  • Operation and monitoringAn update process with user communication

Questions before you sign

  • What is monitored, how often and by whom?
  • What triggers a review?
  • Are users told when the system changes?

The requirement, in our words

Define and document what the system needs for ongoing operation, at minimum monitoring of the system and its performance, repair, updating and support.

What it means for human oversight

Live monitoring is where the overseer sees drift, out-of-range output and use outside the intended conditions. The review must have a cadence, a trigger and an owner.

How to evidence it

Attach the artefacts above to the Operation and monitoring row with the system name, the owner and the date. The first one is the anchor: Operating procedures for monitoring, repair, update and support. The OH-25 file is complete when the named person can produce that artefact and explain the decision it records, without asking someone else where it is.

The reviewer will sample one live decision and ask for Production performance monitoring including drift. If that artefact for OH-25 cannot be produced, the row is a gap, whatever the policy says.

OH-25 carries 3 evidence items and 3 common gaps. For operation and monitoring, test the control on a live system at production volume, since a version that works only in a pilot has not yet been shown to work. The OH-25 statement above is ours, written from ISO/IEC 42001:2023, A.6.2.6, not a reproduction of the licensed text.

Common gaps

  • Drift not monitored
  • Updates pushed without informing users
  • Use beyond the designed purpose not reviewed
Where the FDIS fits. The public abstract says the draft applies to all types of organizations across the AI system life cycle, so operation and monitoring is one of the places the guidance is expected to operate. For OH-25, the FDIS clause numbering and wording are not public, so this page cites ISO/IEC 42001:2023, A.6.2.6 above and does not quote the draft.

Related units

Source for this page: ISO/IEC 42001:2023, A.6.2.6. Open ISO/IEC 42001:2023, A.6.2.6 and compare it with the OH-25 statement above. Retrieved 2026-10-21.