EvidenceSheet
NIST AI RMF 1.0 · MANAGE - NIST AI RMF 1.0

MN-4.1 Post-deployment AI system monitoring plans are implemented, including mechanisms for capturing and evaluating…

Post-deployment AI system monitoring plans are implemented, including mechanisms for capturing and evaluating input from users and other relevant AI actors, appeal and override, decommissioning, incident response, recovery, and change management. A single implemented plan covers the post-deployment lifecycle end to end, and each named element, including appeal and override, is actually operating.

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

  • The appeal and override mechanism and records of its use · Document repository

governing documentDocuments that govern the control

  • The implemented post-deployment monitoring plan and its scope · Policy repository / GRC workspace
  • Mechanisms for capturing and evaluating user and AI actor input · Document repository
  • Incident response, recovery, change management and decommissioning arrangements for the system · Policy repository / GRC workspace

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

MN-3.2 Pre-trained models which are used for development are monitored as part of AI system regular monitoring and… · MN-4.2 Measurable activities for continual improvements are integrated into AI system updates and include regular…