EvidenceSheet

MP-2.1 The specific task, and methods used to implement the task, that the AI system will support is defined

The specific task, and methods used to implement the task, that the AI system will support is defined (e.g., classifiers, generative models, recommenders). The learning or decision task is stated narrowly, together with

4
artefacts
0
held by a system
0
at each review
hard
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

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • The documented task the system performs, stated narrowly · Document repository
  • The method or model class used to implement the task · Document repository
  • The boundary of what the system does not do · Document repository
  • Evidence the definition was updated when the task changed · Document repository

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

Common gaps auditors find

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 sheet

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 · MP-2.2 Information about the AI system's knowledge limits and how system output may be utilized and overseen by humans is documented