EvidenceSheet

MN-4.3 Incidents and errors are communicated to relevant AI actors including affected communities, and processes for…

Incidents and errors are communicated to relevant AI actors including affected communities. Processes for tracking, responding to, and recovering from incidents and errors are followed and documented. Incidents and errors are communicated outward, including to affected communities, and the tracking record shows how each was identified, repaired and how the repair was distributed.

Source: NIST AI RMF 1.0, MN-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
1
held by a system
2
at each review
moderate
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

  • The incident and error record showing how each was identified · Document repository

periodic reviewEvidence produced at each review

  • Communication records to relevant AI actors and affected communities · Policy repository / GRC workspace
  • Evidence of whether the error was repaired and how the repair was distributed to impacted users · Document repository

governing documentDocuments that govern the control

  • The followed process for tracking, response and recovery · Document repository

First move

Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

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

MN-4.2 Measurable activities for continual improvements are integrated into AI system updates and include regular… · MP-1.1 Intended purpose, potentially beneficial uses, context-specific laws, norms and expectations, and prospective…