Calculator
Sprinkler Zone Calculator
A sprinkler system isn't sized by how much yard needs watering — it's sized by how much water your supply line can actually deliver at once, and that flow limit is what decides how many heads can run together on a single zone. Design a zone with more heads than the available flow supports and every head runs starved, delivering less pressure and a smaller, weaker pattern than the same heads would produce on a properly sized zone, no matter how good the heads themselves are.
This calculator works from your measured available flow rather than your lawn's square footage, applies a safety margin because real systems never deliver their full rated capacity in practice, and groups heads into zones that fit inside what's actually available. It then works out the precipitation rate — how fast each zone actually puts water down — because that number, not head count, is what sets your watering schedule.
Calculate your quantity
gpm at the meter, measured with a bucket and a stopwatch.
Never design to 100% of measured flow.
From the nozzle chart, at your operating pressure.
inches
Zones needed
4 zones
Heads per zone
5 heads
- Usable flow
- 7.5 gpm
- Flow per zone
- 7.5 gpm
- Precipitation rate
- 0.642 in/hr
- Runtime for the week
- 93.5 minutes
- Minutes per zone, 3 runs a week
- 31.2 minutes
- Full cycle time
- 124.6 minutes
- At 0.642 in/hr this system takes 93 minutes a week to deliver 1 in. Rotors run far longer than sprays because they put down far less per hour — never share a zone between the two.
Shopping summary
- • 4 zone valves and 4 controller stations
- • 18 heads at 1.5 gpm each
This is an estimate — confirm structural work with a professional.
How this calculation works
Available flow at the meter, measured with a bucket and a stopwatch or read off a flow test, gets reduced by a safety margin first — typically to about 75% of the raw measurement — because pressure loss through the valve, the pipe run and the backflow preventer is real and never shows up in a simple flow test at the spigot. Whatever flow remains, divided by a single head's flow rate, sets how many heads one zone can run at once; the total head count divided by that number sets how many zones the system needs.
Precipitation rate — how many inches of water a zone puts down per hour — comes from the head's flow rate divided by the area each head is spaced to cover, using a standard conversion factor. That rate, not the head count, is what determines runtime: a zone with a low precipitation rate needs to run far longer to deliver the same weekly inches as a zone with a high one, which is exactly why rotor heads (low precipitation rate, wide spacing) and spray heads (high precipitation rate, tight spacing) need very different run times even at similar flow.
- Never design a zone to 100% of measured flow — real systems lose pressure through fittings, elevation change and the backflow device, and a zone sized to the raw number underperforms every head on it.
- Precipitation rate depends on both the head's flow rate and its spacing — the same head spaced wider covers more area with the same water, which lowers the precipitation rate and lengthens the needed runtime.
- Rotors and sprays should never share a zone. Their precipitation rates differ by a wide margin, and a shared zone either drowns the sprays or starves the rotors, whichever runtime the controller is set to.
- Runtime is calculated against a fixed number of watering days per week; changing how often the system runs redistributes the same weekly total across more or fewer, shorter or longer sessions.
The formula
usable flow = available flow × safety %; heads per zone = floor(usable flow ÷ head flow); zones = ceil(head count ÷ heads per zone); precipitation rate = 96.3 × head flow ÷ (head spacing × row spacing)
- usable flow
- Available flow reduced by a safety margin to account for real-world pressure loss through the valve, pipe run and backflow preventer — the number a zone is actually designed against, not the raw measured flow at the meter.
- heads per zone
- The largest number of heads the usable flow can run at once without starving any of them, found by dividing usable flow by a single head's flow rate and rounding down — never up, since rounding up would exceed the available flow.
- precipitation rate
- Inches of water applied per hour by a zone, derived from head flow and the area each head is spaced to cover — this, not head count or zone count, is the number that actually sets how long a zone needs to run.
- 96.3
- A standard conversion constant that turns a flow rate in gallons per minute over a square-foot spacing grid into inches of water applied per hour — the unit conversion at the center of the precipitation-rate calculation.
- safety margin
- The percentage of raw measured flow actually treated as usable for zone design, conventionally around 75%, reflecting real losses in the system that a bucket-and-stopwatch flow test at the spigot doesn't capture.
Where these numbers come from
- 75% design safety margin
- Trade convention among irrigation designers for translating a raw measured flow into a usable design flow, accounting for pressure loss through valves, fittings, elevation change and backflow prevention devices that a simple flow test doesn't isolate.
- 96.3 conversion constant
- Standard irrigation-industry conversion factor for converting gallons-per-minute flow over a square-foot spacing area into inches-per-hour precipitation rate — a fixed unit-conversion figure, not a variable one, that appears throughout landscape irrigation design references.
- 1-3 watering sessions per week
- Trade convention for established turf under typical conditions; this calculator assumes three sessions per week as a working default. Newly seeded or sodded turf, and different climates or soil types, commonly call for a different weekly schedule.
- Rotor vs spray precipitation rates
- General irrigation-industry knowledge rather than a single citable figure: rotor heads apply water at a lower rate over a wider area per head, spray heads apply it faster over a smaller area — which is why the two head types need different runtimes even at comparable per-head flow.
Worked examples
A front yard on spray heads, 18 heads at typical spacing
| Available flow | 10 |
|---|---|
| Design margin | 75 % |
| Flow per head | 1.5 |
| Heads in the system | 18 |
| Head spacing | 15 ft |
| Row spacing | 15 ft |
| Water to apply weekly | 1 |
| Zones needed | 4 zones |
|---|---|
| Heads per zone | 5 heads |
| Usable flow | 7.5 gpm |
| Flow per zone | 7.5 gpm |
| Precipitation rate | 0.642 in/hr |
| Runtime for the week | 93.5 minutes |
| Minutes per zone, 3 runs a week | 31.2 minutes |
| Full cycle time | 124.6 minutes |
10 gpm at the meter becomes 7.5 gpm usable after the safety margin, which supports 5 spray heads per zone at 1.5 gpm each — spreading 18 heads across 4 zones rather than fewer, larger ones a naive '18 heads, pick a round number of zones' approach might land on.
At a 0.642 in/hr precipitation rate, delivering 1 in a week across three sessions takes about 31 minutes per zone per run, or roughly 125 minutes total across all four zones each cycle. That runtime is what actually goes into the controller — the zone and head counts on their own don't tell you how long to run anything.
A backyard on rotor heads, wider spacing and lower flow per zone
| Available flow | 14 |
|---|---|
| Design margin | 70 % |
| Flow per head | 3.5 |
| Heads in the system | 10 |
| Head spacing | 25 ft |
| Row spacing | 25 ft |
| Water to apply weekly | 1.5 |
| Zones needed | 5 zones |
|---|---|
| Heads per zone | 2 heads |
| Usable flow | 9.8 gpm |
| Flow per zone | 7 gpm |
| Precipitation rate | 0.539 in/hr |
| Runtime for the week | 166.9 minutes |
| Minutes per zone, 3 runs a week | 55.6 minutes |
| Full cycle time | 278.1 minutes |
Even with more available flow (14 gpm) and fewer total heads (10), this rotor system needs more zones than the first example — 5 against 4 — because each rotor head draws far more flow per head (3.5 gpm) than a spray head does, so usable flow supports only 2 heads per zone rather than 5.
The bigger difference is runtime: at a precipitation rate of 0.539 in/hr — lower than the spray system's, despite the higher per-head flow, because rotors are spaced much wider apart — delivering 1.5 in a week takes roughly 279 minutes total across all five zones, well over double the spray system's cycle time. This is the concrete version of never sharing a zone between rotors and sprays: put these heads on a controller program built for spray runtimes and the lawn would be badly underwatered.
Common mistakes
- Designing zones against the raw measured flow instead of the flow reduced by a safety margin, then wondering why every head on a fully loaded zone runs weak.
- Sizing zones purely by lawn area rather than by available flow — a system with generous flow can run larger zones than one with limited flow, on the exact same size lawn.
- Mixing rotor and spray heads on one zone. Their precipitation rates differ enough that a runtime correct for one head type badly over- or under-waters the other.
- Setting a controller's runtime from a guess rather than from the calculated precipitation rate — two systems with the same weekly inch target can need very different minutes per zone depending on head type and spacing.
- Ignoring pressure loss from elevation change on a sloped yard — a zone running uphill from the valve loses more pressure than the flat-ground safety margin accounts for, and may need a more conservative margin than the working default.
Shopping summary
Buy a zone valve and a controller station for each zone this page returns, plus the head count and type already chosen — rotors and sprays purchased separately if the system mixes both, since they should never end up sharing a valve.
Where the irrigated area is also getting new turf established at the same time, the sod calculator or the grass seed calculator covers that material separately — get the irrigation zones designed and roughed in first, since head spacing and coverage genuinely depend on the finished bed layout, not the other way around.
A system feeding both sprinkler zones and a separate drip or garden bed line off the same supply should have that split accounted for in the available-flow figure entered here — the flow measured at the meter needs to cover everything running off it, not just the zones this calculation is sizing.
FAQ
Why shouldn't I just design zones to the full flow my meter reads?
Because that reading is measured close to the source, before the water travels through the valve, the pipe run to the heads, elevation change and a backflow preventer — all of which cost pressure and effective flow. A zone sized to the raw number will underperform in practice; the safety margin exists specifically to leave room for those real losses.
How do I actually measure my available flow?
The standard method is timing how long it takes to fill a container of known volume (a 5-gallon bucket is common) from an outdoor spigot fully open, then converting to gallons per minute — divide the container's volume by the fill time in minutes. This gives a raw flow figure that this calculator's safety margin then reduces to a usable design number.
Can I run rotors and sprays on the same zone if I just adjust the runtime?
No — the problem isn't just runtime, it's precipitation rate. A runtime that delivers the right amount of water for a spray head's high precipitation rate will badly underwater a rotor head's much lower one, and there's no single runtime that's correct for both on the same schedule. Keep them on separate zones even if it costs an extra valve.
Does a bigger available flow mean I need fewer zones?
It usually means larger zones rather than automatically fewer zones — more usable flow per zone supports more heads running together, which can reduce the total zone count for a fixed head count, but the actual reduction depends on how the extra flow compares to what a single head draws.
Why is my calculated precipitation rate lower than I expected?
Wider head spacing lowers precipitation rate even at the same per-head flow, because the same water is being spread across more area per head. If your spacing is wider than a head's rated coverage radius calls for, you may be trading precipitation rate (and therefore needing longer runtimes) for fewer total heads — a legitimate design choice, but one worth making deliberately rather than by accident.
How many days a week should each zone actually run?
This page assumes three sessions a week as a working default for established turf, but actual scheduling depends heavily on soil type, climate, slope and grass species — sandy soil generally wants more frequent, shorter sessions to avoid runoff, while clay soil can often take longer, less frequent ones. Local extension service guidance for your specific turf type is a better source than a single fixed number here.
Where to go next
The projects this number is a step of, the guides that explain the method behind it, and the rest of its trade group.