EvidenceSheet
NIST AI RMF 1.0 · GOVERN - NIST AI RMF 1.0

GV-3.1 Decision-making related to mapping, measuring, and managing AI risks throughout the lifecycle is informed by…

Decision-makings related to mapping, measuring, and managing AI risks throughout the lifecycle is informed by a diverse team (e.g., diversity of demographics, disciplines, experience, expertise, and backgrounds). The people making AI risk decisions span disciplines and backgrounds, and where internal composition is narrow, external input is obtained and recorded.

Source: NIST AI RMF 1.0, GV-3.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST AI RMF 1.0 in the compliance library.

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Records of the disciplines represented on AI risk decision forums · Document repository
  • Evidence that a dissenting or external view changed a decision · Document repository

governing documentDocuments that govern the control

  • Documented consultation with external perspectives where internal expertise was thin · Document repository
  • The organisational commitment on composition of AI risk teams · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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-2.3 Executive leadership of the organization takes responsibility for decisions about risks associated with AI… · GV-3.2 Policies and procedures are in place to define and differentiate roles and responsibilities for human-AI…