Toronto Emergency Management

SERIES-EXISTS (GOV-ATLAS-SERIESAUDIT-d1 2026-08-02): prior no-series note OVERTURNED; 3 doc row(s) located and verified. Prior note: no current plan located; candidate Toronto Emergency Plan page returned 404; budget-note

Current this library's internal records: 2026 Program Summary: Toronto Emergency Management (2026)

Completeness

• Document shelf: 3 rows (3 archived · 0 staged · 0 pending · 0 missing)
• Backgrounder: on file
• Strategy-evolution brief: on file
• Custody audit: 3 of 3 row(s) audited, all clean
• Last verified: 2026-08-02 · 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: FOI via central portal

Document shelf (3 rows)

Backgrounder

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

Toronto Emergency Management - backgrounder

Backgrounder / 2026-08-02 / registry row: tor-toronto-emergency-management (this library's government-document registry) / lens file for this org's series briefs

Mandate & statutory basis

Toronto Emergency Management (TEM) is an operating division of the City of Toronto; its administrative existence rests on City Council's general organizing authority under the City of Toronto Act, 2006, S.O. 2006, c. 11, Sched. A, ss.6-8 (https://www.ontario.ca/laws/statute/06c11, fetched 2026-08-02). Its program mandate is set by the Emergency Management and Civil Protection Act, R.S.O. 1990, c. E.9, which requires that "every municipality shall develop and implement an emergency management program" and that council adopt that program by by-law (statute, s.2.1(1); https://www.ontario.ca/laws/statute/90e09, fetched 2026-08-02); the City's own 2026 Program Summary states plainly that "the City's Emergency Management Program is governed by the Emergency Management and Civil Protection Act, which provides the legal basis and framework for emergency management programs in Ontario. Primary functional responsibility for emergency management is delegated to local municipalities" (2026 Program Summary: Toronto Emergency Management, https://www.toronto.ca/wp-content/uploads/2026/03/967d-2026-Public-Book-TEM-V1.pdf, fetched 2026-08-02). ⚠️ still being checked O. Reg. 380/04 (the regulation prescribing the standard program elements) was not independently re-confirmed against current in-force text this review.

Roles, responsibilities & scope

TEM "maintains, coordinates and drives improvements to Toronto's emergency management program," covering mitigation, preparedness, response and recovery, and "coordinates emergency resources across the municipality and, as necessary, across municipal and provincial borders (mutual aid) as well as vertically through the Provincial and Federal Governments" (2026 Program Summary, https://www.toronto.ca/wp-content/uploads/2026/03/967d-2026-Public-Book-TEM-V1.pdf). Historically operating as the Office of Emergency Management, its core functions include maintaining the City's Emergency Plan and Emergency Support Functions, hazard identification and risk assessment, training and exercises for Emergency Operations Centre and Emergency Reception Centre staff, public education, emergency social services coordination (with the Canadian Red Cross under a Memorandum of Understanding), special-event emergency planning review, and the City's Corporate Business Continuity Management program (Emergency Management Program Update, 2017, https://www.toronto.ca/legdocs/mmis/2018/ex/bgrd/backgroundfile-113667.pdf, fetched 2026-08-02).

Governance & reporting line

The registry lists no parent_org for this division (registry row: tor-toronto-emergency-management, parent_org blank); ⚠️ still being checked specific Deputy City Manager cluster — a 2018 subject report was submitted by the Deputy City Manager, Cluster B, but the City's cluster structure has since been reorganized and this review did not confirm the current reporting line (Emergency Management Program Update, 2017, https://www.toronto.ca/legdocs/mmis/2018/ex/bgrd/backgroundfile-113667.pdf). The division's current Executive Director is Joanna Beaven-Desjardins (TEM division page, https://www.toronto.ca/city-government/accountability-operations-customer-service/city-administration/staff-directory-divisions-and-customer-service/toronto-emergency-management/, fetched 2026-08-02).

Budget scale

2026 gross operating budget of $8.9 million, $3.2 million in revenue, and $5.7 million net, with 46.0 approved positions; TEM "does not have a 10-Year Capital Budget and Plan" (2026 Program Summary: Toronto Emergency Management, https://www.toronto.ca/wp-content/uploads/2026/03/967d-2026-Public-Book-TEM-V1.pdf, fetched 2026-08-02).

Institutional history

TEM operated earlier in its history as the City's Office of Emergency Management (per program-update subject reports from 2017-2018, which use that name throughout, e.g. Emergency Management Program Update, 2017, https://www.toronto.ca/legdocs/mmis/2018/ex/bgrd/backgroundfile-113667.pdf) and traces its formal annual-reporting obligation to Council's July 2015 adoption of EX7.5 (Further Update on the Implementation of December 2013 Ice Storm Recommendations), which required annual reporting on emergency management program activities (same source, "Decision History"). ⚠️ still being checked the exact date/instrument of the rename from Office of Emergency Management to Toronto Emergency Management was not independently confirmed this review.

Strategy evolution brief

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

Toronto Emergency Management - strategy evolution

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

TL;DR: Across three documents spanning 2013-2018 — the City of Toronto Emergency Plan (2013/14), a 2017 report proposing Municipal Code amendments, and a 2018 annual program-update report — the Office of Emergency Management's (OEM) governance framework evolves from a static, by-law-defined committee structure toward a more flexible, professionalized program built around the Incident Management System (IMS), first tested City-wide during the 2010 G20 and formalized through 2013 ice-storm lessons. The biggest priority addition across the record is the explicit adoption of IMS as the City's standard emergency-response structure, replacing the older "Joint Operations Team" concept; the biggest quietly-dropped element is the Joint Operations Team itself, formally removed from the Municipal Code by the 2017 amendments. The most load-bearing number is that the Emergency Operations Centre (EOC) had been activated 19 times since 2009 as of the 2017 report, with 4 further activations in 2017 alone (all named institutionally: two fires, two flooding events). One open question the record cannot resolve: whether OEM's governance reforms (all-members-become-Control-Group, delegated authority to set Working Group membership) were themselves further revised after 2018, since the readable record stops there — nothing in this brief speaks to pandemic-era (2020 onward) emergency management, which is entirely outside this three-document window.

Backgrounder summary

Per the Wave 1 backgrounder (our research file for that body, 2026-08-02): Toronto Emergency Management (TEM) is a City of Toronto operating division whose program mandate is set by the provincial Emergency Management and Civil Protection Act, which requires every municipality to develop and implement an emergency management program adopted by council by-law. TEM "maintains, coordinates and drives improvements to Toronto's emergency management program" across mitigation, preparedness, response and recovery, and operated earlier in its history as the City's Office of Emergency Management (OEM) — consistent with this brief's own document series, which is entirely OEM-era (2013-2018). The backgrounder confirms TEM's formal annual-reporting obligation traces to Council's July 2015 adoption of EX7.5. Executive Director per the current TEM division page is Joanna Beaven-Desjardins; 2026 gross operating budget: $8.9 million, $5.7 million net, 46.0 approved positions. The backgrounder flags two unresolved points that bear on this brief: the registry lists no parent_org/reporting cluster for this division (⚠️ still being checked current Deputy City Manager cluster), and the exact date/instrument of the OEM-to-TEM rename was not independently confirmed.

Series inventory

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

Registry (our document registry equivalent — per-org seriesaudit record) carries 3 rows for this org spanning 2014-2018; all 3 are archived and appear below; 0 are staged and 0 are missing — no registry/archive gap exists for this org's three-document set. (Per this library’s standing org-facts rule: "3 rows, census 3 ok.")

Exactly 3 usable, non-stub documents spanning a genuine 2013-2018 window (the 2014-titled document is itself the City of Toronto Emergency Plan as revised December 2013; the 2017-titled document is an October 2017 Executive Committee report; the 2018-titled document is a March 2018 report on 2017 program activity). Per this library’s standing editorial rule, full-form treatment is applied since exactly 3 usable documents meet the threshold, and the 2013→2018 span may show genuine evolution in emergency-management framing — which the record below shows it does, within institutional/governance terms only.

Priority evolution

The 2013 Emergency Plan (the earliest document) establishes the foundational governance architecture: a Toronto Emergency Management Program Committee (TEMPC) of 28 named positions, a smaller 16-member "TEMPC Control Group" that convenes during actual emergencies, and an Emergency Management Working Group (EMWG) of Director/Manager-level representatives from 23 named Agencies, Boards, Commissions and Divisions (90cf6fb4db23). The plan's stated priority is establishing "the framework that ensures the City is prepared" through a four-phase Preparedness Cycle (Plan, Operate, Evaluate, Corrective Action) and 14 named Operational Support Functions. By 2017, the priority shifts to modernizing and rationalizing that same governance structure: the report proposes expanding TEMPC membership (adding the Toronto and Region Conservation Authority, Toronto Hydro, and a newly-created Chief Resilience Officer position), collapsing the distinction between TEMPC and its Control Group so all TEMPC members are Control Group members, and formally adopting the Incident Management System as the City's operating framework in place of the by-law's original "Joint Operations Team" concept (a5383ce3a37b). By 2018, the priority is reporting execution and compliance against that reformed structure: the OEM states it is "100% compliant" with provincial Emergency Management and Civil Protection Act requirements and reports concrete 2017 program metrics — training sessions delivered, exercises run, EOC activations — rather than proposing further structural change (a82de56553f0).

Priorities added, dropped, renamed

Added: The Chief Resilience Officer position, tied to "integration with Resilient Toronto," is proposed for TEMPC membership in 2017 (a5383ce3a37b) and appears as already-integrated into the Emergency Plan update by 2018 (a82de56553f0) — this position and its "Resilient Toronto" connection do not appear in the 2013 plan at all. The Incident Management System is named as the City's adopted operating framework starting in the 2017 report, which traces its first City-wide use to the 2010 G20 and describes it as by-2017 fully "tested and demonstrated as a viable system" (a5383ce3a37b); the 2013 plan does reference IMS as an organizing principle for the EOC and Incident Site response but does not describe it as the City's singular governance-replacement framework the way the 2017 document does. A formalized "Emergency Standby" 24/7 activation-tracking function with specific annual call-volume reporting (126 activations in 2016, 102 in 2017) first appears as a named, measured program element in the 2017 and 2018 reports (a5383ce3a37b; a82de56553f0) — the 2013 plan describes an "OEM 'Standby' Coordinator" role functionally but does not report activation counts. Dropped: The "Joint Operations Team," described in the 2013 plan's underlying Municipal Code framework as the body that would staff the EOC (though not detailed at length in the 2013 plan text itself), is explicitly targeted for removal by the 2017 report, which recommends "references to the Joint Operations Team be removed from the Municipal Code to align with the current Incident Management System structure" (a5383ce3a37b) — its role is described as superseded by IMS. Renamed: No direct renaming of a named committee or program is evidenced across the three documents; the TEMPC and EMWG names persist unchanged from 2013 through 2018, with membership composition changed but the names themselves stable.

Budget & mandate inflection points

• 2013 Ice Storm as a governance catalyst: the 2017 report traces its recommended Municipal Code changes directly to lessons from the December 2013 ice storm and 2013 flooding, noting Council's July 2015 adoption of EX7.5 which required OEM to report annually to Executive Committee on program changes — this annual-reporting requirement is the direct origin of both the 2017 and 2018 documents in this series (a5383ce3a37b; a82de56553f0).
• Chapter 59 (Emergency Management) amendments, approved November 2017: City Council adopted EX28.13, amending the Municipal Code to require TEMPC to report on Emergency Plan changes within a 12-month period (previously tied to the calendar-year Executive Committee cycle), add three new TEMPC members (TRCA, Toronto Hydro, Chief Resilience Officer), merge TEMPC and Control Group membership, remove Joint Operations Team references, delegate EMWG membership decisions to TEMPC, and reduce mandated EMWG meetings from a higher prior count to a "minimum of four per year" (a5383ce3a37b) — the report states these amendments have "no financial implications."
• EOC activation count as a load-bearing operational metric: 19 activations since 2009 as of the 2017 report (a5383ce3a37b), with 4 further activations named institutionally in 2017 alone — fires at two named addresses, May 2024 Don Valley flooding, and Toronto Island flooding (a82de56553f0). ⚠️ Still being checked: the 2018 report's four 2017 activations use only address/location and event-type descriptors, consistent with the private-individual and non-accusatory-voice guardrails; no complainant, resident, or affected individual is named anywhere in this brief's source material, and none should be.
• Provincial Nuclear Emergency Response Plan consultation, 2017: the City participated in a provincial public consultation (May-July 2017) on nuclear emergency planning and specifically flagged, as unresolved, three items: a funding model for ongoing municipal operation of the nuclear program, a compliance-demonstration process, and clarity on the province's lead role in evacuations and training (a5383ce3a37b) — the 2017 report states no financial impact to the City from the associated 20-kilometre Contingency Planning Zone, since no new protective measures were proposed for that zone at that time.
• 2016→2017 program-activity comparison: Emergency Standby activations fell from 126 (2016) to 102 (2017); Emergency Social Services responses fell correspondingly from 62 to 60 (a5383ce3a37b; a82de56553f0) — both documents describe the same category of activity (mostly fire-scene displacement response) using comparable methodology, making this one of the only genuine year-over-year quantitative comparisons the three-document record supports.

Ontario/Toronto relevance

This is a direct, primary-mandate Toronto municipal office: the Office of Emergency Management is a City of Toronto division operating under City of Toronto Municipal Code Chapter 59 and the provincial Emergency Management and Civil Protection Act, with its Emergency Plan and program updates addressed directly to Toronto City Council's Executive Committee (90cf6fb4db23; a5383ce3a37b; a82de56553f0). All three documents describe exclusively City of Toronto emergency-management governance, programming, and response activity; there is no indirect or national-scope framing to qualify, though the 2017 document does describe the City's interaction with a provincial consultation process (the Provincial Nuclear Emergency Response Plan) as an institutional coordination matter, not as evidence of a broader provincial mandate for this office.

Residuals & gaps

• This org had zero recorded documents until 2026-08-02. A prior capture attempt recorded a "Toronto Emergency Plan" landing-page URL as returning 404, and that 404 was recorded as an absence of documents for this org. Per the org's seriesaudit record (this library's internal records), the correct route was a toronto.ca/legdocs/mmis search that located and successfully fetched (200-response, confirmed download) all three documents used in this brief: the City of Toronto Emergency Plan (2013/2014 core planning document), the 2017 program/Municipal Code report, and the 2018 program-update report — described in the seriesaudit as "a genuine subject-report series under Executive Committee, distinct from the budget-note already on file" for this org (a budget note exists in the registry but is not part of this brief's document set, which draws only from the three subject-report _index.json rows).
• The record covers 2013-2018 only; nothing after 2018 is in this archived set. Per this library's standing scope decision, this brief says nothing about pandemic-era (2020 onward) emergency management, since that period is entirely outside the readable record. Any governance changes, program reforms, or activation patterns after March 2018 (when the last document in this set was published) are unestablished by this brief.
• No detector disagreements found. All 3 documents in _index.json are marked "ok" and all 3 were independently confirmed on read to contain full, substantive report content (14,097-80,383 characters each) — no stub-suspected or extract-failed status appears in this org's index, and this brief's own read confirms the detector's "ok" calls were correct in all three cases.
• Private-individual rule applied: this org's source material is emergency-management program and governance reporting, not incident-specific case files; no complainant, victim, resident, or private individual affected by any named incident appears anywhere in the three source documents' text as read, and none is named in this brief. All named persons in the source material are titled officeholders (Deputy City Manager, OEM Director, named committee-chair signatories) acting in an institutional capacity, consistent with the guardrails.
• ⚠️ Still being checked: whether the 2017-approved Chapter 59 amendments (merging TEMPC/Control Group membership, delegating EMWG composition to TEMPC) were implemented as written by the time of the 2018 report, or whether the 2018 report's "100% compliant" statement refers to compliance with the pre-amendment or post-amendment structure — the 2018 document states the Emergency Plan "was updated" to reflect the 2017 Code changes but does not itself re-state the full amended TEMPC/Control Group membership list for independent verification against the 2017 proposal.
• Backgrounder reconciliation, 2026-08-02: this brief was written before the org's Wave-1 backgrounder existed. The backgrounder corroborated every claim in this brief's OEM-era (2013-2018) document series; only the Backgrounder summary section was rewritten. The backgrounder carries two additional unresolved ⚠️ still being checked flags this brief's three-document window cannot itself resolve: (1) the current Deputy City Manager reporting cluster for this division — the registry lists no parent_org, and a 2018 report was submitted under a since-reorganized "Cluster B" structure; (2) the exact date/instrument of the rename from Office of Emergency Management to Toronto Emergency Management, which postdates this brief's 2018 document ceiling and is therefore outside what this brief's own record can confirm or deny.