These are not values. They are commitments a client can check us against while the work is running — and, increasingly, the same places the regulator is looking.
01
Value the decision, don’t rule it
Every approval, limit, price and treatment has an expected value that can be estimated before it is made. A policy rule is a decision taken once, in the past, for a population that has since changed. Wherever the data allows it, we replace rules with valuations.
CBUAE Model Management Standards (Notice 5052/2022) apply to all models supporting decision-making, pricing models included. A credit policy rule set is a decisioning model: it belongs in the inventory, it is tiered for risk, and it is validated — whether or not anyone has ever called it a model.
02
Nothing counts without a control group
An intervention not measured against what would have happened anyway is a story, not a result. We design the control before the programme runs, and we report what the control says — including when it says our own work did not pay.
CBUAE MMS requires ongoing performance monitoring against defined metrics and limits, escalation, and reporting to a Model Oversight Committee at least quarterly. It also names “cherry-picking, reverse-engineering and positive bias” as grounds for supervisory action. A clean control group is the cheapest defence against all three.
03
Built for this market, not translated into it
Credit models carry the assumptions of the market they were built in. Here the dominant factors are different: employer concentration, income that stops discontinuously along with residency, a bureau that is thinnest exactly where the growth is, and structures that must be Shariah-compliant by design rather than by adaptation. Those are not adjustments to an imported model. They are the model.
CBUAE AI & ML Guidance Note (11 February 2026) requires training data to be “sufficiently accurate, relevant and representative of the customer populations to which the models will be applied.” A vendor model trained on another market’s population does not clear that bar by default, and the burden of showing it does sits with the institution.
04
Parameterised and production-grade
What we build is meant to run, not to be presented. Thresholds, weights and segment definitions are exposed as parameters your own team can move, documented well enough to know what moves when. If changing it requires us, we built it wrong.
CBUAE AI & ML Guidance is explicit that institutions “should not employ AI models that they have no control over,” and must retain the immediate ability, with human intervention, to stop using one. MMS adds documentation sufficient for an independent party to assess it, plus archiving for rollback. Control is now a requirement, not a preference.
05
Explainable to the customer, not just to the committee
A decision you cannot explain in a sentence to the person it was made about is a decision you do not fully understand yourself. Explainability is not a reporting layer added at the end — it constrains what you build, and it is worth the constraint. It is also the single least-prepared-for obligation in this market right now.
CBUAE AI & ML Guidance (Feb 2026) requires that consumers can request human review or an explanation of an AI-generated decision, with alternative arrangements for customers who do not want an AI decision at all; disclosures in plain language in Arabic and English; annual bias testing; and human oversight calibrated to risk. Most decisioning stacks here were not built to answer that.
06
Loss avoided is not value created
A credit function measured only on losses will produce a book that is smaller and safer than it should be, and will lose the customers worth having to whoever prices them properly. The objective is the value of the portfolio, and often that means approving more.