Assess whether to pause a product pending a lookback (bf39f9)

SITUATION A small-business desk using a new vendor score cannot treat an underwriter chat that used coded language as incidental context on underwriting exception log by branch. HMDA data-quality manager must close to pause a product from that extract under Fair Lending / Examination and Notices.

DECISION HMDA data-quality manager in a small-business desk using a new vendor score must choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold using underwriting exception log by branch after an underwriter chat that used coded language.

HYPOTHESES TO TEST 1. Authorize Remove access or reverse the item now; underwriting exception log by branch already has the discriminator after an underwriter chat that used coded language. 2. Keep Temporary compensating control in force until underwriting exception log by branch is completed after an underwriter chat that used coded language for HMDA data-quality manager. 3. Treat underwriting exception log by branch as Approve a documented exception because both readings appear after an underwriter chat that used coded language. 4. Refuse a Fair Lending close: HMDA data-quality manager does not have the decision to pause a product turns on in underwriting exception log by branch.

ANALYSIS REQUIRED 1. Test a documented exception versus a pattern a small-business desk using a new vendor score must defend. 2. Match the adverse-action language to the facts in underwriting exception log by branch. 3. Check HMDA coding and underwriting policy against to pause a product. 4. For this Fair Lending Examination and Notices file, read underwriting exception log by branch against an underwriter chat that used coded language and write the one fact that would move to pause a product 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 / Examination and Notices packet (underwriting exception log by branch after an underwriter chat that used coded language). The follow-on Examination and Notices 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 to pause a product, 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 - Named option among Remove access or reverse the item, Temporary compensating control, Approve a documented exception and the fact that kills the others - Owner and next date for HMDA data-quality manager in a small-business desk using a new vendor score