How Town Planning Works | TPW-0180 — The Pre-Application Conference: How Planning Finds the Expensive Problems Before the Formal Review Clock Starts

Series ID: TPW-0180

A developer can spend six months drawing a building that was never going to fit the planning system.

The land use may be wrong for the district. The access may cross a road controlled by another agency. The sewer connection may require an upgrade nobody priced. A wetland, heritage constraint, airport surface, fire-access requirement or school-site issue may sit outside the architect’s first brief. The project may need a rezoning before it can even enter the approval path the team has been preparing for.

None of those problems is necessarily fatal.

They become expensive when they are discovered late.

That is the operating logic of the pre-application conference: bring the project concept into contact with the planning system before the applicant commits to a formal submission, so the difficult questions become visible while the project is still cheap enough to change.

Current practice shows how active this mechanism remains. Larimer County describes its pre-application meeting as the place where staff review procedures, code standards, submittal requirements and key concerns before a formal application. Sacramento County offers pre-application review involving planning, site improvement and transportation staff. Thornton describes the meeting as the first step before initial application review. Anna, Texas, publishes a 2026 process that separates the early pre-application meeting from a later formal application review meeting. Tucson’s 2026 project records show fire, zoning, historic-preservation and other disciplines participating in pre-application review of real proposals.

These systems differ in law, fee, format and mandatory status. The common planning job is the same.

The reader job: use early review to expose risk without pretending the project has been approved

This article has one narrow job. It explains how a pre-application conference can turn an early concept into a more informed application without becoming a private approval, a negotiation that binds future decision-makers, or a substitute for the formal public process.

The neighbouring owners are already clear. The Application Completeness Test owns the moment when a submitted application becomes complete enough for formal review. The Site Plan Review owns the formal assessment of a proposed site. The Plan Stack owns the hierarchy of plans and development control. The Planning Condition Lifecycle owns conditions after approval.

The Pre-Application Conference owns an earlier question: before the applicant starts the formal process, what information can the planning system reveal that materially changes the project, the approval route, the evidence required or the cost of proceeding?

The meeting belongs before the drawings become emotionally expensive

Design teams become attached to work they have already paid for.

A concept that exists as a rough site plan can still rotate, shrink, move, split into phases or change access. A concept represented by months of architecture, consultant reports and lender assumptions becomes harder to change even when the planning problem is obvious.

The pre-application meeting should therefore occur when enough information exists for staff to give useful feedback, but before the design has hardened.

This is why many authorities ask for a concept plan rather than a full formal package. Sacramento County states that at least a conceptual site plan is needed for actionable feedback and that more complete concepts produce more useful comments. Thornton asks for a cover letter describing proposed uses, units, floor area, business types, employees, hours and acreage. The objective is not presentation quality. It is decision-relevant information.

A pre-application meeting is not a free design studio

Planning staff should not design the applicant’s project.

The meeting exists to identify applicable rules, likely approval pathways, known constraints, required agencies, evidence needs and obvious conflicts. Staff may explain that the proposed access location is inconsistent with adopted standards or that a different layout could avoid a variance, but the applicant remains responsible for design.

This boundary matters for fairness. If staff become the private design team for one sophisticated applicant, others do not receive equal treatment. It also protects later review. The planning authority should be able to assess the formal application independently rather than defend a design it helped create.

The first question is not “Do you like the project?”

The strongest opening question is: what approval path does this concept actually require?

Is the proposed use permitted by right? Conditional? Prohibited? Does the site need rezoning? A variance? A subdivision? A heritage approval? Environmental review? A development agreement? A temporary-use permit? A road-access approval? A utility commitment?

A project can lose months by preparing the wrong application type.

The current Permitted Use Table article explains how one land-use classification can determine the path. The pre-application conference is where that classification becomes a project strategy.

Confirm the property before discussing the project

The same concept can require a different planning response on the parcel next door.

Verify parcel identifiers, zoning, overlays, plan designations, legal access, easements, subdivision status, existing approvals and any recognised nonconforming rights. Confirm whether the applicant controls the whole site or only part of it.

This prevents a surprisingly common failure: spending most of the meeting discussing a concept while everyone is working from an incomplete understanding of the land itself.

The property is the planning platform. Establish it first.

Bring the agencies that own the likely bottlenecks

A planning-only meeting can identify planning issues and still miss the issue that later stops the project.

Complex proposals may need transportation, fire, water, sewer, drainage, environmental, heritage, parks, schools, building, accessibility or utility input. Tucson’s current pre-application records demonstrate the value of multidisciplinary review: fire and historic-preservation comments can surface at the concept stage alongside zoning review.

The meeting does not need every department for every shed, extension or small shop. The art is proportionality. Invite the disciplines whose issues could materially change feasibility, layout or approval route.

The agenda should follow risk, not department hierarchy

Meetings often proceed around the table: planning comments, engineering comments, fire comments, utility comments.

A better structure begins with the highest-risk questions.

Is the use allowed?
Does the site have legal and physical access?
Is there a major environmental or heritage constraint?
Is critical infrastructure capacity available?
Does the concept depend on discretionary relief?
Does the proposed density or intensity conflict with the adopted plan?
Will another agency control a decisive permit?
Is land dedication or off-site infrastructure likely?

If one of these answers changes the project fundamentally, discover it before spending twenty minutes on landscape species or sign placement.

Separate fatal constraints from solvable constraints

Not every red flag means stop.

A prohibited use under current zoning may require rezoning rather than abandonment. A full sewer line may be solved by a funded upgrade. A difficult driveway can move. A heritage building can sometimes support adaptive reuse. A steep slope may shift the buildable envelope rather than eliminate development.

The pre-application record should distinguish:

Fatal under the current proposal: the concept cannot proceed as shown.
Route-changing: a different entitlement or approval process is required.
Design-changing: layout or programme should change before formal submission.
Evidence-changing: a technical study or specialist input is required.
Timing-changing: infrastructure, another permit or an adopted project controls the schedule.
Cost-changing: an obligation is likely to affect feasibility but not permission.
Minor: an issue can be resolved during ordinary review.

This hierarchy turns comments into decisions.

The meeting should identify evidence before consultants are hired

Applicants can spend heavily on reports the authority did not need while omitting the study that matters.

The pre-application stage is the place to identify likely requirements: traffic analysis, drainage, flood study, ecological survey, geotechnical report, heritage impact assessment, acoustic analysis, arborist report, school-capacity analysis, market or viability evidence, shadow study or utility modelling.

The authority should also explain the decision each study is meant to inform. “Provide a traffic report” is weaker than “provide peak-hour access and queue analysis because the decision must determine whether vehicles can enter without blocking the arterial.”

Evidence is more useful when its planning job is clear.

Do not promise an approval the formal decision-maker has not made

This is the central governance boundary.

Pre-application advice is commonly non-binding. Staff can say a concept appears consistent, identify likely standards and describe past interpretations. They should not tell the applicant that a discretionary board will approve a variance, conditional use, rezoning or heritage departure.

The advice should contain a clear caveat: formal review may identify additional issues, rules can change, other agencies retain their authority, and the legally designated decision-maker will make the final determination.

That caveat is not bureaucratic evasion. It protects the integrity of the formal process.

Do not use “non-binding” as an excuse for vague advice

Applicants still need useful information.

A good comment says: the current zoning district does not permit this principal use; a map amendment would be required under the present code. Or: the fire department’s initial review indicates the shown access geometry is unlikely to satisfy apparatus access; revise the plan before formal filing. Or: the parcel lies inside the mapped flood overlay and finished-floor elevation evidence will be required.

A weak comment says: “There may be issues; further review required.”

Non-binding advice can still be specific about known rules and visible constraints.

Record the meeting

Memory is not an administrative system.

After the meeting, issue a written summary listing the concept reviewed, date, attendees, applicable approval routes, major issues, likely evidence requirements, agency referrals and any assumptions underlying the advice.

The record protects both sides. The applicant can show its consultants what was discussed. Staff reviewing the formal application can understand the project history. If personnel change, the new planner does not need to reconstruct the meeting from email fragments.

Version the concept that was reviewed

Advice can become misleading if the project changes after the meeting.

A 60-unit apartment concept with one access point may receive different comments from a 180-unit project with retail and a second access. The meeting record should identify the plan version, date and basic programme reviewed.

If the concept changes materially, a second conference may be useful. Anna, Texas, currently uses a process where the pre-application meeting and formal review meeting are time-linked, recognising that stale advice loses value.

The meeting should expose cross-department contradictions

Planning may want buildings close to the street. Fire may ask for access space. Transportation may want fewer driveways. Utilities may need a corridor exactly where landscape standards require trees.

Discovering these conflicts at formal plan review creates redesign cycles.

The pre-application conference gives departments an opportunity to see one another’s requirements. The objective is not to erase every technical standard. It is to identify where standards collide so a coordinated solution can be designed before the applicant receives contradictory redlines.

Infrastructure should be discussed as a system, not a checkbox

“Water available: yes” is not enough for a major project.

Where is the connection? Is capacity reserved? Is a trunk upgrade funded? Does the project need land dedication? Is stormwater managed onsite or through a regional system? Is road access controlled by the city, county or national authority?

The current Concurrency Test article explains how facility capacity changes growth timing. The pre-application meeting is the first place where that capacity question should become visible to a specific proposal.

The meeting can save the applicant from unnecessary discretionary relief

A rough plan may show a setback encroachment, excess height, awkward parking or noncompliant frontage simply because the designer did not yet understand the code.

Moving a building two metres at concept stage may eliminate a variance. Rotating an access point may eliminate a conditional approval. Reclassifying a legitimate accessory activity may avoid an unnecessary use application.

This is one of the highest-value functions of early review: solve an ordinary compliance problem with ordinary design before converting it into a discretionary planning case.

But staff should not redesign the project solely to avoid public review

There is an opposite danger.

If a proposal genuinely requires rezoning, a major conditional use or another public process, the objective should not be to manipulate the design until the project can be approved quietly under a lesser category.

Administrative efficiency cannot replace the legal threshold for public participation.

The pre-application stage should identify the correct process, not the least visible process.

Pre-application meetings can improve application completeness

A formal completeness review asks whether required materials have been submitted.

The pre-application conference improves the chance that those materials are the right ones.

If staff know a project needs a geotechnical report because of mapped slope, or a heritage statement because the site lies in a conservation area, the checklist can be customised before filing. This reduces cycles where the application is rejected as incomplete, resubmitted, rejected again and only then reaches substantive review.

The formal clock should start with a package capable of supporting the decision.

Small projects need a lighter route

A mandatory multidisciplinary conference can be disproportionate for a small deck, shop sign or routine addition.

Jurisdictions can tier early assistance. Simple proposals may use online zoning checks, planner-of-the-day service or short counter consultations. Medium projects may use a standard meeting. Large or unusual projects may receive a multidisciplinary conference with written comments.

The planning service should scale with project risk, not merely with applicant sophistication.

Fees should reflect service without making early advice a luxury product

Some jurisdictions charge for pre-application meetings because professional staff time is real. Others provide basic meetings without charge or offer several levels of paid review.

The policy question is access.

If only major developers can afford early coordination, small builders and community organisations may enter formal review with weaker information and experience more delay. A tiered model can preserve cost recovery while keeping basic guidance available.

Pre-application advice creates public value when it prevents avoidable review work later, so the fee should not be analysed only as a private service charge.

Publish the questions applicants should answer before the meeting

A productive meeting begins before everyone joins the call.

What is the site?
Who controls it?
What uses are proposed?
What approximate floor area, unit count or intensity is expected?
How will vehicles, pedestrians, cycles, servicing and emergency access enter?
What existing buildings remain?
What known constraints has the applicant identified?
What approval does the applicant think is required?
What are the applicant’s most important uncertainties?

Requiring this information makes the meeting a planning conversation rather than an improvised briefing.

The applicant should bring questions, not only a presentation

Teams sometimes spend half the meeting explaining the project and leave five minutes for the issues that matter.

The applicant should identify decision questions in advance. Is this use classification correct? Does the planning department agree that the frontage type applies here? Is a subdivision needed before site-plan approval? What environmental review pathway is likely? Which utility evidence is required?

The best meeting exchanges uncertainty for a list of next decisions.

Staff should prepare too

A meeting where staff first open the zoning map while the applicant is speaking wastes the mechanism.

Basic pre-meeting review should cover zoning, overlays, comprehensive-plan designation, known permits, obvious mapping constraints, nearby infrastructure projects and relevant application types.

The goal is not full review. It is enough preparation to identify the highest-value questions quickly.

Digital portals can make early advice cumulative

A pre-application meeting should create data that follows the project.

Store the concept, comments, agency responses and meeting summary in the same case system that later receives the formal application. When the project is submitted, reviewers can see which issues were identified and whether the applicant responded.

This reduces repetition. It also makes organisational learning possible: which issues appear most often at pre-application? Which departments repeatedly identify late constraints? Which code provisions create the most confusion?

The early-review database can become evidence for code reform.

Do not let the meeting become an invisible queue

If every formal application requires a pre-application conference, meeting availability becomes part of approval time.

A jurisdiction can claim that formal review takes sixty days while applicants wait three months for the required meeting that allows them to submit.

Track the waiting time. Publish available dates. Staff the service according to demand. Allow simple projects to bypass the meeting where appropriate.

Process transparency begins before the statutory clock starts.

Early community contact can be useful, but it is not the same as statutory notice

Some jurisdictions encourage or require neighbourhood meetings before certain major applications.

That can reveal local knowledge early: flooding, traffic queues, school pickup, parking spillover, valued trees, cultural uses or access problems that maps miss.

But early engagement does not replace formal notice or hearing requirements. The applicant should not be able to say “we spoke to the neighbours six months ago” as a substitute for the legally required opportunity to respond to the actual submitted proposal.

Early engagement and formal notice have different jobs.

The conference should identify what is policy and what is law

Applicants often hear comments such as “the city would prefer more active frontage” or “the adopted plan encourages housing here.”

Those statements may be important without being binding standards.

Staff should distinguish:

a mandatory code standard;
a discretionary approval criterion;
an adopted policy;
nonbinding design guidance;
a staff recommendation;
an issue controlled by another agency.

This prevents a planning preference from being mistaken for a legal requirement and prevents an actual requirement from being dismissed as optional advice.

The meeting should end with a route map

The applicant should leave knowing the likely sequence.

For example: confirm utility capacity; prepare traffic and drainage studies; submit rezoning and preliminary subdivision together; complete environmental review; then submit site plan; then building permit. Or: revise the layout to meet the base zone; no variance is expected; submit administrative site plan with landscape and access details.

This route map can change during formal review. It still provides a working sequence around which the team can plan consultants, financing and schedule.

A practical pre-application audit

Site: Are parcel boundaries, ownership and legal access understood?
Zoning: What base district and overlays apply?
Use: Is the proposed activity permitted, conditional, prohibited or unlisted?
Plan: Is the concept consistent with the applicable strategic or local plan?
Approval path: Which applications are actually required?
Decision-maker: Which matters are staff-level and which require a board or elected body?
Relief: Does the concept currently depend on a variance or administrative adjustment?
Subdivision: Must lots, easements or rights of way change first?
Access: Is legal and physical access workable?
Transport: What traffic, parking, pedestrian, cycle and servicing issues are already visible?
Fire: Are apparatus access, hydrants and emergency routes plausible?
Utilities: Is capacity known for water, sewer, power and other essential services?
Drainage: Are flood, stormwater or watercourse constraints present?
Environment: Are ecology, trees, contamination, habitat or geotechnical issues likely?
Heritage: Are protected buildings, archaeology or cultural landscapes involved?
Evidence: Which technical studies will support the formal decision?
Agencies: Which outside bodies control permits or infrastructure?
Community: Is early engagement required or useful?
Fees: What application, review or infrastructure costs should be anticipated?
Timing: Which dependency is likely to control the schedule?
Record: Will a written meeting summary be issued?
Non-binding status: Is the boundary between advice and formal approval clear?
Next step: Does the applicant leave with a concrete route map?

A worked example: discovering the real project before formal submission

Imagine an applicant arrives with a concept for 120 apartments and ground-floor retail on a five-hectare site.

The zoning permits mixed use, so the team assumes the project needs only site-plan approval.

At pre-application, staff discover four issues. The site is actually two legal parcels and the building crosses the internal boundary. The arterial road is controlled by a regional transport authority. The rear of the site lies inside a mapped flood overlay. The wastewater utility has capacity for only the first 70 units until a funded pump-station upgrade opens next year.

None of those facts means the project should be denied.

They change the route.

The applicant restructures the building so it no longer crosses the parcel boundary, begins the access conversation with the road authority, raises and relocates vulnerable ground-floor uses outside the flood area, and phases occupancy around the pump-station upgrade.

The formal application arrives three months later with the right agencies, studies and phasing assumptions already engaged.

The pre-application meeting did not approve the project.

It discovered what the real project was.

The best pre-application conference reduces surprise without eliminating judgment

Planning cannot promise that no new issue will appear after submission.

Detailed engineering reveals things concept plans cannot. Public participation adds knowledge staff may not have. Laws change. Agencies revise standards. A formal environmental review may identify an impact that was invisible at concept stage.

The purpose of pre-application is not certainty about the final answer.

It is a more modest and more valuable form of certainty: understand the site, identify the likely process, expose the major constraints, know which evidence is necessary, and avoid spending heavily on a version of the project that the planning system could have told you was wrong in the first hour.

Good pre-application review makes the formal process more honest because the applicant enters it knowing what the difficult questions are—not because staff have quietly decided the answers in advance.