THE PROBLEM — Policing and surveillance in Toronto

1 · The problem

Policing is Toronto's single biggest discretionary budget line: $1.43 billion net in 2026, up 7.0% year over year, funding 143 net new officers. Layered onto that budget is a growing surveillance apparatus — automated licence-plate readers already scan more than a million plates a day across Toronto Police Service vehicles, and any high-risk AI system the service wants to deploy, including facial recognition, needs the police board's approval first. That board-and-budget decision point is the whole lever: once a surveillance system is purchased and installed, it is almost never removed, so the real window to shape what policing and surveillance look like for the rest of this decade is the procurement decisions happening this council term, not some later review. Everyone living in the city is policed by this budget, but the burden lands unevenly — racialized communities carry documented disparities, and every resident's data footprint grows with each new system the board approves. The city controls the budget and the board, among the strongest levers anywhere in this register; the province sets standards through the Community Safety and Policing Act and the Inspector General of Policing; the federal government holds criminal law. Full framing and receipts: register entry; scheduling context: this term's AI and surveillance procurement decisions are also inventoried in DECISIONS BEFORE 2030 — the full inventory (Phase C, one of this library's own project records) §1–2.

2 · What we're asking — the question hierarchy

The primary question: What is Toronto actually buying with its largest discretionary budget line — police service and the surveillance technology layered onto it — and does that spending make anyone measurably safer?

What the budget buys, and who signs off

The surveillance line — what a system may decide

Crime, need, and what actually reduces harm

Safety on transit and in public space

Who's hit, and who's watching the watchers

3 · What we already have — the evidence shelf

Topic Backgrounder Leaf Brief Card
Community safety, crime & policing (the register's own 44-claim depth citation) link not published link link
Community safety perception gap (felt vs. measured safety) link not published link link
Community safety & wellbeing plans (the mandated CSPA plan, register row A3) link not published link link
Police accountability & oversight (the board itself) link not published link link

Deep surfaces checked, honestly reported: WORKLOG — Toronto "Surveillance Pricing" Council Item (shadow report project) was checked as a candidate deep surface for this row. Its subject — regulating private algorithmic pricing data practices under council item 2026.EX33.33 — maps to the F2+H4 data-governance row (see THE PROBLEM — Data, privacy, and Toronto's own AI §3), not to policing; no content from it is pulled into this file. Depth: the register's own citation is the backgrounder above (44 claims); no dedicated flagship exists yet for this row.

4 · What's unexplored

The register's own named gaps: per-capita harm trend receipt and current TPS surveillance-asset inventory — neither exists as a published document anywhere in the corpus today (harvest CSV, problem-register A1★, gap-cell).

Everything §2's "Raised this review" names has no dedicated evidence shelf yet: there is no published TPS surveillance-asset inventory with board-approval dates (NEW-1); no stated review or sunset mechanism for an already-approved system (NEW-2); no per-capita harm/outcome trend broken out by race alongside the 2026 budget growth (NEW-3); and no public adoption-status record showing whether the board's AI pre-approval rule has ever actually stopped a procurement (NEW-4).


Source tags like (homes HM12) mark questions carried from the project's own question banks (QUESTION_HARVEST.csv); untagged questions were raised in the 2026-08-11 rewrite.

Part of Toronto’s Questions · updated 2026-08-11 · corrections welcome — every claim traces to a source; tell us where we’re wrong.