uniteTOlove.ca

Social Housing Waitlist Data — Playbook

Toronto's subsidized-housing waitlist number gets quoted constantly — what it actually counts, and what it leaves out.

DRAFTThe playbookThe evidence file

v2.0 · 2026-08-11

---

The honest bottom line

Whether the lottery/portal reform is actually running today, or still on paper, is unconfirmed — flagged, not guessed at. Whether "Access to Housing" and its older name, "Housing Connections," name the same function is unresolved from secondary sources alone. Neither recommendation below is costed beyond an order-of-magnitude range anchored to a comparator, not a program-specific dollar figure, and no current funding program was confirmed as the actual target of the second recommendation's reporting condition.

---

a recommendation card — Standardized, Machine-Readable Quarterly Waitlist Reporting

Card id: a recommendation card · Issue: social-housing-waitlist-data · Backgrounder: our research file for that page · Trust: New load-bearing findings (built from this review's direct primary-source fetch)

Problem

The City's own centralized-waitlist reporting has changed its counting rules at least twice in recent years — a 2026 revision that moved reactivated applications into the Total Active Waiting List and renamed "Cancelled Applications" to "Removed from Waiting List," on top of the pre-existing "New/reactivated" combined line used through 2024 (backgrounder, "What the number counts, and what it does not," Trap 2). Combined with a widely repeated press description of the figure as counting "people" when the City's own table defines it as households/applications (backgrounder, Trap 1), this produces exactly the kind of terminology confusion documented at length in this page’s own carried-forward sources (this library's prior synthesis document (Social Housing Waitlist Data)) — a document whose entire reason for existing was untangling a mislabeled figure that had already propagated into at least six other library documents. The report is published as an HTML page with year-tabbed tables and footnoted methodology changes, not as a structured dataset a journalist, researcher, or councillor's office could pull programmatically and diff against prior quarters.

Action

The City publishes the Social Housing Waiting List Reports as a versioned, machine-readable dataset (CSV/JSON via the Toronto Open Data portal) alongside the existing HTML page, with (a) a fixed, explicitly documented unit for every column (households/applications, never "people," unless a genuine person-count field is added separately), and (b) every methodology change (like the 2026 reactivated-applications revision) recorded as a dataset-level changelog entry with an effective-quarter tag, rather than only as a footnote on the current year's table.

Jurisdiction split

Cost

Order-of-magnitude: low-to-mid five figures CAD as a one-time build cost, anchored to the City's own general practice of publishing existing internal reporting datasets through its Open Data portal (e.g., the Shelter System Flow Data and Daily Shelter & Overnight Service Usage series already listed alongside this waitlist report on the same City reports index) — this is a data-publishing exercise on figures the City already compiles quarterly for its own HTML page, not a new data-collection program, so the marginal cost is closer to "publish what you already have" than "build a new system." No independent third-party unit-cost source was found for this specific dataset; the range is anchored to the comparator of the City's existing, already-running Open Data housing/shelter series rather than to a cited dollar figure.

Funding path

Existing Toronto Open Data / Housing Secretariat operating budget — this is a publishing-format change to data the City already produces, not a new program requiring a new funding line.

Who benefits, and how

Researchers, journalists, and council offices, via the ability to diff quarter-over-quarter figures and detect methodology seams (like the 2026 reactivation change) at the moment they occur rather than reconstructing them after the fact, as this page’s own carried-forward documents had to do across several past library documents [This library's prior synthesis document (..) Part 3's propagation-fix table]. Applicants and advocacy organizations, via a public, versioned record of exactly what "on the waiting list" has meant at each point in time.

Who bears the cost, and how

City taxpayers city-wide, via the Open Data/Housing Secretariat operating budget; City staff, via the one-time work of formatting and documenting the changelog (an opportunity cost against other reporting-team priorities).

Who benefits from the status quo

No beneficiary identified in the backing backgrounder's Cui Bono table — social-housing-waitlist-data.md's Cui Bono section reports 0 ESTABLISHED/REPORTED entities, since this page’s subject (waitlist measurement/reporting integrity) is not a contracted-service or procurement relationship.

Financial ROI

No direct fiscal-savings case is asserted here — this is a transparency/data-quality action, not a service-delivery change. Indirect cost avoidance is plausible (fewer future corrections needed across derivative documents, as happened in this page’s own history) but not quantified; flagged as directional only, not costed.

Economic ROI

Not directly modeled for this specific dataset-publication action; genuinely broad open-government-data economic literature exists but is not sized to this narrow a scope. Research commissioned by the UK's Open Data Institute finds open public-sector data assets generate roughly 0.5% of GDP more economic value per year than closed/paid equivalents, and San Francisco is reported to have saved roughly USD 1 million per year after opening real-time transit data (Open Data Institute, "The economic value of open versus paid data" — https://theodi.org/insights/reports/research-the-economic-value-of-open-versus-paid-data/; San Francisco transit example via secondary open-data-outcomes literature, original SFMTA source not independently re-verified this review) — both real, named examples of open-data value, but neither prices a single housing-waitlist dataset conversion specifically, and both are macro or single-case examples from other data domains (transit operations, national-level GDP effects), not social-housing waitlist reporting, so not adopted as a sized estimate for this card. Confidence: low — this remains closer to "not yet estimable" than a genuine range.

Social ROI

Directly traceable to a documented failure mode in this page’s own evidence base: a terminology error (households mislabeled as "people") propagated across at least six prior library documents before being caught and corrected [This library's prior synthesis document (..) Part 3]. Structured, versioned publication with explicit units and a changelog is a direct mitigation for exactly that failure mode recurring elsewhere (news coverage, advocacy materials, other researchers' work), for the same population of downstream readers.

Environmental ROI

Genuinely environmentally neutral. This is a data-publication-format change to figures the City already compiles — it has no construction, land-use, or physical-infrastructure component and therefore no direct emissions, land-use, water, or waste footprint. The marginal server/hosting footprint of an additional Open Data portal dataset is not separately quantified by any source located this review but is negligible relative to any action in this page’s other cards. Confidence: high.

Evidence

Confidence & uncertainties

Medium-high confidence in the problem statement (directly evidenced by this page’s own documented terminology-error history); lower confidence in the specific cost estimate, which is anchored to a general comparator (the City's existing Open Data housing/shelter series) rather than a cited unit cost for this specific dataset. No named Open Data program manager or existing City commitment to do this was found this review — this is a card proposing an action, not describing one already underway.

Status

DRAFT — blocked on: fairness and legal review; a second, independently sourced cost comparator; confirmation of whether Toronto Open Data already has an intake process for exactly this kind of dataset-conversion request.

---

a recommendation card — Tie Provincial/Federal RGI Supply-Expansion Funding to Waitlist Throughput, Not Just Unit Counts

Card id: a recommendation card · Issue: social-housing-waitlist-data · Backgrounder: our research file for that page · Trust: carried-forward (cost/throughput facts) + New load-bearing findings (2019 vacancy-loss figures)

Problem

Toronto's centralized RGI waitlist grew from 81,664 to 105,115 households between 2020 and 2025 (+29%), while 2025 saw 21,538 new applications against only 2,838 households actually housed — an inflow-to-housed ratio of roughly 7.6 to 1 and a 2.7% annual exit-to-housing rate [carried-forward, backgrounder "Comparison to the supply pipeline"]. Separately, the City's own 2019 Auditor General report found housing-unit underuse was itself part of the bottleneck, independent of new-unit supply: "$7 million in vacancy losses" and an estimated 2,200 additional people housable through better use of already-existing stock, without building a single new unit [Toronto Auditor General, "Opening Doors to Stable Housing," June 21 2019, fetched 2026-07-13]. This card addresses the specific gap between "units funded/built" and "people actually moved off the list," not the general housing-supply-affordability question this page hands off elsewhere.

Action

Any new provincial or federal capital/operating funding commitment tied to RGI/social-housing supply expansion in Toronto includes a throughput reporting requirement — the funded program must publish its contribution to the City's own existing "Housed" quarterly metric (already tracked and published, per the backgrounder) and its effect, if any, on existing vacancy/turnover inefficiencies like those the 2019 Auditor General report identified — rather than being reported solely as a unit-count or dollar-committed figure with no link back to the waitlist's own throughput data.

Jurisdiction split

Cost

No new capital cost is proposed by this card itself — it is a reporting-linkage condition attached to funding decisions that would occur regardless. The administrative cost of adding a throughput-reporting requirement is order-of-magnitude low (a reporting-template addition to existing funding-agreement administration), anchored to the same comparator as Card 1: the City already tracks and publishes the "Housed" metric quarterly, so the marginal cost is attribution/tagging, not new data collection.

Funding path

No new funding mechanism required for the reporting condition itself; it would be attached as a term within whatever provincial/federal capital or operating funding path is already being used or negotiated for RGI supply expansion in Toronto (funding path for the underlying supply expansion itself is out of scope for this card — see housing-supply-affordability).

Who benefits, and how

Applicants on the centralized waitlist, via funding decisions that can be evaluated against whether they actually move people into housing (the metric this page’s evidence shows is currently growing far more slowly than the list itself), not just against how many units were nominally funded. Council and oversight bodies (the City's own Auditor General has already done exactly this kind of throughput/vacancy analysis once, in 2019), via a standing reporting linkage rather than a one-off audit.

Who bears the cost, and how

Funding-program administrators (provincial and federal), via the modest added administrative burden of throughput-linked reporting; City staff, via the work of attributing "Housed" outcomes to specific funding sources where more than one program contributes to the same building or intake.

Who benefits from the status quo

No beneficiary identified in the backing backgrounder's Cui Bono table — social-housing-waitlist-data.md's Cui Bono section reports 0 ESTABLISHED/REPORTED entities relevant to funding-throughput reporting conditions specifically.

Financial ROI

Not separately costed here — this card does not itself spend money, it conditions reporting on money already being spent or proposed. Indirect fiscal case: the 2019 Auditor General finding that a 50% improvement in unit-utilization would house 2,200 more people without new construction cost implies real cost-avoidance potential if throughput-linked reporting surfaces similar utilization gaps in newly funded supply — but this is not independently modeled or quantified for present-day dollar terms, flagged as directional only.

Economic ROI

Not directly modeled — this card conditions reporting attached to funding decisions that occur regardless; it does not itself allocate capital, so it has no first-order local-spending or employment effect distinct from whatever underlying supply-expansion funding it attaches to (explicitly out of scope, per Funding path above). The indirect economic case rests on the 2019 Auditor General finding, cited in this card's own Problem section, that improved unit-utilization could house an estimated 2,200 additional people without new construction — a real, City-sourced figure, but one describing a utilization-efficiency gain, not an economic-growth/employment multiplier, and not independently re-modeled here for a dollar figure. Comparator: the card's own already-cited Toronto Auditor General 2019 report, "Opening Doors to Stable Housing" (June 21, 2019), used only as evidence of a utilization-efficiency gap, not as an economic-impact study; no third-party economic-impact study of throughput-linked funding conditions was located this review, and this is a genuinely novel proposed mechanism per this card's own Confidence & uncertainties section. Confidence: low — stated as not yet estimable rather than inferred from the utilization figure.

Social ROI

The 7.6:1 inflow-to-housed ratio and 2.7% annual exit rate [From this library’s earlier research] describe a system where the number of new units funded is not, by itself, informative about how much faster people actually get housed. Throughput-linked reporting is the mechanism by which that gap becomes visible to the public and to Council on an ongoing basis, rather than requiring a dedicated Auditor General special report (as happened once, in 2019) to surface it.

Environmental ROI

Genuinely environmentally neutral for the reporting-condition mechanism itself. This card attaches a reporting requirement to funding decisions rather than making a capital or construction decision itself — it has no direct emissions, land-use, water, or waste footprint of its own, distinct from whatever underlying RGI-supply-expansion construction it conditions (explicitly out of scope for this card, per Funding path above, and would carry its own separate environmental profile depending on build method — see this page’s sibling shelter-capital cards for the general modular-construction embodied-carbon literature). Confidence: high on the reporting condition's own lack of direct footprint; the underlying funded construction it attaches to is a separate question this card does not resolve.

Evidence

Confidence & uncertainties

Medium confidence: the throughput-gap problem statement is well-evidenced directly from primary City data; the specific "condition funding on throughput reporting" mechanism is this card's own proposed design, not something already documented as adopted or even proposed by any government body this review — flagged as this card's own synthesis, not a cited existing policy. No specific current provincial or federal RGI-supply funding program for Toronto was independently confirmed this review; the funding-path section names the mechanism generically rather than a specific program, and that gap should be closed before this card moves past DRAFT.

Status

DRAFT — blocked on: naming the specific current provincial/federal program(s) this condition would actually attach to; fairness and legal review; confirmation of whether any funding agreement already contains a comparable throughput clause.

---

Production record

Version: v1.1 (2026-07-13) → v2.0 (playbook pass, 2026-08-11, Lane L3c): opened with the honest-bottom-line paragraph salvaged from the retired day-one memo (archive/dayone/social-housing-waitlist-data.md, now superseded, kept as history); per-card metadata consolidated to one line; verbose Range/Comparator source/Confidence ROI blocks merged to one paragraph each; all facts and figures preserved. FIX-6 note (W1b cards audit, 2026-08-06) carried forward: headings and self-referencing anchors were normalized from "Card 1"/"Card 2" to the card-ID form (a recommendation card/02) so the anchors resolve; no inbound repo references to the old #card-1/#card-2 anchors were found. Status: DRAFT.

About this file