A Smart Controller Is Only as Smart as the Person Managing It

The hardware got the upgrade. The management didn't.

By Leroy "Lee" Lee, CLIA, Co-Founder and Manager of Irrigation Management, Irrigation Managers · Certified Landscape Irrigation Auditor (Irrigation Association), 25+ years in system-monitoring software and data analytics

As of September 2026. About 59.1% of the contiguous United States was in drought on September 1, up roughly 10.5 percentage points in a month.[^1]

Walk onto almost any commercial or municipal site and you'll find a controller that can do far more than it's doing. Flow monitoring that was never calibrated. ET-based scheduling still running the default plant coefficients from install day. Alerts silenced because nobody has time to chase them.

The hardware got the upgrade. The management didn't.

With drought covering most of the country this fall, that gap is one of the most expensive blind spots in landscape water management. First it shows up in the landscape: uneven color, stressed zones next to soggy ones, and failures that run for weeks. The water bill comes later. Smart controllers create the gap partly because they are so capable.

Key Takeaways

  • The savings from smart controllers vary enormously. A Lawrence Berkeley National Laboratory review found about 15% average savings, but the individual studies ranged from 43% savings to a 35% increase in water use.[^2]
  • Configuration and management explain most of that spread, not the brand of controller. Plant coefficients, precipitation rates, soil data and flow thresholds all have to be right, and they have to stay right.[^3]
  • Installed systems average only about 50% distribution uniformity, according to an Irrigation Association analysis of more than 6,800 landscape audits.[^4] No controller can schedule its way around that.
  • Two-wire diagnostics and flow alerts only protect a site if someone reads them on a schedule. A decoder can report leakage for weeks before it fails.
  • "Smart" moved the skill requirement; it didn't remove it. A timer needed manual adjustment. A smart controller needs someone to interpret what it's reporting.

What Does a Smart Irrigation Controller Actually Do?

A smart irrigation controller adjusts watering automatically based on weather, soil moisture or flow data, so that in principle it applies water only when and where plants need it.

Definition: smart irrigation controller. A smart irrigation controller is a controller that changes run times automatically based on measured or estimated plant water need, usually from weather-based evapotranspiration (ET) data or from soil moisture sensors, instead of following a fixed timer schedule.

Definition: evapotranspiration (ET). Evapotranspiration is the water lost from the soil through evaporation plus the water used by plants through transpiration. It is the baseline measure of how much water a landscape needs.

The Irrigation Association's Smart Water Application Technologies (SWAT) program and EPA's WaterSense specification test weather-based controllers for irrigation adequacy and excess. To be labeled, a controller must meet at least 80% of plant water need in every zone, with no more than 10% excess in any zone, over a 30-day test.[^5] That is a meaningful standard. But it is a test of what the controller can do with correct site inputs. Most real sites aren't set up that way.

Why Don't Smart Controllers Deliver the Savings People Expect?

Because a smart controller only performs as well as the site data, settings and oversight behind it. Real-world results range from large savings to higher water use, depending on how the system is configured and managed.

The Lawrence Berkeley National Laboratory meta-analysis is the clearest evidence. The underlying studies ranged from 43% savings to a 35% increase in water use.[^2] The U.S. Department of Energy's review of advanced irrigation controls reports a 15% to 40% reduction across the studies it looked at.[^6] Controllers from the same product categories produced both ends of that range.

An older University of California field evaluation reached the conclusion that still holds: "use of a weather-sensing controller does not assure landscape water conservation."[^3] That was 2004-era hardware, and controllers have improved a great deal since. The lesson is about programming and uniformity, not about any current product.

Every zone is its own microclimate: sun, shade, slope, soil, plant material and heat reflected off buildings. A single program across 80 zones is wrong in 79 different ways at once. ET scheduling can only correct for that if each zone's inputs are entered correctly.

Get the plant coefficient wrong, misjudge the precipitation rate of a rotor zone, or leave a flow sensor uncalibrated, and the controller isn't optimizing anything. It's guessing with better vocabulary.

Where Do Smart Systems Most Often Fail Without Management?

The failures are usually small configuration and monitoring gaps that go unnoticed until plants decline or water is lost.

Smart feature What it needs to work What happens when nobody manages it
ET-based scheduling Correct plant coefficients, precipitation rates, soil type and root depth for each zone Runs on install-day defaults; some zones are overwatered while others are stressed
Soil moisture sensors Correct placement, calibration and thresholds One sensor in an unrepresentative spot drives the whole schedule
Two-wire decoder diagnostics Someone reviewing leakage current and fault reports on a set schedule A decoder reports intermittent leakage for weeks, then fails outright
Flow monitoring Learned or set flow thresholds per zone, plus alert routing A mainline break or stuck valve is found from a puddle in the parking lot instead of an alert within minutes
Cloud and software platform User access control, firmware updates, connectivity checks Features change behavior after updates, or the controller silently goes offline
Seasonal adjustment A documented record of what changed, when and why A flat percentage change in spring that stays in place all season

Two-wire decoder systems give station-level control and diagnostics: leakage current detection, individual decoder addressing and real-time fault reporting. That detail only pays off if someone reads it. A decoder that throws intermittent leakage warnings before it fails is exactly the signal these systems are built to surface. It's also exactly the signal that gets missed when nobody watches the dashboard on a set schedule.

Flow monitoring has the same problem the other way around. A flow sensor can catch a mainline break or a stuck valve within minutes instead of days, but only if the thresholds were set correctly and someone is watching for the alert.

Is your controller doing what you paid for? A Water Use Analysis compares what your system is programmed to do with what each zone actually needs. Request a Water Use Analysis →

Why Is This a Management Problem, Not a Hardware Problem?

Smart controllers moved the skill requirement from manual adjustment to data interpretation. Most in-house staff and landscape crews aren't resourced or trained for that job.

None of this is a knock on the technology. Baseline, Rain Bird, Toro and others have built capable platforms. A timer demanded someone to turn knobs. A smart controller demands someone who can interpret sensor data, alert patterns, seasonal adjustment logic, and software updates that change how features behave.

Maintenance staff and landscape crews are good at a different job: keeping plants healthy, fixing heads, repairing breaks. The Irrigation Association itself certifies auditors, contractors, designers and water managers separately.[^7] The industry's own credentialing body doesn't expect one person to do all of it.

There's also a limit no software can fix. Across more than 6,800 audits, the Irrigation Association found average distribution uniformity of about 50%, whatever type of sprinkler head was used.[^4] Using the IA scheduling multiplier, a zone at 50% uniformity needs about 43% more run time than a perfectly uniform zone to keep its driest spots healthy.[^8] A controller will happily apply that extra water to the whole zone. Only a person can decide whether the better fix is the schedule or the heads.

Definition: distribution uniformity (DU). Distribution uniformity measures how evenly an irrigation system applies water across a zone. It compares the average of the driest quarter of the area with the overall average. EPA's WaterSense at Work guidance sets 65% as the minimum acceptable for commercial systems.[^9]

What Does Well-Managed Smart Irrigation Look Like?

Well-managed smart irrigation is a repeating cycle: measure each site, program each zone from that data, monitor it constantly, and adjust as conditions change.

  1. Establish a baseline. Measure each zone's plant material, soil, slope, exposure, precipitation rate and uniformity before trusting any schedule.
  2. Program zone by zone. Enter plant coefficients, precipitation rates and soil data for each zone, and stay within the legal watering window.
  3. Calibrate flow. Set or learn flow thresholds for every zone and route alerts to someone who will act on them.
  4. Review diagnostics on a fixed schedule. Check decoder leakage, communication failures and flow anomalies before they become plant loss or water loss.
  5. Repair before you re-water. Fix broken heads, pressure problems and poor overlap rather than adding run time to cover for them.
  6. Document seasonal adjustments. Record what changed, when and why, instead of applying one flat percentage.
  7. Own the software side. Manage user access, firmware updates and cloud connectivity as part of the job.
  8. Report against the baseline monthly. Show plant health, water use and fixed faults against the original numbers.

Your Next 30 Days

  • ☐ Log into your controller platform and count the active alerts that nobody has acknowledged.
  • ☐ Check whether the plant coefficients and precipitation rates are still the install-day defaults.
  • ☐ Confirm that the flow thresholds are set and that alerts reach a named person.
  • ☐ Pull the decoder or station diagnostics history for the last 60 days.
  • ☐ Walk the three worst-looking zones and compare what you see with how they're programmed.
  • ☐ Ask who owns firmware updates and user access, and get a name.
  • ☐ Put irrigation management in next year's budget. HOAs and commercial properties draft it this fall; municipal and school budgets need proposals in by early spring.

How Irrigation Managers Manages Smart Controllers

Irrigation Managers is a remote irrigation management firm built on agronomy, not plumbing. We work with the controller you already have, and white-label for landscape maintenance contractors who want the expertise without adding staff. Our AIM framework:

  • Analyze: a water use analysis that sets baseline need, peak demand and seasonal adjustment for each site.
  • Implement: controller configuration and base scheduling built from measured uniformity, plant demand and the legal watering window.
  • Manage: proactive monitoring 24/7, fault and alert routing, ongoing optimization, and branded report cards against the baseline.

Service starts as low as $1 per zone per month for team support and guidance, up to as low as $5 per zone per month for full management with monitoring and reporting. Our best fit is a site with 50 or more zones and a controller that can be managed remotely.

The goal is a consistent, healthy landscape all season. Using less water is a bonus that follows from managing the system well.

Request a Water Use Analysis →

Frequently Asked Questions

How much water do smart irrigation controllers really save?

It depends mostly on how they're configured and managed. A Lawrence Berkeley National Laboratory meta-analysis found about 15% average savings, with individual studies ranging from 43% savings to a 35% increase in water use.[^2] The U.S. Department of Energy reports a 15% to 40% reduction across the studies it reviewed.[^6]

We installed a smart controller. Why are some zones still brown while others are soggy?

The controller is probably running inaccurate zone data, or it's compensating for poor distribution uniformity. Default plant coefficients, wrong precipitation rates or an unrepresentative sensor can overwater one zone and underwater the next. Installed systems average about 50% uniformity, so dry spots often need a repair, not more run time.[^4]

What is SWAT testing?

SWAT (Smart Water Application Technologies) is an Irrigation Association initiative for testing smart irrigation products. Its protocols, which underpin EPA's WaterSense controller specification, measure whether a controller meets plant water needs in each zone without excess irrigation.[^5] A passing result shows what the controller can do with correct inputs. It doesn't guarantee results on your site.

Can our landscape crew manage the smart controller?

They can handle parts of it, but monitoring and data interpretation are a different job from landscape maintenance. That job includes reviewing diagnostics on schedule, calibrating flow, updating zone data and managing the software. Many properties split the work: the crew handles repairs, and a dedicated irrigation manager handles programming, monitoring and reporting.

How often should a smart irrigation system be audited?

EPA's WaterSense at Work guidance recommends a full audit every three years by a qualified auditor.[^9] Programming and diagnostics should be reviewed far more often, weekly or better during peak season.

Is a flow sensor worth it if we already have a smart controller?

Yes, if its thresholds are set and someone acts on the alerts. A properly configured flow sensor can flag a mainline break or stuck valve within minutes. Without thresholds or alert routing, it's just another unread data point.

References

[^1]: NOAA National Centers for Environmental Information. Monitoring the U.S. Temperature and Precipitation in August 2026. September 2026. https://www.ncei.noaa.gov/news/national-climate-202608

[^2]: Estimates of Savings Achievable from Irrigation Controllers. Lawrence Berkeley National Laboratory, 2014. https://www.osti.gov/servlets/purl/1129575

[^3]: Pittenger, D., Shaw, D., and Richie, W. Evaluation of Weather-Sensing Landscape Irrigation Controllers. University of California Cooperative Extension, 2004. https://ucanr.edu/sites/default/files/2011-03/80078.pdf

[^4]: Irrigation Association. Using Distribution Uniformity to Evaluate the Quality of a Sprinkler System. 2004. https://www.irrigation.org/IA/FileUploads/IA/Resources/TechnicalPapers/2004/UsingDistributionUniformityToEvaluateTheQualityOfASprinklerSystem.pdf

[^5]: U.S. Environmental Protection Agency. WaterSense Specification for Weather-Based Irrigation Controllers, Version 1.0. 2011. https://www.epa.gov/sites/default/files/2017-01/documents/ws-products-spec-irrigation-controllers.pdf · Irrigation Association. Smart Water Application Technologies (SWAT). https://www.irrigation.org/SWAT

[^6]: U.S. Department of Energy, Federal Energy Management Program. Water-Efficient Technology Opportunity: Advanced Irrigation Controls. https://www.energy.gov/cmei/femp/water-efficient-technology-opportunity-advanced-irrigation-controls

[^7]: Irrigation Association. Certification. https://www.irrigation.org/IA/Membership/Certification.aspx

[^8]: Oki, L. Irrigation Scheduling: Determining Distribution Uniformity and Irrigation Run Time. University of California, Davis, 2016. https://ucanr.edu/sites/default/files/2016-12/253019.pdf (scheduling multiplier SM = 1 ÷ (0.4 + 0.6 × DU); DU 0.50 → 1.43)

[^9]: U.S. Environmental Protection Agency. WaterSense at Work, Section 5.3: Irrigation. https://www.epa.gov/system/files/documents/2023-05/ws-commercial-watersense-at-work_Section_5.3_Irrigation.pdf