Setbacks, Stormwater, and the Fine Print: Reading a Zoning Application Without a Planner's Degree

Every zoning case starts the same way. A sign goes up in a yard, a legal notice runs in the back pages of the paper, and maybe nine people in town notice. By the time the hearing arrives, the applicant has a lawyer, a civil engineer, and a traffic consultant on the clock. The neighborhood has a hunch.

The good news is that the hunch is usually correct, and the evidence to support it is already public. A typical site plan packet runs 60 to 300 pages, but only about a dozen of them matter to someone who lives nearby. The rest is boilerplate, cover sheets, and standard notes recycled from the last project. Here is how to find the pages that count.

Start with the ask, not the drawing

Flip past the colorful rendering — the one with the trees that will not exist for another eight years — and find the application form itself. It will tell you three things worth knowing: what zoning district the property is in now, what the applicant wants it to be (or what relief they are requesting), and whether this is a rezoning, a conditional use permit, a variance, or just a site plan review.

Those are very different proceedings with very different standards. A variance asks the board to grant an exception because of a hardship unique to the lot. A rezoning asks for a new set of rules entirely. If you show up to argue about parking at a variance hearing, you may be politely told that parking isn't the question before the board that night. Read the ask first, then aim your comments at it.

Setbacks: a promise about the gap

Setbacks are the distances between the building and the property lines, and they are the easiest numbers to check. Front, side, and rear setbacks each appear in the zoning code, and the site plan should show them in a little table near the drawing.

Two things to watch. First, setbacks are usually measured to the wall, not to the roof overhang, the bay window, or the front porch — check the definition in your code, because that difference can be several feet. Second, look at whether the applicant is asking for a reduction. A request to build four feet from a side lot line where the code requires eight is a real, specific thing you can comment on, especially if the neighboring houses all sit at the required distance.

Density: do the division yourself

Unit counts get discussed in generalities, but density is simple arithmetic. Take the number of dwelling units and divide by the acreage. Forty-eight units on 3.2 acres is fifteen units per acre. Then check whether the applicant is using gross acreage or net acreage — subtracting wetlands, floodplain, or right-of-way can push the real number noticeably higher.

Ask how the project compares to what the comprehensive plan calls for on that parcel. Planners often have a target range in mind, and a proposal that exceeds it by a wide margin is a legitimate topic for public comment. So is the bedroom mix, which drives school enrollment, parking demand, and the number of people who will be using the sidewalk.

Parking: count the spaces, then question the assumptions

Find the parking table. It should list the code requirement, the number of spaces proposed, and the number provided. If the proposal offers fewer spaces than the code requires, there will be a written justification — often shared-parking calculations, a transit argument, or a request for a reduction.

Some of those arguments are sound and some are wishful. Worth asking: Are tandem or compact spaces being counted at full value? Is the parking shared with a business that is open at the same hours? Has the applicant counted garage spaces in the unit total? None of these are gotchas. They are just the places where the math tends to bend.

Traffic: find the counts and the date

Traffic studies are long, but the useful part is short. Look for the intersection analysis and the trip generation table, then find out when the counts were taken. A study based on data from a school holiday, a pandemic year, or a nearby road closure is not necessarily wrong, but it deserves a question.

Also check which intersections were studied. Engineers define a study area, and it occasionally stops one light short of the corner everyone in the neighborhood is worried about. Asking why a specific intersection was excluded is a fair and answerable question.

Stormwater: where does the water go?

The stormwater section tells you how much of the site will be impervious before and after construction, and how stormwater will be detained on site. Look for the pond or underground vault, its size, and where it discharges. Then look for the maintenance agreement — the document that says who cleans out the basin in fifteen years, when the developer is long gone.

If any part of the parcel sits in a mapped floodplain, that should be stated plainly. If it isn't, ask.

Questions that actually move a commission

Planning commissioners hear a lot of "we don't want this" and very little of anything they can act on. The comments that land tend to be specific, tied to a code section, and pointed toward a condition of approval.

• "The code requires a 20-foot buffer. The plan shows 12. Can the approval be conditioned on a 20-foot buffer with a Type B planting?
• "The traffic counts are dated March 2020. Can staff require a new count before the certificate of occupancy?
• "Who is responsible for maintaining the detention basin, and can that be recorded as a deed restriction?

Bring three questions on a single sheet of paper. Hand a copy to the clerk so it becomes part of the record. You are not required to be an expert. You are required to be a reader.