Guides
How to write a compliant adverse action notice
The five required elements
Under Regulation B (12 CFR Part 1002), a compliant adverse action notice must contain: (1) the name and address of the creditor; (2) a statement of the action taken; (3) the specific principal reasons for the action, or a disclosure of the applicant's right to request those reasons within 60 days; (4) the ECOA anti-discrimination tagline; and (5) if a consumer credit report factored into the decision, the FCRA supplemental disclosures identifying the consumer reporting agency used.
The most frequently cited deficiency in examinations is vague or generic reasons — phrases like 'insufficient creditworthiness' or 'did not meet our standards' are not specific enough. The reasons must accurately reflect the actual factors that drove the specific decision, listed in order of importance where multiple reasons apply.
Timing and process discipline
For applications that are complete, a creditor generally must provide the adverse action notice within 30 days of the application date. If the application was incomplete, different rules apply: the creditor may notify the applicant of incompleteness and provide 30 days from that notification. Counteroffers that are accepted or rejected on specific timelines follow their own track under Reg B.
A reliable process maps the notice workflow to the decision event — not the funding event or a later stage. Delays are a common exam finding. Recording the decision date, the notice-sent date, and the method of delivery in an auditable log provides the evidence needed to demonstrate timely compliance. That record should be retained with the application file.
How Hadrian supports the adverse action workflow
Hadrian records each case decision as an immutable event in the audit ledger, including the timestamp, the decision type, and the reasons captured by the operator. When a case is marked as denied, Hadrian enforces the adverse action clock and surfaces the notice-generation step as a required workflow action — ensuring the step is not skipped or delayed as volume increases.
Compliance with ECOA and Reg B is the operator's legal obligation; Hadrian does not verify that any notice is legally sufficient or that the reasons captured are accurate. Operators must review the content of every adverse action notice and should work with qualified compliance counsel to establish the reason codes and language their specific credit programs require.
FAQ
How to write a compliant adverse action notice — common questions
Can I use a template with checkboxes for the reasons?
Yes — Reg B permits using a check-box form listing common reasons, provided the selected reasons accurately reflect the specific decision. If none of the listed reasons apply, the creditor must provide the actual reasons. Pre-built templates do not remove the obligation to ensure the selected reasons are accurate for each file.
Does the requirement apply to business credit applications?
ECOA covers both consumer and business credit. Timing and some format requirements differ for business credit — for example, applicants with gross revenues over $1M may be notified of their right to request reasons rather than receiving them automatically. Confirm the applicable rules for your credit product with qualified counsel.
The institution around the intelligence
See Hadrian run your case lifecycle — intake to close, every decision audited.
Governance-native case processing for lenders and regulated teams.