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

SITUATION A mortgage company after a pricing-regression spike cannot treat a vendor score change with no disparate-impact test as incidental context on model-reason-code mapping that does not match notices. Exam-response coordinator must close line assignments have a from that extract under Fair Lending / Examination and Notices.

DECISION Exam-response coordinator in a mortgage company after a pricing-regression spike 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 1. 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 Examination and Notices file. 2. 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. 3. A mortgage company after a pricing-regression spike already contained a vendor score change with no disparate-impact test before model-reason-code mapping that does not match notices arrived; no new Examination and Notices path. 4. 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 1. Test a documented exception versus a pattern a mortgage company after a pricing-regression spike must defend. 2. Match the adverse-action language to the facts in model-reason-code mapping that does not match notices. 3. Check HMDA coding and underwriting policy against line assignments have a. 4. For this Fair Lending Examination and Notices 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 line assignments have a for exam-response coordinator.

RECOMMENDATION Choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold on this Fair Lending / Examination and Notices packet (model-reason-code mapping that does not match notices after a vendor score change with no disparate-impact test). The follow-on Examination and Notices action is what exam-response coordinator does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Fair Lending option on line assignments have a, then the evidence in model-reason-code mapping that does not match notices, then the action for exam-response coordinator - Hypothesis scorecard against model-reason-code mapping that does not match notices: supported / rejected / untestable - Owner and next date for exam-response coordinator in a mortgage company after a pricing-regression spike - What changes line assignments have a if a vendor score change with no disparate-impact test is later withdrawn