Policy and procedure drafting
Drafts or updates an internal policy or procedure from the rules it implements.
How the register minutes it
| Also called | Policy drafting, procedure drafting, handbook updates |
|---|---|
| Function | Legal |
| Default stakes | drafts, when the paste gives none. A policy is approved by its owner; a rule misstated in the policy is followed by everyone who reads it. |
| Listed use | No Annex III or Article 22 listing |
| Who it faces | Nobody outside the function |
| Where the error lands | The process itself, not a filed statement or return |
| The error that matters | A rule misstated or omitted in the policy. The benchmark measures rule misstatements and omissions against the source rule, checked by the policy owner. |
| Review point | The policy owner reads the draft against the source rule before approval; the record holds the draft, the source and the approval. |
| Oversight record | 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. |
| Contract terms to check | Source currency, version control, approval workflow. |
The benchmark to demand from the vendor
For drafts internal policies and procedures, minuted as drafts: show us performance on 200 of our own labelled cases of policy and procedure drafting, measured as rule misstatements and omissions against the source rule, checked by the policy owner, at a miss rate below 5 percent on the sample, every miss listed and classed, 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
17 clauses across 5 regimesShown 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 literacyProviders 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 ...
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 practicesProhibits 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...
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 systemsDetermine 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...
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 systemsThe 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.
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.9.3 Objectives for responsible use of AI systemIdentify and record the objectives that steer how AI systems are used responsibly.
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 systemMake sure the AI system is used in line with its intended uses and its accompanying documentation.
Common gap: Is off-label use detected and addressed?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.10.3 SuppliersSet 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.
Common gap: standard security due diligence used with nothing AI specific
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.6.2.4 AI system verification and validationAI systems shall be verified and validated, and the results documented. Verification confirms requirements are met; validation confirms intended use is achieved.
Common gap: Are V&V results signed off independently from developers?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42001 A.8.2 System documentation and information for usersThe organization shall determine and provide the necessary information for users of the AI system.
Common gap: Are limitations communicated as clearly as capabilities?
Source framework: ISO/IEC 42001:2023
ISO/IEC 42005:2025
ISO/IEC 42005 5.4 Timing of the assessment, reassessment triggers and triagingWhen 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...
Common gap: Assessment done once at design and never revisited
Source framework: ISO/IEC 42005:2025
ISO/IEC 42005 6.3.4 Intended usesThe 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.
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 documentedAI 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.
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 documentedThe 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.
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 documentedAI 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.
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 controlsThe 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.
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 risksThe 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...
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 exitFor 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...
Common gap: Exit plans exist on paper only, never tested for feasibility
Source framework: APRA CPS 230
Findings this task type can raise
- No benchmark evidence on the entity's own cases
Every classified line where the paste records no benchmark on the entity's own labelled cases. A general benchmark says what the tool does on somebody else's data; the regimes ask for performance demonstrated under conditions like the deployment. The finding is the letter: per line, the sample size, the error type, the rate the stakes class implies and the retest cadence tied to the reporting cycle. - Concentration on one tool
One tool behind a third or more of the lines, or one tool behind every line that decides alone. Concentration is often the right operational choice; the regimes ask that the dependency be recorded, that the supplier be assessed and monitored, and that the entity can keep deciding if the tool is unavailable or withdrawn.
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