uniteTOlove.ca

Development Charges & Building Permits — Playbook

The fees and permit delays builders blame for expensive housing — what they actually add to the cost of a new home.

DRAFTThe playbookThe evidence file

What a mayor does about a development-charge framework that has whiplashed policymakers, developers, and City Finance staff alike since 2022 — without picking a side in the fight over whether DCs are too high or too low.

The honest bottom line

Toronto's development-charge rules have changed five separate times since 2022, from both Council and Queen's Park, while the province's own documents now admit its 1.5-million-homes target won't be hit at the current pace. The week-one job on this file isn't picking a side in a fight over whether DCs are too high or too low — it's fixing the predictability problem that's real regardless of which side is right, and being honest about a legislative change (Bill 17) this office doesn't yet have a clear read on. The City's own Comprehensive Development Charges Review — the vehicle for any serious rethink of Toronto's DC framework — is "in the early stages... expected to continue into 2027," with no published interim milestones. Even AMO, the body that watches this most closely, had to substantially revise its own estimate of Bill 23's cost after the fact, from a preliminary $5.1 billion over nine years down to roughly $1 billion a year — a sign that policy volatility itself is a cost, on top of whatever the substantive rate changes turn out to mean. The City's own page confirms Bill 17 changed the Development Charges Act again in 2025, with provisions taking effect June 5 and November 3 — but nothing in this office's current evidence base says what those changes are worth to Toronto in dollars, unlike the well-documented effects of the 2022 and 2024 changes. That's a plain, named gap, not a political dodge. The pace of provincial legislative change on development charges — three DC Act amendments in three years — is not something Toronto sets or can reliably predict. Neither is the broader macroeconomic climate the province's own 2026 Budget blames for "subdued" 2026 construction activity. Nothing here promises to hit the province's 1.5-million-homes target on Toronto's own authority; that target's own shortfall, on the government's own numbers, is a provincial-scale problem this office's DC and permitting levers touch only at the margin. Neither action below is a rate cut or a rate increase — both are predictability and transparency fixes to a framework that has genuinely whiplashed everyone involved since 2022. The province's own target math is the harder, bigger problem, and it's not this office's to solve alone; what this office can do is make sure Toronto's own piece of the framework stops adding avoidable uncertainty on top of a housing shortfall everyone, including the province itself, now agrees is real.

---

a recommendation card — Complete the Comprehensive Development Charges Review With a Published Stability Commitment

Card id: a recommendation card · Issue: development-charges-building-permits · Backgrounder: our research file for that page §"What development charges are and Ontario's repeated legislative amendments to them" · Trust: New load-bearing findings

Problem

Toronto's DC framework has changed at both the municipal and provincial level at least five distinct times since 2022 (Bill 23, 2022; the City's 2022 DC Background Study; Bill 185, 2024; the City's June 2025 rate update and EX24.2/MM32.5 Council changes; Bill 17, 2025). Even AMO, the body most directly tracking DC-revenue impact on municipalities, revised its own Bill 23 cost estimate substantially after initial passage (from a preliminary $5.1 billion over nine years to approximately $1 billion annually) — evidence that policy volatility itself, independent of which direction any single change moves DC revenue, is a real planning cost for both the City and developers pricing multi-year projects. The City's own Comprehensive Development Charges Review is "in the early stages... expected to continue into 2027," with no published interim milestones.

Action

Council directs staff to publish a public timeline with named interim milestones for the Comprehensive Development Charges Review (currently open-ended through 2027), including a commitment to a minimum notice period before any further rate or bylaw structural change outside that Review's own conclusion.

Jurisdiction split

Cost

Negligible, non-capital — a scheduling and communications commitment, not a new program. Named comparator: the same order of cost as the City's own routine DC Background Study and bylaw-update process it already performs on a multi-year cycle.

Funding path

Existing City Finance/Development Charges division operating budget; no new funding mechanism required.

Who benefits, and how

Developers and builders planning multi-year projects, via reduced regulatory-uncertainty cost when pricing projects against a known DC trajectory rather than three unplanned legislative changes in three years. The City's own budget office, via more predictable DC-reserve revenue forecasting.

Who bears the cost, and how

City taxpayers, via the negligible administrative cost of the commitment itself. No other named cost-bearer — this is a low-cost transparency/predictability action, not a rate change in either direction.

Who benefits from the status quo

No beneficiary identified — the backgrounder's Cui Bono table is empty; this is characterized as a policy-design and intergovernmental-coordination problem, not a case with an identified financial beneficiary, though development-industry lobbying activity around the Bill 23/185/17 sequence is flagged as an unexplored lead for a future Accountability Observatory pass.

Financial ROI

Not separately quantified — no source models a specific dollar value for reduced regulatory uncertainty. The qualitative case (reduced planning-cost volatility for both the City and developers) is real but not converted into a range here.

Economic ROI

Not yet estimable — no source models a specific economic effect of DC-policy predictability itself, as distinct from DC rate levels. The backgrounder's own BC-vs-Ontario C.D. Howe comparison addresses capital-spend timing, not legislative predictability, and is not directly transferable to this narrower claim. Confidence: low — genuine gap.

Social ROI

Directional only: to the extent regulatory predictability supports more consistent housing-construction planning, it indirectly supports Ontario's stated (though currently off-track) 1.5-million-homes goal. No source quantifies this specific card's own contribution to that goal, and this card does not claim one.

Environmental ROI

Genuinely neutral — a scheduling/communications commitment does not itself change construction volume, land use, or emissions. Any environmental effect flows from whatever development activity DC policy eventually supports, not from this card's own action. Confidence: high.

Evidence

Confidence & uncertainties

Medium confidence on feasibility (a scheduling/communications commitment is low-complexity and within clear existing authority). Low confidence on quantified ROI in any of the three modelled dimensions — this is honestly a predictability/governance-quality card, not a program with a modelled financial or economic return, and it is presented as such rather than forced into a false-precision range.

Status

DRAFT — blocked on: nothing structural. Would benefit from direct confirmation with the City's Development Charges division of the Comprehensive Review's actual current internal milestones, if any exist informally but are not yet public.

---

a recommendation card — Track and Publicly Report Bill 17's Actual Local Effect on Toronto's DC Revenue

Card id: a recommendation card · Issue: development-charges-building-permits · Backgrounder: our research file for that page §"What development charges are and Ontario's repeated legislative amendments to them" / "Open questions / data gaps" · Trust: New load-bearing findings

Problem

Bill 17 (2025) further amended the Development Charges Act, with provisions coming into force on two separate 2025 dates (June 5 and November 3) — but this page’s own evidence base, including its inherited master briefing, does not yet characterize Bill 17's specific provisions or their dollar effect on Toronto's DC revenue, unlike the well-documented effects of Bill 23 (2022) and Bill 185 (2024). This is a genuine, named information gap, not a settled fact being ignored.

Action

Council directs City Finance staff to publish a plain-language explainer of Bill 17's specific provisions and a dollar estimate of its net effect on Toronto's DC revenue, using the same methodology AMO used to revise its own Bill 23 estimate, within the City's next DC-related budget or Review reporting cycle.

Jurisdiction split

Cost

Negligible, non-capital — an analysis and reporting task using existing City Finance staff capacity, on the same order as the City's routine DC bylaw and rate-schedule reporting.

Funding path

Existing City Finance operating budget; no new funding mechanism required.

Who benefits, and how

City Council and residents, via a clear, City-sourced account of a legislative change that directly affects municipal infrastructure funding capacity but currently lacks any public local-impact estimate. Future policy analysis (including this project's own backgrounder) that currently lacks this data point.

Who bears the cost, and how

City taxpayers, via the negligible staff-time cost. No other named cost-bearer.

Who benefits from the status quo

No beneficiary identified — the backgrounder's Cui Bono table is empty.

Financial ROI

Not applicable in the traditional sense — this is an information/transparency action, not a program with a fiscal return. The action's value is in enabling better-informed future fiscal decisions, not in itself generating revenue or savings.

Economic ROI

Not yet estimable — an information-transparency action has no direct economic effect of its own. Confidence: low, and a poor fit for this action type rather than a real gap in the evidence.

Social ROI

Genuinely neutral — a reporting action with no direct wellbeing or cohesion effect.

Environmental ROI

Genuinely neutral — an analysis/reporting action does not itself change construction volume or land use. Confidence: high.

Evidence

Confidence & uncertainties

High confidence on feasibility (low-complexity, within existing authority, analogous to work the City and AMO have both already done for prior DC-Act amendments). This card exists specifically because of a confirmed evidence gap (Bill 17's effects are uncharacterized in this page as of this review) — its own justification is the gap itself, stated plainly rather than inflated.

Status

DRAFT — blocked on: nothing structural. This card and a recommendation card are complementary, not sequential — either could proceed independently.

---

Production record

Drafting record

Version: v1.0 (playbook conversion) · Original date: 2026-07-14 · Status: DRAFT · What this page draws on: carried-forward (carried forward from this page’s own sources source document) + newly-discovered live sources (this review) + staged our claim-mining track discovery (2026-07-13, not independently re-fetched this review, flagged per-item). Author voice: The Unknown Soldier.

Playbook conversion (2026-08-11, Lane L3a): opened with "The honest bottom line" adapted from archive/dayone/development-charges-building-permits.md (a recorded standing decision retired day-one memo, kept as history in archive/); ROI sections tightened, repeated "not yet estimable / genuine gap" boilerplate collapsed to one honest line each, matching that page's recommendation cards's playbook shape. No a formally registered claim tokens present in this file; all NEW/carried-forward citations preserved unchanged.

About this file