How to identify and assess AI risks: the six-phase method
AI risk identification finds, describes and records the ways an organisation's AI could cause harm, before anything is scored or controlled. This page summarises the method in the book, phase by phase.
Why identification comes first
Every AI risk framework asks for it. The EU AI Act's Article 9 starts the risk management system with the identification and analysis of known and reasonably foreseeable risks. ISO/IEC 42001 requires an AI risk assessment in clause 6.1.2, and ISO/IEC 23894 gives guidance on running one. None of them tells you how to find the risks in a real organisation, with its vendors, its spreadsheets and its pilots that quietly became production. A risk that is never identified is never scored, never controlled and never reported.
The method comes from bank risk identification, where regulators expect a complete, reconciled and documented risk inventory. It was rebuilt for AI with a new taxonomy, a new register and a fifth impact dimension, harm to individuals.
Phase 1: Foundation setting
Map the standards and laws that apply, set governance and roles, adopt the taxonomy, and set the context. Build the AI system inventory: every system, whether it is bought or built, its model and version, its purpose, its users, the persons it affects, its role and classification under the AI Act, and its owner. Set the risk criteria. Then take the register as a starting universe, so that the work does not begin from a blank page. Chapters 2 to 5.
Phase 2: Dual-track identification
Run two tracks, because each misses what the other sees. Top-down, senior people work through workshops, SWIFT (a structured what-if technique), scenarios, Delphi rounds and red-team review. One SWIFT prompt asks what happens if the vendor changes the model behind the service and does not tell you. Bottom-up, the people who operate each system complete the AI use-case template: a five-line system header and eleven fields, from the underlying drivers to the data quality rating. Ten specialist sub-processes cover what a general template cannot: data protection (DPIA), security (OWASP), fairness testing, model validation, third-party due diligence, content and intellectual property, safety for physical systems, accessibility, environmental impact, and human factors. Chapters 6 and 7.
Phase 3: Reconciliation and the portfolio view
Merge the two lists in five steps: match, gap, challenge, resolve and record. A risk that only one track found is a blind spot of the other, and the disagreement log keeps the arguments that scoring will settle. Then step back to the portfolio: the enterprise AI risk map and the concentrations behind it, such as one foundation-model provider under many use cases. Chapter 8.
Phase 4: Assessment
Score impact on five dimensions (financial, regulatory and legal, reputational, harm to individuals, and customer and operational), and let the highest set the score. Score the likelihood of the harm, not of the technical error, per stated unit of exposure: per output, per decision, per person affected or per year. Record vulnerability and speed of onset beside the score, and rate the evidence behind every score with a data quality rating. Score inherent and residual risk; a control that has not been tested reduces nothing. A line is material if its inherent score is 15 or more on the 5 × 5 grid, or if its impact is 5. Chapter 9.
Phase 5: Interaction
A heat map cannot show links. The interaction matrix records, for each pair of material and linked lines, whether one triggers the other, amplifies it or shares a driver with it. Bow-ties set causes, controls and consequences around each material risk, and the matrix shows cascades: a silent vendor update amplifies automation bias, which triggers decisions that cannot be explained. Look for hidden concentration: two suppliers may run on the same underlying model. Chapter 10.
Phase 6: Documentation
Keep the result as a living AI risk inventory: the fourteen fields of the bank method plus five AI columns (lifecycle stage, role, persons affected, regulatory hooks and ISO/IEC 42001 Annex A references). Each material risk gets a profile that a board member can read in five minutes, and every change leaves an audit trail. Chapter 11.
After the six phases
The register feeds the rest of the AI management system: fundamental rights impact assessments under Article 27 of the AI Act, data protection impact assessments, the ISO/IEC 42001 Statement of Applicability, post-market monitoring and the board report (Chapter 12). It is kept current by a cycle (Chapter 13):
| When | What runs | Output |
|---|---|---|
| Monthly | Indicator review for each material line | Indicator sheet, trends, escalations |
| On an event | Targeted update after a trigger, such as a vendor model change | Updated lines, significance decision |
| Quarterly | Active re-identification | Signed register, change list, disagreement log |
| Annually | Full re-identification from the start | New baseline, comparison with last year |
| At planned intervals | Internal audit and management review | Findings, decisions on residual risk |
Chapter 14 covers technology, including using AI to find AI risk, where the tool proposes and a person decides. Chapter 15 maps the method to the EU AI Act and to rules in the UK, the US, China, Korea and elsewhere. Chapter 16 tests the method against public AI failures.
Questions about AI risk assessment
What is AI risk management?
The coordinated work of finding, assessing, treating and monitoring the risks of the AI an organisation builds, buys and uses, with owners, records and reports to the board. Identification is its first step.
What is an AI risk assessment?
The process of identifying, analysing and evaluating the risks an AI system poses, so that they can be treated. ISO/IEC 42001 requires one in clause 6.1.2. In this method, phase 2 identifies the risks, phase 3 reconciles them and phase 4 scores them.
How do you conduct an AI risk assessment?
Start from an inventory of the AI systems in use. Identify risks top-down with senior people and bottom-up with each system's operators, and reconcile the two lists. Score each risk for impact, likelihood, vulnerability and speed of onset, with a rating for the evidence. Record how the risks interact, document the result, and repeat the cycle.
What is the NIST AI Risk Management Framework?
A voluntary framework from the US National Institute of Standards and Technology, published in January 2023. It is organised in four functions: Govern, Map, Measure and Manage. NIST AI 600-1, published in July 2024, is its profile for generative AI.
What is ISO/IEC 42001?
The international standard for an AI management system, published in December 2023. Organisations can be certified against it. It requires an AI risk assessment, risk treatment and an AI system impact assessment (clauses 6.1.2 to 6.1.4), and lists 38 controls in Annex A.
What is the difference between ISO/IEC 23894 and ISO/IEC 42001?
ISO/IEC 42001 sets requirements for an AI management system and can be certified against. ISO/IEC 23894 is guidance on managing AI risk, built on ISO 31000, and cannot be certified against. The method is mapped to both.
What does Article 9 of the EU AI Act require?
A risk management system for every high-risk AI system: a continuous process across the system's lifecycle that identifies and analyses the known and reasonably foreseeable risks, estimates and evaluates them, including under reasonably foreseeable misuse, and adopts measures to manage them.
What is a fundamental rights impact assessment?
An assessment that some deployers of high-risk AI systems must carry out before first use, under Article 27 of the EU AI Act: public bodies, private bodies providing public services, and deployers of systems for credit scoring or for life and health insurance pricing. It covers the process, how often the system is used, the people affected, the specific risks of harm, human oversight, and the measures to take if the risks materialise.
The full method, free
The book sets out each phase with its templates, scales and worked examples, and Appendix B holds the templates: the system inventory, the use-case template, the assessment record, the SWIFT prompts and the contract clause checklist.
Get the book and the register
Your files are ready. The links are personal to your email address and work for 7 days. A copy is on its way to your inbox.
Start with Chapter 1, then Appendix A for the register. Questions about the method are welcome at rory@eonriskservices.com.