The Same-Controller Overlap Trap

A conflict that is not a conflict

Here is a scenario every irrigation contractor knows. A property has one controller running a dozen zones. Program A fires at 5am. Zone 1 for 10 minutes, zone 2 for 15, zone 3 for 10, on down the line.

Now a piece of scheduling software looks at that program and it sees zone 1 starting at 5:00 and running to 5:10, and zone 2 starting at 5:10, and it decides there is an overlap risk. It flags it. Red warning. "Multiple zones scheduled in the same window."

That warning is wrong, and if you have ever used generic field-service software for irrigation you have probably learned to ignore these alerts entirely, which is its own problem.

Why it cannot happen

A single controller runs its stations in sequence, one at a time. It is not a limitation you configure, it is how the hardware works. The controller opens one valve, waits out that station's run time, closes it, and only then opens the next. There is no mode where a conventional controller runs zone 1 and zone 2 simultaneously off the same program.

So two zones on the same controller cannot draw water at the same time. They cannot fight each other for pressure. The overlap the software is warning about is physically impossible.

The naive version of a scheduling tool does not know this. It treats "two time ranges that touch" as a conflict, the same way it would flag two crew members double-booked on a calendar. But zones are not people. Zones on one controller take turns whether you like it or not.

Where the real conflict lives

Here is the part that matters, because there is a real pressure problem, it is just not the one the naive tool flags.

The real conflict is across controllers. Big properties, especially commercial and HOA sites, run five, ten, fifteen separate controllers. Those controllers do not know about each other. Controller 1 fires its 5am program and pulls water. Controller 2 fires its own 5am program off a different clock and pulls water too. Now you have zones on two different controllers running at the same moment, off the same supply, and the pressure drops.

That is the conflict that actually costs you. Coverage suffers, heads do not pop, the far end of a zone goes dry, and the customer calls. And it is invisible on any single controller, because each controller is behaving perfectly on its own. You only see it when you look at every controller on the property together, on one timeline.

The tell

If you are evaluating any software that claims to catch irrigation scheduling conflicts, this is the ten-second test. Ask it about two zones on the same controller. If it flags them as a conflict, it does not understand irrigation. It is calendar software with a sprinkler icon.

The right behavior is the opposite: never flag same-controller zones, because they run in sequence, and put all your attention on the cross-controller overlaps, because those are the ones that drop pressure. That is a rule you cannot get from a spec sheet. You get it from standing in front of a panel watching it step through stations.

We built FlowSync to skip the same-controller pairs and only warn on the real cross-controller overlaps, ranked by how bad the pressure hit is likely to be. But even if you never touch our software, the lesson is worth carrying: same controller, no conflict. Different controllers, watch out.