Join our early access program and receive free access →
Back to Blogs
BiGyan
November 15, 2026
11 min read
Before you submit a site plan, ask one question: can the reviewer evaluate the proposal without guessing?
A drawing may show the proposed building, parking area, and access points, but still leave important questions unanswered. Missing dimensions, unclear property boundaries, or inconsistent calculations can make it difficult to compare the proposal with the applicable requirements.
A site plan review checklist helps organize those checks before submission. It gives architects, developers, and project teams a structured way to examine the drawing set, identify missing information, and prepare questions for the reviewing department.
This guide covers the main areas to review, explains the difference between completeness and compliance, and shows where AI-assisted site plan review can support the first pass.
Every jurisdiction has its own requirements. Use this checklist as a preparation tool alongside the reviewing department’s current submission checklist and adopted regulations, not as a replacement for them.
A site plan review checklist is a structured list of the information, drawings, and development standards to examine before submitting a proposed project for review.
It typically covers property identification, zoning information, site boundaries, building placement, setbacks, height, parking, access, landscaping, drainage, and supporting documents.
The exact scope depends on the project and jurisdiction. A small addition and a multifamily development will not necessarily require the same information or review process.
For an overview of the process, see what site plan review means.
Before reviewing individual dimensions, confirm what the reviewing department expects to receive.
Locate the current application form, submission checklist, drawing standards, and applicable review procedures. Check whether the project needs related approvals or supporting documents.
Questions to resolve include:
Record unresolved questions rather than filling the gaps with assumptions.
Start by making sure the drawing set clearly identifies the property and the proposed work.
Check that the application, cover sheet, and site plan use consistent information.
If the proposal involves multiple parcels, make their relationship clear. Do not assume the reviewer will infer which boundaries or areas are included in the application.
A site plan needs to be checked against the requirements governing the property, not a similar project or a nearby parcel.
Confirm the zoning district and identify any applicable overlays, site-specific approvals, or other provisions that may affect the proposal.
A compact zoning summary can make the relationship between requirements and proposed conditions easier to review.
Review item
Applicable requirement
Proposed condition
Source or open question
Proposed use
Confirm applicable use provision
Describe proposed activity
Record ordinance reference
Front setback
Confirm minimum and measurement rule
Show proposed dimension
Identify supporting plan sheet
Building height
Confirm limit and measurement method
Show proposed height
Record calculation or detail
Parking
Confirm applicable requirements
Show proposed provision
Explain calculation basis
Avoid entering a number without recording where it came from and how it applies.
The reviewer needs to understand the site geometry and read the information supporting the proposal.
Check that the plan distinguishes property boundaries, rights-of-way, easements, existing improvements, and proposed work.
Where boundary information is uncertain, identify the uncertainty and obtain appropriate documentation rather than treating an approximate line as verified.
Setback review requires more than showing a distance near a building. The dimension needs to connect the correct property boundary with the part of the improvement regulated by the ordinance.
Check the applicable measurement rules and any provisions addressing projections or encroachments.
For a plain-language explanation, see what a setback is.
A useful test is whether someone unfamiliar with the design can locate the dimension and understand how it relates to the cited requirement.
Where these standards apply, show enough information for the reviewer to understand the calculation.
Do not assume that building height, floor area, or lot coverage is defined the same way in every ordinance.
Floor area ratio, or FAR, relates building floor area to lot area. The applicable ordinance determines how the relevant areas are counted.
When a calculation excludes an area, explain the basis rather than leaving the reviewer to reconstruct it.
Where parking and loading requirements apply, show both the layout and the basis for the calculation.
The number of spaces alone may not explain whether the proposal meets the applicable standards.
If a proposed reduction, shared arrangement, or alternative standard is being used, identify the supporting provision or approval process.
The site layout should account for requirements and constraints beyond the building footprint.
Depending on the project, this may include landscaping, buffers, screening, easements, or other site conditions.
Do not assume that zoning compliance alone resolves every restriction affecting the property. Record questions that need separate investigation or professional review.
A site plan may need to be coordinated with civil, utility, landscape, and other drawings.
This checklist does not replace engineering or discipline-specific review. Its purpose is to identify missing information and inconsistencies before submission.
For example, if the architectural site plan and civil plan show different building locations, resolve that difference before submission.
A complete submission and a compliant proposal are not the same thing.
Completeness asks whether the information needed for review is present.
Compliance asks whether the proposal satisfies the applicable requirements.
Review question
Type of check
Is the front setback dimension shown?
Completeness
Does that dimension satisfy the applicable requirement?
Compliance
Is the parking calculation included?
Completeness
Does the calculation use the correct requirement and inputs?
Compliance
Are elevations provided?
Completeness
Does the documented height meet the applicable standard?
Compliance
Missing information should not automatically be treated as proof of noncompliance. It may mean the reviewer cannot yet reach a conclusion.
Keeping these categories separate makes internal review comments more useful: add information, correct a discrepancy, verify a requirement, or revise the design.
AI-assisted review can support an initial check of the drawing set against configured requirements.
Conflation Labs’ AI Plan Review is designed to return a cited, reviewable checklist against measurable development standards, including setbacks, parking, and building height.
The AI Site Plan Review user guide explains that results can identify items as Pass, Fail, or Needs Review. It also makes clear that the system is a screening tool, not a final determination.
Before relying on a finding:
Availability and supported checks depend on the city-specific configuration. Confirm the scope before assuming every requirement in this checklist is covered.
For applicant-focused information, explore site plan review for architects and AEC teams.
Use this as an internal review aid, then compare it with the jurisdiction’s current requirements.
Check
Complete / needs review / not applicable
Current local submission checklist reviewed
Correct application and review process confirmed
Property address and parcel information verified
Project description and contact information included
Governing jurisdiction and zoning district confirmed
Applicable overlays and prior conditions checked
Proposed use reviewed against applicable provisions
Property boundaries and relevant easements identified
Scale, north arrow, labels, and dimensions readable
Existing and proposed conditions distinguished
Setbacks shown and measurement rules checked
Height information and calculation basis included
Lot coverage and FAR calculations checked where applicable
Parking and loading calculations documented
Access and circulation information included
Landscaping and screening requirements addressed
Required drainage and utility documents included
Supporting plans coordinated
Sheet index and revision information consistent
Missing information and unresolved questions logged
Required professional review completed
A site plan commonly shows property boundaries, existing and proposed improvements, relevant dimensions, access, parking, and other information needed to evaluate the proposal. The reviewing department’s current checklist determines the required submission contents.
No. A property survey documents boundary and other surveyed information within its scope. A site plan shows the proposed layout and improvements. Survey information may support preparation and review of the site plan.
No. A complete submission provides the information needed for review. The proposal must still be evaluated against applicable requirements and approval procedures.
AI-assisted screening is not municipal approval. The responsible reviewers and authorities must verify findings and complete the required review process.
Record the specific question, the relevant provision, and the part of the proposal it affects. Seek clarification from the reviewing department or an appropriate professional rather than designing around an unsupported assumption.
A useful pre-submission check connects each requirement with clear information in the drawing set.
The reviewer should be able to identify the property, understand the proposal, locate the supporting dimensions, and see how the applicable standards have been addressed.
Start with the local submission checklist. Use a structured internal review to identify gaps. Keep unresolved questions visible. Treat automated findings as information to verify, not final approval.
Explore Conflation Labs’ AI Plan Review to see how a cited first-pass checklist can support that process.[conflationlabs][conflationlabs]