Housing & homelessness services
Prioritization and prevention scores deciding who reaches scarce housing help first — where a more accurate model can still leave the same people under-served, and the quietest harm is often the person the system never surfaced.
Use cases
What AI is doing here
Homelessness-prevention targeting
PredictiveRanked outreach lists estimating who is at highest risk of becoming (or becoming chronically) homeless, so scarce prevention help can be offered before a crisis.
Coordinated-entry prioritization scoring
PredictiveVulnerability and risk scores that rank people for scarce housing and services at the front door of a coordinated-entry system — where an advisory aid can harden into the de facto decision.
Council early-warning flagging
PredictiveCross-department data integration that flags residents as at risk of homelessness months ahead, for preventive contact by local government.
Benefits-navigation copilots
GenerativeGenerative assistants helping caseworkers navigate housing and benefit programs on a client's behalf — distinct from the public-facing chatbots in the benefits-navigation domain.
Street-population sensing & record linkage
PredictiveCity-scale sensing of unsheltered populations — camera-based encampment detection and cross-agency record linkage into a consolidated street-population picture — where the governed questions are the consolidation itself, who may read it, and what enforcement sits downstream.
Tenant screening & record matching
PredictiveVendor screening products at the rental front door — composite lease-risk scores over credit and eviction data, and criminal-record matching engines returning flags against landlord-configured criteria — where the vendor holds the model and the record store and the landlord holds the formal decision.
Algorithmic rent setting
PredictiveRevenue-management software recommending unit-level rents to competing landlords from pooled nonpublic lease data — no person is scored and no application is decided; the governed object is the shared data substrate and the coordination it enables.
Case files
What has gone wrong and right
Documented deployments, presented as model organizations calibrated to the evidence, with full citations.
Allegheny Housing Assessment
Allegheny County, Pennsylvania, USAA warehouse-data risk score replaced a self-report homelessness survey and got far more accurate — yet a peer-reviewed evaluation found it did not close the racial gap in who actually gets scarce housing.
Explore this deployment in the PAN Lab →VI-SPDAT
United States (multi-state; at least 39 states and the District of Columbia by 2015)A self-report homelessness triage questionnaire became the U.S. coordinated-entry standard across dozens of states without validation — then its own creators retired it in 2020 on equity grounds, after commissioned research found it systematically under-scored people of color.
Explore this deployment in the PAN Lab →LA County Homelessness Prevention Unit
Los Angeles County, California, USAA predictive model that reaches single adults before they lose housing — offering cash and help, never a denial — where the error that matters is the majority it misses, and even the headline 71% result is associational until a 2027 trial.
Explore this deployment in the PAN Lab →Xantura OneView (predictive homelessness flagging)
England, United KingdomA vendor 'single view' that flags residents likely to become homeless months ahead — where the model's real reach is set by how many alerts one officer can act on, and the marquee figures are vendor pre/post numbers a randomised trial was still testing.
Explore this deployment in the PAN Lab →CHAI (chronic-homelessness prediction)
London, Ontario, CanadaA city-built, caseworker-facing model that flags shelter clients at risk of chronic homelessness about six months out — consent-based, open-source and explainable by design, yet resting on a testing-phase accuracy figure no one re-validated after deployment and a shelter-only data frame that cannot see the people who never come through a public shelter door.
Explore this deployment in the PAN Lab →Imagine LA Benefit Navigator copilot
Los Angeles County, California, USAA generative benefits-navigation copilot whose evaluated accuracy gains land hardest on the newest staff and the toughest questions — where the built-in citation check is easiest to skip — in a vendor-and-academic-co-authored 2025 Los Angeles County pilot.
Explore this deployment in the PAN Lab →London's Strategic Insights Tool: one linked memory of rough sleeping read by every borough
Greater London, United Kingdom (all 33 London local authorities — 32 boroughs plus the City of London — with the pan-London bodies GLA and London Councils)A pan-London service that probabilistically links three separately governed record systems — street-outreach contacts, charity casework, and borough statutory applications — into a single rough-sleeping journey per person, read across all 33 London local authorities. It makes no individual-level decisions: its documented weakness is a self-reported 91% recall, meaning roughly 9 in 100 true cross-system matches are missed, an undercount its own DPIA concedes propagates into the figures every borough sees at once. The atlas's memory-consolidation case: the lesson is what happens when many independent readers consolidate onto one shared layer whose known error is never reconciled.
Explore this deployment in the PAN Lab →San Jose's camera car: a low-precision detector aimed at who is sleeping outside
San Jose, California, United States (Phase One data collection confined to City Council District 10)San Jose mounted cameras on a sedan - its "camera car" - and drove one district, training vendor AI to detect potholes and trash — and, in the same pilot, RVs, lived-in vehicles, and homeless encampments. Described by city officials and housing advocates as the first US experiment training AI to recognize tents and lived-in vehicles, it was accurate on infrastructure (97% on potholes) and badly inaccurate on habitation (12.5% on lived-in vehicles). No detection ever drove an operation: the response loop was never wired. The atlas's declared-rule-versus-feasible-flow case — the data policy forbade active law-enforcement use while preserving a police request path to the footage, and a vendor read license plates the policy said it would not, before the city removed every habitation class and declined to recommend deployment.
Explore this deployment in the PAN Lab →LA's coordinated-entry triage revision: the fix that needed fixing
Los Angeles Continuum of Care (Los Angeles County, California, USA) — the single-adult system of the Los Angeles Coordinated Entry System, the largest Continuum of Care in the United StatesThe largest homeless-services system in the U.S. replaced a discredited triage survey with a fairer, regression-derived score — then watched the retired bias walk back in during the transition. Because the old and new instruments ran in parallel at mismatched eligibility thresholds, a client was likelier to qualify for housing under the OLD biased tool, so frontline workers kept administering it. The atlas's judge-replacement-transition case: the lesson is that swapping a biased score is a governance problem in the handover, not just a modeling problem in the tool.
Explore this deployment in the PAN Lab →Santa Clara County Homelessness Prevention System
Santa Clara County, California, USA (national replication to about ten US jurisdictions, 2026 to 2031)A homelessness-prevention program whose targeting runs on a transparent points-based intake questionnaire, not a machine-learning model, and whose intervention - flexible emergency financial assistance - is one of the few in the Atlas backed by a published randomized controlled trial. The domain's positive counterexample: the lever is measured and effective, and the open question is not whether to trust the model but whether the screen reaches the right people on a base rate where most at-risk applicants would have stayed housed anyway - a question the same program is now testing across ten new jurisdictions at once.
Explore this deployment in the PAN Lab →Calgary Drop-In Centre: interpretable screening a shelter's own staff choose to check
Calgary, Alberta, Canada (NGO shelter operator; research partner University of Calgary; data provided in part by Alberta Seniors, Community and Social Services)A Calgary shelter and University of Calgary engineers built deliberately simple, interpretable screening for chronic shelter use — explicit rules like "81+ stays in 90 days" that flag risk months earlier than the official definitions — and then, instead of a score, gave frontline staff an interface that shows the raw client history and lets them read it. They studied their own staff for two and a half years and found the deference calibrated (whether a score of, say, 30% really does mean thirty cases in a hundred) to the stakes: staff read everything for high-stakes barring decisions, treating the data as "the canvas," but leaned on it more for lower-stakes triage. The atlas's directly observed deference case: the lesson is that vigilance can be designed into a tool's form — and that the residual risk then migrates to the low-stakes tail of that deference and to the records the staff themselves author.
Explore this deployment in the PAN Lab →SafeRent Tenant Screening Score
United States — D. Mass. (No. 1:22-cv-10800-AK); screening product sold nationwide, classes and litigation centered on MassachusettsA tenant-screening vendor turned an applicant's credit and eviction file into a 200-800 number and an accept or decline recommendation, while the leasing desk that signed the lease wrote that it could not override the outcome — and a federal settlement responded not by fixing the model but by switching its output off for housing-voucher applicants for five years, with a civil-rights organization holding the only key back in.
Explore this deployment in the PAN Lab →One engine, many rivals: a shared rent-setting model and the record it writes back
United States — federal civil antitrust in the Middle District of North Carolina (United States and Plaintiff States v. RealPage, Inc.), ten plaintiff states, a parallel private multidistrict litigation in the Middle District of Tennessee (docket 3071), per-landlord state consent decrees, at least nine city ordinances, and first-in-nation state statutes in California (AB 325) and New York (A1417B / S.7882)Competing landlords fed RealPage's revenue-management pricing engine their nonpublic lease data — executed rents, renewal rates, terms, occupancy — and the engine recommended daily rents back to all of them. The 2024 federal antitrust complaint alleges roughly 80% of the commercial revenue-management software market and data agreements reaching over 16 million units, including units of landlords who were not customers. The loop is the case: accepted recommendations became executed-lease records in the shared dataset, which shaped the next day's recommendations for every participating rival, while a price-movement band was alleged to damp decreases harder than increases and an automatic setting executed with no human review at all. The remedy is topological rather than accuracy-based — nobody audited whether the prices were right. The proposed decree stales the shared memory to a twelve-month floor, bars sub-state geographic modelling, re-symmetrises the band, turns automatic acceptance off by default, bans vendor-hosted meetings of competitors, and appoints a monitor for three years. Nothing is adjudicated: no admissions, no fine, and final entry was still pending in mid-2026.
Explore this deployment in the PAN Lab →Homebase Risk Assessment Questionnaire
United States — New York City (Department of Social Services / Human Resources Administration; statutory algorithmic-tool register under Local Law 35 of 2022, Admin. Code sec. 3-119.5)New York City routes families toward or away from full homelessness-prevention services on fifteen questions and a point total — and it is the rare targeting instrument bolted into a statutory public self-reporting loop, so the city has had to describe the tool in a public register four years running, including a mid-cycle amendment disclosing its 2023 revision, while the agency's own research office peer-review-published both the screener's accuracy and its distortions: caseworkers' totals piling up at exactly the eligibility cutoff, and supervisor-approved overrides that misjudged risk in both directions.
Explore this deployment in the PAN Lab →CrimSAFE criminal-record tenant screening
United States — D. Conn. and the Second Circuit (Nos. 23-1118(L), 23-1166(XAP)); the denial occurred in Windham, Connecticut, and the criminal-records store spans more than 800 US jurisdictionsA rental application was denied on a flag that said only that a disqualifying record existed — the record was a pending shoplifting charge later withdrawn, the on-site agent had been configured out of seeing it, and the company holding it never completed the file disclosure the law provides. Eight years of litigation ended with a court-certified map of who decides what in automated tenant screening, and with the vendor owing nothing.
Explore this deployment in the PAN Lab →System map
Who is in the system and what pushes on it
Who is in the system
- Frontline workers. Caseworkers, screeners, eligibility staff — the operator network whose judgment the system augments or erodes.
- Supervisors & QA. The institutional correction layer: overrides, second reads, quality review.
- Agency leadership. Owns procurement, policy, and the authority map; answers for the system publicly.
- Served people & families. Those the decisions land on. Deliberately outside the PAN dynamics — their outcomes are measured, never simulated.
- Vendors. Build and update the systems; hold the information asymmetry procurement must govern.
- Regulators & oversight bodies. Boards, auditors, data-protection officers, inspectorates — external correction capacity.
- Advocates & community organizations. Surface harms institutions do not see; historically the earliest accurate signal.
Dominant pressures
- Caseload surge. Demand outruns staffing; per-case attention shrinks and review becomes triage.
- Austerity & recovery incentives. Cost-cutting and overpayment-recovery targets tilt the system toward denial and enforcement errors.
- Vendor opacity. The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
- Data & policy drift. The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
- Compliance over substance. Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.
Governance
Questions leaders should be asking
- 1. When a sharper model replaces an older triage score, does anyone verify the disparity in who actually gets housed shrank — or is a higher accuracy number treated as the end of the equity question?
- 2. Which of the accuracy numbers justifying this system come from the builder's own testing, and which from an evaluation the institution could independently inspect and reproduce?
- 3. For a system that offers scarce help rather than denies it, who counts the people it never surfaced — and is that miss rate as visible to leadership as the success stories?
- 4. Is the score advisory or decisive in practice — and does anyone track how often a worker departs from it, or who never entered the data to be scored at all?
For the actions behind these questions, see the Practice Library.
Seeing your organization in this domain? Mapping its actual pathways, pressures, and correction capacity is engagement work.
Work With Paramerge