Skip to main content

Explainability for bank readers

Explainability means your teams-and, when required, your supervisors-can answer: “Why was this applicant given this outcome?” in language that maps to policy and fair lending expectations.

What AIS provides at a high level​

  • Reason codes or factor summaries that tie back to the information the model was allowed to use.
  • Consistency so the same facts do not silently produce different reasons run to run (subject to approved model updates).
  • Artifacts your risk team can archive with the credit file (format depends on contract).

:::tip What this means for you

You do not need to read SHAP or LIME mathematics to govern AIS. You need clear accountability: who approved the model, who approved the policy mapping, and what evidence is stored with each decision.

:::

What banks should ask for in diligence​

  • A sample explanation for an approved, declined, and referred case.
  • The policy-to-model mapping narrative (who signed it, when).
  • How model updates appear in decision history after a release.

Boundaries​

AIS does not decide what is “fair” in a legal sense for your jurisdiction-your compliance and legal teams do. AIS provides technical explainability within the rules you set.

Regulatory interpretation - confirm with your AIS account team and your counsel.

Next: Boundaries & split · Overview