Maintain an iterative risk file covering identified risks: Which documentation approach best supports risk

High-risk risk management should remain documented and iterative, connecting identified risks, mitigations, and operational learning.

The question

Preparing for AIGP? Take the free 5-min readiness quiz →

1. Maintain an iterative risk file covering identified risks and mitigations. ✓

   High-risk risk management requires an ongoing documented process addressing risks and mitigations across the system lifecycle.
2. Rely on the supplier’s general risk statement without adding school-specific context.

   Supplier information may help, but deployer context and operational risks require relevant documentation beyond generic statements.
3. Record the initial risk workshop and archive later operational findings separately.

   A disconnected initial record does not demonstrate the continuing, lifecycle-oriented risk-management process expected for high-risk systems.
4. Store only incidents that produce measurable admissions errors for annual review.

   Risk documentation should address identified risks broadly, not only realized errors or a single periodic review.

How to remember it

High-risk risk management should remain documented and iterative, connecting identified risks, mitigations, and operational learning.

More Understanding How Laws, Standards and Frameworks Apply to AI questions

• Assess whether the retraining and refund function: Assuming EU AI Act duties apply, which approach best →
• Document data provenance and representativeness gaps: Which evidence is most important first? →
• Issue role-specific instructions and define review: What should the deployer do? →
• All 394 Understanding How Laws, Standards and Frameworks Apply to AI questions →