4 ways Toronto and Vancouver water bylaws shape smart irrigation design

What to take away

Toronto Water restrictions that change controller design

Toronto Water enforces outdoor water use rules in the Toronto Municipal Code, Chapter 681 (Water Supply), at section 681-9. They apply to anyone connected to the municipal supply, which covers most detached homes and many townhouse complexes in Toronto.

The season runs May 15 to September 30. Even-numbered addresses may water on even-numbered days, odd on odd, and only between 6 a.m. and 9 a.m. or 7 p.m. and 9 p.m.

Those hours leave little slack. A controller has to hold the schedule and shift it when a rain event cancels a cycle. The bylaw also requires a working rain sensor on automated systems, so a sensor terminal is not an optional extra.

Ontario frost dates shorten the season. Toronto's last spring frost typically falls in early May and the first fall frost in mid-October, so the controller needs a seasonal shutdown that matches.

The provincial rules behind the municipal bylaws are on the e-Laws statute page for Ontario water and equipment rules.

A designer who ignores the calendar ends up with a timer that waters on the wrong day and a homeowner who gets a warning letter. The fix is a controller that tracks the date, the address parity and the sensor state.

Enforcement usually starts with a warning letter. A repeat offence can bring a set fine. Toronto publishes its set fines in the municipal code, and each Metro Vancouver member city publishes its own penalty schedule in the water shortage bylaw.

Metro Vancouver conservation bylaws and their design impact

Metro Vancouver does not write one watering bylaw for the region. Its board approves the Water Shortage Response Plan, which runs May 1 to October 15 across four stages, and each member municipality enforces the current stage in its own bylaw.

Cities commonly title that instrument a water shortage response bylaw, and the numbers change when councils amend them. Vancouver, Burnaby and Richmond each publish the current number with the bylaw text on the city website. A contractor working across Burnaby, Richmond and the City of Vancouver reads three sets of wording, three day-of-week patterns and three sets of dates.

The stages set the days. Stage 1 allows lawn watering once a week in the morning. Stage 2 keeps lawns at once a week in the morning and adds limits on other outdoor uses. Stage 3 stops lawn watering. Stage 4 stops all outdoor use except hand watering of food gardens, trees and shrubs.

The plan uses the word morning rather than a clock time. Each member bylaw sets the window, and member cities commonly open it from 4 a.m. to 9 a.m. in Stages 1 and 2. A controller profile needs the local window, not the regional wording.

The coastal climate pushes design the other way. Vancouver is wet for much of the year, so a rain sensor that only stops a cycle is not enough. A light shower after a long dry spell leaves clay soil dry below the surface, and a roof-mounted sensor never knows.

BC's provincial rules sit above the municipal bylaws and shape what a conservation plan can require. The BC environmental protection and sustainability rules set that frame, and the BC government entry point is where a homeowner checks current provincial restrictions during a drought.

A smart controller in Metro Vancouver needs a local schedule profile loaded at commissioning, not a single default. That is the difference between a system that passes inspection and one that gets shut off in July.

Way one: mandatory rain sensing and shutoff logic

Rain sensing is the first rule that changes hardware. Toronto's Chapter 681 requires an automated system to stop when the sensor says it has rained, and most Metro Vancouver municipalities carry a version of the same rule with different wording.

A controller without a sensor input cannot be installed legally in either city. The sensor belongs to the base system, not to the accessories list. Controllers such as Hunter's Pro-HC and Rain Bird's ESP-Me ship with sensor terminals, and wireless kits such as the Hunter Rain-Clik or the Rain Bird WR2 do the same job without a wire run.

Most rain sensors trip somewhere between 3 mm and 6 mm (1/8 to 1/4 inch) of rain, and the better models let a technician set that threshold.

Shutoff logic matters more than the sensor itself. A sensor that only delays a cycle by a few hours does not meet the intent. The system should skip the cycle and hold until the next permitted day.

Here is how to set it up:

A system that fails step four is the one a bylaw officer flags. If you are choosing sensor types, the difference between a soil moisture sensor vs tensiometer changes how well the shutoff logic works in heavy clay soils.

Way two: schedule windows and permitted watering days

Permitted watering days are the second rule that changes scheduling. Toronto ties them to address parity and the 6 to 9 a.m. and 7 to 9 p.m. windows. Metro Vancouver municipalities typically cap lawns at one day a week, with the day set by address and by city.

A smart controller has to treat the watering day as a constraint, not a preference. If the profile says Tuesday and the address is odd-numbered, the cycle moves to the next permitted day.

That is where an evapotranspiration override and a window collide. A controller that waters on a non-permitted day because the ET value is high is still breaking the bylaw. The override works inside the window, not around it.

Rain Bird's ESP-Me and Hunter's Hydrawise both store more than one named schedule. Rachio's Flex Monthly schedule recalculates run times from local weather, but the permitted days still go in by hand.

Canadian buyers should know the WaterSense label is a US EPA program. It does not replace Toronto Municipal Code 681-9 or a Metro Vancouver municipal bylaw.

This is also where planning smart irrigation pays off. The schedule is a legal document as much as a watering plan.

Way three: soil moisture and evapotranspiration overrides

Soil moisture and ET overrides are the third rule, and they are why smart controllers exist. Toronto and Metro Vancouver both allow a system to adjust outside the fixed schedule when moisture or ET data shows the water is needed.

That exemption is narrow. The system can skip or shorten a cycle when the soil is already wet, and it can add water when ET demand is high. It cannot water whenever it likes.

The practical build is a controller that reads local weather and soil moisture, then adjusts run times. A rain sensor alone will not do it. You need a moisture threshold and a daily ET figure.

In BC, the Farmwest network run with the BC Ministry of Agriculture and Food publishes reference evapotranspiration from stations across the province. In Ontario, irrigation contractors pull ET and rainfall numbers from Environment and Climate Change Canada climate stations.

Hardware that feeds the override includes Hunter's Soil-Clik, Toro's Turf Guard sensors and the Rain Bird ET Manager cartridge. WeatherTRAK controllers build the schedule from ET rather than from a clock.

Environment and Climate Change Canada provides the weather data that feeds many of these systems. The federal environment and natural resources hub is the starting point for the national picture on water and conservation rules.

For a homeowner, the gain is a lower water bill and a yard that is not overwatered. For a contractor, the gain is a system that can prove it responded to conditions.

Way four: documentation and inspection readiness

Inspection documentation is the fourth rule and the one most often skipped. A bylaw officer or water utility can ask for proof that the rain sensor works and that the schedule follows the permitted days.

When an officer asks, the proof is a short set of records:

A controller that logs run times, sensor events and schedule changes makes that easy. Rachio and Hydrawise both keep a history in the app that can be exported. A basic timer leaves the homeowner arguing from memory.

Keep one file per property: the sensor test result, the controller schedule, the bylaw reference and the date of the last check. Update it whenever the schedule changes.

Systems with a chemical injector or a booster pump need a backflow preventer, usually a reduced pressure zone assembly. CSA B64.10 covers installation and CSA B64.10.1 covers field testing, and the assembly is tested annually.

Toronto Water's Cross Connection Control program wants that test report on file, and the City of Vancouver collects the same reports for assemblies on its water system. A certified tester typically charges $75 to $200 per device, and a plumbing permit for new irrigation wiring or a new connection usually runs $150 to $400 at both cities.

A maintenance routine supports this. A smart irrigation maintenance calendar keeps the sensor clean and the log current, which is what an inspector wants to see.

Use this checklist before the season starts:

A system that passes this checklist is also one that smart irrigation earns its keep on, because the records show what it actually did.

Designing one system that satisfies both cities

Toronto and Vancouver pull design in opposite directions. Toronto is dry in summer and strict about days. Metro Vancouver is wet and strict about runoff and stage changes.

One product line can serve both if the controller holds several named profiles, so a Toronto odd-numbered address and a Burnaby townhouse never share a default. Start with a rain sensor plus a soil moisture input, add ET data for the override, then build one schedule profile per municipality and load it at commissioning.

For buyers, the question is whether the product is real smart irrigation or a garden-store timer with an app. The difference shows up the day a bylaw officer asks for a log.

Common questions