Assess whether line assignments have a disparate impact the bank will defend
August 31, 2026
SITUATION A branch that stopped taking applications in one ZIP put model-reason-code mapping that does not match notices in front of HMDA data-quality manager in a credit union rolling out a special-purpose credit program. This Fair Lending / CRA and Special-Purpose Programs close is line assignments have a 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 HMDA data-quality manager in a credit union rolling out a special-purpose credit program 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 branch that stopped taking applications in one ZIP.
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 branch that stopped taking applications in one ZIP. 2. Keep Temporary compensating control in force until model-reason-code mapping that does not match notices is completed after a branch that stopped taking applications in one ZIP for HMDA data-quality manager. 3. Treat model-reason-code mapping that does not match notices as Approve a documented exception because both readings appear after a branch that stopped taking applications in one ZIP. 4. Refuse a Fair Lending close: HMDA data-quality manager does not have the decision line assignments have a turns on in model-reason-code mapping that does not match notices.
ANALYSIS REQUIRED 1. Match the adverse-action language to the facts in model-reason-code mapping that does not match notices. 2. Check HMDA coding and underwriting policy against line assignments have a. 3. Compare model-reason-code mapping that does not match notices to similarly situated files, second-review notes, and reason codes after a branch that stopped taking applications in one ZIP. 4. For this Fair Lending CRA and Special-Purpose Programs file, read model-reason-code mapping that does not match notices against a branch that stopped taking applications in one ZIP and write the one fact that would move line assignments have a for HMDA data-quality manager.
RECOMMENDATION Choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold on this Fair Lending / CRA and Special-Purpose Programs packet (model-reason-code mapping that does not match notices after a branch that stopped taking applications in one ZIP). The follow-on CRA and Special-Purpose Programs action is what HMDA data-quality manager does next: implement the option, assign an owner, and log the missing fact.
Explore more
More Fair Lending prompts
- Assess whether pricing disparities are justified by legitimate factors
- Assess whether pricing disparities are justified by legitimate factors
- Assess whether a model update needs a fair-lending revalidation (790ba0)
- Assess whether pricing disparities are justified by legitimate factors
- Assess whether the CRA plan is strategy or window dressing (7b2503)
Explore related decision areas
- D&O specialist must resolve whether CAT pricing is defensible given SOVInsurance Underwriting
- Assess whether a generative-AI incident is a policy breach or a model defectAI Governance
- Assess whether loss development requires a rate or a restriction (eed1b0)Insurance Underwriting
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

