Contract, roll out and plan exit
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
The decision should identify approved scope, conditions, accountable owners and success measures. Confirm responsibilities for data, support, incidents and change notification through the proper review process. Roll out in a bounded group with training and a pause route. Check whether the promised value appears after real adoption, including correction and administration costs. Maintain a usable export and transition plan so switching supplier is possible. Renewal should be a fresh decision informed by evidence, not an automatic consequence of accumulated dependence.
Worked example
A supplier changes usage pricing and removes an export field. The owner uses the review and exit plan to assess impact before renewal rather than discovering the dependency during a rushed migration.
Put it into practice
Write a rollout and renewal plan with five acceptance conditions and an exit test.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Name operational owners and the evidence required at each review. Include data return, access removal and continuity during transition. Procurement ends with a maintained service, not merely a signed order.
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.