Land Use & Zoning
Before You File: Making the Most of a Preapplication Meeting
November 16, 2026
A preapplication meeting is easy to treat as a preliminary stop on the way to filing a land use application. Used well, it can shape the application itself.
For a developer or property owner, the opportunity is to discuss a proposal with local staff while there is still room to adjust it. That conversation can help the team understand which assumptions need testing, what information reviewers will expect, and where additional work belongs before the first submission.
Preapplication review in Northern Virginia
The name and format vary by locality. In Fairfax County, the Zoning Case Pre-Application Consultation is generally an optional service. Staff reviews the request internally and follows up with comments; an additional meeting may be recommended. Prince William County calls it a Pre-Application Meeting and generally recommends one before a rezoning application, but requires it for planned district development proposals. For special-exception site plan proposals, Arlington County offers Conceptual Site Plan Review, an optional but encouraged step before formal application.
Whether required or optional, the purpose is to obtain preliminary feedback before formal application review begins. Applicants should confirm the procedure for their particular application rather than assume that every early consultation follows the same format.
What an applicant can learn
One of the most useful subjects is the approval path. An applicant may arrive expecting to amend an existing approval and learn that a different application is needed. A proposed use may also require a closer look at how the business will operate. Hours, deliveries, outdoor activity, and the relationship between different uses on the property can matter as much as the label placed on a drawing.
Existing approvals deserve attention, too. A property may already be subject to conditions governing access, parking, landscaping, or operations. An expansion or change in use creates a reason to examine which conditions still fit and which the applicant will need to ask to change. Identifying that question early helps the team describe the full request rather than leave an important part of it unstated.
The discussion can also reveal what staff needs to understand the proposal. A plan view may show where a building sits without explaining how its height relates to surrounding properties. A circulation diagram may need an explanation of deliveries or customer arrivals. For a phased project, the team may need to distinguish what will be built now from what remains conceptual.
These are useful subjects for a preapplication discussion because they affect what the team prepares next, including the scope of consultant work and the exhibits accompanying the application.
Bring something staff can evaluate
The meeting is most useful when the applicant provides a clear description of the proposal, a concept plan, relevant approval history, and focused questions. Materials should meet the locality's requirements, but their practical purpose is to make the proposal understandable.
A polished rendering alone may not do that. Staff also needs to know what the applicant intends to do on the property, what is changing, and where the team needs guidance. If access, a requested modification, or the treatment of an existing condition is central to the proposal, identify it in advance.
The concept should be developed enough to support a meaningful discussion without presenting every design choice as settled. Where an applicant meeting is part of the process, involve the team members who can explain the intended operations and design. When an answer is not yet available, record the question and follow up rather than make an assumption on the spot.
I help clients prepare by reviewing the property's zoning and approval history and working with the design team on the narrative and questions for staff. I also participate in the discussions and help the team decide how to address the feedback in its application.
Use the feedback in the first submission
After the meeting, the applicant should turn the discussion into assignments. Some comments call for a plan revision. Others require a study, a clearer narrative, or a separate conversation with the agency responsible for a particular issue. The team should also distinguish what must accompany the initial application from details that belong at a later stage. If a separate formal determination is required, a preliminary discussion does not replace it.
In one matter involving the expansion of an existing use, a preapplication discussion drew attention to a traffic-related condition in an older approval. The scope of the transportation study was a separate question from how the proposal would address that condition. The application we subsequently submitted expressly requested that the old condition not be carried forward and explained the proposed operations and circulation. The discussion helped us frame that request before filing, rather than leaving the relationship between the new proposal and the earlier approval unclear.
A stronger first submission addresses the issues already identified. If staff questioned how a proposed use will function, the narrative should explain the operation. If an existing approval creates a restriction, the application should identify the change being requested. If staff needs to understand building scale or site circulation, the appropriate exhibit should be included and coordinated with the plans.
That does not mean accepting every suggestion. A comment may reflect a legal requirement, a planning policy, a preliminary interpretation, or a design preference. The applicant needs to understand the basis for the comment before deciding how to respond. Where the team proposes a different approach, the submission should explain it rather than leave the reviewer to infer the answer.
Keep the meeting in perspective
Preapplication feedback is preliminary. The meeting does not approve the project or replace formal review, and applicants should not treat the feedback as a commitment by the eventual decision-maker. Further analysis, design changes, and public input can raise additional issues. Silence on a subject should not be treated as confirmation that it has been resolved.
The practical benefit is a better-informed first submission. A well-prepared applicant leaves with a clearer understanding of what needs to be explained, investigated, or revised, and uses that information before the application is filed.
For questions about preparing a land use application or evaluating a proposed development, please contact Andrew W. Gregg at 703.284.7254 or agregg@beankinney.com.
This article is for informational purposes only and does not contain or convey legal advice. Consult a lawyer. Any views or opinions expressed herein are those of the authors and are not necessarily the views of any client.