Why Site Plans Get Rejected: The Code Violations Reviewers Catch First

A rejected site plan usually costs somewhere between two and six weeks: the review queue, the revision, the resubmittal, another trip through the queue. For a pool builder or landscape contractor, that's a crew standing idle and a client asking why the dig date moved twice.

The frustrating part is how repetitive the reasons are. Plan reviewers see the same violations week after week, and most of them are checkable before submittal. This guide covers the ones that come up constantly in residential work (additions, pools, decks, detached garages, retaining walls) and where each one tends to hide.

1. Setbacks measured from the wrong line

The classic rejection. Not because the designer didn't know the setback distance, but because they measured it from the wrong place.

The most common version: measuring from the edge of pavement or the back of curb instead of the right-of-way line. On many residential streets the right-of-way extends 10 to 15 feet past the pavement, so a structure that looks like it clears a 30-foot front setback by plenty can actually encroach.

Other versions of the same mistake:

• Corner lots. Many codes treat both street frontages as fronts, which means two front setbacks, not a front and a side. A garage placed against the "side" street is a frequent casualty.
• Easements. A drainage or utility easement along the rear line may prohibit structures entirely, regardless of what the setback table allows.
• Eaves, gutters, and cantilevers. Some jurisdictions allow a projection of 18 or 24 inches into the setback; others measure to the drip line. If the code measures to the drip line and you drew to the foundation, you're over.

If a plan is going to fail, it usually fails here first. Reviewers check setbacks before anything else because they're the fastest thing to check.

2. Accessory structures held to different rules than you assumed

Sheds, detached garages, pool equipment pads, pergolas, cabanas: these don't follow the main structure's setback table, and designers who assume they do get burned in both directions. Sometimes the accessory setback is more lenient (a shed allowed 5 feet from the rear line where the house requires 40). Sometimes it's stricter in ways that surprise people: rear-yard-only placement rules, separation requirements from the main structure, or a limit on how many accessory structures a lot can hold.

Height is the sleeper issue. A code might allow accessory structures up to 24 feet, then cap them at 15 feet if they sit inside the main structure's required setbacks. A two-story garage placed where a one-story shed was fine is a rejection that arrives late, after the client has already seen the rendering.

3. Impervious coverage that doesn't add up

Most residential districts cap impervious surface at some fraction of the lot; 35% and 40% are common. The violation is rarely that someone ignored the cap. It's that they counted the surfaces differently than the jurisdiction does.

The categories that cause disagreements:

Run the arithmetic on a real case: a 12,000-square-foot lot at a 35% cap gives you 4,200 square feet. A 2,600-square-foot house footprint, a 600-square-foot driveway, a 450-square-foot pool deck, and a 400-square-foot pool leaves almost no margin, and whether it passes can hinge entirely on how that pool water surface is counted. Get the counting convention wrong and the plan is over the cap while looking under it on paper.

4. Stream buffers and floodplain lines you didn't draw

Buffer violations kill plans late, because the buffer isn't on the survey the client handed you. It's on a state or county resource map, and it applies whether or not anyone drew it.

In Georgia, for example, state law imposes a 25-foot undisturbed buffer on most streams, and many metro jurisdictions stack local requirements on top. A 50-foot undisturbed buffer plus an additional 25-foot impervious setback is a common pattern. That's 75 feet from the stream bank in which your pool, deck, or wall either can't exist or needs a variance.

If the property backs up to anything that carries water, even seasonally, check for buffers before laying out the design, not after. A variance for buffer encroachment is slow, uncertain, and expensive; redesigning around the buffer on submission two is worse.

5. Height measured from the wrong datum

"Maximum height 35 feet" sounds unambiguous until you ask: from where? Codes variously measure from average finished grade, average natural grade, the lowest point of the structure, or the adjacent street. On a flat lot the answers converge. On a sloped lot with a walkout basement they can differ by a full story.

A house that's 32 feet from average grade can be 41 feet from the low side. If the code measures from the low side, the design is over by six feet and nobody noticed because everyone was picturing the front elevation.

6. Retaining walls that quietly became structures

Small walls are landscaping. Somewhere around 4 feet (the threshold varies) they become engineered structures that need permits, sealed drawings, and sometimes setback compliance of their own. Three ways this goes wrong:

• The wall is 3'6" on the plan and 4'2" as built, because grade never matches the survey exactly.
• Terraced walls are drawn as separate short walls, but the code measures them as one wall when they're closer together than some multiple of their height.
• The wall retains a surcharge, meaning a driveway or pool sits above it, which drops the engineering threshold below the usual number.

Codes increasingly regulate wall placement inside setbacks too, particularly along side lines where drainage disputes between neighbors end up in front of the zoning board.

7. The drawing itself

Some rejections have nothing to do with zoning. The plan fails because the reviewer can't trust the drawing:

• No units. CAD files without stamped units force everyone downstream to guess whether that wall is 20 feet or 20 meters long. It sounds absurd; it happens constantly.
• Scale that doesn't match the labels. A dimension string says 25'-0" but measures 23'7" at the stated scale. Now every number on the sheet is suspect.
• Unclosed boundaries. If the lot line or building footprint doesn't close, area calculations, including that impervious coverage number, are meaningless.
• Mislabeled layers. The pool deck drawn on the landscaping layer gets missed in the coverage calculation and found by the reviewer.

Reviewers are within their rights to bounce a plan on legibility alone, and the ones with deep queues will.

Before you submit

The short version, as a checklist:

1. Confirm the zoning district from the jurisdiction's GIS, not from memory or a listing site.
2. Locate the right-of-way line and every easement. Measure setbacks from those.
3. Pull the accessory structure table separately. Check placement, height, and separation rules against it.
4. Recompute impervious coverage using the jurisdiction's counting rules, not yours.
5. Check state and local buffer maps for any stream, wetland, or floodplain within 100 feet of the work.
6. Find the height datum definition and re-measure from it.
7. Verify the drawing: units stamped, boundaries closed, dimensions matching scale, surfaces on the right layers.

None of this is difficult. It's just tedious, which is why it gets skipped when the deadline is close, and why the same seven problems keep filling rejection letters.

Or check it in about 90 seconds

This checklist is what Muniscan automates. Upload the DXF, and it pulls your jurisdiction's actual zoning code, extracts the applicable rules, runs the geometric checks (setbacks, coverage, buffers, heights), and cites the code section behind every result. It also flags the drawing problems (missing units, unclosed boundaries, scale mismatches) before a reviewer does.

Run a precheck on your plan →

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.