← Return to the book

FUTURECENTRAL PRESS · APPLIED EXERCISE SAMPLE

AI for Retail Banking

The Guide for Retail Banking Professionals

Chapter 3: AI in Personal Lending and Unsecured Retail Credit

The AI-native unsecured-credit stack, the four-outcome decision engine, and the credit officer’s loop that now holds it to account

Retail Credit Exercise Sample

This sample shows the applied work in AI for Retail Banking: The Guide for Retail Banking Professionals. Examine the five components of the Retail Credit Underwriting Architecture, work through the five-step audit and consider seven reflection questions. The deliverable is a one-page map identifying where the unsecured lending process takes a risk without a matching control.

Framework overview

The Retail Credit Underwriting Architecture is the five-component map this chapter uses to hold the unsecured stack together, and it is built to be placed over the reader’s own book so the officer can name where each risk is taken and each control sits. The components run in sequence, and a weakness in an early one cannot be repaired by a later one.

Component one is the data and feature layer. This is the bureau record, the Account Aggregator consented data, the alternative and device signals, the KYC and internal customer data, and the feature pipeline that turns them into model inputs. The officer’s control point is data quality and consent: a confident model on bad or improperly-consented data lends badly and unlawfully, and most surprising losses trace to this layer rather than to the model.

Component two is the scoring-model layer. This is the application score, the behavior and bureau-derived models, the affordability assessment, and the fraud models that run alongside them. The officer’s control point is knowing what each model can and cannot see, and reading a model’s score as a ranked input to a decision rather than as the decision itself.

Component three is the decision engine. This is the policy layer that routes each application to one of four outcomes, auto-approve, auto-decline, refer, or conditional approve, at a set price, limit, and tenor. The officer’s control point is the boundaries between the outcomes, because the referral band and the conditional state, not the score, are where the bank’s risk appetite is actually set.

Component four is the override and human-in-the-loop layer. This is the officer’s loop: the referral queue, the override decision, the structured reason code, and the adverse-action communication. The officer’s control point is keeping the override a live act of judgment that captures learnable reasons, because this layer is where the bank demonstrates that a human owns the lending decision.

Component five is the monitoring and governance layer. This is model-risk management, drift and performance monitoring, fairness testing, and the documentation the FREE-AI and Digital Lending architecture requires, run by the second line over the whole stack. The officer’s control point is building the first four components for inspection, because the speed at which the bank can run the stack is set by how much of it the second line can actually govern. Used together, the five components let the officer answer the question the chapter opened with: where, in this book, does a human still decide, and can the bank prove it?

Applied exercise

The deliverable for this chapter is a one-page map of the credit officer’s own unsecured stack across the five components, a working document for finding where the bank takes a risk without a matching control. Work the five steps in order; alone it takes about two hours, and with a colleague from model risk, half a day.

Step one, the data layer. Name the sources the unsecured book underwrites on, bureau, Account Aggregator, alternative and device signals, internal data, and for each note the main blind spot and the consent basis. Close with the one data-quality or consent issue most likely to be causing surprising declines or first-payment defaults in the book today.

Step two, the model layer. List the scoring, affordability, and fraud models the book runs, and for each name the segment it was tuned on, the date of last validation, and one thing it cannot see. Flag any model being used on a segment it was not trained for, because that is where the thin-file drift in the Failure Modes sidebar begins.

Step three, the decision engine. Write down where the four outcome boundaries currently sit, the auto-approve and auto-decline cut-offs, the width of the referral band, and the conditions on the conditional state, and note who owns each boundary. Mark the one boundary that has moved in the last year to hit a volume or cost target, and what it did to the tail.

Step four, the override loop. Record the current override rate on each referral desk, whether overrides carry structured reason codes, and whether the reasons feed the next model version. Name the desk closest to a zero-override rate, because that is the desk where automation bias is most advanced and the human check is most nearly gone.

Step five, the governance layer. Note what the second line currently sees of the stack, the override data, the fairness tests, the drift monitoring, the Digital Lending evidence, and what it does not. Close the map with the single component where the bank takes a risk the second line cannot yet inspect, because that is where the officer’s next quarter of work pays off.

Reflection questions

  1. Lay the officer’s own unsecured book over the five components of the Retail Credit Underwriting Architecture. At which component does the bank currently take a risk without a matching control, and what would closing that gap cost in the next quarter?
  2. Find the referral desk in the book closest to a zero-override rate. Is that desk handling genuinely easy cases, or has automation bias set in? What review would tell the difference, and who should run it?
  3. Identify one boundary in the decision engine, a cut-off, the referral band, or a conditional-state condition, that has moved in the last year to hit a volume or cost target. What did the move do to the tail, and was the credit function or the business head the one who actually decided it?
  4. Take one unsecured decline the book made this month and trace whether the reason in the adverse-action notice, the reason in the override record, and the reason the model used are the same reason. If they are not, where does the chain break?
  5. Pick one segment the book underwrites on Account Aggregator or alternative data. What fairness test currently runs on it before deployment, and if none does, what is the bank’s exposure and who owns it?
  6. Take one fintech partnership the bank funds or co-lends into. Can the bank prove it owns and can audit the credit policy, and does the structure meet the Digital Lending requirements on disbursal, the Key Fact Statement, and the loss-guarantee cap? Where is the weakest point?
  7. Consider the AGM (Retail Credit Risk) Lens. Of the five components, which does the officer’s own second line see most clearly today and which least, and what would it take to make the override loop fully legible to them?