EvidenceSheet

MS-4.3 Measurable performance improvements or declines based on consultations with relevant AI actors including…

Measurable performance improvements or declines based on consultations with relevant AI actors including affected communities, and field data about context-relevant risks and trustworthiness characteristics, are identified and documented. Change in performance over time is measured against a baseline using field data and consultation, so decline is detected as decline rather than absorbed as normal variation.

Source: NIST AI RMF 1.0, MS-4.3. 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
Policy repository / GRC workspace
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

  • Consultation records with AI actors and affected communities on observed change · Document repository

governing documentDocuments that govern the control

  • Baseline measures for the trustworthiness characteristics being tracked · Policy repository / GRC workspace
  • Field data showing performance over time against that baseline · Policy repository / GRC workspace
  • Documented identification of improvement or decline and the action taken · 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

MS-4.2 Measurement results regarding AI system trustworthiness in deployment contexts and across the AI lifecycle…