234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-031
Housing & real estate · United States · 2024 · Algorithmic discrimination

A Tenant-Screening Score Allegedly Shut Housing Voucher Holders Out of Homes

By Ellie Harris · Filed Application denied May 2021; suit filed May 2022

Alleged: SafeRent Solutions (formerly CoreLogic Rental Property Solutions) developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

A Tenant-Screening Score Allegedly Shut Housing Voucher Holders Out of Homes

What happened

It was reported that in May 2021, a woman in Massachusetts was denied an apartment after a tenant-screening system gave her a low score, despite having a government housing voucher that would have covered most of her rent.

The software, developed by SafeRent Solutions, helped landlords assess prospective tenants by producing a score based largely on factors such as credit history and debt. The problem, according to the lawsuit, was that the system did not adequately account for housing vouchers, which substantially reduce the amount of rent tenants need to pay themselves.

In May 2022, two women and a housing assistance organisation brought a class action against SafeRent, arguing that its scoring system unfairly disadvantaged Black and Hispanic applicants and people who relied on housing vouchers.

The case was settled in November 2024 for 2.275 million USD, without a court finding that the company had discriminated against applicants. Under the agreement, SafeRent also committed to stop providing scores or rental recommendations for housing voucher holders in Massachusetts for five years, unless its system was independently validated as non-discriminatory.

What an auditable version would have shown

The difficulty with automated tenant screening is that applicants may receive a rejection without understanding how the decision was reached or whether the same system consistently disadvantages people in similar circumstances.

An auditable system would have recorded which factors contributed to each score, how housing vouchers were considered and whether applicants receiving government assistance were rejected more frequently than those who did not need it.

Looking at these results across thousands of applications could help identify unfair patterns that would be almost impossible for an individual renter to recognise.

Where the gap was

Headlights identifies overconfidence, where organisations place too much faith in a scoring system without sufficiently questioning whether its assumptions reflect the circumstances of the people being assessed.

SafeRent’s software was designed to help landlords predict rental risk, but the plaintiffs argued that relying heavily on credit history while giving insufficient weight to housing vouchers could make applicants appear riskier than they actually were.

There is a familiar human tendency behind this kind of decision because numbers often create an impression of objectivity, particularly when they come from software designed to simplify complicated judgements.

A landlord looking at a low score might assume the applicant represents a financial risk, without realising that a government voucher could already guarantee a substantial portion of the rent.

The case illustrates how an apparently neutral scoring method can be challenged for producing unequal outcomes, even when discrimination is not an explicit part of its design.

What governance should have looked like

A system influencing whether someone can secure housing should be tested to understand how its recommendations affect different groups of applicants, particularly when the consequences of rejection can be significant.

A ConductRecord could document the factors used in each assessment, while a MetricRecord could measure whether rejection rates differed between voucher holders and other applicants, allowing potential disparities to be investigated before they became widespread.

Independent testing would also help establish whether the information used to calculate risk genuinely reflected a person’s ability to pay rent, rather than relying on assumptions that might disadvantage particular groups.

The broader lesson is that reducing a person to a number can make decisions easier for organisations, but it does not necessarily make those decisions fairer or more accurate.

Failure Pattern: SafeRent faced allegations that its tenant-screening system unfairly disadvantaged housing voucher holders and minority applicants, resulting in a 2.275 million USD settlement and restrictions on scoring voucher holders in Massachusetts.

Governance Principle: Automated screening systems should be tested for unequal outcomes, with transparent assessment criteria and independent validation where decisions affect access to essential services such as housing.

The reference implementation of ConductRecord and MetricRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and SafeRent Solutions (formerly CoreLogic Rental Property Solutions) could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →