Common Reasons Site Plans Get Rejected (And How to Avoid Them)
Getting a site plan rejected by a city or county can feel frustrating, especially when the feedback is short or vague. The reality is that most site plan rejections happen for the same handful of reasons, regardless of location. After reviewing thousands of permit comments and resubmittals, a clear pattern emerges. Cities are not looking for perfection. They are looking for clarity, consistency, and compliance with basic requirements. Below are the most common reasons site plans get rejected, along with simple explanations of what reviewers are actually looking for.
<section>
<h2>1. Missing or Incorrect Scale</h2>
<p>
This is the single most common reason site plans are rejected.
</p>
<p>
Cities need to verify setbacks, distances, and lot coverage. If the plan is not drawn to scale or the scale is unclear, the reviewer cannot reliably verify anything else on the page.
</p>
<p><strong>Common issues include:</strong></p>
<ul>
<li>No scale listed</li>
<li>Scale listed but incorrect</li>
<li>Printed at the wrong paper size</li>
<li>Scaled drawing that does not match labeled dimensions</li>
</ul>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Always include a written scale</li>
<li>Make sure the plan is printed at the intended paper size</li>
<li>Use dimensions to reinforce distances instead of relying on visuals alone</li>
</ul>
<p>
Learn more in our guide on
<a href="https://www.siteplancreator.com/construction-permit-site-plans">how to draw a site plan for a building permit</a>.
</p>
<hr>
<h2>2. Property Lines Do Not Match Public Records</h2>
<p>
Many applicants use aerial imagery or parcel data as a starting point, which is perfectly reasonable. Problems arise when property boundaries are not adjusted to match recorded dimensions.
</p>
<p><strong>Cities frequently cross check:</strong></p>
<ul>
<li>Lot width and depth</li>
<li>Angled or irregular boundaries</li>
<li>Corner lots</li>
<li>Flag lots</li>
</ul>
<p>
If property lines look approximate or inconsistent with assessor records, the plan is often rejected.
</p>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Use known parcel dimensions when available</li>
<li>Adjust property lines to match recorded data</li>
<li>Avoid freehand or eyeballed boundaries</li>
</ul>
<hr>
<h2>3. Required Setbacks Are Not Shown or Labeled</h2>
<p>
Even if your layout is correct, cities often reject plans that do not explicitly show setbacks.
</p>
<p><strong>Reviewers typically want to see:</strong></p>
<ul>
<li>Distance from structures to property lines</li>
<li>Front, side, and rear setbacks clearly labeled</li>
<li>Proposed structures clearly differentiated from existing ones</li>
</ul>
<p>
A plan that visually appears compliant but does not label distances creates extra work for the reviewer and increases the chance of rejection.
</p>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Label all setback distances clearly</li>
<li>Do not assume the reviewer will measure it themselves</li>
<li>Show dimensions even if the structure is obviously compliant</li>
</ul>
<p>
Common examples include
<a href="https://www.siteplancreator.com/fence-deck-site-plans">fence and deck site plans</a>
and other residential projects.
</p>
<hr>
<h2>4. Existing and Proposed Structures Are Unclear</h2>
<p>
One of the fastest ways to get a rejection is ambiguity.
</p>
<p><strong>Cities need to understand:</strong></p>
<ul>
<li>What already exists on the property</li>
<li>What is being added, removed, or modified</li>
<li>Whether structures are permanent or temporary</li>
</ul>
<p><strong>Common mistakes include:</strong></p>
<ul>
<li>No legend</li>
<li>No distinction between existing and proposed structures</li>
<li>Overlapping shapes without labels</li>
</ul>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Clearly label existing versus proposed structures</li>
<li>Include a simple legend</li>
<li>Keep the drawing uncluttered and readable</li>
</ul>
<hr>
<h2>5. Driveways, Parking, or Access Paths Are Missing</h2>
<p>
Many applicants focus only on buildings and forget site access.
</p>
<p><strong>Cities often require:</strong></p>
<ul>
<li>Driveway locations</li>
<li>Parking spaces</li>
<li>Access paths for emergency or service vehicles</li>
</ul>
<p>
Even small residential projects can trigger access requirements depending on scope.
</p>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Always show driveways and parking areas</li>
<li>Label widths where relevant</li>
<li>Include access paths if the project affects circulation</li>
</ul>
<p>
This is especially common on
<a href="https://www.siteplancreator.com/pool-site-plans">pool site plans</a>
and hardscape projects.
</p>
<hr>
<h2>6. North Arrow or Orientation Is Missing</h2>
<p>
This may seem minor, but it matters more than people realize.
</p>
<p><strong>Without clear orientation, reviewers cannot confirm:</strong></p>
<ul>
<li>Front versus rear yard</li>
<li>Setback direction</li>
<li>Lot orientation relative to the street</li>
</ul>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Always include a north arrow</li>
<li>Keep orientation consistent across pages</li>
<li>Do not rotate the plan without clearly indicating direction</li>
</ul>
<hr>
<h2>7. Lot Coverage or Impervious Area Is Not Addressed</h2>
<p>
Some cities require lot coverage or impervious area calculations directly on the site plan.
</p>
<p><strong>This is especially common for:</strong></p>
<ul>
<li>ADUs</li>
<li>Additions</li>
<li>Pool and hardscape projects</li>
<li>Flood or coastal zones</li>
</ul>
<p>
If coverage is required and missing, rejection is highly likely.
</p>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Check whether lot coverage is required</li>
<li>Include basic calculations when applicable</li>
<li>Label impervious surfaces clearly</li>
</ul>
<hr>
<h2>8. The Site Plan Does Not Match the Permit Application</h2>
<p>
Cities review the permit application and drawings together.
</p>
<p><strong>Common examples include:</strong></p>
<ul>
<li>Different structure size</li>
<li>Different structure location</li>
<li>Missing scope items</li>
</ul>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Double check the site plan against the permit application</li>
<li>Ensure scope descriptions match exactly</li>
<li>Update both documents when changes are made</li>
</ul>
<hr>
<h2>9. Poor Readability or Cluttered Layout</h2>
<p>
A technically correct site plan can still be rejected if it is difficult to read.
</p>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Use clean, consistent line weights</li>
<li>Avoid excessive text</li>
<li>Space labels clearly</li>
<li>Keep the layout visually organized</li>
</ul>
<hr>
<h2>10. City Specific Requirements Are Not Addressed</h2>
<p>
While many site plan requirements are common nationwide, every city has its own nuances.
</p>
<p><strong>These may include:</strong></p>
<ul>
<li>Tree protection zones</li>
<li>Coastal overlays</li>
<li>Fire setbacks</li>
<li>Flood zones</li>
<li>Easements</li>
</ul>
<p><strong>How to avoid it:</strong></p>
<ul>
<li>Review city or county checklists when available</li>
<li>Look at example approved plans</li>
<li>Expect small but important differences between jurisdictions</li>
</ul>
<hr>
<h2>Final Takeaway</h2>
<p>
Most site plan rejections are not about design quality. They are about missing information, unclear labeling, or scale issues.
</p>
<p><strong>
If a site plan clearly shows:
</strong></p>
<ul>
<li>Accurate property lines</li>
<li>Labeled setbacks</li>
<li>Existing and proposed structures</li>
<li>Access features</li>
<li>Correct scale and orientation</li>
</ul>
<p>
It already meets the majority of building department expectations.
</p>
<p>
This is why software tools, clear checklists, and standardized layouts dramatically reduce rejection rates. They force clarity where most DIY plans fall short and help reviewers approve plans faster.
</p>
</section>