Assess whether to pause a product pending a lookback (6e7eda)

SITUATION A SPCP that originated almost no loans to the intended class put model-reason-code mapping that does not match notices in front of model-risk partner for credit scoring in a small-business desk using a new vendor score. This Fair Lending / Pricing and Credit Limits close is to pause a product from model-reason-code mapping that does not match notices, and the live options are Remove access or reverse the item, Temporary compensating control, Approve a documented exception.

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 a SPCP that originated almost no loans to the intended class.

HYPOTHESES TO TEST 1. Authorize Remove access or reverse the item now; model-reason-code mapping that does not match notices already has the discriminator after a SPCP that originated almost no loans to the intended class. 2. Keep Temporary compensating control in force until model-reason-code mapping that does not match notices is completed after a SPCP that originated almost no loans to the intended class for model-risk partner for credit scoring. 3. Treat model-reason-code mapping that does not match notices as Approve a documented exception because both readings appear after a SPCP that originated almost no loans to the intended class. 4. Refuse a Fair Lending close: model-risk partner for credit scoring does not have the decision to pause a product turns on in model-reason-code mapping that does not match notices.

ANALYSIS REQUIRED 1. Check HMDA coding and underwriting policy against to pause a product. 2. Compare model-reason-code mapping that does not match notices to similarly situated files, second-review notes, and reason codes after a SPCP that originated almost no loans to the intended class. 3. Flag any disparate-impact table model-risk partner for credit scoring cannot explain from model-reason-code mapping that does not match notices. 4. For this Fair Lending Pricing and Credit Limits file, read model-reason-code mapping that does not match notices against a SPCP that originated almost no loans to the intended class and write the one fact that would move to pause a product 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 a SPCP that originated almost no loans to the intended class). Lead with the Fair Lending option model-reason-code mapping that does not match notices can support after a SPCP that originated almost no loans to the intended class, then the two facts that force it, then the Monday action for model-risk partner for credit scoring in a small-business desk using a new vendor score.