Assess whether the CRA plan is strategy or window dressing (177a54)

SITUATION A HMDA resubmission that still fails quality edits put model-reason-code mapping that does not match notices in front of HMDA data-quality manager in a credit-card issuer changing line-assignment logic. This Fair Lending / Redlining and HMDA Data decision is the CRA plan is from model-reason-code mapping that does not match notices, and the live options are The CRA plan is strategy, Window dressing.

DECISION HMDA data-quality manager in a credit-card issuer changing line-assignment logic must choose The CRA plan is strategy / Window dressing using model-reason-code mapping that does not match notices after a HMDA resubmission that still fails quality edits.

HYPOTHESES TO TEST 1. The population in model-reason-code mapping that does not match notices is the one a HMDA resubmission that still fails quality edits named, so The CRA plan is strategy follows for this Redlining and HMDA Data file. 2. The population in model-reason-code mapping that does not match notices is adjacent only to a HMDA resubmission that still fails quality edits; Window dressing is the honest Fair Lending call. 3. A credit-card issuer changing line-assignment logic already contained a HMDA resubmission that still fails quality edits before model-reason-code mapping that does not match notices arrived; no new Redlining and HMDA Data path. 4. Provenance on model-reason-code mapping that does not match notices after a HMDA resubmission that still fails quality edits is broken; do not pick The CRA plan is strategy or Window dressing yet.

ANALYSIS REQUIRED 1. Test a documented exception versus a pattern a credit-card issuer changing line-assignment logic 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 the CRA plan is. 4. For this Fair Lending Redlining and HMDA Data file, read model-reason-code mapping that does not match notices against a HMDA resubmission that still fails quality edits and write the one fact that would move the CRA plan is for HMDA data-quality manager.

RECOMMENDATION Choose The CRA plan is strategy / Window dressing on this Fair Lending / Redlining and HMDA Data packet (model-reason-code mapping that does not match notices after a HMDA resubmission that still fails quality edits). Lead with the Fair Lending option model-reason-code mapping that does not match notices can support after a HMDA resubmission that still fails quality edits, then the two facts that force it, then the Monday action for HMDA data-quality manager in a credit-card issuer changing line-assignment logic.

COMMAND RETURNS - Bottom-line Fair Lending option on the CRA plan is, then the evidence in model-reason-code mapping that does not match notices, then the action for HMDA data-quality manager - Hypothesis scorecard against model-reason-code mapping that does not match notices: supported / rejected / untestable - What changes the CRA plan is if a HMDA resubmission that still fails quality edits is later withdrawn - Named option among The CRA plan is strategy, Window dressing and the fact that kills the others