An AI leasing assistant should be reviewed as part of the housing provider's actual process, including the information it uses, the questions it asks and the actions it can take. A vendor saying its model is trained to be fair does not establish that a particular workflow is appropriate.
This is an operational vendor-review checklist, not legal advice or a compliance certification. Use it with qualified counsel or your compliance lead, who can assess the rules and circumstances applicable to your properties. It focuses on U.S. leasing and does not replace a jurisdiction-specific review.
Start with the legal context and the workflow
The Department of Justice's Fair Housing Act overview, linked below, describes federal protections involving race, color, religion, sex, national origin, familial status and disability. It also discusses discriminatory availability statements and steering. Your review should consider the actual answers and choices presented to prospects, not just whether certain words are blocked.
Separate routine information and scheduling from screening or eligibility decisions. Ask the vendor to show every point where the system ranks, routes, excludes or treats an enquiry differently. Have the responsible reviewer assess both the rule and the information used to apply it.
Test information and treatment with controlled examples
- Availability: give equivalent fictional enquiries the same current inventory and compare the options offered. Investigate unexplained differences.
- Unsupported questions: ask about a detail missing from the approved material. The assistant should acknowledge the gap and use the review route.
- Personal details: introduce irrelevant personal information into an otherwise identical enquiry. Check that it does not alter the service or options without an approved, lawful basis.
- Requests for help: test different wording for a request to speak with a person or obtain assistance. Check that the workflow remains accessible.
- Changed instructions: update a property policy and repeat the test to verify which information the assistant actually uses.
These tests are proposed review methods, not proof of compliance. Preserve the test inputs, outputs and configuration so the reviewer can reproduce a failure and verify a correction.
Give accommodation requests a real review path
HUD and DOJ's joint guidance explains that reasonable accommodations can involve changes to rules, policies, practices or services. It also explains that treating everyone identically can sometimes deny a person with a disability equal opportunity. A simple instruction to apply every policy the same way is therefore not a complete accommodation process.
Design the assistant's role around receiving the request and reaching the designated reviewer. Have that reviewer approve what information may be collected and what the customer should be told. A generic policy response should not automatically reject or close the request. Do not require the customer to use one exact phrase before the workflow recognises that help may be needed.
Review communications separately
Calls, texts and follow-up campaigns also need their own review. Document the purpose of the communication, the technology used, the evidence of consent where required and how stop requests are handled. Have counsel verify the applicable requirements instead of applying a blanket statement that every outbound message has the same legal basis.
The FCC resource below provides official information about unwanted calls and texts. Use current legal advice for the specific campaign and channel, including any relevant state requirements, rather than treating a general article as a complete implementation specification.
Ask for evidence and ownership
Request approved response sources, permission boundaries, escalation records and a process for investigating complaints. Review logs with appropriate access and retention controls. Name the people who can pause the workflow, correct information and verify a fix before it resumes.
Security assurance and housing compliance answer different questions. Review security documentation, but do not treat a SOC 2 report or a partnership badge as proof that a particular leasing conversation meets legal requirements. The final review must cover the configured workflow and the people responsible for operating it.