For Real Estate Investors ·
What you'll accomplish
Collecting pay stubs, ID copies, and reference calls from every applicant by hand doesn't scale past a couple of vacancies, and it's easy to end up asking one applicant for more documentation than another without meaning to. TurboTenant runs your rental application intake and pulls credit, background, and eviction reports directly from the applicant, so every person you consider goes through the exact same process. By the end of this setup, you'll have an application live and know exactly how to order and read a screening report. The decision on who to approve stays yours. TurboTenant hands you the data. It doesn't make the call.
What you'll need
Do this before you open TurboTenant. Decide, on paper, the minimum credit score, income-to-rent ratio, and any other qualifying standards you'll apply to every applicant for this unit, and apply the same criteria to every applicant, every time. This single step is your strongest protection against a fair housing complaint, since a documented, consistently applied standard shows you rejected or approved someone based on the criteria, not on who they are.
What you should see: A short written document or note, specific enough that you could hand it to someone else and they'd apply it the same way you would. Troubleshooting: If your criteria are vague ("good credit," "stable income"), tighten them into numbers now. Vague criteria are the easiest to apply inconsistently without realizing it.
Go to turbotenant.com and sign up. TurboTenant's core software, listing, applications, and screening, is free for landlords, since the applicant typically pays the screening fee instead.
What you should see: A property listed in your dashboard with a status showing it's active and accepting applications. Troubleshooting: If you already have a prospective tenant and don't need the listing distributed publicly, you can still generate an application link to send directly to them.
Have the applicant fill out TurboTenant's online rental application before you request screening. It collects employment, income, and rental history details upfront, which gives you more context to weigh alongside the screening report itself.
What you should see: A completed application in your dashboard showing employment, income, and rental history the applicant entered themselves. Troubleshooting: An incomplete application is worth following up on before you move to screening. Missing rental history in particular is worth a direct question to the applicant.
Screening works in three steps, and notably, you never collect the applicant's Social Security number yourself. You enter their email or phone number, TurboTenant verifies their identity directly with them, and you're notified when the report is ready.
What you should see: A status change on the applicant's record from "screening requested" to "report ready," typically within a day or two, sometimes the same day. Troubleshooting: If an applicant's credit is frozen, the report can't pull until they lift the freeze with the credit bureau. That's a normal consumer protection step, not a red flag on its own.
The report includes a credit score and credit history, lines of credit, credit inquiries, debt in collections, a nationwide criminal background check, and an eviction check. Read it against the written criteria from Step 1, in that order, rather than forming an impression first and looking for facts to support it.
What you should see: A pass or fail against each individual criterion, not just a vague overall impression. Troubleshooting: If an applicant fails on one criterion but you're tempted to make an exception, apply the same exception standard to every applicant going forward, or don't make it at all. Inconsistent exceptions are exactly what creates fair housing exposure.
You make the accept or deny decision, based on the written criteria you set in Step 1, applied the same way to this applicant as to every other one for this unit. If you deny an applicant, raise the deposit, or add a co-signer requirement because of something in the screening report, federal law requires a prompt adverse action notice naming the reporting agency and telling the applicant they can get a free copy of their report and dispute anything inaccurate.
What you should see: A finalized decision recorded against the applicant, and if applicable, a sent adverse action notice. Troubleshooting: If you're ever unsure whether a decision needs an adverse action notice, the safer default is to send one. It costs you nothing and closes a real compliance gap if you skip it when required.
Screening reports and applicant data never belong in a chatbot prompt, full stop. Where a chatbot genuinely helps is drafting communications and thinking through your criteria, using no applicant-specific details.
Drafting your written selection criteria: "Help me draft written tenant selection criteria for a rental unit, covering minimum credit score, income-to-rent ratio, and eviction history lookback period, that I can apply consistently to every applicant. I want it specific enough to avoid ambiguity, and I'll review it for fair housing compliance separately."
Drafting a response to a qualified applicant: "Write a short, warm email to a rental applicant letting them know their application was approved and outlining next steps for lease signing, move-in date, and deposit. Keep it under 150 words."
Drafting an adverse action notice cover note: "Help me write a brief, professional cover note to accompany a required adverse action notice to a rental applicant whose application was denied based on their screening report. Keep it factual and courteous, no explanation of specific report details."
Use GPT-5.6 Sol or Sonnet 5 for any of these. Never paste an actual screening report, an applicant's name paired with financial detail, or their Social Security number into any of these prompts. The drafts above work fine with no applicant-specific information at all.