Service · AI Governance Fixed fee 2–4 weeks

AI Inventory Sort

Supervisors on both sides of the Atlantic now expect banks to inventory their AI and tier it by risk. Neither says which controls each system needs. Machine learning, generative and agentic AI overlap, so most inventories put a credit model, a chatbot and a rules engine in the same bucket and give them the same controls. We sort your inventory by what each system outputs, tier it by the consequence of failure, assign each one the controls it needs, and show you the gaps against SS1/23, the FCA’s October 2026 review and the OCC’s November 2026 AI framework.

Book a 30-Minute Call How It Works
3 × 4
Output classes by consequence tiers
2–4 wks
From inventory extract to report
1 answer
What model risk should — and should not — own

01 The Problem

In the UK, the FCA’s review of AI in financial services (19 October 2026) points to an inventory of AI use cases and the models behind them, and to risk scoring or tiering to calibrate governance — but leaves the method to each firm. Its own terms — machine learning, generative AI, agentic AI — overlap, so they cannot serve as a classification. In the US, OCC Bulletin 2026-54 (4 November 2026) gives examiners a framework for all AI — including the generative and agentic AI that the April model risk guidance left out — under which use cases may be tiered by potential consequences, transfer of agency and the degree of human oversight, rather than technical sophistication. Both point the same way. Neither tells a bank which controls each system needs.

MRM over-reaches
Model risk tries to validate a GenAI chatbot it cannot open. The result is documentation that passes review without controlling the risk.
MRM under-reaches
An LLM that returns a typed decision is filed as “GenAI” and escapes validation it could and should have, against labelled outcomes.
Rules fall through
Deterministic rules mostly sit outside the SS1/23 model definition, but SS1/23 still expects documented controls on them — and asks firms to consider model risk management for material, complex rules. Both get missed.
Nobody can defend the sort
When the PRA or FCA asks why a system is governed the way it is, the answer is a label, not a reason.

02 Sort by Output

The question that decides the controls is not what technology a system uses, but what it returns. The same task — sanctions alert triage, for example — can be built three ways, and each needs a different control set.

Typed decisionValidate itGenerativeGovern the useRulesOwn the rules
What it returnsA choice from a fixed set, often with a confidence score — even when an LLM produces itOpen-ended content with no single right answer; the same input can give different outputsThe result of written logic, the same every time for the same input
How it failsConfident wrong picks; calibration drifts with data, prompt or vendor changesPlausible but wrong content; behaviour shifts with prompts, retrieval and vendor updatesA misread policy, applied consistently to every case
Main controlsIndependent validation against labelled outcomes, calibration testing, change control over model, prompt and configurationUse-case evaluation sets, red-teaming, human oversight, live outcome sampling, configuration change controlRule review against source policy, regression testing, change approval, exception review
Under SS1/23A model: the full framework appliesMay meet the model definition, but validation alone cannot carry the weightOutside the model definition, but documented controls expected (1.1(c)); consider MRM where material and complex (1.1(b))

Systems that act on their own — AI agents — are sorted by the output they act on, with additional controls on access, approvals and autonomy.

Then tier by consequence

Output decides which control set applies. Consequence decides how intensive those controls must be. Each system is tiered by what happens if it fails, how much it can do on its own, whether its actions can be reversed, and how much human oversight remains — consistent with the consequence-based approach in the OCC’s framework.

Tier 1
Critical
Acts directly on customers or money, little or no reversibility. Pre-approval for actions, circuit breakers, tested kill switch, independent testing.
Tier 2
High
Acts, or heavily shapes decisions, with a human on the loop. Substantive human review, independent testing, close outcome monitoring.
Tier 3
Moderate
Decision support with a mandatory human in the loop; reversible. Evaluation before release, sampling, change control.
Tier 4
Low
No customer or financial data, no direct action, fully human-controlled. Approved-tool list, usage rules, inventory entry.

The same output class can land in any tier: an LLM summarising internal memos and an LLM drafting customer complaint responses are both generative, but they are not governed with the same intensity.

03 How It Works

Three steps, each feeding the next. We work from your existing inventory and policies; where the inventory is incomplete, finding what is missing is part of the work.

1
Classification & tiering
Every use case, sorted, tiered and justified
We list each AI use case — including vendor tools, embedded AI and unregistered GenAI — sort it by output (typed decision, generative or rules) and tier it by consequence and autonomy. Each classification is documented with its reasoning, so you can defend it to the PRA, the FCA and, for US operations, the OCC.
OutputA classified AI register, one line per use case, with owner, output class, tier and rationale.
2
Separate controls
The right control set for each class
Each class is mapped to the controls that fit it: model risk validation for typed decisions, use-case governance for generative systems, rule controls for deterministic logic — with model risk management considered where rules are material and complex. The tier then sets how intensive each control is. Ownership is set across model risk, technology, data protection and conduct.
OutputA control map by class, with owners, and a clear statement of what model risk owns.
3
Gap analysis
What you have versus what each system needs
We test your current controls against the control set and tier for each system, against SS1/23, against the practices highlighted in the FCA’s October 2026 review and, for groups with US operations, against OCC Bulletin 2026-54. Gaps are prioritised by tier and customer impact.
OutputA prioritised gap list with owners and target dates, and a two-page board summary.

04 The Practicalities

Designed to be light on your teams and quick to a decision.

Who it’s for
CROs, heads of model risk and AI governance leads at banks and regulated firms
What we need
Your model or AI inventory, relevant policies, and three or four short interviews
Timeline
Two to four weeks, depending on the size of the inventory
Fee
Fixed, agreed after a 30-minute scoping call
Practitioner Insight
London and Washington have now landed in the same place: inventory your AI, tier it by consequence, and keep generative AI out of a model risk framework that cannot validate it. Both leave the sort to you. That is an opportunity as much as a burden: a firm that can explain why each system is governed the way it is will have a far easier supervisory conversation than one that can only show a list. Sort by output, tier by consequence, and keep model risk for the systems it can genuinely validate.

05 Try It First

Two free checks show the thinking on a single system before you commit to the whole inventory.

Make your AI inventory defensible

A 30-minute call is enough to see how the sort would apply to your inventory and to agree a fixed scope.

Book a 30-Minute Call Read: The CRO’s AI Framework

References to the FCA’s October 2026 review AI in financial services: good practice and areas for improvement describe practices it highlights; the review creates no new requirements. OCC Bulletin 2026-54 Super Intelligence: Supervisory Framework is an examiner resource and does not establish new requirements for banks; the tiers above are LINXS’s, informed by its consequence-based approach. Nothing on this page is regulatory or legal advice.