EvidenceSheet

MN-1.1 A determination is made as to whether the AI system achieves its intended purpose and stated objectives and whether its development or deployment should proceed

A determination is made as to whether the AI system achieves its intended purpose and stated objectives and whether its development or deployment should proceed. A recorded determination weighs measured risk against bene

4
artefacts
0
held by a system
1
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

  • The measured risk and benefit evidence the determination rested on · Document repository

governing documentDocuments that govern the control

  • The recorded determination on whether the system achieves its intended purpose · Document repository
  • The decision to proceed or not, with the deciding authority named · Document repository
  • Consideration of whether an AI system is the appropriate solution at all · 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

GV-6.2 Contingency processes are in place to handle failures or incidents in third-party data or AI systems deemed to be high-risk · MN-1.2 Treatment of documented AI risks is prioritized based on impact, likelihood, or available resources or methods