EvidenceSheet
NIST AI RMF 1.0 · MAP - NIST AI RMF 1.0

MP-3.4 Processes for operator and practitioner proficiency with AI system performance and trustworthiness, and…

Processes for operator and practitioner proficiency with AI system performance and trustworthiness – and relevant technical standards and certifications – are defined, assessed and documented. Operator proficiency is defined as a requirement, assessed rather than assumed, and recorded, because the human-AI configuration only works if the human can do the job assigned.

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

  • Assessment records showing proficiency was tested, not assumed · Document repository

governing documentDocuments that govern the control

  • Defined proficiency requirements for operators and practitioners of the system · Document repository
  • Relevant technical standards or certifications identified for the role · Policy repository / GRC workspace
  • Refresh arrangements when the system or its performance changes · 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

MP-3.3 Targeted application scope is specified and documented based on the system's capability, established context… · MP-3.5 Processes for human oversight are defined, assessed, and documented in accordance with organizational…