Community-development lender must resolve whether a redlining pattern exists

Situation

Pricing and Credit Limits work in a bank with thin HMDA LAR quality now turns on a redlining pattern exists because an underwriter chat that used coded language put model-reason-code mapping that does not match notices in play. Community-development lender should say what model-reason-code mapping that does not match notices proves.

Decision

Community-development lender in a bank with thin HMDA LAR quality 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 an underwriter chat that used coded language.

Hypotheses to test

• The population in model-reason-code mapping that does not match notices 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.
• The population in model-reason-code mapping that does not match notices is adjacent only to an underwriter chat that used coded language; Temporary compensating control is the honest Fair Lending call.
• A bank with thin HMDA LAR quality already contained an underwriter chat that used coded language before model-reason-code mapping that does not match notices arrived; no new Pricing and Credit Limits path.
• Provenance on model-reason-code mapping that does not match notices 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

• Test a documented exception versus a pattern a bank with thin HMDA LAR quality must defend.
• Match the adverse-action language to the facts in model-reason-code mapping that does not match notices.
• Check HMDA coding and underwriting policy against a redlining pattern exists.
• For this Fair Lending Pricing and Credit Limits file, read model-reason-code mapping that does not match notices against an underwriter chat that used coded language and write the one fact that would move a redlining pattern exists for community-development lender.

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 (model-reason-code mapping that does not match notices after an underwriter chat that used coded language). If model-reason-code mapping that does not match notices cannot force a Fair Lending label under Pricing and Credit Limits, stop. Do not invent pages a bank with thin HMDA LAR quality does not have.