Do I Need a Pre-Application Meeting? Hillsboro, Beaverton, Tigard, and Washington County
When a pre-app is required, when it's worth having anyway, and when you should skip it and submit the permit
A pre-application meeting can sound like a formality—a box to check before submitting for permits. In Hillsboro, Beaverton, Tigard, and unincorporated Washington County, it can be much more valuable than that.
For the right project, a pre-app can identify the land-use path, site constraints, infrastructure requirements, and outside-agency coordination before substantial money is spent on design. For a straightforward project, however, scheduling one may add a step that provides little value.
The important question is not simply, "Do I need a pre-app?"
It is: "What approval path is this project actually on?"
I spent eight years working on the jurisdiction side as a plans examiner and building inspector before becoming an architect. One of the recurring problems I saw was not owners misunderstanding a particular code section—it was owners beginning design before anyone had clearly established the regulatory path.
A pre-application meeting can help prevent that, but only when it is the right tool.
Building Code and Permit Support · Permit Path Review
JR-DBA reviews zoning, land-use history, and site constraints to confirm whether your project needs a pre-application meeting, a land-use application, or can go straight to building permit—and, when a pre-app is worth having, prepares the site plan, narrative, and questions that make the meeting productive.
Schedule a Permit Path Review → · Visit JR-DBA →
What a Pre-Application Meeting Actually Is
A pre-application meeting or conference is an early discussion with jurisdiction staff about a proposed development or land-use project before the formal application is submitted.
Depending on the jurisdiction and project, representatives may include planning, engineering, transportation, building, fire, utilities, or other agencies.
The applicant typically provides preliminary information such as:
A site plan
A description of the proposed use and scope
Existing and proposed development
Known site constraints
Specific questions for staff
The purpose is to identify the likely approval path and major issues before the project is substantially designed.
It is important to understand what a pre-app is not.
It is not a building permit review, and it generally does not constitute a final approval or guarantee that a later application will be approved. Conditions can change as the design develops, additional information becomes available, or the formal application is reviewed against the applicable approval criteria.
Think of the pre-app as early regulatory due diligence, not an approval.
When a Pre-App May Be Required—or Worth Having Anyway
This is where jurisdiction matters.
There is no single "Washington County pre-app rule" that applies equally to Hillsboro, Beaverton, Tigard, and unincorporated Washington County. Each jurisdiction administers its own development process.
For example, Beaverton's Development Code requires a pre-application conference for proposals that need Type 2 or Type 3 applications. Tigard's code similarly requires one for most Type II and Type III applications, though the director may waive it. (Tigard Development Code 18.710) Washington County recommends a pre-application conference but allows applicants to proceed without one by signing a pre-application waiver. (Washington County land development process) Hillsboro offers pre-application meetings to help applicants identify site constraints and land-use issues before filing. (Hillsboro pre-application meeting request)
That distinction matters.
Rather than assuming a pre-app is always mandatory, I generally look first at whether the project involves issues such as:
New commercial or multifamily development
A land division, partition, or planned development
Conditional-use approval
Design review
A variance, adjustment, or other discretionary land-use request
A change of use with potential land-use implications
Significant site development or frontage improvements
Floodplain, wetland, natural-resource, or steep-slope constraints
Significant tree impacts
Transportation or access issues
Clean Water Services coordination
Uncertainty about which land-use application or review procedure applies
Even where a pre-app is technically optional, one may be worthwhile when resolving these questions early could prevent substantial redesign later.
When You Probably Don't Need One
Many projects do not need a formal pre-application meeting.
A straightforward residential remodel that complies with zoning, an addition that meets applicable development standards, or certain interior commercial tenant improvements may proceed directly toward the applicable permit process without a formal land-use pre-app.
The key is confirming that assumption first.
For example, an interior tenant improvement might appear to be building-permit-only work until the proposed use raises questions about parking, occupancy, site improvements, or an existing land-use approval.
Similarly, a residential addition may appear straightforward until a setback, easement, environmental overlay, or other site constraint changes the approval path.
That is why I generally recommend a short zoning and permit-path review before automatically requesting a pre-app.
Sometimes the correct answer is:
You don't need the meeting. You need to submit the permit.
That can save both time and unnecessary process.
The Projects Where I Would Still Consider a Pre-App
There is another category: projects where a pre-app may not be strictly required but is still a good investment.
Suppose you are evaluating a commercial property before signing a lease. The proposed use appears allowed, but you are unsure whether a change of use will trigger site improvements, parking requirements, accessibility work, transportation review, or other development conditions.
That is exactly the type of situation where an early jurisdiction conversation can be valuable.
Commercial Due Diligence · Before You Sign
Evaluating a lease or purchase in Washington County? JR-DBA reviews zoning, change-of-use triggers, and existing-building conditions before you commit—so the pre-app, if you need one, confirms a plan rather than uncovering a surprise.
The same applies to a difficult residential site. If the property contains a steep slope, drainage issue, sensitive area, unusual access condition, or unclear development history, resolving those questions before completing the design can be far less expensive than discovering them during permit review.
The purpose is not to ask the jurisdiction to design the project.
It is to identify the regulatory constraints the design needs to solve.
How Not to Waste the Meeting
If you decide a pre-app is worthwhile, the quality of the meeting depends heavily on the information you provide.
I recommend going in with four things.
1. A Useful Site Plan
Show property lines, existing buildings, proposed work, access, setbacks, parking, and known site features.
It does not necessarily need to be a permit-level drawing, but it needs to communicate the proposal clearly enough for staff to evaluate it.
2. A Clear Project Narrative
Explain what exists, what you are proposing, approximate square footage, intended use, and anything about the project that could affect the approval path.
Do not make staff reconstruct the project from a collection of drawings.
3. Specific Questions
"Do you see any problems?" is not a particularly useful pre-app question.
Better questions are:
Does this proposal require a land-use application before building permit submittal?
What application type applies?
Is an adjustment or variance required?
Will frontage improvements be triggered?
Does the site require Clean Water Services review?
Is a traffic analysis required?
Are there tree, floodplain, or natural-resource reviews?
What approvals must be completed before the building permit can be issued?
Specific questions tend to produce specific answers.
4. Document the Answers
Pre-app comments are generally preliminary, not final land-use decisions.
Still, written meeting notes can become an extremely useful roadmap for the project team.
After the meeting, convert the discussion into a simple list:
Requirement → Responsible Party → Required Before → Next Action
That turns a meeting into a permitting strategy.
A Pre-App Does Not Replace Due Diligence
This is one of the most important distinctions.
Jurisdiction staff can identify applicable processes and raise potential concerns, but they are not the project's architect, engineer, land-use consultant, or owner's representative.
The applicant still needs to understand the property and ask the right questions.
Before a pre-app, I typically want to understand:
Zoning and permitted uses
Existing land-use approvals
Property boundaries and easements
Applicable overlays
Existing building and occupancy information
Proposed use
Site-development implications
Known utility and infrastructure constraints
Likely discretionary approvals
Doing that work beforehand makes the jurisdiction meeting substantially more productive.
It also helps distinguish between a question that actually needs jurisdiction interpretation and one that can be answered by reviewing the applicable code.
Where the Pre-App Fits Into the Permitting Strategy
A pre-application meeting is one possible step in a larger sequence.
For a project requiring land-use approval, that sequence may look something like:
Feasibility → Zoning Review → Pre-Application Meeting → Land-Use Application → Building Permit → Construction
For a straightforward project, it may be much shorter:
Feasibility → Zoning Confirmation → Building Permit → Construction
Knowing which sequence applies is more important than automatically scheduling every possible meeting.
This is the same distinction I discuss in Land Use First, Building Permit Second: zoning and land-use approval are separate from building-code review. If a land-use approval is required, completing a technically excellent building permit set does not eliminate that requirement.
The jurisdictions across Washington County—including Hillsboro, Beaverton, Tigard, and unincorporated Washington County—also administer development differently. Processes, application types, fees, and review requirements can change across jurisdictional boundaries.
That is why early permit-path research is often more valuable than simply beginning drawings. And if a project has already moved forward and the permit has stalled, My Oregon Building Permit Was Rejected or Stalled walks through how to diagnose where it stopped.
The Bottom Line
A pre-application meeting is neither something every project needs nor something complex projects should casually skip.
The right question is whether the meeting will resolve a meaningful uncertainty before that uncertainty becomes expensive.
If the zoning, land-use path, site constraints, and permit sequence are already clear, a formal pre-app may add little value.
If they are not clear—particularly for commercial development, changes of use, difficult sites, discretionary land-use applications, or projects involving multiple agencies—an hour spent resolving those issues early can be one of the more productive meetings on the project.
The goal is not to add another step to permitting.
It is to make sure you are on the right path before you start spending money moving down it.
Ready to Move Your Project Forward?
If you're planning a residential or light commercial project in Washington County and aren't sure whether you need a pre-application meeting, land-use approval, or a straightforward building permit, JR DBA can help establish the permitting path before design proceeds too far.
Schedule a Permit Path Review →
Joshua Richards Principal | JR Design Build Architect (JR DBA) Residential Design | Building-Code and Permit Support | Owner's Representation ICC Certified Commercial and Residential Building Inspector + Plans Examiner
www.jr-dba.com Joshua@jr-dba.com 971.217.7967
Service Area: Oregon and Southwest Washington—including Portland, Beaverton, Hillsboro, Tigard, Lake Oswego, Washington County, Vancouver, Camas, and Battle Ground. Projects outside these areas are considered case by case.
Related Reading
Land Use First, Building Permit Second: Oregon's Most Misunderstood Rule for ADUs and Small Projects
My Oregon Building Permit Was Rejected or Stalled—What Should I Do Next?
Permit Fees in Oregon: Plan Review, Reinspection, SDCs, and Other Costs That Surprise Owners
Suggested meta title: Do I Need a Pre-App Meeting? Washington County, OR Guide
Suggested meta description: Pre-app rules differ across Hillsboro, Beaverton, Tigard, and Washington County. Here's when a pre-application meeting is required, worth it, or skippable.
Category (SEO Funnel): Permitting & Building Code, Due Diligence
Service Alignment: Permitting / Due Diligence
Tags: pre-application meeting, pre-application conference Oregon, Washington County pre-app, Hillsboro pre-application meeting, Beaverton pre-application conference, Tigard pre-app, pre-app waiver, land use vs building permit, change of use, Clean Water Services, permit path, commercial due diligence
