Decision Register
Regimes ยท ISO/IEC 42005

ISO/IEC 42005:2025

Attaches to every line through the timing and intended-use items, to listed uses through the thresholds, and to the lines that decide through the performance, recording, monitoring and documentation items of the impact assessment.

On the register, tick "ISO/IEC 42005" and these rows appear on every line the regime reaches. Source framework: ISO/IEC 42005:2025.

Which lines it reaches, and with what

On every classified line

5.4, 6.3.4. When the impact assessment is performed and reassessed, and the intended uses and users the assessment documents.

On listed-use lines (Annex III, or Article 22 on a line that decides alone)

5.7. The thresholds for sensitive and restricted uses: a listed use is the case the thresholds exist for.

On lines that decide (with review or alone)

5.8, 5.10, 5.12. Performing, recording and monitoring the assessment on a line that decides.

6.7.2, 6.8.2, 6.8.3, 6.9. The documented items: the parties directly affected, the benefits and harms, the failures and foreseeable misuse, and the measures adopted.

The record it expects

informsThe tool produces a summary, a ranking or a flag that a person reads before deciding; the person owns the decision. The record holds: who read the output and what it informed; date and the tool version; the output kept with the decision it informed.
draftsThe tool produces the draft of a document, a figure or a position that a person edits and signs; the person owns the content. The record holds: who edited and who signed; date and the tool version; the draft kept beside the signed version; what was changed, classed as omission, misstatement or wording.
decides with reviewThe tool takes the decision and a named person reviews every case or a stated share before the effect; the reviewer can change the outcome. The record holds: reviewer, role and the competence that qualifies them (Art. 26); date and the tool version; sample reviewed: the count out of the total, and the share; overrides: count and rate; escalations and to whom; log reference and retention period (Art. 12, Art. 26); input data checked as relevant and representative (Art. 26).
decides aloneThe tool takes the decision and the effect follows with no person in between; a person may audit afterwards. The record holds: who audits the line afterwards, role and competence (Art. 26); date, the tool version and the volume decided; audit sample: the count out of the total, and the share; reversals after audit: count and rate; escalations and to whom; log reference and retention period (Art. 12, Art. 26); input data checked as relevant and representative (Art. 26); incidents reported to the provider and the date (Art. 26).

The clauses, quoted

10 of 31 in the framework

Requirement text in our own words, read clause by clause from the published standards: our statement of each clause, not the instrument verbatim.

ISO/IEC 42005 5.4 Timing of the assessment, reassessment triggers and triaging

When setting up the process the organization should decide when assessments are carried out and in how much depth, and when an earlier assessment can be used again, adapted to a new purpose or updated, and to what extent. Timing can be shaped by applicable law; contractual and professional duties; the organization's own structures, policies, processes, procedures and resources, technology among them; the AI system's risk level (clause 6.3.4 of ISO/IEC 23894:2023 offers guidance); what relevant interested parties, customers among them, expect; and the internal AI life cycle processes (Annex D covers timing alongside other assessments). Reassessment should be considered when something changes: the intended use, including who uses the system; customer expectations; the AI system itself (its data, its complexity or type, its performance); its operating environment; or the context around it (applicable law, contracts, internal policies, relevant interested parties, and the places and sectors the organization works in or plans to). Risk and impact assessments should be done before the triggering change is put into effect. Timing questions include how often assessments happen, at which life cycle stage, how often they are refreshed, what circumstances call for a new or updated assessment, and which other impact assessments are tied to it. The organization should also consider triage: if only high-risk AI systems are to be assessed, the process should state what makes a system high-risk and what triggers an assessment, and a shortened assessment can be used to decide whether a full one is needed.

Evidence an auditor accepts: Timing rules per life cycle stage and reassessment triggers; Triage criteria defining high-risk systems; Evidence that changes were assessed before implementation
Common gap: Assessment done once at design and never revisited
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 6.3.4 Intended uses

The document should describe the intended uses of the AI system and its intended users (people or information systems), the contexts and conditions of use the system is designed for, and any restricted or sensitive uses identified under 5.7.

Evidence an auditor accepts: Intended use and intended user description; Restricted and sensitive uses flagged
Common gap: Intended users undefined
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 5.7 Establishing thresholds for sensitive uses, restricted uses and impact scales

Documented thresholds, above all for how an AI system is used, are central to the process: the organization should set them for its own context, taking into account applicable law, the expectations of relevant interested parties, the current state of the art, the benefits the AI system brings, cultural, labour and societal norms, and the ethical frameworks for AI that apply. Depending on the kinds and number of thresholds it can add processes such as reviews and approvals; it may decide, for instance, that some uses, or some misuses that can reasonably be foreseen, count as sensitive or are forbidden by its policy, and law and other external requirements can also make a use sensitive. Where an assessment shows that a planned use is sensitive or restricted, the organization should record what the next steps in the overall process are. Automated credit decisions are given as an example of sensitive use because of their potential financial harm to individuals, and a system with a significant effect on human rights, particularly children's rights, whose harms cannot be removed by technical changes alone is given as a case to escalate to higher management, including on whether to redesign it. The organization should also decide how the overall scale of impact is set and how foreseeable impacts are measured, because a use that is not sensitive can still reach a very large population; it should weigh scale when shaping the assessment's components and set criteria for the types of impact an AI system can cause, for example ranking an impact as very severe when it can lead to significant adverse consequences for the organization, groups or societies.

Evidence an auditor accepts: Documented sensitive-use, restricted-use and impact-scale thresholds; Escalation and approval steps for uses crossing a threshold; Impact scale method
Common gap: No definition of sensitive or restricted uses
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 5.8 Performing the AI system impact assessment

The organization should carry out the assessment by its documented process: find where impacts can come from, the events and their outcomes; weigh how serious and how likely they are; judge them against the thresholds and criteria; choose how to treat them; and record the results in the clause 6 structure. It should take account of the data the system was built on, the AI techniques it uses and what the whole system does (ISO/IEC 42001:2023, B.5.2), draw on the interested parties who can contribute, and cover each impact area in scope: fairness, accountability, transparency and explainability, privacy and security, health and safety, financial effects, accessibility and human rights.

Evidence an auditor accepts: Completed assessments following the documented steps; Evidence of interested-party input
Common gap: Assessment reduced to a checklist with no analysis of consequences and likelihood
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 5.10 Recording and reporting

The organization should record the assessment and its results and report them to the functions and interested parties that need them (other organizational processes, management review, and where appropriate users and other relevant interested parties), retaining the records for a defined period and updating them as needed (ISO/IEC 42001:2023, B.5.3), using the clause 6 documentation structure so that reports are consistent and comparable across systems.

Evidence an auditor accepts: Assessment records retained for the defined period; Reports issued to the defined recipients; Template use evidenced
Common gap: Results reported nowhere beyond the project team
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 5.12 Monitoring and review

The organization should monitor the AI system and its context after the assessment and review the assessment at planned intervals and on the 5.4 triggers, checking whether identified impacts materialised, whether measures are effective and whether new impacts have emerged, and feeding the results into the management review and the next assessment cycle (the NIST crosswalk places this clause under GOVERN 1 and MEASURE 3 and 4).

Evidence an auditor accepts: Monitoring plan and review schedule per assessed system; Review records showing effectiveness of measures and new impacts
Common gap: Assessment treated as a one-off deliverable
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 6.7.2 Directly affected interested parties

The document should identify the individuals and groups directly affected by the AI system, including users, those whose data is processed and those subject to its decisions or outputs, with specific attention to groups with particular protection needs such as children, impaired persons, elderly persons and workers (ISO/IEC 42001:2023, B.5.4; the NIST crosswalk places 6.7 under GOVERN 5 and MAP 1).

Evidence an auditor accepts: Affected-party identification including vulnerable groups
Common gap: Affected parties limited to customers
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 6.8.2 Benefits and harms

The document should set out the benefits and harms, actual and reasonably foreseeable, that the AI system brings to individuals, groups and societies in each impact area (fairness, accountability, transparency and explainability, privacy and security, health and safety, financial effects, accessibility, human rights; ISO/IEC 42001:2023, B.5.4 and B.5.5). That includes effects on a person's legal position or life chances, physical or mental well-being and universal human rights, and effects on societies (B.5.2), sorted with the Annex C taxonomy of harms and benefits.

Evidence an auditor accepts: Benefit and harm analysis by affected group and impact area; Use of the Annex C taxonomy
Common gap: Only benefits documented
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 6.8.3 AI system failures and reasonably foreseeable misuse

The document should describe the impacts of AI system failures (errors, performance degradation, drift, unavailability, adversarial manipulation) and of reasonably foreseeable misuse (6.8.3.3, per the NIST crosswalk), including who is affected, how severely and how likely, and the detection and response arrangements.

Evidence an auditor accepts: Failure and misuse impact analysis with severity and likelihood; Detection and response arrangements documented
Common gap: Failure modes not analysed for impact on people
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 6.9 Measures to address harms and benefits

The document should describe the measures adopted or planned to address the identified harms and to realise the benefits: technical and organizational mitigations, human oversight, transparency to affected parties, redress mechanisms, residual impacts accepted and by whom, and how the measures will be monitored under 5.12 (ISO/IEC 42001:2023, B.5.2 treatment and B.5.4 the means to address expectations).

Evidence an auditor accepts: Measures register linked to each identified harm and benefit; Residual impact acceptance records; Monitoring arrangements
Common gap: Harms identified with no measures
Source framework: ISO/IEC 42005:2025

See what it attaches to your list

Paste the list, tick the regime, and every line it reaches carries these rows. Eight lines free, no account.

Build my decision register