uniteTOlove.ca

A Government That Works: Service Delivery Basics — Playbook

Potholes, permits, and 311 calls — how well the basic, everyday business of running Toronto actually gets done.

DRAFTThe playbookThe evidence file

What Toronto can actually do on service delivery basics — each move with its costs, its beneficiaries, and its receipts.

v2.0 · 2026-08-11

---

The honest bottom line

Most people experience city government through the pothole, the permit, and the 311 call — and Toronto has real strengths to build on: a 311 line running 24/7 in more than 180 languages, plus genuine, dated movement on gaps this page’s own founding research flagged. The City launched a public 311 Service Standard Dashboard in October 2025, is actively expanding an AI-assisted predictive pilot for pothole management, and grew its digital permitting program (ApplyTO) through 2025 to cover more building types. But the original critique that prompted this work — that Toronto's open-311 data reportedly covered only 30-35% of requests and 6 of 45 divisions — was itself flagged as unconfirmed against a primary source, and this review could not resolve it either way; a real dashboard now exists where there used to be only an unresolved question, which is a genuine improvement, but not proof the original gap has closed by any specific amount. The same pattern holds elsewhere: permit-processing figures found this review suggest actual turnaround still runs longer than the Building Code Act's own statutory maximums, even as the digital-modernization program expands, and pothole-filling volume keeps growing — over 250,000 filled in 2025 — but nothing in the evidence separates how much of that is the predictive pilot actually working versus simply more crews doing more reactive filling. Several of the newest figures here (the 2025 pothole total, ApplyTO's specific "28 days faster" claim, the permit-turnaround ranges) come from secondary, aggregator-style sources rather than the City's own primary data, and are flagged as needing confirmation rather than presented as settled.

Publish the actual 311 coverage number, not an unconfirmed one. (a recommendation card) The City already runs a real 311 transparency dashboard as of October 2025 — the missing piece is a specific, numeric, regularly-updated statement of what share of 311 requests and how many of the City's 45 divisions it actually covers, replacing a figure that has circulated publicly without ever being confirmed against a primary source. This is a documentation addition to a program that already exists and is already funded — genuinely low-cost, genuinely high-clarity.

Prove the pothole prediction is doing something, before scaling it further. (a recommendation card) Toronto is expanding an AI/forecasting pilot for pothole management, and the raw output numbers look good — but output volume alone doesn't show whether prediction is finding problems before residents report them, or whether the city is just spending more on the same reactive approach. A targeted evaluation, comparing prediction-flagged locations against a fair comparison group, would answer that question directly before the City commits to expanding the approach into new service categories.

What this office does not settle. Neither the original 30-35% transparency figure nor its replacement has been confirmed against a primary source — a dashboard now existing doesn't close that question by itself. The predictive pilot's own causal effect on outcomes is genuinely unknown, not just under-documented — nobody has yet isolated it from the general growth in maintenance spending. Several of the newest, most specific figures here — the 2025 annual pothole count, ApplyTO's turnaround-reduction claim, current permit-processing time ranges — rest on secondary sources that should be checked against the City's own data before anyone repeats them as settled fact. And the deepest question from this page’s original research remains open: how much of Toronto's service performance gap is underfunding, and how much is management — new programs existing doesn't resolve that question, it just shows the City is actively working on delivery in the meantime.

---

a recommendation card — Complete and Independently Audit the 311 Transparency Dashboard's Coverage

Card id: a recommendation card · Issue: government-that-works-basics · Backgrounder: our research file for that page · Trust: carried-forward

Problem

The master briefing's central transparency critique — that Toronto's open-311 data covered only ~30-35% of requests and 6 of 45 divisions — was itself flagged by the master briefing as unconfirmed against a primary source [backgrounder, "311: from partial transparency to a real published dashboard"]. This review confirms the City has since launched a real, dated 311 Service Standard Dashboard (October 2025) covering a named set of service areas, but neither the master briefing's original gap figure nor how much of it the new dashboard closes has been independently confirmed [backgrounder, "Key tensions / tradeoffs"]. This card addresses only the coverage-verification gap — not whether 311 service itself is adequate, a separate, broader question this page’s evidence does not fully resolve.

Action

The City publishes a specific, numeric statement of what share of total 311 request volume and how many of the City's 45 divisions the new Service Standard Dashboard and the underlying open-data feed actually cover, updated on a fixed schedule (e.g., annually alongside the dashboard's own data refresh), replacing the ambiguous, unconfirmed figure that has circulated in prior public discussion of Toronto's transparency performance.

Jurisdiction split

Cost

Order-of-magnitude: low — a reporting/documentation addition to an already-funded, already-operating dashboard program, not a new system build. No specific cost comparator was located this review, but the marginal cost of adding a coverage-disclosure statement to an existing published dashboard is plausibly minimal relative to the dashboard's own existing operating cost. Flagged: no specific costed comparator identified; this is a qualitative, not sourced, cost characterization.

Funding path

Within the Customer Experience Division's existing operating budget for the 311 Service Standard Dashboard program, which is already funded and operating as of October 2025.

Who benefits, and how

Toronto residents and civil-society researchers/journalists, via a resolved, citable, current figure for 311 transparency coverage, replacing an unconfirmed number that has circulated in public discussion since before the master briefing's own writing; the City's own credibility on transparency claims, via closing a gap the master briefing itself flagged as needing to be "checked or softened before public use."

Who bears the cost, and how

City taxpayers, via the Customer Experience Division's existing operating budget — no new distinct cost centre identified as required.

Who benefits from the status quo

No beneficiary identified in the backing backgrounder's Cui Bono section [backgrounder, "Cui Bono"].

ROI (four dimensions) — schema v2

(a) Financial ROI

Not separately quantified — a low-cost documentation addition to an existing program, not a spending program with its own return. No comparator identified. Confidence: low — a genuine gap, though the underlying action's cost is plausibly trivial.

(b) Economic ROI

Not yet estimable; not applicable in the traditional sense — a transparency/documentation action, not an economic-activity-generating program. No comparator identified. Confidence: low.

(c) Social ROI

Directionally supported by the backgrounder's own finding that a real transparency upgrade already exists but its actual coverage remains unconfirmed — closing that specific gap directly serves the trust-building case the master briefing makes as its central thesis (competent, transparent basics earn the trust the rest of the platform depends on) [master briefing-carried-forward §The strongest case FOR, item 1]. Confidence: medium — the trust-building logic is well-established in the master briefing; this specific action's own marginal trust effect is not independently measured.

(d) Environmental ROI

Not applicable — a documentation/reporting action has no material environmental footprint or benefit. Confidence: high — genuinely neutral, stated plainly rather than left thin.

Evidence

Confidence & uncertainties

Medium-high confidence this is a low-cost, high-clarity action directly responsive to a specific, named gap in the evidence base (an unconfirmed figure the master briefing itself flagged). Lower confidence on the precise mechanism the City would use to compute and verify the coverage figure, which is not addressed in this page’s sources.

Status

DRAFT — blocked on: a primary-source data analysis of the underlying 311 CKAN dataset to establish a baseline coverage figure (out of scope for this page’s live-discovery method), fairness and legal review.

---

a recommendation card — Independently Evaluate the 311 Predictive-Maintenance Pilot's Own Causal Contribution

Card id: a recommendation card · Issue: government-that-works-basics · Backgrounder: our research file for that page · Trust: carried-forward

Problem

Toronto is actively expanding an AI/predictive 311 pilot for pothole management, and pothole-filling volume has grown substantially (from 87,925 in Q1 2025 alone to a reported 250,000+ across all of 2025) [backgrounder, "Predictive/proactive service"]. But volume filled is an output measure, not evidence the prediction itself — as opposed to simply more crews and more budget — is doing the work; no source located this review isolates the pilot's own causal contribution [backgrounder, "Key tensions / tradeoffs"]. This card addresses only the evaluation-design gap — not whether to continue or expand the pilot, a separate decision this card does not make for the City.

Action

The City commissions or conducts an evaluation specifically isolating the predictive/forecasting pilot's own marginal contribution to service outcomes (e.g., comparing prediction-flagged locations' repair timelines against a comparable non-flagged control, or a similar quasi-experimental design), distinct from simply reporting aggregate output volume, before further scaling the pilot to additional service categories beyond potholes.

Jurisdiction split

Cost

Order-of-magnitude: low, consistent with a program-evaluation study rather than new infrastructure — no specific comparator cost was located this review for a 311-predictive-analytics evaluation specifically. Flagged: no costed comparator identified.

Funding path

Within Transportation Services' or the Customer Experience Division's existing program-evaluation or research budget, if one exists; not confirmed as a currently budgeted line item in this page’s sources.

Who benefits, and how

Toronto residents and City budget decision-makers, via a clear answer to whether the predictive pilot itself is worth its own marginal cost as the City considers scaling it beyond potholes — directly serving the master briefing's own "genuine value for money, not cosmetic efficiency" standard [master briefing-carried-forward §The strongest case AGAINST, "Genuine value for money is not service cuts in disguise"].

Who bears the cost, and how

City taxpayers, via whichever division's budget funds the evaluation.

Who benefits from the status quo

No beneficiary identified in the backing backgrounder's Cui Bono section [backgrounder, "Cui Bono"].

ROI (four dimensions) — schema v2

(a) Financial ROI

Not yet estimable — the evaluation itself is a small cost; its finding could support either continued investment or reallocation, but the return depends entirely on what the evaluation finds, which this card cannot pre-determine. No comparator identified. Confidence: low — appropriately so, since this card's own action is designed to produce the missing evidence, not assume its conclusion.

(b) Economic ROI

Not yet estimable. No comparator identified. Confidence: low.

(c) Social ROI

Indirectly supported by the master briefing's own "proactive over reactive" success criterion [master briefing-carried-forward §What determines success vs failure, item 4] — an evaluation that confirms the pilot works would strengthen the case for the proactive-service shift the master briefing already endorses; one that finds no marginal effect would be equally valuable information, since it would redirect resources rather than continue an unproven approach. Confidence: low-medium — the value of the evaluation itself is well-supported by the master briefing's own logic; the underlying pilot's actual effect is unknown.

(d) Environmental ROI

Not applicable — an evaluation study has no material environmental footprint or benefit distinct from the underlying pilot it studies. Confidence: high — genuinely neutral.

Evidence

Confidence & uncertainties

Medium confidence this evaluation is a genuinely useful, low-cost action given the master briefing's own emphasis on "genuine," not cosmetic, value for money. Low confidence on what the evaluation would actually find, which is precisely the point — this card does not presume the pilot works or doesn't, only that the current evidence base (output volume alone) cannot answer the question either way.

Status

DRAFT — blocked on: confirmation of whether Transportation Services or CXD already has an internal evaluation of this kind under way (not identified in this page’s sources), fairness and legal review.

---

Production record

Drafting record

Status: DRAFT v1.0 · Date: 2026-07-14 · · Backgrounder: our research file for that page. Provenance: cards draw only on the backgrounder's carried-forward and NEW-cited claims; no new factual claims are introduced in card prose beyond what the backgrounder already establishes, per the L6 template's firewall discipline. Author voice: The Unknown Soldier.

v2.0 restructure (2026-08-11, a recorded standing decision/PLAYBOOK conversion, Lane L3b): opened with "The honest bottom line," adapted from archive/dayone/government-that-works-basics.md (retired day-one memo, a recorded standing decision); each card tightened, verbose ROI Range/Comparator-source/Confidence blocks collapsed into flowing one-line-per-dimension form under the file's existing "(a)/(b)/(c)/(d)" ROI wrapper structure; per-card File:/Status: header fields dropped as redundant with the version line above; all citation tokens (carried-forward tags) preserved verbatim.

About this file