What is the most common gap auditors find on MP-5.2?

Engagement run as a one-off consultation at launch

`MP-5.2` Practices and personnel for supporting regular engagement with relevant AI actors and integrating feedback…

Q: What evidence do auditors commonly ask for on MP-5.2 Practices and personnel for supporting regular engagement with relevant AI actors and integrating feedback…?

The documented engagement practice and its cadence; Personnel assigned to conduct and integrate engagement; Records of impacts reported through engagement, including unanticipated ones; Evidence reported impacts were integrated into the impact record.

Practices and personnel for supporting regular engagement with relevant AI actors and integrating feedback about positive, negative, and unanticipated impacts are in place and documented. Engagement with affected actors is a resourced standing practice with named personnel, and unanticipated impacts have a route back into the impact record.

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

artefacts

held by a system

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

Records of impacts reported through engagement, including unanticipated ones · Document repository
Evidence reported impacts were integrated into the impact record · Document repository

governing documentDocuments that govern the control

The documented engagement practice and its cadence · Document repository
Personnel assigned to conduct and integrate engagement · 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

Engagement run as a one-off consultation at launch
No named personnel, so engagement depends on individual initiative
Unanticipated impacts reported with no route into the risk record

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-5.1 Likelihood and magnitude of each identified impact are identified and documented, based on expected use, past… · MS-1.1 Approaches and metrics for measurement of AI risks enumerated during the MAP function are selected for…