In-ground irrigation: understand zones, sprinklers and watering changes

What carries the water, and what tells it to start?

An in-ground irrigation system brings water to selected parts of a yard through buried pipes and watering heads. A controller tells a valve when to let water into a group of those pipes. The water route and the electrical instruction have different jobs: a timer is not a pump, and a message on its screen is not a flow measurement.

Follow the familiar parts. The supply brings water to the system. Any applicable backflow protection has a drinking-water protection job. A zone valve controls a branch. Buried pipes carry its water to sprinkler heads or other distribution devices. The controller provides the watering request; installed sensors may affect that request.

The actual supply might differ from the example in a diagram. Ask the provider to identify where yours comes from, whether a master valve or pump arrangement is present, and which records describe it. A municipal-water example cannot establish the equipment or permissions for a different supply.

Begin with existing records and an ordinary look from dry, stable ground. Do not open electrical compartments, lift buried equipment out, dig for pipes or operate unfamiliar valves to discover the route. A significant active water problem needs prompt help from the responsible provider or utility, rather than a longer observation exercise.

Numbers identify the parts explained below.

Request wateringControl the branchDistribute water

Learning illustration • see the labels and limits below.

The explanations below remain available as you explore.

1. Controller

   Requests watering according to its instructions. The pictured box is closed and has no visible control connection.

2. Zone valve

   Controls water into the branch. Its visible body does not establish the actual model or operating condition.

3. Pipe and heads

   The continuous conceptual pipe joins three head bodies. Actual supply, distribution and depth need their own records.

What does this illustration leave out?

Upstream supply, backflow protection and control wiring are not drawn. No burial depth, valve operation, measured flow or installed condition is established. Read the part names and jobs below the picture.

A BETTER QUESTION

Which station, valve and heads are recorded as one zone in this yard?

Explore this with HomeAI ↗Opens an editable question. Nothing is sent until you choose to send it.

What is a zone, and how is it different from a programme?

A zone is a group of watering outlets served through a controlled branch. On a controller, a station is the numbered output associated with a valve. A programme is a set of watering instructions. These names connect the equipment to the schedule, but do not tell you which patch of lawn a handwritten number actually serves.

In the named Rain Bird ESP-TM2 manual, each station terminal supports one valve solenoid: the electrical part of that valve control. The manual separately describes programmes, start times, station run times and watering days. This is a useful model example, not a wiring instruction or a promise that another controller uses the same arrangement.

Ask for a zone map that links each controller station to the corresponding valve and watering area. Keep uncertain labels marked uncertain. “Front lawn” on an old controller card may describe a former arrangement after a planting bed, head or valve was changed.

A zone is therefore a useful unit for describing a complaint: which recorded area changed, and when? It is not a guarantee of even coverage or proof that every buried connection was documented. Ask the provider whether the map reflects the installed system now.

Numbers identify the parts explained below.

Name the yard areaMatch the stationRead the programme

Learning illustration • see the labels and limits below.

The explanations below remain available as you explore.

1. Zone

   Ask which valve and watering area belong to the group.

2. Station

   Match the controller label to the actual valve and zone map.

3. Programme

   Match start times, run times and days to the correct model and actual record.

What does this illustration leave out?

The actual zone map, labels, controller model, field connections and suitable schedule remain unknown. Compare the three names and their jobs below.

A BETTER QUESTION

Does the present zone map match the controller labels?

Explore this with HomeAI ↗Opens an editable question. Nothing is sent until you choose to send it.

Why can the controller show watering while nothing sprays?

The controller starts the chain by requesting valve operation. Water still needs an available supply and a functioning route through the relevant equipment. Separating those jobs helps explain why a lit screen and a dry lawn can occur together without immediately choosing a failed controller.

The ESP-TM2 troubleshooting table lists a supply issue or loose, incorrect or damaged wiring when its watering symbol flashes but the system does not water. It lists sensor and valve-related possibilities for other no-start complaints. Those alternatives belong to that manual; the guide does not turn them into a diagnosis of your equipment.

Record the exact visible message, station name if shown, date and area affected during ordinary permitted operation. Include whether the event involved one area or the whole yard, without starting additional runs to compare them. A screen photograph preserves the message; it cannot show a concealed valve opening or available flow.

Ask the qualified provider what they will assess on the instruction side and the water side. Sensor, controller, field connection, valve and supply questions may require different access. Do not bypass a sensor, open a controller, follow another model’s reset sequence or manually force a valve to test a theory.

Numbers identify the parts explained below.

Record the requestDescribe the water eventAssess both jobs

Learning illustration • see the labels and limits below.

The explanations below remain available as you explore.

1. Controller request

   The message concerns the watering request, not a measured water quantity.

2. Water route

   Supply and the route through the relevant valve and equipment still matter.

3. Assessment

   Ask what the provider will check on both sides without owner bypasses or test runs.

What does this illustration leave out?

No working signal, valve movement, available supply, measured flow or diagnosis is established. Follow the request and water lanes separately.

A BETTER QUESTION

What will the provider assess on the instruction side and the water side?

Explore this with HomeAI ↗Opens an editable question. Nothing is sent until you choose to send it.

Why might the same area seem to water again?

A repeated watering event can be a schedule question before it is a broken-pipe question. Start time means when a programme begins; run time concerns how long a station is requested to water. Confusing those two can make an apparent sequence hard to interpret.

The named ESP-TM2 manual identifies unintended multiple programme start times as one possible cause of excessive watering. A start time is not required separately for each valve in that model’s programme. This explanation does not instruct you to edit settings, or prove that repeated watering in another system has the same cause.

Keep a simple chronology of the events you actually noticed. Separate “the head sprayed again” from “the grass stayed wet.” Record any existing programme information supplied by the provider, a recent service visit and a reported change in who manages the controller.

Ask the provider to match the observed sequence to the present programmes and the correct manual. Also ask whether water continued outside that sequence and whether a valve or other water-route question remains. A programme review can explain a request without proving that the valve opened and closed as intended.

What does backflow protection do here?

Backflow means water moves in the unwanted reverse direction toward a drinking-water system through a connection. Normal irrigation sends supplied water toward the yard. Backflow protection has a separate job from deciding when a zone waters: it addresses that reverse-flow connection.

Calgary’s FAQ describes two mechanisms. Backsiphonage involves lowered pressure or a vacuum on the supply side. Backpressure involves pressure downstream that exceeds the supply pressure. You do not need to create either condition to understand why an irrigation connection deserves its own protection question.

The Calgary programme names several protection types, while its irrigation page gives local examples for in-ground systems. Have the local utility and qualified provider identify the appropriate requirement and actual device for your address. A device name, photograph or another city’s example cannot select or approve yours.

This device is not the wastewater backwater valve that addresses reverse sewer flow. Ask for identification, relevant local records and any actual test report, keeping its date, device and findings together. Calgary notes that internal parts can wear; an installed-looking assembly or a paid visit alone is not a current functioning test.

Numbers identify the parts explained below.

Identify the jobIdentify the routeMatch the local record

Learning illustration • see the labels and limits below.

The explanations below remain available as you explore.

1. Zone control

   Decides which branch receives water; it does not replace applicable backflow protection.

2. Drinking-water protection

   Identify the actual protection device and local assessment records.

3. Wastewater protection

   A backwater valve belongs to a different water route and question.

What does this illustration leave out?

The actual device, local requirement, test result and suitability are not supplied. No device-selection rule applies nationally from this picture. Read these separate jobs; the cards are not connected pipes.

A BETTER QUESTION

Which device, local requirement and actual report apply to this address?

Explore this with HomeAI ↗Opens an editable question. Nothing is sent until you choose to send it.

Why has one sprinkler’s coverage changed?

A sprinkler head distributes water into an area. Its nozzle and surroundings matter to the visible pattern. Some distribution devices spray over turf; other arrangements deliver water closer to plant roots. Identify the equipment in the actual zone before comparing it with a general lawn-sprinkler picture.

Calgary’s irrigation guidance identifies broken or clogged heads, leaks and other operating problems as maintenance concerns. It also discusses changing landscape needs and runoff. A short, uneven or redirected spray is useful to report, but does not establish which component caused it.

From an ordinary safe position, describe what you already see: water reaching a path, a head leaning, foliage in the spray path, or a changed area of coverage. Include recent mowing, planting or landscaping history as context. Do not pull up the head, remove its nozzle or clear it while it is operating.

Ask the provider to compare the head, its distribution task and the zone’s present landscape. A new planting bed may raise a design question even when a head still sprays. A photograph cannot measure flow, pressure, even distribution or whether the current equipment suits the plant and soil needs.

Numbers identify the parts explained below.

Describe the patternRecord nearby changesAsk about the cause

Learning illustration • see the labels and limits below.

The explanations below remain available as you explore.

1. Sprinkler head

   Distributes water from its connected branch. The generic form does not identify an installed nozzle or rating.

2. Planting in the path

   Foliage meets the left example’s spray. Ask what changed around the actual head.

3. More open patch

   The right example shows a different setting. It does not prove suitable watering or a repair.

What does this illustration leave out?

The spray shapes give no measured reach, pressure, volume, even distribution or suitable head spacing. No real dry patch is diagnosed. Compare the two garden examples without treating them as measurements.

A BETTER QUESTION

What changed around the head, and what should the provider compare with the original zone plan?

Explore this with HomeAI ↗Opens an editable question. Nothing is sent until you choose to send it.

Does a wet patch or dry patch prove a buried leak?

A wet patch tells you where water is visible, not necessarily where it started. Irrigation, rainfall and surface drainage can all matter to the story. A dry patch likewise does not identify a failed pipe: the distribution pattern and the landscape’s ability to receive and retain water are separate questions.

Calgary identifies installation problems, construction damage, freezing and thawing, and improper winterization as possible leak causes. These are alternatives for an assessment, not a conclusion from the season or a nearby building project. Record the changed area and the timing of relevant work without assigning blame.

The historical BC agricultural manual explains that soil texture, structure and ground cover affect infiltration: how water enters soil. Its water-storage discussion also distinguishes soils and roots. Those basic mechanisms help explain why water application and soil condition both matter; its farm rates and calculations are not a prescription for your lawn.

Report whether the patch was noticed after rain, during ordinary watering, or when no watering was known to be taking place. Keep uncertainty about that timing visible. Do not excavate, pressurize, run extra watering or use a whole-home bill to declare one zone’s leak rate. The provider chooses the appropriate investigation.

How do rain, soil and the season change the question?

Plants use water, and moisture also evaporates from plant and soil surfaces. The BC manual calls that combined process evapotranspiration. Weather changes water demand, while soil and roots affect storage. These mechanisms explain why one fixed schedule is not automatically suitable throughout a Canadian growing season.

Calgary describes controllers that respond to weather or environmental information. The ESP-TM2 manual separately describes an optional rain/freeze sensor and controller choices that affect whether its signal is followed. A sensor-shaped object or a “smart” label cannot establish which information the installed controller currently receives or uses.

Ask the provider which sensor or weather service is actually connected, what it is intended to do and how its operation was assessed. Keep a rain observation separate from a confirmed sensor finding. Do not disconnect a sensor or deliberately water in unsuitable conditions to see what the controller does.

Watering permission is another question. Check current rules with the municipality or water supplier for the address and date, including temporary restrictions. A permitted day does not determine plant need; a weather-based request does not override a local restriction. This guide gives no Canada-wide calendar or timer-setting recipe.

What should spring and freeze-season care cover?

Seasonal preparation concerns more than the controller’s calendar. Water remains part of the physical system, including its valves, pipe routes and distribution devices. Calgary’s guidance recommends professional maintenance and winterization, while identifying freeze-related and improper-winterization damage among possible problems.

Ask the provider to match the seasonal work to the actual equipment, supply and local conditions. Request what was prepared, what was inspected or found, and any remaining access or repair question. A winterization invoice describes its stated visit; it cannot establish the condition of every buried pipe or a later spring assessment.

Keep any required protection-device records separate from the watering schedule. Local programmes and actual models determine their own duties. Do not copy a compressed-air blowout, drainage, isolation, valve or electrical sequence from a generic article. Arrange the appropriate professional scope rather than treating this guide as a shutdown checklist.

Use the existing freeze-preparedness guide for the wider household planning question. This page stays focused on understanding yard watering and preparing a clear irrigation service request.

What changes after landscaping or a new-build handover?

A finished lawn can hide the irrigation route as effectively as an older one. Ask for the zone map, equipment identification and work records while the builder or landscape provider can still explain what was installed. A fresh controller and new sod do not establish complete documentation or an assessed system.

Later planting, fences, paths and ground work can change the setting around heads or introduce a question about buried equipment. Calgary includes construction damage among possible leak causes. A nearby truck or a new walkway is context to investigate, not proof that a pipe was damaged.

Before proposed ground work, have the responsible parties establish which buried services and private irrigation routes need locating and protection. Keep supplied plans and actual locating or assessment records distinct. Do not use this conceptual cutaway or a remembered head position to decide a safe digging route.

Irrigation documentation does not replace the home’s drainage or site records. Link a grading concern to new-home grading stages and a rainwater question to rain and foundation drainage. Where a septic system is present, keep its separate yard-use and location records with the project team.

What could a changed-watering service request look like?

Fictional homeowner Maya notices the front-lawn heads spraying again later in the morning. A separate wet patch appears beside a recently changed planting bed. She has an old controller card but no current zone map. These are invented observations, with no known failed component, measured flow or repair result.

Maya records the events she actually noticed and keeps the two observations separate. She supplies the controller model, old card, landscaping invoice and available seasonal-care record. She does not add watering runs, open a valve box or change settings to produce a clearer demonstration.

She asks two questions. Does the present programme explain the repeated watering request? Separately, what assessment would distinguish water distribution, a pipe or valve concern, and rainfall or surface-water context near the wet patch? Neither the controller label nor the planting invoice answers both.

A useful written report would attach findings to the assessed parts and conditions: the matched programme, identified zone, actual observed operation, any professional measurements and inaccessible areas. This example deliberately ends at the service scope. It supplies no diagnosis, passing backflow test, builder responsibility decision, cost or promised repair.

Numbers identify the parts explained below.

Keep observations separateChoose the recordAsk a scoped question

Learning illustration • see the labels and limits below.

The explanations below remain available as you explore.

1. Repeated spray

   Match the actual event to the correct model and programme record.

2. Wet patch

   Keep rainfall, site context and the stated watering timing visible.

3. Useful records

   Request a scope and findings for each question; do not run extra watering to investigate.

What does this illustration leave out?

All observations and records are fictional. No fault, measured quantity, test result, responsibility decision or successful repair is supplied. This is an invented service request, not a property finding.

A BETTER QUESTION

Which assessed finding would answer each question, and what would remain unknown?

Explore this with HomeAI ↗Opens an editable question. Nothing is sent until you choose to send it.

Who should assess it, and what should the record keep?

Ask an appropriately qualified irrigation provider about the watering route, equipment and landscape task. A backflow question may require the locally recognized tester or plumbing scope; electrical work may require a different qualified trade. Confirm actual credentials and local acceptance for the proposed work, rather than treating one job title as permission for every task.

Request a written scope before the visit: which zone and concern, what access is needed, which existing records will be reviewed, and what testing or measurement is proposed. A pressure or flow result needs its units, location and operating conditions. The household pressure guide explains why an impression of weak flow is a different kind of evidence.

Keep the model/manual edition, zone map, dated observation, task description, findings and remaining questions together. If equipment or programming changes, ask what the updated record should show. The home-care record guide helps retain that history without converting an invoice into an unrestricted condition finding.

For a purchase or sale, ask the actual realtor and technical team how they will coordinate records, access and unresolved irrigation questions. Confirm any claimed HAUSE training and available specialist scope. A knowledgeable adviser helps connect the documents and decisions; they do not replace the provider’s assessment or promise concealed pipes are sound.

Go to the source.

Original HomeAI explanation informed by these public references. Sources support the underlying guidance; they have not reviewed or endorsed HomeAI. Diagrams are conceptual, and calculator outputs depend on your inputs.

Canadian overview with a Calgary municipal example, the named Rain Bird ESP-TM2 manual and historical BC agricultural soil/climate context. Actual equipment, local water-supplier rules and qualified scope must be identified separately. No national watering calendar, backflow-device selection or owner installation/winterization procedure is supplied.

• City of Calgary · Efficient irrigation
  Where this reference applies

  Jurisdiction: Calgary, Alberta; municipal irrigation education

  Edition: No substantive publication or revision date established; the 2026 footer and dated price examples are not an edition date.

  Source reviewed: 2026-10-06 · America/Edmonton

  Complete substantive body read. Automatic-system parts, controller signals, sprinkler distribution, changing weather, possible damage and professional seasonal care. Calgary device examples remain local. Owner start-up/shutdown, catch-container experiments, numerical watering schedules, test intervals and cost figures are excluded.

• City of Calgary · Cross connection frequently asked questions
  Where this reference applies

  Jurisdiction: Calgary, Alberta; named local drinking-water programme

  Edition: No substantive publication or revision date established; capture time is not a publication date.

  Source reviewed: 2026-10-06 · America/Edmonton

  Complete substantive body read. Cross connection, unwanted reverse flow, backsiphonage/backpressure, mechanical protection and qualified testing roles. A wastewater backwater valve is distinct. No national device selection, code adoption, permit requirement or testing interval is supplied.

• Rain Bird · ESP-TM2 controller user manual
  Where this reference applies

  Jurisdiction: Named manufacturer controller; North American manual with Canadian support and interference statement

  Edition: 690299-01 Rev.05/16; ©2016. This exact copy is currently linked by the support page; URL folder dates are not its edition.

  Source reviewed: 2026-10-06 · America/Edmonton

  All 11 English text pages read; actual pages 3, 10 and 11 inspected. Station/valve relationship, separate programme/start/run-day roles, optional master valve, optional rain/freeze sensor and stated alternative explanations. Installation, wiring, jumpers, owner test runs, reset sequences, settings and numerical ratings are excluded. Does not describe every controller or the accessories fitted in a home.

• B.C. Sprinkler Irrigation Manual · Chapter 4, Crop, Soil and Climate
  Where this reference applies

  Jurisdiction: British Columbia agricultural design reference; historical qualitative context only

  Edition: 2014 ISSUE on the actual chapter cover; current access does not make it a current residential code or climate forecast.

  Source reviewed: 2026-10-06 · America/Edmonton

  Complete 22-page chapter text read, including covers and printed pages 33–52; actual PDF pages 3, 4, 9 and 10 inspected. Soil water storage, infiltration and evapotranspiration explain why water application and plant need differ. Agricultural tables, crop prescriptions, historical climate estimates, calculations, licensing statements and design instructions are excluded. No residential watering recipe is transferred.

• B.C. Sprinkler Irrigation Manual · Title page and preface
  Where this reference applies

  Jurisdiction: British Columbia; agricultural professional manual

  Edition: 2014 ISSUE. The current directory says July 2, 2024; that webpage update does not revise this PDF edition.

  Source reviewed: 2026-10-06 · America/Edmonton

  All 10 front-matter text pages read, including blank pages, preface and contents; actual title-page pixels inspected. Establishes historical edition and agricultural professional scope only. Listed linked chapters are not treated as read.