How Town Planning Works | TPW-0111 — The Site Plan Review: How a Permitted Use Becomes a Real Building, Driveway, Footpath, Drainage System and Public Edge

Series ID: TPW-0111

A parcel can have the right zoning and still produce a bad site.

The use may be allowed. The building may fit within the permitted height. The floor area may be legal. Parking may meet the numerical requirement. Yet the entrance can still be in the wrong place, the loading bay can cut across the pedestrian route, stormwater can flow toward the neighbour, fire access can fail, trees can be squeezed into unusable strips and the public edge can become a blank service wall.

That is why planning systems often need a second layer after zoning permission: site plan review.

Site plan review is the point where the abstract development right becomes a physical arrangement on a real parcel. It asks not merely whether a use belongs here, but how the building, entrances, driveways, paths, parking, loading, drainage, landscape, utilities, lighting, refuse, fire access and public edge will actually fit together.

The American Planning Association has long described site plan review as a way to ensure that development proposals meet adopted development policies and site-specific design requirements. The mechanism remains visible in contemporary regulations. Charlotte, Vermont’s land-use regulations, adopted in March 2026, for example, include site-plan review standards alongside conditional-use and planned-unit-development provisions. The exact legal process differs by jurisdiction, but the planning job is widely recognisable.

The reader job: understand the last regulatory mile before a drawing becomes a site

This article explains what site plan review is for, what it should examine, how it differs from rezoning and conditional use review, how to prevent it from becoming an open-ended design negotiation, and how a modern planning department can make the process predictable enough for applicants while still protecting the public realm.

Neighbouring owners already cover the surrounding territory. The By-Right Approval owns the question of objective compliance under fixed standards. The Conditional Use Permit owns the decision about uses that are permitted only when findings and conditions make them compatible. The Objective Code owns measurable design rules. The Building Edge owns the street-facing relationship between private development and public space.

The Site Plan Review owns the operational question in between: once the development right is established, how do we verify that all of the physical systems on one parcel work together before construction begins?

Site plan review begins after the land-use question is mostly answered

Suppose a parcel is zoned for apartments over shops.

The zoning code may already answer the major use questions. Housing is permitted. Retail is permitted. The maximum height is six storeys. The required setbacks are known. The floor-area ratio is known. The broad development right exists.

Site plan review should not reopen the basic political question of whether apartments belong there. If it does, every by-right development becomes discretionary in practice.

Instead, site plan review asks whether the submitted arrangement complies with the adopted rules and whether the different site systems have been coordinated correctly.

The site plan is a systems diagram

A good site plan is not merely a bird’s-eye picture of a building.

It is a systems diagram showing how many physical networks occupy the same land.

Buildings need foundations, entrances, service areas and fire access.
People need safe routes from the street, transit stop, parking and neighbouring parcels.
Vehicles need driveways, turning space, loading, parking and emergency access.
Water needs grading, drainage paths, storage, infiltration and safe discharge.
Utilities need easements, transformers, meters, valves and maintenance access.
Waste needs storage, collection and truck access.
Trees need soil volume, water and canopy space.
Lighting needs coverage without excessive glare.
Neighbours need protection from runoff, noise, headlight spill and service conflicts.

The site plan review is where those systems are forced to coexist on one drawing.

Completeness should be tested before quality

One of the most common planning delays begins when a review starts before the application contains enough information to be reviewed.

A planner comments on the parking layout. The drainage engineer later discovers that a stormwater facility occupies the same space. The fire reviewer asks for a turning path that moves the building. The revised building then changes the landscape plan and accessible route.

This is not efficient iteration. It is incomplete intake.

A mature system separates completeness review from substantive review. The completeness stage asks whether the required plans, calculations, ownership information, surveys and studies are present. Only then does the technical review begin.

The application checklist should match the project type

A two-storey shop extension should not need the same package as a hospital campus.

Application requirements can be tiered by size, use, hazard and complexity. A small project may need a simple site plan, photographs and basic drainage information. A major project may require traffic analysis, landscape calculations, fire-truck turning templates, photometric plans, utility coordination, stormwater modelling and phasing information.

The rule should be proportionate: ask for the evidence needed to test the applicable standard, not every study the department knows how to request.

Pre-application meetings are useful when they reduce uncertainty rather than create unwritten rules

A pre-application meeting can reveal obvious constraints before expensive design begins.

The planning department can identify applicable overlays, major access issues, likely studies, utility constraints, heritage requirements and approval sequence. The applicant can explain the concept and ask how the code will be interpreted.

The danger is that informal advice becomes a shadow ordinance. “We usually ask for another five metres here” is not a substitute for an adopted setback. “The committee prefers this material” should not become an invisible condition on a by-right project.

Good pre-application guidance distinguishes legal requirements, staff recommendations and unresolved issues.

The first spatial question is usually building placement

Where the building sits affects almost everything else.

Move the building forward and parking may shift behind it. Move it backward and the street edge may weaken. Rotate it and the entrance may connect better to transit but create a servicing problem. Increase the rear setback and fire access may improve while the front plaza disappears.

Site plan review should therefore test placement early against the zoning envelope, frontage requirements, easements, environmental constraints and access needs.

Pedestrian movement should be drawn as a continuous route

Many plans show sidewalks as decorative lines around buildings.

The better test is a journey.

Start at the public footpath. Can a person reach the main entrance without crossing a loading bay? Start at the accessible parking space. Is there a protected route? Start at the bus stop. Is the path direct? Start at the neighbouring parcel. Is a connection possible or has the site been designed as an island?

A site can contain the required amount of pavement and still fail as a pedestrian network.

Vehicle access should be treated as a conflict problem, not only a geometry problem

A driveway can be wide enough for vehicles and still be badly located.

Its proximity to an intersection may reduce safety. Multiple driveways may fragment the footpath. A loading entrance may conflict with school arrival times. A garage ramp may place headlights directly into a neighbour’s windows.

The site plan should therefore show not only dimensions but relationships: sight distance, turning movement, pedestrian crossings, queue storage, adjacent access points and street function.

Fire access should be coordinated before the landscape plan is celebrated

Emergency access is one of the classic late-stage redesign triggers.

A landscaped courtyard may be beautiful until the fire service requires an access route through it. A narrow internal street may support walkability until turning geometry proves impossible for the required apparatus. A building projection may block aerial access.

The solution is not to let fire requirements automatically dominate urban design. It is to coordinate fire, building, access and planning standards early enough that one discipline does not undo the others after the design is mostly complete.

Parking review should ask what the parking does to the site

The number of spaces is only one question.

Where are the spaces? What does the pedestrian route cross? Does surface parking dominate the street? Is accessible parking near the correct entrance? Can shared parking work? Is bicycle parking useful or merely technically present? Is the loading area using the same manoeuvring space?

The broader parking policy belongs to The Parking Equation. Site plan review deals with the operational arrangement of whatever parking the applicable code requires or permits.

Loading is where elegant site plans often reveal whether they understand real buildings

Buildings need deliveries.

Restaurants need food and waste collection. Apartments need move-in access. Shops need stock. Offices receive couriers. Hospitals require specialised servicing. Large developments need maintenance vehicles and sometimes generators, fuel or medical deliveries.

If the site plan does not place these functions deliberately, they will happen anyway—often on the footpath, cycle lane or street.

Review should test bay dimensions, route, turning, hours, screening and conflicts with public movement.

Waste storage is a land-use interface

Refuse and recycling areas can generate odour, noise, pests and truck movement.

Putting them at the back of a drawing is not enough. The collector still needs access. Residents or tenants need a practical internal route. Neighbours need screening and separation. The bins need enough space for the actual service system.

Site plan review turns the invisible operational life of the building into a spatial design problem before occupancy begins.

Drainage begins with topography, not with a note that says “stormwater by engineer”

Water follows gravity regardless of zoning.

The plan should show existing and proposed levels, drainage direction, storage, infiltration, discharge points and how runoff interacts with buildings, neighbouring land and public streets.

A grading change that appears minor can redirect water onto the next parcel. A retaining wall can block an old surface path. A basement ramp can become a collection point. A landscape basin can fail if utilities occupy the same soil.

Stormwater review should therefore be integrated with site layout rather than appended after architecture is fixed.

Landscape review should measure living systems, not green colour on a plan

A plan can show many tree symbols and still provide too little soil for any tree to mature.

Review should consider species, soil volume, rooting space, irrigation, conflicts with utilities, canopy spread, visibility, maintenance and survival conditions.

Landscape is infrastructure when it shades footpaths, manages stormwater, screens servicing, supports habitat and improves thermal comfort. The site plan should give it enough physical space to perform those jobs.

Utility coordination is the underground site plan

Water, sewer, power, telecoms, district energy, drainage and gas can all need space below or beside the site.

Utilities require clearances, access for repair and equipment locations that often collide with trees, bicycle parking, accessible routes or active frontages.

The existing Hidden Town explains the larger network. Site plan review is where those networks touch one development parcel.

Lighting review should be about visibility and spill

Too little light can create unsafe routes. Too much can create glare, ecological impact and neighbour conflict.

A photometric plan can show light levels and spill at boundaries, but numbers should be interpreted with the site use. A loading yard, pedestrian plaza, residential entrance and car park have different needs.

The existing Night Lighting Code owns the wider regulatory logic. Site plan review checks how those standards are applied on one property.

The street edge should be reviewed from eye level

A plan view can hide a hostile frontage.

The building may technically touch the street while presenting a blank wall. Landscaping may look generous from above but form a visual barrier. The main entrance may face a car park rather than the public path.

Elevations, sections and simple perspective diagrams can help reviewers test what a pedestrian will actually experience.

Site plan review should not become architectural taste review

The process becomes unpredictable when comments move from adopted standards to personal preferences.

“Add a protected walkway because the code requires one” is a regulatory comment. “I would prefer a more elegant entrance” is not, unless the jurisdiction has an adopted standard that can be applied consistently.

Where subjective design review is intentionally part of the legal system, its scope and findings should be stated. Otherwise site plan review should remain tied to objective and adopted criteria.

Conditions should cure identifiable problems

A condition is strongest when it points to a standard, finding or documented impact.

Move the driveway because sight distance is inadequate. Add a pedestrian connection because the code requires a route from the public sidewalk. Relocate the refuse enclosure because the truck manoeuvre blocks emergency access.

A condition should not become a bargaining chip unrelated to the site-plan issue under review.

Interdepartmental review needs one consolidated answer

A single site may be reviewed by planning, transport, drainage, utilities, fire, parks, waste, accessibility and environmental staff.

If each department sends comments independently, the applicant can receive contradictions. Transport asks for a wider driveway. Planning asks for a narrower curb cut. Fire asks for a turning circle where landscape requires a tree grove.

The planning authority needs a coordination mechanism that resolves internal conflict before issuing comments.

One consolidated review letter is not merely better customer service. It is evidence that government itself has integrated its standards.

Comment cycles should distinguish major and minor revisions

Not every revision should restart every review.

If the applicant moves one bicycle rack, the drainage model need not be re-reviewed. If the building shifts five metres, several disciplines may need another look.

Digital workflows can track which sheets changed and route revised material only to affected reviewers. This reduces delay without weakening technical review.

Review clocks are useful only when the application is complete

Fast permitting policy often focuses on statutory time limits.

A clock helps only if everyone knows when it starts, what stops it and what information the applicant must provide.

Otherwise departments race through incomplete packages or applicants repeatedly submit partial responses that keep the clock technically alive while substantive issues remain unresolved.

Clear completeness rules make review-time targets meaningful.

Digital plan review should compare versions, not merely store PDFs

A document portal is not automatically a digital workflow.

A stronger system can identify the controlling version, compare revised sheets, record comments against locations, show issue status and preserve the final approved set.

This matters because construction inspectors later need to know which drawing was actually approved. A site plan review system should end with a definitive record, not a folder containing twelve similarly named uploads.

Machine-readable standards can accelerate simple checks

Many site-plan standards are geometric: setback, aisle width, accessible-route slope, landscape percentage, parking count, build-to line or maximum driveway width.

Where codes are written clearly, software can assist with early compliance screening. It can flag a missing dimension or apparent encroachment before human review.

Automation should not be confused with planning judgment. It is useful for repeatable checks. Humans remain necessary where context, evidence and competing public objectives must be weighed.

The review should identify the controlling drawing set

Large submissions contain civil drawings, architectural plans, landscape sheets, utility plans and specialist reports.

Those documents can contradict one another. The civil plan shows a transformer where the landscape plan shows a tree. The architectural plan moves the entrance but the accessible route remains on an older layout.

Final approval should therefore include a coordinated issue set with revision date and sheet index. If one document controls a conflict, say so.

Approval should distinguish design intent from construction detail

Planning approval should not try to perform the job of every technical permit.

Site plan review may establish where the driveway, building, trees and drainage facilities go. Detailed structural reinforcement, pipe sizing, electrical design and construction tolerances may belong to later engineering or building permits.

Trying to resolve every technical detail during planning can slow the process and duplicate later professional review. Resolving too little can leave major spatial conflicts until construction documents.

The line should be drawn around planning consequences: approve enough detail to know the site can work.

Minor field changes need a controlled amendment path

Construction reveals surprises.

A utility is not where the survey expected. Rock prevents the planned tree pit. A supplier changes equipment dimensions. A stormwater inlet needs to move.

The approval system should distinguish minor field changes from material amendments. A small technical adjustment that preserves all standards may be approved administratively. A change that moves the building, removes a public connection or alters a protected buffer may require formal amendment.

Without this distinction, every field adjustment becomes bureaucratic or every significant change becomes invisible.

Inspection closes the loop

A perfect approved plan has no public value if the site is built differently.

Inspection should verify the elements that mattered in review: accessible routes, landscape installation, drainage systems, parking layout, lighting, screening, public connections and required infrastructure.

Some features can be inspected during construction. Others should be checked before occupancy. Landscape may require replacement guarantees if planting dies shortly after completion.

The site-plan system is complete only when the built site matches the approved public commitments.

As-built information matters for future change

The approved plan shows intended conditions. The as-built record shows what was actually constructed.

That record becomes useful years later when the owner proposes an extension, utility repair, new entrance or redevelopment. It prevents the next planner from rebuilding the site’s history from incomplete permits.

Planning information becomes cumulative when each approval improves the parcel record rather than disappearing into an archive.

Site plan review is especially important for reuse

APA’s June 2026 Zoning Practice argues that zoning needs to move beyond a blank-slate bias and become better at reuse and redevelopment of already serviced land.

Site plan review is where that principle becomes operational.

An existing building may not be able to meet every new-site standard without demolition. The review process needs rules for lawful nonconformity, practicable upgrades and incremental improvement. Reuse should not be forced through a checklist written only for greenfield development.

The planning question becomes: which changes are necessary to make the new use safe and compatible, and which old conditions can remain because the alternative is losing a useful building entirely?

Small infill projects need a lighter path

A city that wants incremental infill should not subject a four-unit project to the same review architecture as a regional shopping centre.

Administrative review, standard details, pre-approved access arrangements and simpler submission requirements can make small projects predictable while preserving essential safety and public-realm standards.

Proportional process is part of housing and small-business policy.

Large sites need phasing plans that remain functional at every stage

A campus or master-planned project may build over many years.

The site plan should show not only the final condition but interim states. Where will pedestrians walk in Phase 1? Is emergency access complete? Does temporary parking block the future park? Is drainage functional before the final basin is built?

Every phase should work as a real place rather than as a fragment waiting for a future drawing to become true.

A worked example: one mixed-use corner

Imagine a six-storey mixed-use building proposed at a transit corner.

The zoning permits the use and height. The building meets the floor-area ratio. No conditional-use permit is needed.

The first site plan places the vehicle entrance on the main pedestrian street, the loading bay beside the bus stop, surface visitor parking in front of the building and the refuse enclosure at the neighbouring residential boundary.

Nothing about the underlying land use is wrong. The site arrangement is.

Site plan review can require the design to use the side street for vehicle access where the adopted access standard supports it, move loading away from the transit stop, relocate parking behind the building, create a direct public-footpath connection, screen refuse properly and demonstrate stormwater treatment.

The process does not renegotiate whether six-storey mixed use belongs there. It makes the permitted project function correctly on its parcel.

A practical site plan review audit

Entitlement: Is the proposed use and intensity already permitted, conditional or otherwise approved?
Completeness: Does the application contain every plan and study needed for the applicable standards?
Parcel: Are boundaries, easements, levels and existing features accurately shown?
Building placement: Does the building fit setbacks, frontage and other dimensional controls?
Pedestrians: Is there a continuous safe route from public space and transit to entrances?
Accessibility: Are accessible routes, parking and entrances integrated rather than added later?
Vehicles: Are driveways, sightlines, queues and turning movements safe?
Emergency access: Can required apparatus reach and operate without destroying the intended urban form?
Parking: Does parking placement support rather than dominate the public edge?
Loading: Can deliveries occur without blocking pedestrian, cycle or emergency routes?
Waste: Are storage, screening and collection workable?
Drainage: Does grading keep water away from buildings and neighbouring land?
Landscape: Do planting areas provide enough soil and space for intended performance?
Utilities: Are equipment and easements coordinated with trees, access and frontage?
Lighting: Is the site visible without excessive glare or spill?
Public edge: Do entrances, windows and site functions support the street?
Interagency coordination: Have contradictory departmental comments been resolved internally?
Conditions: Is each condition tied to an adopted standard or documented impact?
Version control: Is there one coordinated final drawing set?
Minor changes: Is there a clear administrative path for nonmaterial field adjustments?
Inspection: Who verifies that the approved site is actually built?
Record: Will as-built information be preserved for future permits and redevelopment?

The site plan is where planning stops being abstract

Zoning can say what may happen.

A site plan shows how it will happen.

That difference is the reason site plan review exists.

The building has to meet the ground. People have to enter it. Trucks have to service it. Rain has to leave it safely. Utilities have to reach it. Firefighters have to access it. Trees have to grow somewhere. Neighbours have to live beside it. The public footpath has to continue past it.

A mature site plan review process does not use those realities as excuses for endless negotiation. It translates them into a predictable checklist of spatial relationships and adopted standards.

The success test is whether a permitted project can move from entitlement to construction with fewer surprises because the important physical conflicts were discovered, coordinated and resolved while they were still lines on a drawing.