What FCRA Adverse Action Requirements Must Your Tenant Screening App Meet

If your tenant screening app helps landlords evaluate rental applications using credit reports, criminal background checks, or eviction history, the Fair Credit Reporting Act (FCRA) requires you to implement adverse action notice workflows. These aren't optional features or nice-to-have compliance checkboxes. They're mandatory legal protections for applicants, and getting them wrong exposes both your users and your platform to federal liability.

An adverse action under FCRA occurs when a landlord denies a rental application, increases a deposit, or raises the rent based wholly or partly on information in a consumer report. When that happens, the landlord must send the applicant a specific notice with specific content within a specific timeframe, and your app needs to facilitate that process correctly.

What the FCRA Adverse Action Process Requires

The FCRA adverse action process has two distinct steps: pre-adverse action and final adverse action.

Pre-adverse action notice goes out before the landlord makes a final decision. This notice must include a copy of the consumer report that prompted the potential denial, a written notice explaining the applicant's rights, and contact information for the screening company that provided the report. The applicant then has a reasonable period, typically interpreted as at least five business days for mailed notices or at least five calendar days for electronic delivery, to dispute any inaccurate information in the report.

Final adverse action notice is sent after that waiting period if the landlord proceeds with the denial. This notice must state that the application was denied, identify the consumer reporting agency that provided the report (including name, address, and phone number), clarify that the screening company did not make the decision and cannot explain why it was made, and inform the applicant of their right to obtain a free copy of the report within 60 days and to dispute inaccurate information.

Required Information in Each Notice

Your app's adverse action workflow must capture and include specific data points in each notice type.

For the pre-adverse action notice, you need the applicant's name and contact information, a complete copy of the consumer report exactly as the landlord received it, the name and contact details of the consumer reporting agency, and a Summary of Rights document. The Consumer Financial Protection Bureau publishes the required Summary of Rights text, and it must be included verbatim.

For the final adverse action notice, you need the applicant's name and contact information, a clear statement that adverse action was taken (e.g., "Your rental application has been denied"), the name, address, and phone number of the consumer reporting agency that provided the report, a statement that the agency did not make the adverse decision and cannot provide specific reasons for it, notice of the applicant's right to dispute the report's accuracy, and notice of the right to request a free copy of the report within 60 days.

Timing and Delivery Requirements

Timing matters under FCRA. The pre-adverse action notice must go out before the final decision, and the applicant must have a reasonable opportunity to respond. While FCRA does not specify an exact number of days for the waiting period, the Federal Trade Commission's informal guidance and industry practice treat five business days for mailed notices or five calendar days for electronic notices as reasonable minimums.

Your app should not allow a landlord to send the final adverse action notice until that waiting period has elapsed. If an applicant disputes the report during the waiting period, the landlord must reconsider the application in light of any corrections from the screening company before proceeding.

The final adverse action notice must be sent promptly after the decision is made. While "promptly" is not defined with a specific day count in the statute, sending it within three business days of the final decision is standard practice and reduces compliance risk.

How Consumer Reporting Agency Relationships Affect Your App

If your app merely connects landlords to a third-party screening provider, your compliance obligations differ from those when you act as the consumer reporting agency yourself or resell reports under your own brand.

When you're a pass-through platform that directs users to an external screening service, the screening company typically remains responsible for providing the reports and much of the adverse action documentation. However, your app still needs to prompt landlords to complete the adverse action process and should provide workflow tools (templates, tracking, reminders) to help them comply. Many landlords do not understand FCRA requirements, and building the workflow into your app reduces their legal exposure and yours.

If your company obtains reports from data providers and furnishes them to landlords under your app's branding, you are likely acting as a consumer reporting agency under FCRA. That brings significantly broader obligations, including registration, reasonable procedures to ensure maximum possible accuracy, dispute handling, and direct liability for report content. In this scenario, your app must programmatically generate and deliver both adverse action notices with the required content, maintain records of delivery, and handle applicant disputes.

Electronic Delivery and Consent

FCRA permits electronic delivery of adverse action notices if the recipient has consented to receive them electronically in a manner that meets the E-SIGN Act requirements. Consent must be affirmative (not buried in a terms of service acceptance), and the applicant must be able to withdraw consent.

Your app should explicitly ask applicants during the authorization step whether they consent to electronic delivery of notices, including adverse action notices. If they decline or do not respond, default to requiring mailed notices. If they consent, deliver the notices to the email address they provided, log the delivery with a timestamp, and retain proof of consent.

Do not assume that applying online constitutes consent to electronic adverse action notices. Courts have found that assumption insufficient under E-SIGN.

What Happens When Landlords Skip the Process

FCRA violations carry statutory damages of $100 to $1,000 per violation, actual damages, punitive damages in cases of willful noncompliance, and attorney's fees for successful plaintiffs. A landlord who skips adverse action notices for dozens of applicants faces significant liability. So does a platform that enables or encourages that non-compliance by omitting the workflow or making it easy to bypass.

Even if your terms of service place compliance responsibility on the landlord, your app will likely be named in any lawsuit, and you will spend time and money defending your design choices. Building the adverse action process as a mandatory, not optional, step in your application workflow is both the right legal approach and a competitive feature, because it protects your users.

Implementation Checklist for Your Tenant Screening App

Before you ship adverse action functionality, confirm your app does the following: collects explicit written consent from applicants before ordering reports, triggers a pre-adverse action workflow when a landlord indicates intent to deny based on the report, includes the complete consumer report and Summary of Rights in the pre-adverse action notice, enforces a waiting period of at least five days before allowing final adverse action, generates a final adverse action notice with all required elements, logs timestamps for each notice sent, supports both electronic and mailed delivery based on applicant consent, and provides landlords with an audit trail showing compliance for each application.

If your app operates in multiple states, note that some states impose additional requirements beyond federal FCRA. California, for example, requires specific language in application denial notices, and New York City has additional disclosure rules for consumer reports. Your adverse action workflow should accommodate state-specific addenda.

References

• FCRA Background Checks: How to Comply When Screening Tenants - TurboTenant
• FCRA Adverse Action Letter for Tenant Screening - TurboTenant

Building compliant tenant screening workflows requires both technical implementation and a clear understanding of the regulatory landscape. If you're developing a proptech platform and need help designing FCRA-compliant features or integrating with consumer reporting agencies, Stardelite builds software for property technology companies navigating these requirements. Reach out through our contact page to discuss your project.