SOIL / IRRIGATION DIAGNOSTICS
When Irrigation Signals Disagree, Check the Assumptions Before You Water
Use a short diagnostic sequence when a water budget, soil-moisture reading, rain record, or field observation points to a different irrigation decision.
- irrigation scheduling
- soil moisture
- evapotranspiration
- field observations
- diagnostics
Treat disagreement as a diagnostic, not a vote
A daily water balance estimates root-zone depletion from crop evapotranspiration, precipitation, and irrigation. A soil-moisture sensor measures conditions at its installed location and depth. University of Minnesota Extension describes soil-moisture sensing and weather-based water accounting as two irrigation-scheduling approaches, and its sensor guidance recommends combining in-field monitoring with daily water accounting. USDA NRCS also lists evapotranspiration, soil moisture, and plant monitoring as scheduling inputs. When they disagree, first ask whether their inputs still describe the same field decision.[1][3][5]
Do not average conflicting numbers or assume the newest reading is correct. A mismatch can come from an unrepresentative sensor, a rainfall or irrigation amount that did not reach the root zone, an ET or crop-stage assumption, runoff, drainage, or a change in rooting depth. The corrective action depends on the source of the mismatch.[4][2]
Confirm that the records refer to the same decision
Start with the management zone. Compare a sensor only with the water balance, rainfall, irrigation record, crop, soil, and rooting depth for the zone it represents. A sensor in a different soil texture, irrigation pattern, or crop condition is evidence about that location, not a correction for the whole field.[2][3]
Then compare the time window. Record when the sensor was read, when rain was measured, when irrigation ran, and which day’s ET was used. UMN's checkbook method calls for regular field visits and adjustment when field conditions do not align with its estimated deficit. A same-day comparison is more useful than reconciling records that describe different days.[2]
Check water added to the root zone before changing the schedule
Verify rainfall with on-site gauges where practical, then verify the irrigation amount and whether it infiltrated the intended root zone. The water-balance method treats precipitation and irrigation as additions, but runoff and deep percolation can make a simple account differ from field conditions. A recorded application is not proof that every part of the root zone received that amount.[4][2]
If the sensor indicates wetter soil than the balance predicts after an application, verify the application and rainfall records before changing the balance. If it indicates drier soil, verify sensor placement and the active root depth before increasing the next irrigation. UMN's sensor guidance says to use representative locations and depths, and its water-balance guidance calls for checking calculated deficit against field conditions.[3][2][4]
Recheck the demand estimate and field conditions
Crop ET changes with weather and crop development. Colorado State University Extension notes that crop ET estimation requires a crop-stage basis, while UMN advises checking whether field conditions agree with the calculated deficit. Review the ET source, crop coefficient or local method, and any crop-stage change before calling the water balance wrong.[4][2]
Field observations can reveal a problem the account does not contain, such as uneven irrigation, runoff, a damaged line, or a sensor that no longer represents the active root zone. They do not set a universal irrigation threshold on their own. Use them to decide what to verify next, alongside the field's documented allowable depletion, application capacity, and crop-risk conditions.[5][1]
Make a bounded next decision and record why
After checking the inputs, choose one of three actions: irrigate when the remaining evidence and your documented threshold support it, wait and recheck when the account still has usable storage, or investigate the measurement or application system before changing the schedule. NRCS specifies that timing and depth should account for factors such as root-zone water-holding capacity, allowable depletion, current soil moisture, crop stage, and application uniformity.[5]
Log the disagreement, the zone, sensor depth, readings, ET source, rain and irrigation records, field observations, and the action taken. UMN's checkbook method uses field observations, precipitation, irrigation, and crop-water-use records to compare the estimate with field conditions. Keeping those inputs with the decision gives the next comparison a documented starting point. For the full timing-and-depth framework, see Schedule Irrigation With Soil Moisture and ET. For a daily calculation, see Work Through a Daily Irrigation Water Budget.[2]
Research record
Sources
Every factual claim in this note is tied to the numbered evidence below.
- university extension[1] University of Minnesota Extension, Evapotranspiration-based irrigation scheduling or water-balance method. Water-balance inputs, the distinction between water-balance and soil-moisture scheduling approaches, and the method's scheduling limits.
- university extension[2] University of Minnesota Extension, Irrigation scheduling checkbook method. Field visits, representative rain measurements, root-zone deficit accounting, and adjustment when field observations do not agree with the estimate.
- university extension[3] University of Minnesota Extension, Soil moisture sensors for irrigation scheduling. Using soil-moisture data with other scheduling tools and considering application capacity and efficiency.
- university extension[4] Colorado State University Extension, Irrigation Scheduling: The Water Balance Approach. Water-balance assumptions, sources of mismatch including runoff and deep percolation, crop ET inputs, and comparing calculated and observed deficits.
- government[5] USDA Natural Resources Conservation Service, Irrigation Water Management standard (Code 449). ET, soil-moisture, and plant monitoring as scheduling methods, and the field factors used to determine irrigation timing and depth.
Continue through the archive
Related operating questions
Schedule Irrigation With Soil Moisture and ET
Use a root-zone water budget, representative soil-moisture readings, and field observations together to decide whether to irrigate, wait, investigate, or adjust depth.
Work Through a Daily Irrigation Water Budget
Use a simple daily root-zone deficit example to track depletion, record the assumptions, and correct the estimate when field measurements disagree.
Place soil-moisture sensors where they represent the root zone
Choose representative management zones, depth bands, and in-row locations before treating a soil-moisture reading as an irrigation decision input.