Building A-du · Part Three: A-du Rent
Building A-du: Part Three
Chris Koss, AIA|Published May 8, 2026|Last updated May 29, 2026
When a screening doesn't pass, the part of the platform you'll hopefully never need. Denying a tenant under federal law is a sequence of steps that has to happen in a specific order, on a specific clock. A-du does it 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 do a specific, ordered sequence of things:
- Send the applicant a pre-adverse action notice that tells them they may be denied, gives them a copy of the report the decision was based on, 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, send a final adverse action notice confirming the decision and pointing the applicant at the consumer reporting agency.
That dance 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 dispute window has to be honored. The right notices have to go out, with the right contents, to the right people, at the right times. The report has to be available when the applicant asks for it. Disputes have to be tracked. 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 the right legal contents, including a secure link they can use to pull up a copy of the consumer report we relied on. The tenant gets a clear path to dispute or supply explanation. The landlord doesn't have to draft anything; the notice is generated from the platform's templates with the specific report and decision attached.
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 a successful dispute or a withdrawal. Each one gets escalated automatically to final adverse action. There is no "oops, I forgot to send the final notice" failure mode on A-du Rent. The schedule sends it.
Third, the lifecycle is reversible. If a landlord changes their mind during the dispute window, or if the applicant disputes successfully, the platform 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 PDF directly. That would scatter sensitive financial data across mail servers forever. The notice contains a secure, time-limited link that the applicant uses to fetch the report through the platform, with access counted against the screening request so there's an audit trail.
What it means for you
If you're a landlord and a screening result doesn't pass, you don't have to know what an FCRA pre-adverse notice looks like. You click "deny," A-du sends the right notice with the right contents, and we run the dispute clock. If the applicant disputes, you'll see it in your dashboard. If they don't, the final notice goes out at the right time, on its own.
If you're a tenant and you receive a pre-adverse notice from A-du, you can read the consumer report we relied on directly through a link in the email, and you have an explicit dispute path. You don't have to call a phone tree to find out what the report said, 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.