Risk · R-084 · Model Performance & Reliability
Use beyond validated scope
A model approved for one purpose is reused for another, or for a new population, without reassessment.
- Severity
- High
- Audience
- Heads-of · Practitioner
- Frameworks
- Article 25 · Article 26 · Annex A.9 · Principle 3
- Responsible AI domain
- Lifecycle stage
- Reviewed
- 2026-11-10
What it is
Approval of a model is approval for a stated use. Models are attractive to reuse: the work is done, the output is available, and a neighbouring team has a similar need. Each reuse quietly extends the model beyond what was tested. General-purpose models make this easier still, since the same system will attempt whatever it is asked. The risk is governance failure more than model failure: nobody decided that the new use was acceptable.
How it happens
- A score built for marketing is adopted for credit or pricing decisions.
- A model validated for one country or product is rolled out to others.
- An assistant approved for internal drafting is exposed to customers.
- The approved purpose was recorded so loosely that anything fits.
Why it matters
The evidence of fitness does not transfer. Risk tiering, impact assessment and legal classification were all done for the original use and may be wrong for the new one, including classification under the EU AI Act, where a change of intended purpose can bring a system into the high-risk category.
Warning signs
- The inventory records a model's owner and not its approved uses.
- Other systems consume a model's output without the owner's knowledge.
- Usage has grown in areas the original case did not mention.
- No trigger exists for reassessment when use changes.
Who owns it
The model owner is accountable for where the model is used. Each business owner who adopts it is accountable for obtaining approval for their use. Governance maintains the record.
In practice
A propensity score that predicts which customers will respond to a savings offer is picked up by the collections team as an indicator of financial resilience and used to set repayment plans. The same pattern generalises to any model whose output is available to people beyond those it was approved for.
Mitigating controls
Primary controls
- Intended-use definition and use restrictions Directive
- States the approved purpose, users and population, with reuse requiring reassessment. The approved purpose, users, population and conditions of use of each AI system are stated precisely, and any use outside them requires reassessment before it begins.
Supporting controls
- AI inventory and registration Detective
- Records each system's approved use. All AI systems and models, whether built, bought or embedded in other products, are recorded with owner, purpose, tier, data, supplier and status, and the record is reconciled periodically.
- AI use-case intake and approval Preventive
- A new use of an existing model goes through approval. Every proposed AI use is registered, screened, tiered and approved by a named authority before build or purchase begins, and again before it goes live.
- Periodic AI review and recertification Detective
- Periodic review compares actual with approved use. Each AI system is reassessed on a cycle set by its tier, covering use, performance, risk and controls, and its approval lapses if the review is not completed.
Framework and clause references
| Framework | Clause | Title |
|---|---|---|
| EU AI Act | Article 25 | Responsibilities along the AI value chain Changing the intended purpose can make a deployer a provider. |
| EU AI Act | Article 26 | Obligations of deployers of high-risk AI systems Use in line with instructions. |
| ISO/IEC 42001:2023 | Annex A.9 | Use of AI systems Intended use. |
| SS1/23: Model Risk Management Principles for Banks | Principle 3 | Model development, implementation and use Use within approved scope. |
Sources
- EU AI Act: Regulation (EU) 2024/1689 European Union (EUR-Lex) · official text
- SS1/23: Model Risk Management Principles for Banks Bank of England PRA · official text
- ISO/IEC 42001:2023 – AI management systems ISO/IEC · framework
Related terms
How to cite
Axiom Verity (2026). Use beyond validated scope. Reference Library, R-084. https://axiom-verity.com/risks/use-beyond-validated-scope. Reviewed 2026-11-10.
Found an error or a better source? Report a correction.