Deputy City Manager - Community and Emergency Services

DCM portfolio cluster; Internal office w/o dedicated site; FOI via central portal; no current plan located; corporate-plan-chapter (no dedicated DCM-cluster budget note found for this cluster)

Current this library's internal records: City of Toronto Corporate Strategic Plan (2019)

Completeness

• Document shelf: 2 rows (2 archived · 0 staged · 0 pending · 0 missing)
• Backgrounder: not written yet
• Strategy-evolution brief: on file
• Custody audit: 2 of 2 row(s) audited, 1 flagged
• Last verified: 2026-08-04 · this org has NOT had a full discovery-verification pass (our discovery-verification log)

Endpoints

• Website
• Open data: not yet verified
• API: not yet verified
• RSS: not yet verified
• Newsroom: not yet verified
• FOI / access requests: not yet verified

Document shelf (2 rows)

Backgrounder

No backgrounder written for this org yet.

Strategy evolution brief

Source: this library's internal records — a mechanical research draft, not independently reviewed for publication; reproduced as-is.

Deputy City Manager - Community and Emergency Services - strategy evolution

2026-08-02 / registry: tor-deputy-city-manager-community-emergency-services / grounded in archived copies (cited document id + sha256) / read through our research file for that body

TL;DR: This org is the other half of the FY2026 split described in the shared backgrounder: its FY2025 document is byte-identical (sha256 b8b601f1f647) to tor-deputy-city-manager-community-development-social's FY2025 document, the same ten-program "Community and Social Services" cluster book, and this org's FY2026 standalone document retains the other six programs (Economic Development and Culture, Toronto Fire Services, Parks and Recreation, Toronto Paramedic Services, Toronto Shelter and Support Services, plus a genuinely new sixth line, Toronto Emergency Management). The biggest addition is that Toronto Emergency Management line itself — absent from the FY2025 shared cluster book entirely and, per the sibling tor-deputy-city-manager-infrastructure-services brief, present in Infrastructure Services' own FY2025 document instead, indicating a cross-cluster program transfer into this org between FY2025 and FY2026. The most load-bearing clean number is FY2026 net expenditures of $1,447.5M, up $84.9M (6.2%) from this document's own restated FY2025 baseline of $1,362.6M (Toronto's FY2025 Budget). One open question: the FY2026 per-program budget table in this document extracted with significant OCR corruption, so the exact program-level split of that $84.9M increase cannot be stated with full confidence (see Residuals & gaps).

Backgrounder summary

This org is one of five Deputy City Manager portfolios reporting to Toronto's City Manager under the City of Toronto Act, 2006 governance structure; full statutory/governance grounding is in the shared backgrounder our research file for that body (written for this batch per that batch’s own build note §B3). Portfolio-specific: as of the FY2026 budget document, this DCM's cluster comprises Economic Development and Culture, Toronto Fire Services, Parks and Recreation, Toronto Emergency Management, Toronto Paramedic Services, and Toronto Shelter and Support Services (tor-deputy-city-manager-community-emergency-services-bud-2026, efdf9e945012) — the "emergency response and public space" half of the ten-program "Community and Social Services" cluster this DCM title covered as recently as January 2025, plus one apparent transfer-in from Infrastructure Services (see Priorities added, dropped, renamed).

Series inventory

_index.json: 2 ok / 0 stub-suspected / 0 extract-failed.

Registry (our document registry) carries 2 rows for this org, both archived and both appearing below (2025, 2026); no staged or missing rows exist for this org.

Shared-document note (that batch’s own build note §B2): the 2025 document is a shared cluster book titled "Community and Social Services (2025 Budget Committee presentation)," identical byte-for-byte (sha256 b8b601f1f647) to the FY2025 document cited by tor-deputy-city-manager-community-development-social; full split narrative is in our research file for that body. Analysis below is scoped to the five programs that carried forward into this org's FY2026 successor cluster (Economic Development and Culture, Toronto Fire Services, Parks/Forestry & Recreation, Toronto Paramedic Services, Toronto Shelter & Support Services) — Court Services and the four programs that instead moved to tor-deputy-city-manager-community-development-social are that org's concern, not analyzed here.

SHORT-FORM RULE APPLIES: 2 usable documents, not a like-for-like pair — same structural reason as the sibling org: the 2025 document covers this org's five legacy programs as rows within a ten-program cluster book, while the 2026 document is a standalone six-program presentation (five carried forward plus one apparent transfer-in). What follows states only what the two documents, read against each other, establish about this reorganization.

Priority evolution

Not a comparable time series for the reasons given above. What the record does establish: the FY2025 shared cluster vision ("Together We Thrive," b8b601f1f647) covered all ten programs including the four now under the sister cluster. The FY2026 standalone vision, scoped to this org's six programs, reads "United in Service / Across every community, people find welcoming and animated public spaces, resilient local economies, clear pathways to support, and trust in emergency response" (efdf9e945012) — the phrase "trust in emergency response" aligns the vision language to the cluster's now-explicit emergency-services composition (Fire, Paramedic, and the newly added Emergency Management function), a framing absent from the FY2025 cluster-wide statement.

Priorities added, dropped, renamed

• Added — Toronto Emergency Management, described as coordinating "preparedness, response and recovery activities with all City Divisions, Agencies, Corporations, and external stakeholders" and owning "the City's Emergency Plan, Emergency Operations Centre, Emergency Social Services Policy, and Heat Relief Strategy" (efdf9e945012). This program has no equivalent row or service description anywhere in the FY2025 shared cluster document (b8b601f1f647). Per the sibling tor-deputy-city-manager-infrastructure-services brief, Toronto Emergency Management appears instead in Infrastructure Services' own FY2025 document with its own $5.2M net budget line, and is absent from Infrastructure Services' FY2026 document — indicating the function transferred from the Infrastructure Services DCM cluster into this one between FY2025 and FY2026. Neither this org's document nor Infrastructure Services' documents state a reason for the transfer.
• Dropped from this org's own FY2026 document (reassigned, not eliminated) — Children's Services, Court Services, Seniors Services and Long-Term Care, Social Development/Finance/Administration, and Toronto Employment and Social Services all appear in the shared FY2025 document (b8b601f1f647) but not in this org's FY2026 document; four of the five reappear in tor-deputy-city-manager-community-development-social's FY2026 document (Court Services' FY2026 disposition is unconfirmed by either successor document read this batch).
• Renamed — "Community and Social Services" → "Community & Emergency Services." The cluster name itself changed, consistent with the composition shift toward emergency-response functions (b8b601f1f647; efdf9e945012).
• Framing shift — equity language recedes from this cluster's own priority-action headings. The FY2025 shared document's five priority-action categories included "Advance equity and social justice" as a standalone heading (b8b601f1f647); the FY2026 document's four priority-action categories ("Provide Proactive Supports for Vulnerable Populations," "Reinforce Community Safety and Emergency Response," "Create and Promote Safe, Welcoming, and Vibrant Neighbourhoods," "Deliver Innovations and Improvements in Client Experience") have no equivalent standalone equity heading (efdf9e945012) — consistent with the sister org's brief finding that Reconciliation/equity language concentrated in the FY2026 Community Development and Social Services document instead.
• New citywide event driver visible for the first time: FIFA World Cup 2026 references appear in this org's FY2026 priority actions ("Connect more youth to jobs through FIFA World Cup community benefits"; "Support emergency preparation and coordination for FIFA and other major festivals and events," efdf9e945012) with no equivalent in the FY2025 document — consistent with the same citywide theme appearing independently in the sibling tor-deputy-city-manager-community-development-social and tor-deputy-city-manager-infrastructure-services FY2026 documents.

Budget & mandate inflection points

• The FY2026 cluster split and the Emergency Management transfer-in are the dominant inflection points in this window; full cross-org detail is in our research file for that body.
• Clean, document-level numbers: FY2026 gross expenditures $2,440.8M (down $30.5M/-1.2% from this document's own restated FY2025 baseline of $2,471.4M), FY2026 net expenditures $1,447.5M (up $84.9M/+6.2% from a restated FY2025 baseline of $1,362.6M), approved positions up 268.1 (+2.2%) to 12,731.0 (efdf9e945012). Revenue fell sharply, -$115.4M/-10.4%, to $993.3M.
• The restated FY2025 baseline in this document ($1,362.6M net) is lower than a reconstruction from the original shared FY2025 document would suggest. Summing this org's five legacy programs' own FY2025 line items as reported in the shared cluster book (Economic Development & Culture $91.9M, Parks Forestry & Recreation $380.0M, Toronto Fire Services $548.4M, Toronto Paramedic Services $130.4M, Toronto Shelter & Support Services $241.2M; b8b601f1f647) yields $1,391.9M — roughly $29M higher than this document's restated $1,362.6M baseline for six programs including Emergency Management's own ~$5.4M restated baseline. This is the mirror image of the sister org's finding (its four programs' restated FY2025 baseline came in ~$38M higher than the original document's own subtotal); read together, the two restatements move in roughly offsetting directions, consistent with a corporate cost-reallocation across the split rather than two independent errors, but ⚠️ Still being checked: neither document explains the mechanism.
• Individual program figures extracted from this document's FY2026 "By Program" table (Toronto Fire Services $548.9M→$558.9M, +$10.0M/+1.8%; Toronto Paramedic Services $140.3M→$175.2M, +$34.9M/+24.9%) reconciled internally (base + enhanced = total; prior + change = current) and are reported with reasonable confidence; other rows in the same table (Economic Development and Culture, Parks and Recreation, Toronto Shelter and Support Services, Toronto Emergency Management) required reconstruction from partially garbled OCR text — see Residuals & gaps before relying on those figures.

Ontario/Toronto relevance

Direct — this is a City of Toronto Deputy City Manager portfolio; both documents are City of Toronto Budget Committee presentations covering City-delivered fire, paramedic, shelter, parks/recreation, economic development, and emergency-management services within Toronto specifically (b8b601f1f647; efdf9e945012).

Residuals & gaps

• Detector calls confirmed correct. _index.json marks both documents ok; both were read in full and are genuine, substantive budget presentations — no stub-suspected or extract-failed disagreement in either direction.
• OCR corruption in the FY2026 "By Program" Net Operating Budget table. Unlike every other document read in this batch, this specific table extracted with garbled characters (e.g. "ge_s," "9r3_Q," "e19,_9" in place of clean digit strings) — likely reflecting a graphically-styled table in the source PDF that did not extract cleanly to text. Fire and Paramedic Services figures reconciled internally and are reported above with confidence; Economic Development and Culture (~$92.8M→$97.2M), Toronto Shelter and Support Services (~$219.9M→$235.1M), and Toronto Emergency Management (~$5.4M→$5.7M) figures are reconstructions from partial OCR text cross-checked against internal arithmetic, not direct high-confidence reads — flagged here explicitly rather than stated as certain. This is a live QA signal for the batch: other docs in this cohort extracted cleanly, so this is likely a source-PDF formatting issue specific to this file, not a systemic extraction problem.
• Court Services' FY2026 disposition is unconfirmed (see sister org's brief) — it does not appear in either FY2026 successor document read for this batch.
• The offsetting-restatement observation (Budget & mandate inflection points, above) is grounded in both this org's and the sister org's own documents but its cause is not established by any document read this batch; a future pass should attempt to source the underlying Budget Committee staff report or Council decision authorizing the FY2026 reorganization.
• No private-individual, candidate, or named-donor content encountered in either document.