Assess whether notices match the actual decisioning reasons after a branch

SITUATION In a lender expanding into majority-minority census tracts, underwriting exception log by branch is the evidence after a branch that stopped taking applications in one ZIP. HMDA data-quality manager has to pick Remove access or reverse the item or Temporary compensating control for this Fair Lending Pricing and Credit Limits close using underwriting exception log by branch.

DECISION HMDA data-quality manager 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 underwriting exception log by branch after a branch that stopped taking applications in one ZIP.

HYPOTHESES TO TEST 1. The population in underwriting exception log by branch is the one a branch that stopped taking applications in one ZIP named, so Remove access or reverse the item follows for this Pricing and Credit Limits file. 2. The population in underwriting exception log by branch is adjacent only to a branch that stopped taking applications in one ZIP; Temporary compensating control is the honest Fair Lending call. 3. A lender expanding into majority-minority census tracts already contained a branch that stopped taking applications in one ZIP before underwriting exception log by branch arrived; no new Pricing and Credit Limits path. 4. Provenance on underwriting exception log by branch after a branch that stopped taking applications in one ZIP is broken; do not pick Remove access or reverse the item or Temporary compensating control yet.

ANALYSIS REQUIRED 1. Match the adverse-action language to the facts in underwriting exception log by branch. 2. Check HMDA coding and underwriting policy against notices match the actual. 3. Compare underwriting exception log by branch 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 Pricing and Credit Limits file, read underwriting exception log by branch against a branch that stopped taking applications in one ZIP and write the one fact that would move notices match the actual 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 / Pricing and Credit Limits packet (underwriting exception log by branch after a branch that stopped taking applications in one ZIP). The follow-on Pricing and Credit Limits action is what HMDA data-quality manager does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Fair Lending option on notices match the actual, then the evidence in underwriting exception log by branch, then the action for HMDA data-quality manager - Hypothesis scorecard against underwriting exception log by branch: supported / rejected / untestable - Regulatory or exam hook Pricing and Credit Limits would cite - Pricing and Credit Limits finding in underwriting exception log by branch that a second reviewer can re-perform