Translate needs into verifiable requirements
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
Write requirements as observable behaviour under a scenario. Include permissions, accessibility, data handling, integrations, export and failure recovery. Ask suppliers to distinguish available functionality from roadmap commitments. Claims about accuracy or fairness need evidence relevant to the intended use. Assign a verification method to each must-have: document review, demonstration with your case or a controlled test. Contractual promises and technical behaviour both matter, and appropriate legal or security review should handle specialist concerns. Do not infer assurance from a badge without understanding its scope.
Worked example
Instead of supports integrations, the requirement states that a candidate withdrawal must cancel queued outreach and preserve the restriction after record merge. The trial tests that exact behaviour.
Put it into practice
Create eight requirements with priority and verification method.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
At least three should cover failure, exit or handling constraints. Mark unsupported claims as unverified and distinguish a future roadmap item from an available feature.
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.