EvidenceSheet

MP-1.3 The organization's mission and relevant goals for the AI technology are understood and documented

The organization’s mission and relevant goals for the AI technology are understood and documented. The system's connection to a stated organisational goal is written down, which is what makes a go or no-go decision revie

4
artefacts
0
held by a system
2
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 go or no-go decision record referencing that linkage · Document repository
  • Evidence of review when goals or the system changed · Document repository

governing documentDocuments that govern the control

  • Documented mission and the specific goals the AI technology serves · Document repository
  • The linkage from system objectives to those organisational goals · Policy repository / GRC workspace

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.2 Inter-disciplinary AI actors, competencies, skills and capacities for establishing context reflect demographic diversity and broad domain and user experience expertise, and their participation is documented · MP-1.4 The business value or context of business use has been clearly defined or, in the case of assessing existing AI systems, re-evaluated