Irrigation Optimization: ET Scheduling, Soil-Moisture Sensors, and Distribution Uniformity

Replace water lost—not minutes on a controller

Fixed runtimes are convenient, but they do not account for changes in weather, rainfall, wind, or the condition of a sprinkler system. A run of cool, cloudy days may call for little replacement water; a hot, windy afternoon can draw substantially more from the root zone. ET-based scheduling starts with that changing demand rather than assuming yesterday’s runtime is right for today.

Reference evapotranspiration, usually written as ET₀, estimates atmospheric water demand from weather data. It is commonly reported in inches or millimeters per day. Because ET₀ describes a reference surface—not a particular golf-course turf—the estimate is adjusted using a turf coefficient, K_c, selected for the turf and conditions:

Estimated turf ET = ET₀ × K_c

The resulting value is an estimate of water lost through evaporation and plant transpiration. The coefficient is not a permanent property of a species. It can vary with canopy density, mowing height, growth stage, rooting, and local climate. A superintendent should use a coefficient supported by local guidance or field calibration, then compare the estimate with turf response and soil-moisture trends.

Suppose adjusted ET for a day is 0.18 inches and effective rainfall is 0.05 inches. The initial net replacement estimate is 0.13 inches. That is a water-depth estimate, not a runtime and not a universal prescription. The number still needs to be tested against the root zone, surface, forecast, and irrigation system.

Turn an ET estimate into a zone decision

Daily ET bookkeeping is useful, but it should not become an automatic instruction to irrigate the full calculated amount every night. Water can be stored in the root zone only where roots can reach it, and the practical storage capacity depends on soil texture, profile construction, rooting depth, and current moisture. A shallow-rooted bentgrass green on a sand-based profile does not have the same water reserve as a deeper-rooted bermudagrass fairway.

Separate the course into management zones with meaningful differences: greens, tees, fairways, roughs, and areas with distinct soils, slopes, exposure, or sprinkler coverage. Within a zone, note locations that repeatedly dry first or remain wet longer. Those patterns may point to differences in root depth, soil, shade, wind exposure, or application—not simply different plant water use.

Rainfall deserves the same care. A gauge near the maintenance facility may record a storm that delivered a different amount across the property. Rain may also run off a compacted slope, collect in a low area, or wet only the surface of a dry profile. Use local gauges and field inspection to estimate effective rainfall: the portion retained where roots can use it. When rainfall is uncertain or uneven, avoid treating the entire course as though it received one uniform depth.

For an initial schedule, calculate daily turf ET, subtract effective rainfall, and keep a running estimate of the balance. Then use root-zone readings and visual checks to decide whether to apply water, how much to apply, and whether the zone needs a short cycle or a longer event. The calculation sets a starting point; field conditions determine the operation.

Sensor placement matters as much as sensor accuracy

A soil-moisture sensor reports conditions at its location and depth. It does not describe every green, fairway, or sprinkler head connected to the same controller. A sensor placed in a convenient, consistently wet spot may produce reassuring readings while a hot edge or high point is under stress. Representative placement is therefore an agronomic decision, not just an installation task.

Start by identifying the active root zone for the turf and site. Install sensors at more than one depth when practical: a shallow reading can show rapid surface drying, while a deeper reading helps reveal whether water is reaching below the upper profile or moving beyond the main roots. Exact depths should reflect construction and rooting observed in the field rather than a standard copied from another course. For a sand-based green, inspect the profile and roots before choosing installation depths; a sensor positioned below the active roots can report moisture that is not immediately available to the turf.

Place sensors in locations that capture useful contrasts, such as an exposed slope and a representative interior area. Keep them clear of obvious sprinkler overspray, localized drainage channels, and unusual depressions unless those are precisely the problem areas being investigated. A sensor close to a head may read well after an application even when the rest of the irrigation block received less. Record the location, depth, turf, and profile so readings can be interpreted consistently.

Most electronic probes report volumetric water content (VWC), expressed as a percentage of soil volume. A displayed value is not automatically a universal “irrigate now” threshold. Soil texture and construction affect the relationship between VWC and water availability; the same numerical reading can mean different things in different profiles. Build a site-specific working range by observing readings alongside hand sampling, profile inspection, rooting, turf firmness, and plant response through wet and dry periods.

Read sensors at a consistent time and compare trends, not isolated numbers. A sudden change may reflect a probe disturbance, poor contact, temperature effects, or a shifted installation—not a dramatic change in the whole root zone. Periodically check the sensor against a nearby soil sample and inspect cables, housings, and data transmission. A sensor that is not maintained can add a false sense of precision to an otherwise sound schedule.

Use the readings to protect bentgrass without overwatering

Bentgrass greens can have a narrow operating margin during hot, dry weather. Their shallow, sand-based root zones may lose plant-available moisture quickly, while excess water can reduce oxygen in the profile and encourage soft conditions. The useful question is not simply whether a sensor value is “low.” It is whether the moisture trend, weather demand, rooting depth, and turf condition indicate that the plant is approaching stress.

During periods of high evaporative demand, a superintendent might use overnight irrigation to replenish the root zone, then make carefully targeted hand-watering applications to isolated dry areas. These are different tools. A block irrigation cycle applies water across a zone; hand watering corrects a local deficit. Extending a whole-block runtime to rescue one dry edge can leave the rest of the green excessively wet.

On fairways or bermudagrass areas with deeper rooting, the schedule may tolerate a different depletion pattern. Greater rooting depth can provide access to a larger soil-water reservoir, but only if roots are healthy and the profile permits water infiltration. Compaction, shallow soil, restrictive layers, and poor drainage can limit that advantage. Use observations and sensor records to set zone-specific triggers rather than transferring a green threshold to a fairway.

Firmness and playability remain part of the decision. Moisture data should help the crew maintain turf function without routinely saturating the surface. Where a green becomes soft despite modest ET, investigate drainage, localized infiltration, irrigation coverage, and water movement through the profile before concluding that the sensor is wrong or simply reducing all irrigation.

A catch-can test reveals what the system delivers

Even a well-calculated net requirement can fail in the field if sprinklers apply water unevenly. Catch-can testing measures that distribution. Place identical, straight-sided cans across a representative irrigation area, run the zone for a recorded period, and measure the water collected in each can. Use enough cans to reveal patterns between heads and at edges; a small cluster near the sprinkler does not represent an entire block.

One widely used metric is low-quarter distribution uniformity, abbreviated DU_lq. It compares the average catch in the lowest 25 percent of containers with the average catch across all containers:

DU_lq = average depth in the lowest quarter ÷ average depth in all cans

If DU_lq is 0.70, the lowest quarter receives, on average, 70 percent of the overall average depth. That does not mean every location receives exactly 70 percent. It does signal that some parts of the test area receive substantially less than the mean. A low-quarter value below 0.70 warrants investigation: increasing runtime alone may water already-wet locations beyond what the turf needs while the dry spots remain comparatively dry.

For example, if the cans average 0.20 inches and the lowest quarter averages 0.13 inches, DU_lq is 0.65. The arithmetic is simple, but the diagnosis takes care. Check for clogged or mismatched nozzles, incorrect pressure, damaged heads, poor head alignment, obstructions, wind during the test, and spacing that no longer provides adequate overlap. Repeat the test in suitable conditions if gusts or setup errors may have distorted the result.

Catch-can testing also helps estimate application rate. Divide the average measured depth by the run time, converting units as needed, to determine the system’s average precipitation rate for that test. Treat it as a measured property of that zone under those conditions, not a number to apply indiscriminately to every block. Nozzle combinations, pressure, head spacing, and system changes can produce different rates elsewhere.

Correct distribution before adding time

When a catch-can test shows poor uniformity, inspect the irrigation system in a deliberate order. Compare nozzle type and condition, verify that heads pop up and rotate or sweep as designed, check for leaks and plugged screens, and confirm operating pressure against manufacturer specifications. Look for turf growth, trees, or other obstructions that interfere with spray. Where coverage depends on head-to-head spacing, check that heads remain aligned and that later landscape or construction changes have not created a gap.

Pressure deserves particular attention. Too little pressure can distort a sprinkler’s throw and shorten its effective radius; excessive pressure can create misting and drift. A pressure reading at the pump does not necessarily represent pressure at a distant head under operating conditions. Where pressure variation is suspected, measure at relevant points while the system is running and compare results with equipment requirements.

After repairs, run the catch-can test again. A before-and-after record shows whether a nozzle change or pressure adjustment improved the low quarter rather than merely changing the average. Keep the test date, weather, run time, zone, can locations, readings, and any maintenance performed. These records make it easier to distinguish a recurring hardware problem from a temporary effect of wind or unusual turf conditions.

Do not equate DU_lq directly with application efficiency. Uniformity describes how evenly water is distributed in the tested area; efficiency also depends on runoff, evaporation, drift, infiltration, and whether the applied water reaches the intended root zone. A uniform system can still waste water if it runs during windy conditions or applies more than the soil can accept.

Translate net replacement into runtime carefully

Once the net water requirement and the zone’s precipitation rate are known, a simple estimate of runtime is:

Runtime in hours = target application depth ÷ average precipitation rate

If a zone’s tested average rate is 0.10 inches per hour and the target average application is 0.20 inches, the preliminary runtime is two hours. This worked example does not account for poor uniformity, runoff, wind, or a rate that varies across the zone. It should be treated as a planning calculation and checked against field measurements.

Do not automatically divide the net requirement by DU_lq and apply the resulting amount everywhere. Such a correction may raise the mean application enough to compensate for a dry low quarter, but it can overwater the better-served locations. First improve distribution where feasible; then evaluate whether a carefully managed runtime or targeted supplemental irrigation is appropriate. The right approach depends on the zone, the deficit pattern, and the consequences of additional water.

Where slopes, compacted areas, or hydrophobic patches cause runoff or slow infiltration, use cycle-and-soak scheduling if the system and course operations allow it. Several shorter cycles separated by soak intervals can improve infiltration compared with one continuous application. Confirm the result on the ground: if water still runs off or collects at the surface, investigate the underlying soil or drainage condition rather than adding more cycles by default.

Make ET, sensors, and uniformity work together

Each tool answers a different question. ET estimates how much water the atmosphere has removed. Sensors indicate moisture at specific locations and depths. Catch cans show how evenly a particular irrigation zone applies water. A practical program uses all three rather than expecting any one measurement to provide a complete schedule.

• Use ET to set the starting estimate. Apply a turf coefficient appropriate to the zone and review the source and limits of the weather data.
• Account for effective rainfall. Use local observations and gauges, especially when storms are patchy or runoff is likely.
• Check root-zone moisture. Compare readings at representative depths with site-specific experience, turf condition, and profile observations.
• Verify irrigation delivery. Use catch cans to find low-quarter deficits and measure zone-specific application rates.
• Make a targeted adjustment. Correct hardware, alter cycles, or hand-water localized dry areas instead of extending an entire zone without diagnosis.
• Review the outcome. Record the next sensor readings, turf response, and any signs of excess moisture, runoff, or stress.

This sequence is especially useful when the weather and turf seem to disagree. If ET indicates a modest demand but sensors fall quickly, inspect rooting depth, wind exposure, sensor placement, and the accuracy of the weather station. If the ET balance calls for replacement but the profile remains wet, investigate effective rainfall, drainage, and whether the chosen coefficient is appropriate. If moisture is adequate near one sensor but dry areas persist, compare the sensor location with catch-can results and field patterns.

Keep records that support better decisions

A compact irrigation log can expose patterns that are difficult to see during a busy season. Record daily ET₀, the turf coefficient used, rainfall, estimated effective rainfall, irrigation depth or runtime, sensor readings by depth, and any hand watering. Add relevant observations such as high wind, heat stress, disease pressure, recent cultivation, or changes in mowing and traffic.

Review the records by zone, not only by date. A green that repeatedly needs supplemental water at the same perimeter may have a coverage or exposure problem. A fairway section that stays wet after surrounding areas dry may have a drainage limitation or a different soil profile. Sensor trends and catch-can tests help distinguish those possibilities from a general increase in water demand.

Seasonal calibration matters. Recheck system uniformity after repairs or nozzle changes, and revisit sensor thresholds as rooting and weather conditions shift. ET scheduling does not eliminate the need for a superintendent’s judgment; it gives that judgment a measurable framework. The goal is not to obey a number, but to apply enough water at the right place and time to maintain functional turf while avoiding unnecessary saturation, runoff, and loss below the active root zone.