Building A-du · Part Three: A-du Rent
Building A-du: Part Three
Chris Koss, AIA|Published: May 8, 2026
Last updated: September 25, 2026
When a screening doesn't pass, the part of the platform you'll hopefully never need. Denying a tenant under federal law takes a notice with specific contents, and a fair process adds a dispute window before the decision is final. A-du sends the first notice and runs the window for you.
The problem
Screening tenants is the easy part. Denying tenants is the hard part.
Under the Fair Credit Reporting Act, if a landlord declines an applicant in whole or in part because of information in a consumer report, the landlord has to send an adverse action notice. It names the consumer reporting agency, says the agency did not make the decision, and tells the applicant they can get a free copy of the report and dispute it. Federal law requires a warning notice before the decision only for employment screening, not rentals. A-du runs the fuller sequence on every decline anyway, because it gives an applicant a chance to fix a bad report first:
- Send the applicant a pre-adverse action notice that tells them they may be denied, names the screening agency whose report the decision was based on, tells them they can get a free copy of that report from the agency, and explains how to dispute it.
- Wait a reasonable amount of time for them to respond. A-du gives the applicant seven calendar days.
- If the applicant doesn't successfully dispute, close the window and hand the final decision back to the landlord.
The adverse action notice is the part the law requires, and getting its contents wrong is one of the easier ways for a landlord to end up in a Fair Credit Reporting Act lawsuit, not because anyone is trying to be unfair, but because the rules are specific and easy to forget. The waiting period is A-du's own fairness practice, and a practice only means something if it runs every time. Once we promise an applicant seven days, the window has to be honored. The notices have to go out, with the right contents, to the right people, at the right times. The applicant has to be told exactly where to get a free copy of the report and where to send a dispute. Withdrawals have to roll the process back.
None of that is something a landlord using a rental marketplace should be expected to track manually.
So we automated it.
What we built
When a screening result triggers a decline, a landlord on A-du clicks "deny." A few things happen behind the scenes.
First, a pre-adverse action notice goes out to the tenant by email, with a copy in their A-du inbox. It names the screening agency (RentPrep) with its address, phone number, and email, says the agency didn't make the decision, gives the date the dispute window closes, and links to the federal Summary of Rights. The tenant gets a clear path to a free copy of their report and to a dispute, both directly with the agency. The landlord doesn't have to draft anything; the notice is generated from the platform's templates.
Second, the platform starts a clock. The seven-day dispute window is tracked on a row in our database. A scheduled job runs every six hours and looks for pre-adverse rows whose dispute window has elapsed without the landlord withdrawing the denial. Each one is closed automatically, and the landlord gets an email and an in-app message saying the window has closed and the final decision is now theirs. Nobody has to remember to check a calendar. The schedule does it.
Third, the lifecycle is reversible. If a landlord changes their mind during the dispute window, for example because the applicant got an error in the report corrected, the landlord can roll the action back cleanly through a withdraw flow. Every state change leaves a durable record, and the next thing that happens reads from that record rather than guessing.
A small but real detail: we don't email the consumer report. That would scatter sensitive financial data across mail servers forever. We don't hand it out through A-du either. The applicant's free copy comes from the screening agency named in the notice, which is also where a dispute goes. Inside A-du, the full report opens only for the landlord who ordered it, and every step of the adverse action process is written to an audit log, along with a snapshot of each notice that went out.
What it means for you
If you're a landlord and a screening result doesn't pass, you don't have to know what the FCRA requires a denial notice to say. You click "deny," A-du sends the applicant a notice with the screening agency's contact details and the applicant's rights, and we run the dispute clock. The applicant takes any dispute to the screening agency directly. If you change your mind during those seven days, you can withdraw the denial from your dashboard. Otherwise, you'll hear from us when the window closes, and the final decision is yours.
If you're a tenant and you receive a pre-adverse notice from A-du, it tells you which screening agency supplied the report, how to reach them, and the date your dispute window closes. You have the right to a free copy of the report from that agency, and you dispute any errors directly with them. You don't have to guess who produced the report, or argue about it through email forwards.
Both sides get to live inside one workflow. Neither side has to become an FCRA expert.
What I learned
The thing I keep relearning on A-du is how much "automation" is really just disciplined record-keeping. The dispute clock is barely any code. The hard part is making sure every state change writes a durable row, every email writes its own log, every PDF is reachable through a permissioned link, and every withdrawal cleanly rolls back the right transitions. If any of those pieces is informal, an automated process is dangerous, because it'll act on incomplete state. If all of them are rigorous, the same automated process is harmless and useful.
A second lesson, more about voice than code: when a flow is legally important, write it with the field names you'd use in court, not the field names you'd use in a meeting. "Pre-adverse-sent-at" and "final-adverse-sent-at" are slightly more verbose than "sent-at" and "decided-at." They're also self-explaining to a future engineer who has never seen the FCRA dance, and to me six months from now when I have to debug a withdrawn action. Naming for future-you is part of the work.
A real moment of candor: this part of the platform is almost entirely invisible when it's working, and very visible when it isn't. Nobody sends me email saying "thank you for the well-formed pre-adverse notice." That's fine. The job here is to be quietly correct, every time, on behalf of landlords and tenants who deserve a fair process.
Next in the series: how A-du closes a deal. Generating an e-signed lease, and the addendum that has to sign before move-in.