A “perfect” construction site plan isn’t the one with the most detail — it’s the one a plan reviewer can approve without a single correction comment. Every rejection letter costs weeks of resubmittal time, and most rejections come from the same handful of missing items. This guide covers what a code-compliant site plan must contain, the government requirements that appear in almost every jurisdiction, and the review categories where plans most often fail.

What “Perfect” Means to a Plan Reviewer

A site plan serves two audiences: the government reviewer verifying code compliance, and the contractor building from it. A perfect plan satisfies both with zero ambiguity. In practice that means three qualities: completeness (every required item present), consistency (dimensions, labels, and legends agree across all sheets), and traceability (every design decision can be checked against a cited code section).

The Non-Negotiable Contents of a Code-Compliant Site Plan

Identification and reference data: project address and legal description, property lines with bearings and distances, north arrow, graphic scale, benchmark and datum reference, zoning designation, and the code edition the design references. Reviewers check the code edition first — designing to an outdated code version is an automatic correction.

Site geometry: building footprint with setback dimensions to every property line, easements, right-of-way lines, and lot coverage calculations. Setback violations are the single most common zoning rejection.

Grading and drainage: existing and proposed contours, spot elevations, drainage flow direction, and stormwater management facilities. Nearly every jurisdiction now requires demonstrating that post-development runoff does not exceed pre-development rates.

Utilities: water, sanitary sewer, and storm connections with pipe sizes, slopes, and invert elevations; connection points to public mains.

Access and circulation: driveway locations and widths, sight distance at access points, parking count with accessible stall calculations, and fire apparatus access routes.

Life safety and accessibility: accessible routes from the public way to entrances, ADA-compliant parking and ramps, and fire hydrant locations within required hose-lay distance.

The Popular Government Requirements That Appear Almost Everywhere

Across US jurisdictions (and with close equivalents internationally), five review categories drive approval:

  1. Zoning compliance — use, setbacks, height, lot coverage, parking counts. Checked against the local zoning ordinance or land development code.
  2. Stormwater — erosion and sediment control plans (SWPPP) are federally driven by the EPA’s construction general permit for sites disturbing one acre or more, then enforced through state and local programs.
  3. Fire access — the International Fire Code requires apparatus access roads within 150 feet of all portions of a building, a minimum 20-foot width, and hydrant spacing based on required fire flow.
  4. Accessibility — ADA (or local equivalent) accessible route, parking ratios, and slope limits (running slope max 1:20 on routes, 1:12 on ramps).
  5. Structural and building code compliance — for the building itself: IBC occupancy classification, construction type, and allowable area/height, all of which must be stated on the plans.

How Plans Fail Review — The Top Correction Comments

  • Setback dimensions missing or measured to the wrong line (foundation vs. roof overhang)
  • Stormwater calculations absent or not matching the grading plan
  • Accessible route shown but exceeding slope limits when checked against spot elevations
  • Fire access lane radii too tight for apparatus turning templates
  • Legend symbols used on the plan but not defined, or defined but never used
  • Code citations referencing a superseded edition

A Pre-Submittal Checklist Approach

The most reliable way to reach zero-comment approval is to review your own set against the jurisdiction’s published submittal checklist — most planning departments publish these publicly. Cross-check every checklist line against your sheets before submittal, and have someone who didn’t draw the plans do the check.

For the fieldwork and CAD side of getting your base plan right in the first place, use our Civil Site Field Data & CAD Setup Checklist — a working two-part checklist covering everything from boundary documentation to pre-submittal QA/QC.

Conclusion

A perfect site plan is a boring site plan — from the reviewer’s perspective. Everything they look for is exactly where convention says it should be, every number is consistent across sheets, and every requirement has a visible answer. Master the five universal review categories, mirror your jurisdiction’s checklist, and approval becomes a formality instead of a negotiation.