Shelter Security Contracting — Playbook
How much Toronto spends on private security guards at shelters, which firms hold the contracts, and who oversees them.
v2.0 · 2026-08-11
---
The honest bottom line
This doesn't confirm whether the Auditor General's oversight gap has actually been closed. It doesn't reconcile the two different Garda Canada encampment-security figures. It doesn't produce an actual profit-margin number for any contractor, because no source anywhere gives a matched cost breakdown for a specific contract. And it doesn't resolve whether the Council member or the Mayor's Office has the better read on what this spending accomplishes — that's a real, unsettled disagreement between two institutional positions, reported here as exactly that.
---
a recommendation card — Close the Auditor General's Operator-Procured Security Oversight Gap
Card id: a recommendation card · Issue: shelter-security-contracting · Backgrounder: our research file for that page · Trust: carried-forward (CL-330) + New load-bearing findings (backgrounder NEW-2026-SEC-1)
Problem
A 2025 City Auditor General background file found no standardized oversight of safety teams that individual shelter operators procure themselves, separate from the City's own eight direct security contracts (worth roughly $109 million in potential total value, per this review's live discovery). No source located in this review confirms whether this gap has been addressed as of 2026. This card addresses only the operator-procured-team oversight gap, not the City's own direct-contract management, which is not documented as having the same finding against it.
Action
The City extends its own direct-contract security oversight standards (whatever standard applies to its eight direct contracts) to third-party shelter operators' independently-procured safety teams, either by requiring operators to use City-vetted contractors or by requiring operators to report security-incident and procurement data to TSSS on a standardized basis comparable to what the City's own contracts already require.
Jurisdiction split
- City does: this is within existing TSSS contract-management and purchase-of-service agreement authority — extending an existing oversight standard to a category the AG already found lacking one.
- City demands of Province: none identified as required.
- City demands of Feds: none identified as required.
Cost
Order-of-magnitude: low — an oversight/reporting-standard extension, not a new spending program; comparator: the existing $109 million direct-contract spending envelope already carries whatever oversight structure applies to it, which this card extends rather than duplicates.
Funding path
Existing TSSS contract-management operating capacity; no new funding mechanism required for the standard-setting itself. If operator-side compliance requires new staff capacity at individual non-profit operators, that cost is not quantified in this review and is flagged as an open question.
Who benefits, and how
Shelter residents and staff at sites using operator-procured (as opposed to City-direct) security, via consistent oversight standards regardless of which entity procured their site's security; City taxpayers and Council, via closing a documented accountability gap the AG itself identified.
Who bears the cost, and how
Primarily the City's existing TSSS administrative capacity; potentially individual purchase-of-service operators if new compliance reporting requires new capacity on their end — not quantified in this review.
Who benefits from the status quo
No registered entity/claim pair exists yet in the Accountability Observatory's claims register for any named shelter-security contractor. The backgrounder's own Cui Bono section flags Garda Canada Security Corporation's $11.9 million-plus encampment-support contract, combined with the documented oversight gap, as a LEAD-equivalent pointer for the Observatory's own future intake — not a public Cui Bono row, since no ESTABLISHED or REPORTED finding yet names a specific beneficiary claim.
ROI (four dimensions) — schema v2
(a) Financial ROI
Not yet estimable — no source quantifies the cost of extending oversight standards to operator-procured teams, nor any offsetting savings from improved oversight (e.g., avoided improper billing, of the kind documented in this project's separate warming-centre financial-oversight findings for a different program category). The companion warming-centres-winter-respite page’s own AG financial-oversight findings (documented improper billing/unverified cost claims in a structurally similar operator-procured-and-self-reported context) is a directionally relevant comparator for the type of risk this oversight gap presents, though not a security-specific precedent. Confidence: low.
(b) Economic ROI
Not yet estimable — a standard-setting/oversight action with no direct construction or spending-program component; no comparator identified. Confidence: low.
(c) Social ROI
Directional: consistent security oversight across all shelter sites, regardless of procurement path, plausibly reduces the risk of the kind of unaddressed security-conduct allegation this project's companion shelter-system-capacity-strain backgrounder documents at Union Station (security-violence allegations tied to World Cup posture, City response limited to describing existing protocols rather than addressing the allegations directly) — no claim in this page’s own sources directly measures oversight-standard extension against incident rates, so this is stated as directional. Confidence: low-medium.
(d) Environmental ROI
Genuinely environmentally neutral — an oversight/reporting-standard change with no physical-infrastructure component. Confidence: high on the neutrality of this specific action's own footprint.
Evidence
- CL-330 · carried-forward (leaf-source) · 2025 AG finding: no standardized oversight of operator-procured safety teams
- NEW-2026-SEC-1 · source quote (this review) · $109M aggregate contract value, eight contracts, directly fetched
Confidence & uncertainties
Medium confidence on the problem statement (the oversight gap is a direct AG finding, not an inference). Low confidence on cost and most ROI dimensions, genuinely not estimable from sources reviewed. Whether this gap has already been closed since the 2025 finding is unconfirmed either way.
Status
DRAFT — blocked on: fairness and legal review; confirmation of current (2026) implementation status against the AG's 2025 finding.
---
a recommendation card — Publish a Consolidated, Standing Shelter/Encampment Security Contract Disclosure
Card id: a recommendation card · Issue: shelter-security-contracting · Backgrounder: our research file for that page · Trust: New load-bearing findings (backgrounder NEW-2026-SEC-1, NEW-2026-SEC-3)
Problem
The $109 million aggregate private-security contract figure this review located was disclosed only because a journalist requested it directly from the City — it does not appear to exist as a standing, published disclosure Council or the public can access without a similar direct request. A named councillor's own response ("I think it's something that we should look into") indicates even Council itself may lack routine visibility into this aggregate figure. This card addresses the disclosure gap, not the underlying policy question of whether the spending level itself is appropriate (which a recommendation card addresses).
Action
The City publishes a standing, at-minimum-annual consolidated disclosure of all private-security contracts touching shelter, encampment, and directly-adjacent sites (mirroring the eight-contract breakdown this review's live discovery obtained only via direct data request) — contract value, counterparty, site category, and year-to-date spending — as a routine budget-document or open-data-portal disclosure rather than a data request response.
Jurisdiction split
- City does: entirely within existing municipal budget-transparency and open-data practices; the underlying data already exists (the City provided it to a journalist on request) — this action standardizes and routinizes its publication.
- City demands of Province: none identified as required.
- City demands of Feds: none identified as required.
Cost
Order-of-magnitude: low — a disclosure/reporting exercise using data the City has already compiled at least once (per NEW-2026-SEC-1's own sourcing), comparable in scale to other low-cost reporting actions this project's companion leaves propose (e.g., shelter-system-capacity-strain's a recommendation card).
Funding path
Existing City budget-office/open-data operating capacity; no new funding mechanism required.
Who benefits, and how
Council and the public, via routine visibility into a spending category currently disclosed only on ad hoc journalist request; taxpayers, via the accountability pressure routine disclosure typically creates on contract-value growth or renewal terms.
Who bears the cost, and how
City taxpayers, negligibly, via existing budget-office/open-data staff time — no new payer class.
Who benefits from the status quo
No registered entity/claim pair exists yet; see the backgrounder's own Cui Bono section for the LEAD-equivalent pointer this card's action would help surface into a citable, public finding if routine disclosure reveals further concentration or growth in specific contractors' shares.
ROI (four dimensions) — schema v2
(a) Financial ROI
Not separately estimated; this is a disclosure action, not a spending program. Its financial case is entirely about the accountability pressure routine, standardized disclosure typically exerts on contract-value discipline at renewal — not quantified in this review. No comparator identified specific to Toronto security contracting; general open-contracting-data literature (Open Contracting Partnership's OCDS standard, named in the Accountability Observatory Charter §5) supports the general mechanism but was not re-cited here to avoid overstating a general literature's applicability to this specific narrow action. Confidence: low.
(b) Economic ROI
Not yet estimable — a disclosure action with no direct spending or construction component; no comparator identified. Confidence: low.
(c) Social ROI
Directional: routine disclosure plausibly improves public trust and Council's own ability to respond to spending-level concerns (of the kind a sitting Council member's own reported response already demonstrates exists) before they require a direct data request to surface. Comparator: a sitting Council member's own reported response (NEW-2026-SEC-3) as evidence the current disclosure gap is a live, not hypothetical, problem. Confidence: low-medium.
(d) Environmental ROI
Genuinely environmentally neutral. Confidence: high on the neutrality of this specific action's own footprint.
Evidence
- NEW-2026-SEC-1 · source quote (this review) · $109M aggregate figure, obtained via direct data request, directly fetched
- NEW-2026-SEC-3 · source quote (this review) · a sitting Council member's response indicating limited routine visibility, directly fetched
Confidence & uncertainties
Medium confidence. The disclosure gap is directly evidenced by the fact that this review's own key figure came from a journalist's direct data request rather than a published document. Whether the City already has an internal (non-public) version of this disclosure that simply isn't published is a real possibility this card cannot rule out.
Status
DRAFT — blocked on: fairness and legal review; confirming whether an internal, non-public version of this disclosure already exists.
---
Production record
Version: v1.0 (2026-07-14) → 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/shelter-security-contracting.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, CL-330 token, dollar figures, and named contractors preserved. Status: DRAFT.