Approve a bounded use and revisit it
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
An approval should specify permitted tasks, data, users, controls, evaluation results and review triggers. Keep a record of supplier changes and incidents. The UK responsible-AI recruitment guide discusses assurance across procurement and deployment, so review should continue after purchase. EU requirements and implementation dates should be checked against current official material rather than memorised from a static course. Suspend or restrict a use case when evidence no longer supports the approved scope. Publish internal decisions clearly enough that operators know what is allowed today.
Worked example
A supplier adds an emotion-scoring feature to an approved transcription product. The old approval does not automatically cover the new feature. The owner disables it pending separate assessment.
Put it into practice
Write an approval record with scope, five conditions and three re-review triggers.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Include model or feature changes, new data types and serious incidents. State who can suspend the use. A procurement signature is not permanent approval for every future capability.
Sources and further reading
Original Academy teaching and fictional examples. These references provide context, not endorsement. Edition 2026.09; updated 2026-09-24.
- GOV.UK: Responsible AI in recruitment
UK guidance on procuring and deploying recruitment AI.
- NIST: AI Risk Management Framework
Voluntary framework for organising AI risks and controls.
- European Commission: AI regulatory framework
Check the current rules, scope and implementation dates for EU operations.