Assess whether line assignments have a disparate impact the bank will defend

SITUATION Pricing and Credit Limits work in a small-business desk using a new vendor score now turns on line assignments have a because an underwriter chat that used coded language put model-reason-code mapping that does not match notices in play. Model-risk partner for credit scoring should say what model-reason-code mapping that does not match notices proves.

DECISION Model-risk partner for credit scoring in a small-business desk using a new vendor score must choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold using model-reason-code mapping that does not match notices after an underwriter chat that used coded language.

HYPOTHESES TO TEST 1. Model-risk partner for credit scoring can defend Remove access or reverse the item from model-reason-code mapping that does not match notices after an underwriter chat that used coded language in a Fair Lending challenge. 2. Model-risk partner for credit scoring cannot defend Remove access or reverse the item from model-reason-code mapping that does not match notices; Temporary compensating control is what the extract actually supports after an underwriter chat that used coded language. 3. An underwriter chat that used coded language never reached the population in model-reason-code mapping that does not match notices — reopen intake, do not close line assignments have a. 4. Two facts in model-reason-code mapping that does not match notices after an underwriter chat that used coded language conflict for model-risk partner for credit scoring; hold this Pricing and Credit Limits file.

ANALYSIS REQUIRED 1. Compare model-reason-code mapping that does not match notices to similarly situated files, second-review notes, and reason codes after an underwriter chat that used coded language. 2. Flag any disparate-impact table model-risk partner for credit scoring cannot explain from model-reason-code mapping that does not match notices. 3. Test a documented exception versus a pattern a small-business desk using a new vendor score must defend. 4. For this Fair Lending Pricing and Credit Limits file, read model-reason-code mapping that does not match notices against an underwriter chat that used coded language and write the one fact that would move line assignments have a for model-risk partner for credit scoring.

RECOMMENDATION Choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold on this Fair Lending / Pricing and Credit Limits packet (model-reason-code mapping that does not match notices after an underwriter chat that used coded language). If model-reason-code mapping that does not match notices cannot force a Fair Lending label under Pricing and Credit Limits, stop. Do not invent missing evidence a small-business desk using a new vendor score does not have.