A controller left on its original settings is running last year's summer, or nobody's summer at all.
Most controllers get programmed once, at installation, and never touched again except to turn a zone off when something breaks. A schedule that fit the yard three summers ago is not necessarily fitting it now, and Utah's summer heat and dryness make that gap more noticeable than a milder climate would.
Watering deeply in the early morning outperforms short daily cycles. Early morning keeps evaporation loss low before the day heats up, and a deeper, less frequent cycle encourages roots to grow down toward available moisture rather than staying shallow, which makes the lawn more resilient during the hottest stretches.
A single run time applied to every zone ignores that zones differ in head type, sun exposure and soil. A zone of rotors on a slope needs a different approach than a shaded zone of sprays, and treating them identically means one is overwatered while the other stays dry.
A schedule set in May is already wrong by August, when temperatures and water demand have both climbed. Utah's swing from a wet spring to a genuinely dry summer is large enough that the schedule should move with it rather than being set once and left alone.
Water pooling or running off before a cycle finishes is a sign the run time exceeds what the soil can absorb at once — often better solved by splitting one long cycle into two shorter ones with a gap between, rather than cutting total water.
A schedule that is actually tuned to the season removes a lot of the reason people call about dry patches or a spiking water bill in the first place — not because it fixes hardware problems, but because it stops layering a bad schedule on top of them.
Describe the symptom and we will match you with an irrigation contractor who traces the actual cause before replacing anything.
Get an Irrigation Pro OutA rough description is plenty — we will follow up to narrow it down before anyone comes out.
