Contain incidents before optimising diagnosis
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
An incident is an event requiring coordinated action because service, data or people may be affected. Define severity by impact and urgency, not embarrassment. First prevent further harm: pause affected actions, restrict access or switch to a supported manual route. Preserve relevant evidence securely and record what is known and unknown. Notify the appropriate internal specialists promptly; external reporting obligations depend on the facts and jurisdiction and should be handled through the approved process. Do not promise that nothing happened before the scope is understood.
Worked example
A pack contains another candidate’s contact details. The owner pauses further sends, identifies recipients and affected records, involves the privacy lead and follows the incident process before resuming.
Put it into practice
Write the first thirty minutes of an incident response for a misdirected pack.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Name containment, investigation and communication owners. Keep factual timestamps and avoid speculative assurances. Include how essential candidate coordination continues safely during the pause.
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.