Transition Zones

The concept

Where the approach could apply, and how to assess it.

Transition Zones plan for a change in housing and uses across the properties between a main street or transit area and the neighbourhood beyond. Selection criteria and classifications help determine where that change should occur and what it should look like.

How the idea works

Across several properties.

A rear setback or stepback adjusts an individual building. A Transition Zone considers the relationship among several properties. It asks where small apartments, multiplexes, townhouses and suitable neighbourhood uses could contribute to a gradual change in scale.

Development could take place through conversions, additions and new buildings over time. The framework should allow useful buildings to remain and give individual owners practical options. It should not depend on every property being assembled or redeveloped.

The original proposal used roughly 100 to 200 metres as an initial study depth, with boundaries to be refined through local analysis. A distance helps identify where to look. Lot patterns, services and other conditions then determine the extent and form of change.

Conceptual street showing a retained older house, new small apartment buildings and buildings of different scales across neighbouring properties
A gradual change can be achieved through a mix of retained buildings and new development. Conceptual rendering from The Space Between (2026), by Blair Scorgie.

Selection criteria

Choosing suitable areas.

The original framework called for a coordinated review across Toronto’s four planning districts. A contemporary assessment should retain that citywide perspective while testing the conditions below.

01

Transit and centres

Identify nearby centres and station areas, then examine service frequency, reliability, capacity and the actual walking and cycling connections. Proximity alone is an incomplete measure.

02

Community services and amenities

Assess schools, childcare, libraries, parks, recreation and other services. Establish current use, available capacity, unmet needs and opportunities to expand or share facilities.

03

Infrastructure and access

Review water, sewer, drainage, utilities, emergency access, waste collection and the street network. Identify upgrades and responsibilities early enough to inform the permissions.

04

Lots, streets and blocks

Test lot widths and depths, corners, lanes, building orientation and possible assembly. Distinguish what can work on an individual property from what would require a coordinated approach.

05

Housing need and delivery

Consider household needs, accessibility, tenure, existing rental housing and displacement. Test realistic land, construction, financing and operating costs for the forms being proposed.

06

Environmental and built conditions

Account for trees, natural hazards, heritage, sunlight, privacy and the public realm. Some conditions will limit an area’s potential; others can be addressed through design or investment.

Refine the boundary after the assessment.

Follow the lot pattern, streets, lanes and local constraints. Publish the reasons for including an area, the intended forms of change and any improvements needed to support them. The result should explain the planning judgment behind the map.

Classifications

A response to
local conditions.

The original proposal grouped areas by transit mode and performance against the evaluation criteria. The classification would then guide the extent and intensity of change. It was a method for developing local responses, with the detailed classes and standards still to be worked out.

Proposed classification process: assess transit context and local conditions together, then define mapped boundaries, housing and uses, built form standards and delivery requirementsTRANSIT CONTEXTGO / commuter rail · subway · LRTStreetcar · bus rapid transit · busFrequency, capacity and actual connectionsLOCAL CONDITIONSLots and blocks · housing needs · feasibilityServices · infrastructure · constraintsExisting and planned neighbourhood contextClassify the area and test a responseMapped extentHousing and usesForm and standardsDelivery requirementsA proposed method for developing local classifications. No fixed classes, heights or distances are prescribed here.

This proposed classification process retains the original two considerations: transit context and the conditions found through local assessment.

A subway or GO station, a streetcar corridor and a bus-served main street offer different opportunities. The service itself is only part of the assessment. Two areas served by the same mode may have very different lot patterns, infrastructure needs and development economics.

A classification should translate those findings into the geographic extent of the area, the housing forms and non-residential uses to be permitted, the scale of development, and the improvements or conditions needed to support it. Where station-area permissions already apply, the framework should work from that existing policy direction.

Illustrative contextQuestions to testWhat the response should establish
Major transit stationWhich permissions are already in effect? How do the local streets, station entrances and nearby services connect? Which properties can accommodate the intended forms?Coordinate with approved station-area policies and zoning work, then define suitable forms and supporting improvements for adjacent blocks.
Frequent surface-transit corridorWhat service and capacity are available? How do stops, crossings, main-street businesses and the residential lot fabric relate?Identify which blocks behind the corridor can support additional housing and compatible uses, and how people will reach transit and daily destinations.
Shallow lots or a constrained blockCan the intended housing fit on existing lots? Would a lane, assembly, different massing or another access arrangement help? Are there conditions that limit change?Set workable standards or a coordinated approach for that condition. Avoid importing an envelope that cannot produce a usable building.
Next / ImplementationTurn the framework into permissions