MP-1.6 System requirements are elicited from and understood by relevant AI actors, and design decisions take socio-technical implications into account to address AI risks
System requirements (e.g., “the system shall respect the privacy of its users”) are elicited from and understood by relevant AI actors. Design decisions take socio-technical implications into account to address AI risks.
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Design decision records showing socio-technical implications considered · Document repository
periodic reviewEvidence produced at each review
- Record of who requirements were elicited from and how · Document repository
governing documentDocuments that govern the control
- Written system requirements including non-functional and trustworthiness requirements · Document repository
- Traceability from a requirement to the design element that satisfies it · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Requirements captured as model performance targets only
- Elicited from the commissioning stakeholder alone, missing operators and affected parties
- Requirements written but no traceability, so nothing shows they were built
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetMP-1.5 Organizational risk tolerances are determined and documented · MP-2.1 The specific task, and methods used to implement the task, that the AI system will support is defined