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

SITUATION HMDA data-quality manager is responsible for line assignments have a in a credit-card issuer changing line-assignment logic, using model-reason-code mapping that does not match notices as the only working extract. A marketing mailer that skipped majority-minority tracts is what reset the timeline for this Fair Lending Redlining and HMDA Data file.

DECISION HMDA data-quality manager in a credit-card issuer changing line-assignment logic 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 marketing mailer that skipped majority-minority tracts.

HYPOTHESES TO TEST 1. A marketing mailer that skipped majority-minority tracts is noise around an already-controlled Redlining and HMDA Data process in a credit-card issuer changing line-assignment logic, given model-reason-code mapping that does not match notices. 2. A marketing mailer that skipped majority-minority tracts is the event in model-reason-code mapping that does not match notices that forces Remove access or reverse the item for HMDA data-quality manager under Fair Lending. 3. Model-reason-code mapping that does not match notices shows a one-file miss after a marketing mailer that skipped majority-minority tracts, not a Redlining and HMDA Data program failure. 4. Model-reason-code mapping that does not match notices cannot decide line assignments have a yet after a marketing mailer that skipped majority-minority tracts; hold is the only Fair Lending close a credit-card issuer changing line-assignment logic can defend.

ANALYSIS REQUIRED 1. Flag any disparate-impact table HMDA data-quality manager cannot explain from model-reason-code mapping that does not match notices. 2. Test a documented exception versus a pattern a credit-card issuer changing line-assignment logic must defend. 3. Match the adverse-action language to the facts in model-reason-code mapping that does not match notices. 4. For this Fair Lending Redlining and HMDA Data file, read model-reason-code mapping that does not match notices against a marketing mailer that skipped majority-minority tracts and write the one fact that would move line assignments have a 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 / Redlining and HMDA Data packet (model-reason-code mapping that does not match notices after a marketing mailer that skipped majority-minority tracts). Lead with the Fair Lending option model-reason-code mapping that does not match notices can support after a marketing mailer that skipped majority-minority tracts, 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.