Assess whether to pause a product pending a lookback after an underwriter

SITUATION HMDA LAR validity and quality edits arrived with an underwriter chat that used coded language for fair-lending officer. That is a Fair Lending Pricing and Credit Limits decision on to pause a product in a mortgage company after a pricing-regression spike.

DECISION Fair-lending officer 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 HMDA LAR validity and quality edits after an underwriter chat that used coded language.

HYPOTHESES TO TEST 1. The population in HMDA LAR validity and quality edits is the one an underwriter chat that used coded language named, so Remove access or reverse the item follows for this Pricing and Credit Limits file. 2. The population in HMDA LAR validity and quality edits is adjacent only to an underwriter chat that used coded language; Temporary compensating control is the honest Fair Lending call. 3. A mortgage company after a pricing-regression spike already contained an underwriter chat that used coded language before HMDA LAR validity and quality edits arrived; no new Pricing and Credit Limits path. 4. Provenance on HMDA LAR validity and quality edits after an underwriter chat that used coded language is broken; do not pick Remove access or reverse the item or Temporary compensating control yet.

ANALYSIS REQUIRED 1. Compare HMDA LAR validity and quality edits to similarly situated files, second-review notes, and reason codes after an underwriter chat that used coded language. 2. Flag any disparate-impact table fair-lending officer cannot explain from HMDA LAR validity and quality edits. 3. Test a documented exception versus a pattern a mortgage company after a pricing-regression spike must defend. 4. For this Fair Lending Pricing and Credit Limits file, read HMDA LAR validity and quality edits against an underwriter chat that used coded language and write the one fact that would move to pause a product for fair-lending officer.

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 (HMDA LAR validity and quality edits after an underwriter chat that used coded language). If HMDA LAR validity and quality edits cannot force a Fair Lending label under Pricing and Credit Limits, stop. Do not invent missing evidence a mortgage company after a pricing-regression spike does not have.

COMMAND RETURNS - Bottom-line Fair Lending option on to pause a product, then the evidence in HMDA LAR validity and quality edits, then the action for fair-lending officer - Hypothesis scorecard against HMDA LAR validity and quality edits: supported / rejected / untestable - Pricing and Credit Limits finding in HMDA LAR validity and quality edits that a second reviewer can re-perform - Missing page in HMDA LAR validity and quality edits after an underwriter chat that used coded language, if any