Impervious Coverage: What Counts and How It Is Actually Measured
Setback violations get caught early and fixed cheaply. Coverage violations are worse. They surface after the design is done, they implicate the whole plan rather than one wall, and the fix usually means deleting something the client wanted.
The rule itself is simple: your jurisdiction caps impervious surface at some percentage of the lot, commonly between 25% and 50% for residential districts. The trouble is that "impervious surface" and even "lot" mean different things in different codes, and the difference between counting conventions can be the entire margin on a tight project.
Start with the denominator
Before counting surfaces, confirm what you're dividing by. Codes measure the cap against different definitions of lot area:
- Gross lot area. Everything inside the deeded boundary. The most common and most generous basis.
- Net lot area. Gross minus the right-of-way, and sometimes minus access easements or private street stubs. On a lot where the right-of-way takes a 20-foot strip off the front, net can run 10% smaller than gross.
- Buildable area. A few codes exclude floodplain, buffers, or steep slopes from the denominator entirely.
A 40% cap against net area can be stricter than a 35% cap against gross. Read the definition, not just the percentage.
The numerator: what counts
Roofs, concrete, and asphalt count everywhere. After that, codes diverge. The surfaces that generate the most rejection letters:
| Surface | Range of treatment across codes |
|---|---|
| Roof overhangs and eaves | Some codes measure the foundation, others the drip line |
| Wooden decks | 0% if water passes between boards, 50% as a compromise, 100% in strict codes |
| Pool water surface | Excluded in some codes as "pervious," fully counted in others |
| Pool decks and coping | Counted everywhere; the water-surface exclusion never extends to the apron |
| Gravel driveways and paths | Usually counted as impervious; compaction defeats infiltration |
| Permeable pavers | Full credit, partial credit, or credit only with an engineered stone base |
| Artificial turf | Increasingly counted; the backing sheds water |
| AC pads, generator pads, trash enclosures | Small, but they count, and reviewers add them up |
Two of these deserve special attention. Gravel surprises almost everyone; it feels pervious, but a driven-on gravel surface compacts until runoff behaves like it would on asphalt, and most codes treat it accordingly. And permeable pavers only earn their credit when the code says so. Installing them and assuming a 100% exemption is a common way to be over the cap while holding an invoice that says "permeable."
Run the math like a reviewer
Take a 12,000-square-foot lot in a district with a 35% cap: 4,200 square feet of budget. Now count the way a reviewer counts.
| Item | Square feet |
|---|---|
| House footprint (drip line) | 2,750 |
| Driveway | 640 |
| Front walk | 120 |
| Pool | 420 |
| Pool deck | 510 |
| Equipment pad | 24 |
| Total | 4,464 |
Over by 264 square feet. If the code excludes pool water, the total drops to 4,044 and the plan passes with 156 to spare. One counting convention, and the same drawing is either approvable or not.
This is why "are we under the cap?" is not a yes-or-no question until you know which code applies. The percentages are easy to find; the definitions section of the ordinance is where the answer actually lives.
Existing conditions are part of your budget
On renovation and addition work, the lot rarely starts at zero. A house built in 1995 with a wide driveway may already sit at 30% coverage before you draw anything. The pool your client wants adds 900 square feet against a budget that has 600 left.
Pull the existing coverage number first, from a current survey if you have one, before promising anything. Discovering the deficit at submittal converts a design conversation into a bad-news phone call.
Some jurisdictions also treat legally nonconforming lots differently: a lot already over the cap may be frozen (no net new impervious surface at all), which is stricter than the headline percentage suggests.
When you're over: the levers
In rough order of how much they usually recover:
- Shrink the hardscape. Driveways are the biggest discretionary surface on most residential lots. A 10-foot ribbon instead of a 16-foot slab recovers hundreds of square feet.
- Use credited permeable systems. If your code grants credit for engineered permeable paving, use it where the spec can be met and documented.
- Trade footprint for height. A two-story addition delivers the same floor area at half the coverage.
- Check for stormwater offsets. Some ordinances allow coverage above the cap when runoff is detained or infiltrated on site. This buys square footage at the cost of engineering and maintenance obligations.
- Variance. Slow and uncertain, and coverage variances get less sympathy than setback variances because the harm (runoff) is cumulative and invisible.
Before you submit
- Read the code's definition of impervious surface and of lot area. Both, not just the percentage.
- Measure the house to whichever line the code uses, foundation or drip line.
- Classify every deck, pool, gravel, and paver surface against the code's list, not against intuition.
- Add the small stuff: pads, walks, trash enclosures.
- On existing lots, compute current coverage before designing.
- Keep a margin. As-built dimensions drift, and a plan that passes by 40 square feet on paper can fail its final inspection.
Check the math automatically
Muniscan reads the surfaces from your DXF by layer, pulls your jurisdiction's actual coverage rules and counting conventions, and reports the calculation with the code section cited next to the result. If wooden decks count at 50% in your district, the math reflects it; if the lot is already near the cap, you find out in the first pass instead of the rejection letter.
This guide is general information about common zoning patterns, not legal advice. Requirements vary by jurisdiction and change over time; verify against your jurisdiction's current code before relying on any of it.