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

GV-1.4 The risk management process and its outcomes are established through transparent policies, procedures, and…

The risk management process and its outcomes are established through transparent policies, procedures, and other controls based on organizational risk priorities. The process and the decisions it produced are both documented in a form a reviewer outside the delivery team can follow, including who decided and on what basis.

Source: NIST AI RMF 1.0, GV-1.4. 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
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. 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

  • Completed records for deployed systems showing the process was followed, not just defined · Document repository

governing documentDocuments that govern the control

  • The documented AI risk management process, with the decision points it contains · Document repository
  • Standardised documentation templates used across AI work products · Document repository
  • Named accountable contacts recorded on work products so decisions are traceable to people · 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-1.3 Processes and procedures are in place to determine the needed level of risk management activities based on… · GV-1.5 Ongoing monitoring and periodic review of the risk management process and its outcomes are planned…