Decision Register

Contract review against a playbook

Compares counterparty paper with the playbook and lists the deviations for a lawyer.

How the register minutes it

Also calledContract review, redlining, playbook review
FunctionLegal
Default stakesinforms, when the paste gives none. The tool lists deviations; the lawyer decides which to negotiate. A missed deviation is the error.
Listed useNo Annex III or Article 22 listing
Who it facesNobody outside the function
Where the error landsThe process itself, not a filed statement or return
The error that mattersA missed deviation from the playbook. The benchmark measures deviations missed against a lawyer-marked set of the same contracts.
Review pointA lawyer reads the counterparty paper with the list beside it; the record holds the list and what the lawyer added.
Oversight recordWho read the output and what it informed; date and the tool version; the output kept with the decision it informed.
Contract terms to checkPlaybook version, confidentiality, no training on the matter.

The benchmark to demand from the vendor

For reviews counterparty paper against the playbook, minuted as informs: show us performance on 100 of our own labelled cases of contract review against a playbook, measured as deviations missed against a lawyer-marked set of the same contracts, at the error rate reported and every miss listed, with no ceiling, because the reader needs to know what the summary omits, retested every year and on any change of model or version, with the test set, the metric definitions and the tool version documented so the test can be repeated.

The sample size, the acceptable rate and the cadence follow the stakes class; the register renders this paragraph per line in the vendor benchmark letter.

What each regime attaches

15 clauses across 5 regimes

Shown on a register for the regimes you tick, on a line minuted at the default stakes; with none ticked, the ISO/IEC 42001 rows are the default. Requirement text in our own words, read clause by clause from the published standards: our statement of each clause, not the instrument verbatim.

The EU AI Act, as deployer

EU AI Act Art. 4 AI literacy

Providers and deployers of AI systems must take measures to ensure, to their best extent, a sufficient level of AI literacy among their own staff and any other persons who deal with the operation and use of AI systems on their behalf. The measures must be calibrated to those persons' technical knowledge, experience, education and training, to the context in ...

Evidence an auditor accepts: A register of the staff and contracted persons who operate or use AI systems on the organisation's behalf; Training content differentiated by role, prior technical knowledge and the deployment context; Attendance, completion and comprehension records per cohort
Common gap: One generic awareness module issued to everyone regardless of role or technical starting point
Source framework: EU AI Act, Regulation (EU) 2024/1689
EU AI Act Art. 5 Prohibited AI practices

Prohibits a defined set of AI practices, including subliminal/manipulative techniques causing significant harm, exploitation of vulnerabilities, social scoring by public authorities, predictive policing based solely on profiling, untargeted scraping of facial images, emotion recognition in workplace/education, biometric categorisation inferring sensitive att...

Evidence an auditor accepts: Pre-deployment screening against the Art.5 prohibition list
Common gap: Treating exceptions as routine basis
Source framework: EU AI Act, Regulation (EU) 2024/1689
EU AI Act Art. 6 Classification rules for high-risk AI systems

Determine and record, for each AI system, whether it is high-risk. A system is high-risk where it is intended to be used as a safety component of, or is itself, a product covered by the Union harmonisation legislation listed in Annex I and that product must undergo third-party conformity assessment, or where it falls within an Annex III use case. Where the p...

Evidence an auditor accepts: A classification record per AI system naming the Annex I legislation or the Annex III use case considered, and the conclusion reached; The documented Art.6(3) assessment where an Annex III system is judged not high-risk, dated before placing on the market; Evidence the profiling rule was applied, so any system profiling natural persons is classified high-risk regardless of the derogation
Common gap: Classification decided once at design time and never revisited when the intended purpose broadened
Source framework: EU AI Act, Regulation (EU) 2024/1689

ISO/IEC 42001:2023

ISO/IEC 42001 A.9.2 Processes for responsible use of AI systems

The organization shall define and document processes for the responsible use of AI systems, including processes for the use by employees of AI systems provided by third parties.

Evidence an auditor accepts: Responsible use procedure; Acceptable use policy for AI; Training records
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.9.3 Objectives for responsible use of AI system

Identify and record the objectives that steer how AI systems are used responsibly.

Evidence an auditor accepts: Responsible use objectives; Linkage to risk treatment
Common gap: Are use objectives distinct from development objectives?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.9.4 Intended use of the AI system

Make sure the AI system is used in line with its intended uses and its accompanying documentation.

Evidence an auditor accepts: Intended use statements; Use case approval records; Monitoring of use
Common gap: Is off-label use detected and addressed?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.10.3 Suppliers

Set up a process so that the services, products or materials the organization obtains from suppliers fit its approach to developing and using AI systems responsibly.

Evidence an auditor accepts: supplier assessment criteria covering responsible AI; completed assessments for AI suppliers including model, dataset and component providers; contract terms binding suppliers to the organization's AI requirements
Common gap: standard security due diligence used with nothing AI specific
Source framework: ISO/IEC 42001:2023

ISO/IEC 42005:2025

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, proce...

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

The NIST AI RMF 1.0

AI RMF MS-2.3 AI system performance or assurance criteria are measured qualitatively or quantitatively and demonstrated for conditions similar to deployment settings, and measures are documented

AI system performance or assurance criteria are measured qualitatively or quantitatively and demonstrated for conditions similar to deployment setting(s). Measures are documented. Performance is demonstrated under conditions resembling deployment rather than only on held-out test data, and the measures are recorded.

Evidence an auditor accepts: The performance or assurance criteria set for the system; Measurement results obtained under conditions similar to the deployment setting; The argument that the test conditions resemble deployment
Common gap: Performance demonstrated only in silico on a static test set
Source framework: NIST AI RMF 1.0
AI RMF MS-2.5 The AI system to be deployed is demonstrated to be valid and reliable, and limitations of the generalizability beyond the conditions under which the technology was developed are documented

The AI system to be deployed is demonstrated to be valid and reliable. Limitations of the generalizability beyond the conditions under which the technology was developed are documented. Validity and reliability are demonstrated before deployment, and the boundary beyond which the demonstration does not carry is written down.

Evidence an auditor accepts: Validation results demonstrating validity and reliability prior to deployment; Documented limitations on generalisability beyond the development conditions; The conditions under which the system was developed and tested
Common gap: Validity claimed from training performance rather than independent validation
Source framework: NIST AI RMF 1.0
AI RMF MN-3.1 AI risks and benefits from third-party resources are regularly monitored, and risk controls are applied and documented

AI risks and benefits from third-party resources are regularly monitored, and risk controls are applied and documented. Third-party data, model, software and hardware dependencies are monitored on an ongoing basis, not assessed once at procurement, and the controls applied are recorded.

Evidence an auditor accepts: The inventory of third-party resources the AI system depends on; Monitoring records showing regular review of those dependencies; The risk controls applied to each and evidence they are in place
Common gap: Third parties assessed at onboarding and not monitored afterwards
Source framework: NIST AI RMF 1.0

APRA CPS 230

CPS 230 para 28 Design, implement and embed internal controls

The entity must design, put in place and embed internal controls that reduce its operational risks consistently with its risk appetite and that allow it to meet its compliance obligations.

Evidence an auditor accepts: Control library with control objectives, owners and the risks and obligations each control addresses; Control design assessments; Mapping of key controls to the operational risk appetite metrics
Common gap: Controls documented but not linked to risks or obligations
Source framework: APRA CPS 230
CPS 230 para 48 Register of material service providers and management of their risks

The entity must identify its material service providers, keep a register of them and manage the material risks of using them. A material service provider (or material arrangement) is one the entity relies on to carry out a critical operation or one that exposes it to material operational risk; it may be an unrelated third party, a related party or a connecte...

Evidence an auditor accepts: Register of material service providers with service, critical operation supported and materiality rationale; Materiality assessments covering related parties and aggregated arrangements; Risk assessments and treatment plans per material provider
Common gap: Intra-group providers left off the register
Source framework: APRA CPS 230
CPS 230 para 55 Manage the risks of each material arrangement, including BCP execution and orderly exit

For each material arrangement the entity must (a) identify and control risks to the provider's ability to keep delivering the service; (b) identify and manage risks the arrangement creates for the entity itself, such as contagion or step-in risk; (c) make sure it can carry out its BCP if required; and (d) make sure it can exit the arrangement in an orderly w...

Evidence an auditor accepts: Ongoing risk assessment per material arrangement covering provider viability, step-in and contagion risk; BCP linkage showing how each arrangement is covered in continuity planning; Exit plan per material arrangement with trigger events, alternatives and transition steps (unless exempt under para 57 or 58)
Common gap: Exit plans exist on paper only, never tested for feasibility
Source framework: APRA CPS 230

Findings this task type can raise

Do this for every line on your list

Paste the list and get this minute for every task at once, with the stakes class, the listed-use flags, the findings and the obligation rows per regime. Eight lines free, no account.

Build my decision register

Contract clause drafting · Contract summary and key-term extraction