Skip to content

Domain Atlas

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

Predictive

Ranked 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

Predictive

Vulnerability 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

Predictive

Cross-department data integration that flags residents as at risk of homelessness months ahead, for preventive contact by local government.

Benefits-navigation copilots

Generative

Generative 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

Predictive

City-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

Predictive

Vendor 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

Predictive

Revenue-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.

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 →

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. 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. 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. 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. 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