Before Revit is booted up or an application is filed, one of the most important steps in the development process is the pre-application meeting. These meetings are designed to bring developers, architects, and city staff together early, giving everyone a chance to align expectations and identify potential challenges before the project advances too far.

Many developers, especially those new to commercial projects, assume a pre-application meeting is simply a box to check. In reality, it can be one of the most valuable parts of the entire entitlement process. For seasoned operators, it offers a way to confirm timelines and reduce risk. For first-time developers, it provides clarity on the complex web of codes, standards, and approvals that must be satisfied.

What a Pre-Application Meeting Covers

A typical pre-application meeting includes representatives from several city departments, such as planning, zoning, traffic, water, utilities, and fire. Each department reviews the concept and provides feedback. Some comments may be straightforward, like confirming required setbacks. Others can completely change the scope of a project.

In a recent meeting for a proposed car wash and service facility, the city identified several issues that reshaped the project direction:

  • Zoning conflicts. The site was zoned to allow a car wash but did not permit vehicle repair or service. Identifying this early avoided the wasted time and money that would have gone into designing for a use that could never be approved.

  • Utility requirements. The water department required that at least 75 percent of the water be recycled for in-bay automatic car washes, along with specific agreements for larger meters. These conditions have direct implications on engineering and cost.

  • Traffic and access standards. The city required a traffic letter, truck turning templates, and specific access spacing. Knowing this in advance allowed the design team to plan site circulation correctly from the beginning.

  • Drainage dependencies. The site’s design relied on grading and infrastructure from an adjacent parcel that had not yet been constructed. The city noted that if that work was not completed in time, the project would need revisions to its civil engineering plans.

Each of these findings could have derailed the project if discovered during formal review. By surfacing them early, the development team could adjust their strategy before committing significant resources.

Why It Matters for First-Time Developers

For someone starting their first development, the pre-application meeting is often an eye-opening experience. It reveals how many different agencies have a say in whether a project is approved. It also highlights the level of detail that must be accounted for long before construction begins. From landscaping requirements to traffic safety measures, the city uses this meeting to outline the expectations that will ultimately decide whether a project moves forward.

Without this guidance, a first-time developer may overestimate how quickly a project can move through approvals or underestimate the costs of compliance. Pre-application meetings provide a clearer picture of what lies ahead, which helps with both budgeting and scheduling.

Why It Matters for Experienced Operators

For those who have gone through the process before, pre-application meetings are equally important. Even if you know what to expect, each jurisdiction has its own codes and standards, and those standards are updated regularly. What was permitted in one city may not be allowed in another. Meetings provide an opportunity to confirm the rules, learn about recent code changes, and avoid making assumptions that could cost valuable time.

Different Cities, Different Processes

Take Aurora, Colorado as an example. Aurora requires detailed staff review across multiple departments, and the feedback is extensive. Developers can expect comments on zoning, landscaping, utilities, drainage, traffic, and even architectural materials. The city has adopted a layered process with defined timelines, multiple phases of review, and community engagement requirements.

Now compare that with Phoenix, Arizona. While Phoenix is also a large and highly regulated city, the process has a slightly different character. The city emphasizes zoning and design standards. Developers familiar with Phoenix often remark that the process moves quickly once a project meets code, but that initial compliance is heavily scrutinized.

On the other end of the spectrum is a smaller jurisdiction such as Greenville, Texas. In communities like this, requirements may be less prescriptive. A project may only involve a handful of city staff members, and the review process may move with fewer layers of oversight. That flexibility can be helpful for developers seeking speed, but it also comes with the responsibility to self-regulate. Without as many checks in place, it becomes even more important that design, drainage, and safety measures are addressed properly by the architect

These examples show why assuming all jurisdictions operate alike can be costly. Each city has its own development culture, and the pre-application meeting is the best opportunity to learn how that culture will shape your project.

The Value of Certainty

At its core, the pre-application meeting provides some level of certainty. Instead of guessing how a city will respond, you walk away with written staff comments that serve as a roadmap for the next steps. This allows you to design with confidence, respond to issues before they become problems, and prepare submittals that align with city expectations.

For developers of all experience levels, certainty is invaluable. It saves money by preventing redesigns. It saves time by smoothing the review process. And it increases the likelihood that your project will move forward without unnecessary obstacles.

Ready to Navigate the Development Process With Confidence?

The development process is complex, and every step involves coordination among multiple parties. By treating the pre-application meeting as more than a formality, you position your project for success.

At Hover Architecture, we prepare clients thoroughly for these meetings so they can get the most out of the feedback provided. The insights gained in this early stage often make the difference between a project that struggles through approvals and one that moves forward smoothly.

Pre-application meetings are just the first step in a much larger journey. To help developers see the full picture, we’ve created a Development Roadmap that outlines every stage from land acquisition through opening day.

You can request a complimentary copy by filling out the short form below. Once submitted, you’ll receive the roadmap directly to your inbox.

Get Your Development Roadmap Today!

Name(Required)