EvidenceSheet

MP-1.2 Inter-disciplinary AI actors, competencies, skills and capacities for establishing context reflect…

Inter-disciplinary AI actors, competencies, skills and capacities for establishing context reflect demographic diversity and broad domain and user experience expertise, and their participation is documented. Opportunities for interdisciplinary collaboration are prioritized. The people establishing context bring domain and user-experience expertise beyond the build team, and their participation is recorded so the basis of the context statement is auditable.

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

  • Record of the disciplines and expertise represented in context establishment · Document repository
  • Evidence that interdisciplinary collaboration was prioritised and resourced · Document repository

governing documentDocuments that govern the control

  • Documented participation of domain and user-experience specialists · Document repository
  • The competency requirements set for context establishment work · HR system / LMS

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-1.1 Intended purpose, potentially beneficial uses, context-specific laws, norms and expectations, and prospective… · MP-1.3 The organization's mission and relevant goals for the AI technology are understood and documented