311 Toronto: Service Requests, Open Data and Service Standards

🤖 AI-generated summary · 🔎 Last verified 2026-07-26

This overview was generated with AI from the public sources listed below and checked against them before publication. It has not had a complete human fact-check — treat it as a starting point and follow the sources.

How this atlas is made · What “last verified” means · What “source-checked” means

Every request since 2010 is published as open data, but the extract carries no closure date. Whether a request marked closed was ever fixed has not been audited.

Outcome🔄 Ongoing

Evidence🏛️ Official

what does this mean?

The strongest source is the operator's or the city's own reporting — an official report, dataset or press release. It grades who did the looking — not how well the project went. All four grades →

Run byCity of Toronto — Customer Experience Division (311 Toronto)

Scale🏙️ City-wide

Part of 1001 Smart Cities — 1,167 documented projects · 🏙️ 9 more in Toronto · 🪪 Digital government guide · 🏛️ Governance projects

Toronto's 311 line opened on 24 September 2009 and takes non-emergency requests around the clock, with interpretation offered in more than 180 languages. Service requests are published as open data — one archive per calendar year since 2010, refreshed monthly — but the extract carries creation date, type, status, division and ward, with no closure date and no service-level target. Those targets sit instead on a separate public dashboard that reports how many requests were addressed within standard, division by division. The city's own glossary concedes a standard 'may be met through an initial investigation rather than full resolution of the issue'.

Live 📅 since 2009

📊 Impact

1.29 million contacts in 2024, about 487,000 of them service requests (479,000 the year before); 82% of calls answered within 75 seconds against an 80% target — all figures self-reported by the Customer Experience Division.

🎓 Lesson

No audit has tested whether a Toronto request marked closed was actually fixed. The closest anyone has come is a February 2025 Auditor General review of the Parks Branch, which found the division had no centralized system to track, log and manage public complaints at all — and the city's own dashboard glossary warns that meeting a standard can mean an initial investigation rather than a repair.

🏛️ Governance Digital government Open data Citizen participation

Sources

↗ City of Toronto — About 311 (FAQ)Operator page, hours and languages: 'Customer service representatives are available to answer your questions or fill a service request 24 hours a day, seven days a week', with interpreters available in 'more than 180 languages'.

↗ MobileSyrup — City of Toronto launches 311 service for non-emergency infoContemporaneous coverage published 24 September 2009, the launch day, quoting the city: 'This is a pivotal day for customer service for the City of Toronto.' Confirms 24/7 operation and 180 languages at launch. Used for the start year only; no superlative about being first in Canada is claimed.

↗ City of Toronto Open Data — 311 Service Requests, Customer Initiated (CKAN package metadata)Authoritative field and cadence source, queried 2026-07-26: refresh rate monthly, last refreshed 2026-07-08, one ZIP resource per year from 2010 to 2026. Attributes are creation date/time, location, original request type, status (Initiated, In Progress, Canceled, Closed), division, section-unit and ward — there is no closure date, no due date and no service-level target, and no channel column despite the description noting requests arrive by phone, fax, email, web, mobile API and Twitter. Note for the editor: the human-facing page at open.toronto.ca is a JavaScript shell that renders an empty 'Retired' template to fetchers; the dataset is live.

↗ City of Toronto — 311 Service Standard Dashboard: Glossary & NotesThe load-bearing caveat, verbatim: 'A service standard defines the expected timeframe within which a service request is to be addressed or actioned by the responsible City division' and 'In some cases, a service standard may be met through an initial investigation rather than full resolution of the issue.' Requests addressed/actioned are counted 'in accordance with the applicable service standard within a specified timeframe', excluding cancelled requests and those with no standard.

↗ City of Toronto — 311 Service Standard DashboardThe dashboard the targets live on: 'an interactive view of service request volumes, service levels, geographic distribution, and 311 call responsiveness across the city', covering six divisions, with static dashboards for property standards, noise, graffiti, dead wildlife pickup, garbage collection, overflowing bins, potholes, and trees and pruning.

Show 4 more sourcesShow fewer

↗ Auditor General of Toronto — Audit of Parks Branch Operations Phase 2 (5 February 2025)The nearest thing in this series to an independent check on what happens after a 311 complaint is filed, verbatim: 'The Parks Branch does not have a centralized system to effectively track, log and manage public complaints, making it difficult to compile and analyze data to identify trends or address the underlying causes of recurring issues.' The report also says the branch can improve its targets for 'assessing, acknowledging, and resolving complaints received from Torontonians'. It audits one division's handling of complaints, not the accuracy of 311 closure codes.

↗ Auditor General of Toronto — 311 Toronto: Full Potential For Improving Customer Service Has Yet To Be Realized (23 November 2011)Cited for existence and date only: Toronto is one of the few cities in this series whose auditor has examined 311 itself. The report PDF could not be parsed in this environment, so no figure from it is used in the entry — including the often-repeated claim about unanswered calls.

↗ City of Toronto — Customer Experience Division Annual Report 2024Origin of every volume figure in the impact field, operator self-reported: 'In 2024, CXD-311 responded to 1.29 million interactions with a Service Level of 82% for the phone', of which about 487,000 became service requests, against a target of answering 80% of calls within 75 seconds. These come from the operator's own report to committee, not from the open dataset.

↗ Open311 GeoReport v2 server directory — Toronto entryRegistration record: jurisdiction_id 'toronto.ca', base_url 'https://secure.toronto.ca/webwizard/ws/', test_url 'https://secure.toronto.ca/open311test/ws/', version 'georeport-v2', production_ready true. Tested 2026-07-26: the production services list returned HTTP 404 and the test server returned HTTP 404. The discovery document at secure.toronto.ca/open311test/discovery.json still resolves but is dated December 2011.

Continue exploring

Compare this project

🇺🇸 DC 311 and the Open311 API It Started · Washington D.C. D.C. wrote the Open311 standard and its endpoint no longer answers; Toronto's registered endpoint returns 404 as well. 🇺🇸 Miami 311: A County Line and a City Record That Stops in 2024 · Miami Miami's extract carries a goal in days, days taken and an overdue flag; Toronto's has a status field and no closure date at all. 🇨🇦 Toronto Open Data: CKAN portal under a bespoke municipal licence · Toronto The yearly request archives sit in the city's CKAN catalogue — the same catalogue whose bespoke licence only 115 of 554 records name.

Explore the wider context

🗺️ Your City's Problem Map Is Really a Map of Who Complains 📖 Civic participation platform 📖 Digital identity 📖 Government super-app

📎 Cite this project

1001 Smart Cities (2026). “311 Toronto: Service Requests, Open Data and Service Standards” — Toronto, Canada. The Smart City Atlas. https://1001smartcities.org/projects/toronto-311/ (last verified 2026-07-26). Data: CC BY 4.0.

The underlying data is free to reuse with attribution — see the open data page.

🚩 Report an error · 🔔 Follow changes to this entry (RSS)