Click here to view prior versions of this section.
1. To acquaint city and other agency staff with a sufficient level of detail about the proposed development to enable staff to advise the applicant of applicable approvals and requirements; and
2. To acquaint the applicant with the applicable requirements of the Vancouver Municipal Code and other laws and to identify issues and concerns in advance of a formal application to save the applicant time and expense through the process. However, the conference is not intended to provide an exhaustive review of all the potential issues. The pre-application conference does not prevent the city from applying all relevant laws to the application.
3. To inform applicable city recognized neighborhood associations of potential development activity within their neighborhoods.
B. Pre-application waivers.
1. A pre-application conference is required for all Type II, Type III and applicant-initiated Type IV applications, and certain Type I applications, unless waived by the planning official. Generally, the planning official may waive the pre-application conference only if he determines that the proposal is relatively simple (e.g., has few, if any, development-related issues), or it involves subsequent phases of an approved development where requirements are known, or an application is substantially similar to a prior proposal affecting substantially the same property, as determined by the planning official. Planning official shall notify affected Neighborhood Associations of proposed development application and copy of pre-application waiver letter. Pre-application conferences shall not be waived for infill developments, pursuant to Chapter 20.920 VMC.
2. To request a waiver of a pre-application conference, the applicant shall submit:
a. A completed pre-app waiver request form provided by the planning official;
b. A written narrative justifying the request for pre-application waiver; and
c. Required fee.
C. Information required for contingent vesting. To qualify for contingent vesting under Section 20.210.110 VMC, the applicant shall submit at a minimum the pre-application items listed in Sections 20.210.080(D)(1)-(6) VMC; provided, that an applicant shall not contingently vest unless the applicant submits all of the information required for the actual application within the timeframe set forth in Section 20.210.110 VMC. The planning official may modify requirements for pre-application materials and may conduct a pre-application conference with less than all of the required information. However, failure to provide all of the required information may prevent the planning official from identifying all applicable issues or providing the most effective pre-application conference and may preclude contingent vesting under Section 20.210.110 VMC. Review for completeness of the pre-application submittal will not be conducted by staff at the time of submittal and completeness is the responsibility of the applicant.
D. Application for a pre-application conference – Application – Fees. The applicant must submit a completed application form as prescribed by the planning official with applicable fee per Chapter 20.180 VMC. The planning official may waive submittal requirements upon request if found to be inapplicable to the proposed development:
1. Completed and signed pre-application conference request form provided by the planning official.
2. Information legible for digital reproduction and clearly marked with the following: project name; vicinity map; scale; north arrow; date; applicant’s name, phone and fax numbers; contact person’s name, phone and fax numbers.
3. A GIS packet obtained from Clark County’s Department of Assessment and GIS department for all properties covered by the application.
4. A narrative description of the following:
a. Uses proposed for the site.
b. Hours of operation.
c. Estimated vehicular traffic to and from the site.
5. Preliminary architectural information. A brief narrative description of the following:
a. Gross square footage of each structure and outdoor activity center proposed to be built or retained on site.
b. Proposed and potential uses and occupancy group of each structure proposed to be built or retained on site.
c. Number of floors, building height, and construction type of each structure and outdoor activity area proposed to be built on site.
d. Conceptual plans showing at least the gross square footage of each structure proposed to be built or retained on site.
e. Conceptual elevation drawing of each structure proposed to be built or retained on site.
f. Show the dimensions and area of the project site.
6. Existing and Proposed on-site Structures and Improvements:
a. Identify use(s) of all existing and proposed structures.
b. Location, dimensions, and height of all existing and proposed buildings and structures.
c. Location and dimensions of existing and proposed recreation areas and open space.
d. Location of existing and proposed driveways, off-street parking and loading areas, bicycle parking, and pedestrian and bicycle pathways.
e. Location, dimensions, and screening of proposed solid waste/recyclables storage areas.
f. Existing or conceptual plan showing lighting and landscaping. Landscape plan should include location of driveways and buffering off-street parking and loading areas.
g. Location and dimensions of existing and proposed streets, rights-of-way and public and private access easements on and adjoining the site.
h. Location and dimensions of all existing and proposed above ground and below ground utilities.
7. Preliminary engineering information. Provide a conceptual drawing or sketch showing the following:
a. Approximate location of existing fire hydrants within a one-hundred foot (100’) radius of the site.
b. Preliminary assessment of low impact development implications and proposed method of providing storm-water drainage on the site as required in VMC 14.25.
c. Strategy narrative for proposed erosion control measures as required in VMC 14.24.
d. Proposed grading activity for the site, indicating areas of native soil preservation, compaction prevention, and proposed cuts and fills.
E. Notice. Within 14 calendar days after receipt of an application for a pre-application conference, the planning official shall mail written notice to the applicant and to other interested agencies and parties, including the neighborhood association in whose area the property in question is situated. The notice shall state the date, time, location, and purpose of the pre-application conference.
F. Planning Official’s role. The planning official shall coordinate the involvement of agency staff responsible for planning, development review, roads, drainage, parks and other subjects, as appropriate, in the pre-application conference process. Relevant staff shall attend the pre-application conference or shall take other steps to fulfill the purposes of the pre-application conference.
G. Scheduling. The pre-application conference shall be conducted at least five calendar days after the notice is mailed but not more than 28 calendar days after the planning official accepts the application for pre-application conference. The planning official shall reschedule the conference and give new notice if the applicant or applicant’s representative cannot or does not attend the conference when scheduled.
H. Pre-application conference summary. The planning official shall provide to the applicant, other attending parties, and those who request a copy of the pre-application summary report in writing. The written summary generally shall do the following to the extent possible given the information provided by the applicant:
1. Summarize the proposed application(s);
2. Identify the relevant approval criteria and development standards in the Vancouver Municipal Code or other applicable law and exceptions, adjustments or other variations from applicable criteria or standards that may be necessary;
3. Evaluate submitted information the applicant offered to comply with the relevant criteria and standards, and identify specific additional information that is needed to respond to the relevant criteria and standards or is recommended to respond to other issues;
4. Identify applicable application fees in effect at the time, with a disclaimer that fees may change;
5. Identify information relevant to the application that may be in the possession of the city or other agencies of which the city is aware, such as:
a. Comprehensive plan map designation and zoning on and in the vicinity of the property subject to the application;
b. Physical development limitations, such as steep or unable slopes, wetlands, well-head protection areas or water bodies, that may exist on and in the vicinity of the property subject to the application;
c. Those public facilities that will serve the property subject to the application, including fire services, roads, storm drainage, and, if residential, parks and schools, and relevant service considerations, such as minimum access and fire-flow requirements or other minimum service levels and impact fees; and
d. Confirm the application submittal requirements and what submittal information is waived.
e. Where applicable, indicate whether the pre-application submittal was complete so as to trigger contingent vesting under Section 20.210.110 VMC.
I. Request for second conference. An applicant may submit a written request for a second pre-application conference within one calendar year after an initial pre-application conference. There is no additional fee for a second conference if the proposed development is substantially similar to the one reviewed in the first pre-application conference or if it reflects changes based on information received at the first pre-application conference. A request for a second pre-application conference shall be subject to the same procedure as the request for the initial pre-application conference.
J. Expiration. The pre-application comments from the city shall expire one year from the date the pre-application conference is held. A counter-complete application that the planning official finds is substantially similar to the subject of a pre-application conference must be submitted within one calendar year after the last pre-application conference or after approval of waiver of pre-application conference. Once the pre-application comments have expired the applicant must file a new request for a pre-application conference or receive approval of a pre-application waiver request in order to submit a development application. (Ord. M-4325 § 3, 2020; Ord. M-4179 § 67, 2016; Ord. M-3692 § 14, 2005; Ord. M-3643, 2004)