Assess whether comparative files show second-review bias (2efb38)
August 31, 2026 · SmartSolo
Situation
A lender expanding into majority-minority census tracts cannot treat a vendor score change with no disparate-impact test as color commentary on model-reason-code mapping that does not match notices. Second-review underwriter must close comparative files show second-review from that extract under Fair Lending / CRA and Special-Purpose Programs.
Decision
Second-review underwriter in a lender expanding into majority-minority census tracts 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 vendor score change with no disparate-impact test.
Hypotheses to test
- The population in model-reason-code mapping that does not match notices is the one a vendor score change with no disparate-impact test named, so Remove access or reverse the item follows for this CRA and Special-Purpose Programs file.
- The population in model-reason-code mapping that does not match notices is adjacent only to a vendor score change with no disparate-impact test; Temporary compensating control is the honest Fair Lending call.
- A lender expanding into majority-minority census tracts already contained a vendor score change with no disparate-impact test before model-reason-code mapping that does not match notices arrived; no new CRA and Special-Purpose Programs path.
- Provenance on model-reason-code mapping that does not match notices after a vendor score change with no disparate-impact test is broken; do not pick Remove access or reverse the item or Temporary compensating control yet.
Analysis required
- Compare model-reason-code mapping that does not match notices to similarly situated files, second-review notes, and reason codes after a vendor score change with no disparate-impact test.
- Flag any disparate-impact table second-review underwriter cannot explain from model-reason-code mapping that does not match notices.
- Test a documented exception versus a pattern a lender expanding into majority-minority census tracts must defend.
- For this Fair Lending CRA and Special-Purpose Programs file, read model-reason-code mapping that does not match notices against a vendor score change with no disparate-impact test and write the one fact that would move comparative files show second-review for second-review underwriter.
Explore more
More Fair Lending prompts
- Assess whether the exam response should concede a finding (ab398d)
- Assess whether the CRA plan is strategy or window dressing (db4191)
- Assess whether line assignments have a disparate impact the bank will defend
- Assess whether dealer overlays introduce prohibited steering (51e343)
- Assess whether the CRA plan is strategy or window dressing (7982a6)
Explore related decision areas
- Assess whether to non-renew a deteriorating book segment (1f240f)Insurance Underwriting
- Assess whether umbrella attachment is too thin for the hazard (5d4ef8)Insurance Underwriting
- Assess whether the vendor can be used in a regulated process (9bcb1a)AI Governance
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.

