Smart irrigation and ET water management field guide

What smart irrigation is, and why watering to the weather beats a clock

Smart irrigation waters the landscape to its actual demand instead of to a fixed timer. A clock-based controller runs the same minutes on the same days whether it is 95 degrees and dry or raining sideways. A smart controller adjusts the run time to local conditions, either by tracking the weather and the plants' water loss, called evapotranspiration, or by reading the moisture already in the soil. The landscape gets what it needs and no more.

That difference is most of the water bill. A standard timer set once at install and left alone overwaters for years, because it was set to the wettest week of the season so nothing browned out on the walk-through. Smart control replaces the guess with a number that moves through the season on its own.

Setting it up right is more than buying the controller. It takes a sound base schedule, the right sensors, accurate site data per zone, and a system that does not leak the savings back out through a broken line. The controller-programming and audit guides cover the base schedule and the coverage numbers. This guide is the smart layer that rides on top of them.

Why watering to a clock costs you

A clock waters in the rain. That single sentence is the case for smart control. A timer has no idea what the sky is doing, so it runs the Tuesday cycle straight into a Tuesday storm, and the property pays for water the plants did not use and never wanted.

The cost lands three ways. Water bills, because overwatering is the default failure of every set-and-forget timer, and on a metered commercial site the gap between a July schedule and an October schedule is real money. Plant health, because constant overwatering drowns roots, invites fungus, and grows shallow root systems that cannot ride out a dry spell. And compliance, because watering districts across drought-prone regions now cap outdoor watering to assigned days and hours, and a dumb timer running off-schedule into a restriction is a fine waiting to happen.

Then there is runoff. Water applied faster than the soil takes it, or applied when the soil is already full, sheets off into the gutter carrying fertilizer and soil with it. That is wasted water and a stormwater problem at the same time. The fix the controllers use is cycle-and-soak: split a long run time into shorter pulses with soak intervals between them, so each pulse soaks in before the next instead of running off a slope or tight clay. Smart control goes after all of it by matching the water to the demand.

What is evapotranspiration?

Evapotranspiration, ET, is the water a landscape loses to the air, evaporation from the soil surface plus transpiration from the plants. It is the demand side of the equation. When ET is high, on a hot, dry, windy day, the landscape loses water fast and needs it replaced. When ET is low, on a cool, humid, overcast day, it loses almost nothing. ET is the number a smart controller exists to replace.

Reference ET, written ETo, is the loss from a standard reference surface, usually a clipped cool-season grass, computed from temperature, solar radiation, humidity, and wind. A controller turns reference ET into a specific plant's demand by multiplying it by a crop coefficient, Kc, that accounts for the plant type. Turf and shrubs do not lose water at the same rate, so they do not get the same coefficient.

The practical point is that ET drives the schedule. Irrigation replaces what ET took out. Get the ET data right and the plant coefficient right and the run time follows from physics instead of habit. Local reference ET varies by region and season, so the value has to come from the local weather data or a regional historical curve, not a single national figure.

ET and weather-based controllers

A weather-based, or ET, controller sets the run time from local evapotranspiration and waters to replace what the landscape lost. The base program tells it the zone's plant type, soil, and how fast the heads apply water. The ET data tells it how much demand has built up since the last cycle. The controller does the arithmetic and trims or extends the run time.

ET controllers get their weather three ways, and the difference matters. Signal-based controllers pull real-time data from a nearby weather station by wireless or internet and update daily, which is the most responsive. Historical controllers run a pre-programmed water-use curve built from long-term regional ET averages, sometimes nudged by an on-site temperature or solar sensor. On-site controllers measure the weather at the controller itself.

Signal-based is the most accurate when the data source is close and the connection holds, and most fall back on the historical curve when the signal drops. Historical-only beats a fixed clock but cannot react to an unusual hot spell or a cold snap. Match the type to the site, and confirm which weather source the model uses before you quote it, because the manufacturer's setup decides how the controller actually gets its ET.

Soil-moisture sensor controllers

A soil-moisture controller waters only when the soil actually needs it. A sensor buried in the root zone reads how much water is in the soil, and the controller compares that reading to a threshold you set. If the soil is wetter than the threshold when a cycle is due, the controller skips, or bypasses, that cycle. If it is drier, the cycle runs.

Most of these use the bypass approach. A normal schedule lives on the timer, and the sensor sits in the loop allowing or canceling each scheduled event based on the moisture in the ground. The common sensor reads volumetric water content, the percentage of the soil that is water, by measuring the soil's dielectric constant.

The threshold is the setting that makes or breaks it. It runs roughly from a dry setting to a wet setting, and the right value depends on soil and plant type, often somewhere between 10 and 40 percent volumetric water content. Set it too wet and the system waters when it does not need to. Set it too dry and the plants stress before a cycle runs. Sensor placement matters as much as the number. A sensor in the wrong spot or the wrong zone reads the wrong soil, and the controller acts on bad data.

What is the difference between ET and soil-moisture controllers?

Both are smart controllers, but they decide differently. An ET controller waters to predicted demand: it calculates how much water the weather pulled out and replaces it. A soil-moisture controller waters to measured supply: it checks what is in the ground and waters only when the soil drops below the threshold. One looks at the air, the other looks at the dirt.

That drives where each one fits. ET works best on large or varied landscapes where you want the whole system scaled by the season and you have a reliable local weather source. Soil-moisture works best where the soil and microclimate are hard to predict, on shaded zones, heavy clay, or spots where the weather model and the actual root zone disagree. Many of the better setups run both: an ET-driven base schedule with a soil-moisture sensor as the final check that stops a cycle when the ground is already full.

Neither one fixes a bad base schedule or bad site data. They both act on the program and the inputs you give them. The smart layer decides whether to run the cycle and for how long. It does not invent the cycle.

WaterSense labeled controllers and rebates

WaterSense is the EPA's efficiency label, and for irrigation it covers both smart types. The agency certifies weather-based controllers under one specification and soil-moisture controllers under another, and a controller that uses both kinds of data has to meet both specs to carry the label. The label means an independent lab verified the controller actually saves water against a clock, not just that the box says smart.

The savings the program cites are concrete. EPA estimates that swapping a standard clock timer for a WaterSense labeled controller can save an average home up to 15,000 gallons a year. That number is what makes the rebates work.

Rebates are local and they move. Many water utilities pay $100 to $200 toward a WaterSense labeled controller, and some restrict eligibility by purchase date and require both the model and the install to qualify. The label is usually the gate: utilities rebate from the WaterSense product list, not from a generic smart controller. Before you spec a model on a rebate job, pull the current eligible-product list from the local water authority and confirm the model is on it, because a controller that is smart but unlabeled often does not qualify.

Smart control still needs a sound base schedule

Garbage base, garbage smart. A smart controller does not invent a watering schedule from nothing. It scales one you build. The base program sets each zone's plant type, soil, root depth, and the run time that puts the right depth of water on the root zone, and the smart layer dials that base up or down with the weather or the soil reading. Feed it a base schedule that already overwaters and the smart controller will overwater more efficiently, which is not the same as correctly.

The base run time comes from the precipitation rate, how fast the zone applies water in inches per hour, and the depth the root zone needs. That is the work covered in the controller-programming and audit guides, and it is the foundation the smart layer rides on. Skip it and the percentages the controller applies are percentages of a wrong number.

The most common version of this mistake is dropping a smart controller onto an old system, running the auto-setup, and walking away without ever setting a real base run time per zone. The controller is only as good as the program under it. Build the base first, then let the smart layer manage it.

The site data the controller runs on

A smart controller is only as accurate as the data you enter. For each zone it needs the plant type, the soil type, the slope, the sun or shade exposure, the sprinkler type, the precipitation rate, and the root depth. Those inputs are how the controller turns regional ET or a soil reading into a run time for that specific zone. Wrong inputs produce a confident, wrong schedule.

Each input does a job. Plant type sets the crop coefficient. Soil type sets how much water the root zone holds and how fast it takes it in. Slope and sprinkler type set how long the zone can run before it sheets off. Precipitation rate, measured by a catch-can audit, sets how long it takes to apply a given depth. Root depth sets how deep to water. Miss any of them and the controller scales the wrong base.

This is where the audit feeds the smart system. The precipitation rate and uniformity from a catch-can test are the real numbers behind the run time, not the manufacturer's nozzle chart. Enter measured data, not assumed data, and re-enter it when the planting or the heads change. The cross-linked audit guide covers how to get those numbers.

Rain shutoff and freeze sensors

A rain sensor stops the system from watering in the rain, and a freeze sensor stops it from watering in ice. Both are basic protection and both are often required by code. Several states, including Florida and Texas, require a rain or rain-shutoff device on new automatic irrigation systems, and many western water districts require one as a condition of the irrigation permit. Confirm the requirement with the local authority before you treat it as optional, because the rule and the trigger vary by jurisdiction.

A rain sensor trips when it has absorbed a set amount of rainfall and tells the controller to skip the cycle. A combination rain and freeze sensor adds a low-temperature cutoff, commonly around 37 degrees Fahrenheit, so the system does not run when water will freeze on the heads and walks and crack the pipe.

Here is the part crews get wrong on smart jobs. A weather-based controller pulling forecast data is not a substitute for a physical rain sensor. The forecast can be wrong, the station can be miles away, and the internet can drop. A wired or wireless rain sensor is the real-time backstop, and many specifications and codes require it on a smart controller anyway. Install the sensor, then verify it actually interrupts a running cycle before you leave.

Wind and the sensor suite

Wind is the sensor people skip, and on spray-head zones it matters. High wind shreds the spray pattern, blows water off the target, and wrecks the uniformity the schedule assumes. A wind sensor, or a controller that reads wind from its weather feed, can pause watering above a set wind speed and pick it up when the air calms.

It earns its place on exposed commercial sites and tall spray on open turf. On drip and low-angle rotors it matters less. Treat the wind input as one more sensor in the suite alongside rain and freeze, and confirm the controller supports it before you promise it. Not every model reads wind, and the ones that do often need the feature turned on in setup.

Precipitation rate and matched heads

Precipitation rate is how fast a zone applies water, in inches per hour, and it is the number the smart schedule is built on. The controller can compute a run time only if it knows how long the heads take to put down a given depth. That rate comes from a catch-can audit, not a guess, and the audit guide covers the 96.25 formula and the catch-can method that produce it.

Matched precipitation rate is the rule that the heads on one zone all apply water at the same rate. Mix a half-circle and a full-circle nozzle that are not matched and the half-circle puts down water twice as fast over its smaller area, so half the zone floods while the other half stays dry. No smart schedule fixes that, because the controller runs one run time for the whole zone.

The audit feeds the smart layer directly here. The measured precipitation rate becomes the controller's per-zone input, and the uniformity number tells you whether the zone is even enough for a single run time to work. Get the heads matched and the rate measured first, then let the controller schedule it.

Water budget and seasonal adjust

The water budget, or seasonal adjust, is the percentage that scales the whole system up or down by season. At 100 percent the zones run their full base times. At 50 percent they run half. On a clock controller you move it by hand through the year. On a smart controller the ET data or the soil reading moves it for you, which is most of the point of going smart.

The seasonal pattern is real and large. Summer demand can run several times winter demand, so a single fixed run time is wrong most of the year by definition. A budget that tracks ET puts down July water in July and October water in October without anyone touching the panel.

Water budget also has a second meaning on commercial sites, and it is worth knowing. Some water authorities assign each large landscape an annual water allocation, a budget in gallons based on lot size or planted area, and bill surcharges for exceeding it. A smart controller helps a property stay inside that allocation, but the allocation itself is set by the local authority. Confirm whether the site is on a budget program before you assume the only budget that matters is the one in the controller.

The flow sensor that protects the savings

A flow sensor plus a master valve is what keeps a broken line from draining the savings into the ground. The flow sensor sits on the mainline and measures how much water is moving. The controller learns each zone's normal flow, then compares real-time flow against it every cycle. When the numbers do not match, something is wrong.

High flow means a mainline break, a stuck valve, or a blown head, and a flow-monitoring controller can shut the system down through the master valve and send an alert instead of running a geyser all night. Low flow means a clogged filter or a blocked nozzle, which the controller can also flag. A break on a smart system without flow monitoring runs until someone notices the water bill or the washout. A break on a system with flow monitoring shuts off in minutes.

This is the protection that separates a real smart system from a fancy timer. All the ET savings in the world do not matter if a cracked lateral runs unnoticed for a week. Install the flow sensor on the mainline after the master valve and backflow, set the per-zone flow thresholds during commissioning, and confirm the shutoff actually fires on a fault.

The master valve and fault shutoff

The master valve is the shutoff the flow sensor acts through. It sits on the mainline and closes whenever no zone is calling for water, so the mainline is not sitting under constant pressure between cycles. Pair it with the flow sensor and it becomes the automatic shutoff on a fault: when the controller sees abnormal flow, it closes the master valve and stops the water.

Program it to close on a leak, not to fight the normal cycle. A master valve set up wrong can chatter or interfere with zone operation. Set up right, it is the difference between a broken line that floods for minutes and one that floods until Monday. On any site where a mainline break would cause real damage, the master valve and flow sensor belong together.

Hydrozones: group plants by water need

A hydrozone is a group of plants with the same water need on the same zone. Smart control works only if the zone is a hydrozone, because the controller runs one schedule for everything on that valve. Put turf and shrubs on the same zone and you have asked the controller to do the impossible: turf wants frequent shallow water and shrubs want deep infrequent water, and one run time cannot serve both.

The classic failure is a zone that mixes a thirsty cool-season turf strip with established drought-tolerant shrubs. Water for the turf and the shrubs drown. Water for the shrubs and the turf browns. The operator splits the difference and both suffer, and the smart controller faithfully applies the wrong compromise to both.

Separate zones by plant water need, by exposure, and by precipitation rate. Sun and shade on the same zone is the same problem in a quieter form, because the shaded plants need far less. If the existing system mixes plant types on a zone, the honest fix is re-valving, not a smarter controller. The controller can scale a hydrozone correctly. It cannot un-mix one.

Drip and high-efficiency heads with smart control

Smart control and efficient application multiply. The controller decides when and how much. The heads decide how much of that water reaches the root zone instead of the air or the pavement. Pair a smart controller with drip on beds and high-efficiency nozzles on turf and the savings stack, because you are cutting waste on both the timing side and the delivery side.

Drip applies water slowly right at the root zone, so almost nothing is lost to evaporation or overspray, and it changes the schedule. Drip zones run longer and less often than spray, at a much lower precipitation rate, and the controller has to know that rate to schedule them. High-efficiency rotary nozzles apply water more slowly and evenly than old spray heads, which cuts runoff and improves the uniformity the smart schedule depends on.

The catch is the same one as everywhere else. The controller needs the right precipitation rate per zone, and drip and spray are not interchangeable inputs. Set the zone type correctly so the smart layer schedules drip as drip and spray as spray.

Central and cloud control for multiple sites

On a single yard you stand at the panel. On a portfolio of sites you cannot, and that is where central or cloud control earns its place. A central system manages many controllers from one dashboard, pushes schedule and budget changes across the whole fleet at once, and sends alerts when a flow sensor trips or a controller goes offline. For a contractor running dozens of properties, that is the difference between finding a break on the next monthly visit and finding it the hour it happens.

The value is the alerts and the remote control. A flow alarm on a Saturday means someone can shut a zone from a phone instead of paying for a washout until Monday. A region-wide watering restriction can be applied to every site at once instead of driving to each panel.

Pair the irrigation telemetry with a field operations record so the alert becomes a tracked job. A tool like FieldOS keeps the controller event, the site, the dispatched tech, and the fix in one place, so a flow alarm turns into a documented repair instead of a note that gets lost. The savings are only real if someone acts on the alert and the work gets recorded.

How do watering restrictions affect a smart system?

Local watering restrictions set which days and hours you may water, and the smart system has to comply with them, not around them. Across drought-prone regions, water authorities cap outdoor irrigation to assigned days and time windows. Denver allows two assigned days a week, before 10 a.m. or after 6 p.m. under Stage 1 drought. San Antonio allows sprinkler watering once a week in set hours on a designated day. Florida districts can drop to one day a week in an extreme shortage. The specific days, hours, and drought stage are set by the local authority and they change, so confirm the current rule for the site before you program it.

A smart controller does not exempt you from the rules. It helps you live inside them. You set the allowed days and windows as hard limits, and the ET or soil-moisture logic decides whether to water at all within that window and for how long. The result is a system that waters less than the restriction allows when demand is low, and never outside the window.

Some large landscapes run under a water-budget variance instead of fixed days, watering more often as long as they stay inside an annual allocation. That is an authority-specific arrangement. Know which regime the site is under, because programming for fixed days when the site is on a budget, or the reverse, gets it wrong either way.

Commissioning: set it up, do not install and leave

A smart controller does nothing smart until it is commissioned. Commissioning is entering the real site data per zone, setting the base run times, configuring the sensors, setting the allowed days and windows, and then verifying the system actually adjusts. Install-and-leave is the single most common way a smart controller ends up running like a dumb one.

Walk every zone. Confirm each one runs, the heads are matched and unbroken, and the zone type, plant, soil, slope, and precipitation rate entered into the controller match what is in the ground. Set the rain and freeze sensor and trip it by hand to confirm it interrupts a cycle. Set the flow thresholds and confirm a simulated fault closes the master valve. Then check that the schedule moves: a smart controller should show a different run time on a hot week than on a cool one.

The job is not done when the controller powers up. It is done when you have watched it react and confirmed every sensor does what it claims. A smart controller handed over without commissioning is a clock with a better marketing label.

Keeping it smart: maintenance and drift

Sensors drift and site data goes stale, so a smart system needs upkeep to stay smart. A soil-moisture sensor can shift its reading over a season as the soil settles around it. A rain sensor's absorbent element degrades and stops tripping. A weather feed can lose its station. None of these announce themselves, which is why a seasonal check is the maintenance that pays.

At each seasonal visit, confirm the rain sensor still interrupts a cycle, check the soil-moisture reading against the actual soil, verify the weather connection is live, and walk the zones for broken or misaimed heads that wreck the uniformity the schedule assumes. Update the site data when the planting changes, because a bed that matured from new shrubs to established ones needs less water and a different coefficient.

The smart controller is not a set-and-forget appliance, even though it is sold as relief from set-and-forget. It trades the old manual chore of moving the seasonal adjust for a new one of keeping the sensors honest and the data current. Skip the seasonal check and the system drifts back toward watering wrong, quietly, the same as the timer it replaced.

Savings, rebates, and payback

The savings are real and documented, but the payback depends on the site. EPA estimates a WaterSense labeled controller can save an average home up to 15,000 gallons a year against a clock. On a commercial site with a high water rate and a long overwatering habit, the controller can pay for itself in a season or two. On a small, already-conservative site, it takes longer.

Three things drive the payback: the local water rate, how badly the old schedule overwatered, and whether a rebate offsets the hardware. A $100 to $200 rebate on a WaterSense model shortens it directly. The actual number varies with the site and the water authority, so run it for the specific property rather than quoting a national average to the owner. The honest pitch is that smart control cuts a real, measurable amount of water, and the dollar payback is a calculation, not a promise.

What the record proves

A smart system generates information worth keeping: the program per zone, the site data entered, the flow alerts, and the season's water use. The record is what proves the system is working and what lets the next tech pick up where you left off without re-deriving every input.

Capture the per-zone program and the site data behind it, the sensor configuration, the flow thresholds and any alerts that fired, and the before-and-after water use that shows the savings. On a rebate job the record is also the evidence the utility may ask for. Tie the irrigation data to a field operations tool like FieldOS so the controller settings, the site, the alerts, and the repairs live in one place instead of on a sticky note in the panel. A flow alarm that turns into a tracked, documented repair is worth more than one that gets cleared and forgotten.

Where smart systems fail in the field

Most smart-system disappointments are not the controller. They are the setup around it. The pattern repeats across sites, and it is worth knowing before you commission one.

Smart control on a bad base schedule scales the wrong number efficiently. Wrong site data makes the controller confidently water wrong. No rain or freeze sensor lets it run in a storm or an ice event, sometimes against code. Mixed hydrozones force one run time onto plants with different needs, so something always suffers. No flow sensor lets a broken line drain the savings into the ground. Install-and-leave hands over a smart controller that never got its real inputs. And ignoring the local restrictions gets the system watering on the wrong day no matter how efficient the schedule is.

Every one of these is a setup or maintenance failure, not a hardware failure. The controller did what it was told. It was told wrong, or told nothing, or never checked again.

What to document

A smart system you cannot reconstruct from a record is a smart system the next tech will re-guess. Write down the inputs and the settings so the schedule can be defended and rebuilt.

Common mistakes

• Running smart control on a base schedule that already overwaters, so it overwaters efficiently.
• Entering inaccurate or assumed site data instead of measured plant, soil, and precipitation-rate values.
• Skipping the rain or freeze sensor and relying on a forecast feed that can be wrong or offline.
• Mixing turf and shrubs, or sun and shade, on one zone so a single run time cannot serve both.
• Installing no flow sensor, so a mainline break drains the savings until someone sees the bill.
• Installing the controller and leaving without commissioning the data, the sensors, and the shutoff.
• Programming around the local watering restrictions instead of setting them as hard limits.

Field checklist

Standards and references

The EPA WaterSense program sets the efficiency framework. It labels weather-based controllers under one specification and soil-moisture controllers under another, and a controller carrying the label has been tested to save water against a clock. The label is also the gate for most utility rebates, so it is the reference to cite when a model has to qualify.

The Irrigation Association and certified-auditor practice are where the field methods come from: the catch-can audit, the precipitation-rate math, distribution uniformity, and ET-based scheduling. The audit and controller-programming guides cover those numbers in detail. State and local code is where the rain and freeze sensor requirements live, and they vary, with several states requiring a rain-shutoff device on new systems.

The hedge that keeps this honest: the ET values, the water budgets, and the watering restrictions are all set by the local water authority and they change with the drought stage and the season. The controller setup and the sensor behavior follow the manufacturer's instructions. The plant, soil, and precipitation-rate inputs are specific to the site. Confirm the ET data and the restrictions with the local authority, the setup with the manufacturer, and the inputs against the actual landscape before you commit a schedule. Water to ET on a sound base, feed the controller accurate site data with rain and freeze sensors, and protect the savings with a flow sensor and proper hydrozones.

Units and terms

Smart irrigation borrows terms from weather science, soil physics, and the controller's own menu, so the same idea can read differently across an ET report, a manufacturer manual, and a water authority's restriction notice.

Evapotranspiration (ET / ETo)

Water lost from soil and plants to the air; reference ET (ETo) is the loss from a standard grass surface, the demand a controller replaces

Smart / ET controller

A controller that sets run time from local weather and evapotranspiration instead of a fixed clock

Soil-moisture sensor

A buried sensor reading volumetric water content in the root zone; the controller bypasses a cycle when the soil is above the threshold

Water budget / seasonal adjust

A percentage that scales every zone's run time up or down by season; also a utility's annual gallon allocation for a site

Hydrozone

A group of plants with the same water need on one zone, so a single run time fits them all

Flow sensor

A mainline meter that lets the controller detect abnormal flow and shut off through the master valve on a break

WaterSense

The EPA efficiency label for irrigation controllers verified to save water, and the gate for most utility rebates

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• How long should you run each zone?
• What is distribution uniformity in irrigation?
• What is the difference between a tank toilet and a flushometer?
• What is drip irrigation?
• How do you size an irrigation pump?