Zoneomics Logo
search icon

Port Orchard City Zoning Code

Subtitle II

PERMITTING AND DEVELOPMENT APPROVAL

§ 20.20.010 Purpose.

The purpose and intent of this subtitle is to establish standard procedures for all land use and development applications to provide for an integrated and consolidated land use permit and environmental review process that insures compliance with the adopted plans, policies, and ordinances of the city of Port Orchard. This subtitle is further intended to provide for the examination of development proposals with respect to overall site design and to provide a means for guiding development in a logical, safe, and attractive manner while also ensuring the issuance of a timely decision on development applications.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.20.020 Definitions.

Unless the context clearly requires otherwise, the definitions in this section apply throughout this chapter.
(1) 
"Closed record appeals"
are administrative appeals which are heard by the hearing examiner.
(2) 
"Open record hearing"
means a hearing, conducted by a single hearing body or officer authorized by the city to conduct such hearings, that creates the city's record through testimony and submission of evidence and information, under procedures prescribed by the hearing body or officer. An open record hearing may be held prior to a city's decision on a project permit, to be known as an "open record predecision hearing."
(3) 
"Project permit" or "project permit application"
means any land use or environmental permit or license required from the city, including, but not limited to, subdivisions, binding site plans, conditional use permits, variances, shoreline substantial development permits, site plan review, site development permits, design reviews, permits or approvals required by critical areas regulations, and site-specific rezones, which do not require a comprehensive plan amendment.
(Ord. 019-17 § 18 (Exh. 1); Ord. 019-24 § 1)

§ 20.20.030 Applicability.

(1) 
All applications for development shall be subject to the provisions of this subtitle, except where specifically exempted, which shall include, without limitation:
(a) 
Any change of occupancy of a building from one International Building Code group or division of a group to another or a change of use of land;
(b) 
Any new nonresidential and nonagricultural use of land;
(c) 
The location or construction of any nonresidential or nonagricultural building, or any multifamily project in which more than four dwelling units would be contained; and
(d) 
Any addition to such structure or remodel or substantial revision of the site plan associated with such use.
(2) 
The construction and development of projects reviewed under this subtitle shall be in strict compliance with the approved site plan and conditions attached thereto.
(3) 
All land uses, activities, construction, clearing, grading, filling, development, intensification, and structural modifications or alterations shall comply with the POMC.
(4) 
All permits and approvals granted for the use, activity, construction, clearing, grading, filling, development, intensification, or structural modifications or alterations shall comply with the POMC. No permit or approval shall be issued for any parcel of land developed in violations of the POMC.
(Ord. 019-17 § 18 (Exh. 1); Ord. 010-18 § 5)

§ 20.20.040 Administration and interpretation.

(1) 
The director shall be responsible for the interpretation and administration of the provisions of this subtitle. The director's interpretation and administration shall be in keeping with the spirit and intent of this subtitle, Chapter 36.70B RCW, and the comprehensive plan.
(2) 
Within this subtitle, when the director is identified as responsible for a procedural action, this authorization includes the director's authorized city representative; further, the action made by the director or authorized city representative may occur upon consultation with other city staff.
(3) 
Should a conflict arise between the provisions of this subtitle or between this subtitle and the laws, regulations, codes, or rules promulgated by other authority having jurisdiction within the city, the most restrictive requirement shall be applied, except when constrained by federal or state law, or where specifically provided otherwise.
(4) 
The procedures set forth in this subtitle shall be deemed additional to any other procedures set forth in city ordinances applicable to land use decisions, and in the event of any conflict, the procedures in this subtitle shall be controlling.
(5) 
Relative to land use permitting and development, the director shall interpret and apply the applicable provisions of this title unless otherwise indicated in this title.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.20.050 Delegation of authority.

Upon finding that any proposed land use and associated construction is exempt from environmental review pursuant to this chapter and WAC 197-11-800, the director may waive appropriate land use application fees and may delegate review and approval of a proposed land use application and associated improvements to a designee as deemed appropriate by the director.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.20.060 Effect of permit.

The issuance or granting of a permit or approval of plans and specifications shall not be deemed or construed to be a permit for, or an approval of, any violation of any of the provisions of this code. No permit presuming to give authority to violate or cancel the provisions of this code shall be valid except insofar as the work or use which it authorized is lawful.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.20.070 Exempt actions.

(1) 
As authorized by RCW 36.70B.140(1), the following land use actions are not subject to the provisions of RCW 36.70B.070, 36.70B.080, 36.70B.090, 36.70B.110, 36.70B.120, and 36.70B.130 because the city council has determined that these projects present special circumstances that warrant a review process different from the processes specified by this subtitle:
(a) 
Street vacations and other actions relating to use of public areas or facilities (POMC Title 12);
(2) 
As authorized by RCW 36.70B.140(2), the following Type I land use actions shall not be subject to the provisions of RCW 36.70B.060, 36.70B.110, 36.70B.120, and 36.70B.130:
(a) 
Boundary line adjustments (Chapter 20.84 POMC).
(b) 
Construction permits that are categorically exempt from environmental review under Chapter 20.160 POMC, State Environmental Policy Act (SEPA), or for which environmental review has been completed in conjunction with other project permits.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.20.080 Severability.

If any provision of this title or its application to any person or circumstance is held invalid, the remainder of the title, or the application of the provision to other persons or circumstances, is not affected, and to this end the provisions of this code are declared to be severable.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.22.010 Classification.

The review and approval of land use and development permit applications shall be classified as either Type I, II, III, IV, or V based on who makes the decision, the amount of discretion exercised by the decision maker, the level of impact associated with the decision, the amount and type of public input sought, and the type of appeal opportunity. The types of decisions are set forth in this chapter. The application procedures identified in this chapter shall be pursuant to Chapter 20.24 POMC.
(Ord. 019-17 § 18 (Exh. 1); Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 008-25 § 4 (Exh. C))

§ 20.22.020 Determination of types – Table.

(1) 
Determination of Proper Decision Type. The director shall determine the proper review procedure for all land use and development permit applications and actions. If there is a question as to the appropriate type of process, the director shall resolve it in favor of the higher process type number.
(2) 
Optional Consolidated Permit Processing. An application that involves two or more procedures may be processed collectively under the highest numbered procedure required for any part of the application or processed individually under each of the procedures identified by the code. The applicant may determine whether the application shall be processed collectively or individually. If the application is processed under the individual procedures option, the highest numbered type procedure must be processed prior to the subsequent lower numbered procedure. If the individual procedure option is chosen, the applicant will be eligible for any fee reduction contained in the current fee schedule.
Table 20.22.020 – Permit Review Type Classifications
Type I
Director Decision Judicial Appeal
Type II
Director Decision HE Appeal
Type III
HE Decision Judicial Appeal
Type IV
City Council Decision Judicial Appeal
Type V
City Council Decision GMHB Appeal
Building Permit1 (Subtitle X of this title)
Short Plat, Unit Lot Subdivisions, Preliminary, Alteration of Preliminary, Alteration of Final, Vacation of Final (Chapters 20.86 and 20.96 POMC)
Preliminary Plat, Preliminary Plat Major Modifications, Alteration of Final, Vacation of Final (Chapters 20.88 and 20.96 POMC)
Final Plat (Chapter 20.90 POMC)
Development Agreement (Chapter 20.26 POMC)
Binding Site Plan, Final (Chapter 20.94 POMC)
Temporary Use Permit (Chapter 20.58 POMC)
Variance (Chapter 20.28 POMC)
Site-Specific Rezone without Comprehensive Plan Amendment (Chapter 20.42 POMC)
Comprehensive Plan Amendment – Land Use Map Amendment, Text Amendment (Chapter 20.04 POMC)
Preliminary Plat – Minor Modifications (Chapter 20.88 POMC)
Binding Site Plan – Preliminary, Alteration of Preliminary, Alteration of Final, Vacation of Final (Chapter 20.94 POMC)
Conditional Use Permit (Chapter 20.50 POMC)
Legislative Zoning Map Amendment (Chapter 20.06 POMC)
Minor Land Disturbing Activity Permit (Chapter 20.140 POMC and POMC § 20.150.100)
Stormwater Drainage Permit (Chapter 20.150 POMC)
Shoreline Substantial Development Permit, Conditional Use Permit, and Nonadministrative Variance (Chapter 20.164 POMC)
POMC Title 20 Code Amendment (Chapter 20.06 POMC)
Boundary Line Adjustment (Chapter 20.84 POMC)
Sign Permit (if SEPA required) (Chapter 20.132 POMC)
Planned Residential Developments
Annexations2
Code Interpretation (Chapter 20.10 POMC)
Shoreline Substantial Development Permit, Administrative (Chapter 20.164 POMC)
Final Plat – Alteration or Vacation (Chapter 20.96 POMC)
Legal Nonconforming Permit (Chapter 20.54 POMC)
Sign Variance (Chapter 20.132 POMC)
 View Protection Overlay District (VPOD) Variance (POMC § 20.38.860)
Short Plat, Final (Chapter 20.86 POMC)
Major Land Disturbing Activity Permit (Chapter 20.140 POMC and POMC § 20.150.100)
Flood Damage Prevention Variance (Chapter 20.170 POMC)
Sign Permit (if SEPA not required) (Chapter 20.132 POMC)
Variance – Administrative (Chapter 20.28 POMC)
Flood Damage Prevention Appeal (Chapter 20.170 POMC)
Master Sign Plan
Shoreline Permit Exemption (Chapter 20.164 POMC)
Temporary Use Permit, Extension (Chapter 20.58 POMC)
Notes:
Untyped review and decision actions: preapplication meeting (Chapter 20.24 POMC), design review board review and recommendation (POMC § 20.127.030), tax exemption for multifamily development (Chapter 3.48 POMC), capacity reservation certificate (Chapter 20.180 POMC), public works design variation, right-of-way permit (Chapter 12.04 POMC), street use permit (Chapter 12.24 POMC), water/sewer connection permit (Chapter 13.04 POMC).
1 If a building permit application does not require SEPA review, no public notice is required. If a building permit application requires SEPA review, public notice shall be provided consistent with the requirements for Type II applications pursuant to Chapter 20.25 POMC.
2 A development agreement that is consolidated with a Type I, II, III, or IV project permit application may be appealed pursuant to Chapter 36.70C RCW.
(Ord. 019-17 § 18 (Exh. 1); Ord. 010-18 § 4; Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 029-19 § 1; Ord. 030-20 § 2; Ord. 033-20 § 3; Ord. 059-21 § 2; Ord. 008-25 § 4 (Exh. C))

§ 20.22.030 Type I (administrative decision, judicial appeal).

(1) 
General. Type I applications are defined pursuant to POMC § 20.22.020. All Type I actions must meet all applicable requirements of the POMC in addition to the requirements specified in this subtitle.
(2) 
Preapplication Conference. Type I applications do not require a preapplication conference.
(3) 
Notice of Application. Type I applications do not require a notice of application, unless environmental review is required under SEPA pursuant to Chapter 20.160 POMC.
(4) 
Review of Application.
(a) 
The director shall commence permit review pursuant to Chapter 20.24 POMC. The director shall determine which city departments are responsible for reviewing or commenting on an application and shall ensure the affected departments receive a copy of the application, or appropriate parts of the application.
(b) 
Following a determination of technical completeness and determination of consistency pursuant to POMC § 20.24.090, the director shall approve, deny, or approve with conditions all Type I applications. Conditions may be imposed directly on the plans (red-lining) or through other documentation reflected on the plans to ensure the requirements of city codes and regulations are met without going through another correction cycle before permit issuance.
(5) 
Decision.
(a) 
Unless a permit type has been excluded from the permit decision timelines established in POMC § 20.24.110, pursuant to RCW 36.70B.140, all Type I applications are subject to the permit decision timelines. If no correction cycles are required, review should be complete within approximately 30 calendar days from the date of technical completeness. Correction cycles will extend review time in proportion to the time the city must wait for an applicant to submit additional or corrected information.
(b) 
The decision of the director may be reflected on the plans or permit itself or may be documented in a written report or letter of approval.
(6) 
Notice of Decision. Public notice of a Type I decision is not required. The applicant shall be notified in writing or by email that the permit is ready to issue or the application is approved.
(7) 
Administrative Appeal. There is no administrative appeal of a Type I decision except for decisions that are appealable to the building board of appeals in accordance with this title and the International Codes as adopted by the city.
(8) 
Judicial Appeal. A Type I decision not appealable to the building board of appeals may be appealed directly to superior court.
(Ord. 019-17 § 18 (Exh. 1); Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 019-24 § 2; Ord. 008-25 § 4 (Exh. C))

§ 20.22.040 Type II (administrative decision, hearing examiner appeal).

(1) 
General. Type II applications are defined pursuant to POMC § 20.22.020. All Type II applications must meet all applicable requirements of the POMC in addition to the requirements specified below.
(2) 
Preapplication Conference. Type II actions are required to participate in a preapplication conference pursuant to POMC § 20.24.010. A limited preapplication conference may be allowed for projects that do not require substantial review by other departments such as variances and design review without SEPA or street improvement requirements.
(3) 
Notice of Application. Type II applications require a notice of application pursuant to Chapter 20.25 POMC.
(4) 
Review of Application.
(a) 
The director shall commence permit review pursuant to Chapter 20.24 POMC. The director shall determine which city departments are responsible for reviewing or commenting on an application and shall ensure the affected departments receive a copy of the application, or appropriate parts of the application.
(b) 
Following a determination of technical completeness and determination of consistency pursuant to POMC § 20.24.090, the director shall approve, approve with conditions, or deny all Type II applications. Conditions may be imposed directly on the plans (red-lining), through other documentation reflected on the plans, or in a written staff report or other decision document, to ensure the requirements of city codes and regulations are met without going through another correction cycle before permit issuance.
(5) 
Public Hearing. No public hearing is required for Type II decisions.
(6) 
Decision. Type II decisions are subject to the maximum 100-day timeline requirement pursuant to POMC § 20.24.110. A decision for a Type II action shall be made in writing by the director and shall include the following information:
(a) 
A description of the proposal and a listing of permits or approvals included in the application;
(b) 
A statement of the applicable criteria and standards in this code and other applicable law;
(c) 
A statement of background information and facts relied upon by the department which show the application does or does not comply with the approval criteria;
(d) 
A summary of public comment received and how the department or applicant responded to the public comments or concerns; and
(e) 
The decision to deny or approve the application and, if approved, any conditions of approval necessary to ensure the proposed development will comply with applicable law.
(7) 
Notice of Decision. Public notice of a Type II decision shall be provided pursuant to POMC § 20.24.100. Notice of a short plat or binding site plan shall be provided in the same manner as notice of application as set forth in Chapter 20.25 POMC.
(8) 
Administrative Appeal. A Type II decision, except for shoreline substantial development permits and shoreline variances, may be appealed to the hearing examiner within 14 calendar days of the notice of decision. A decision on a shoreline substantial development permit or shoreline variance may be appealed to the State Shorelines Hearings Board pursuant to Chapter 20.164 POMC. Shoreline appeal procedures and information are available from the department or from the State Department of Ecology. Administrative appeals of director decisions to the hearing examiner are to be made on forms provided by the city and shall include the following information:
(a) 
A brief statement regarding how the appellant is significantly affected by or interested in the matter appealed;
(b) 
A specific clear and comprehensible statement of the appellant's issues on appeal, noting appellant's specific exceptions and objections to the decision or action being appealed;
(c) 
The specific relief requested, such as reversal or modification; and
(d) 
Signature, address, and phone and fax number of the appellant, and name and address of appellant's designated representative, if any.
(9) 
Judicial Appeal. The decision of the hearing examiner on a Type II appeal may be appealed to superior court.
(Ord. 019-17 § 18 (Exh. 1); Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 019-24 § 3; Ord. 008-25 § 4 (Exh. C))

§ 20.22.050 Type III (hearing examiner decision, judicial appeal).

(1) 
General. Type III applications are defined pursuant to POMC § 20.22.020. All Type III applications must meet all applicable requirements of the POMC in addition to the requirements specified below.
(2) 
Preapplication Conference. Type III applications are required to have a preapplication conference pursuant to POMC § 20.24.010.
(3) 
Notice of Application. Type III applications require a notice of application pursuant to Chapter 20.25 POMC.
(4) 
Review of Application.
(a) 
The director shall commence permit review pursuant to Chapter 20.24 POMC. The director shall determine which city departments are responsible for reviewing or commenting on an application and shall ensure the affected departments receive a copy of the application or appropriate parts of the application.
(b) 
Following a determination of technical completeness and determination of consistency pursuant to POMC § 20.24.090, the director shall prepare a written recommendation to the hearing examiner. The director's recommendation shall provide a description of the proposal, a listing of the permits or approvals included in the application, a statement of the criteria and standards applicable to the proposal, and a review of the background information and facts relied upon by the director for the recommendation. The recommendation shall enumerate any conditions needed to ensure the application meets each of the applicable decision criteria.
(c) 
If a director recommendation is not available to the hearing examiner as provided in this section, the hearing examiner may reschedule or continue the hearing upon their own motion or upon the motion of a party, or the hearing examiner may decide the matter without the recommendation.
(d) 
The director's recommendation, and any additional staff reports, shall be consistent with RCW 36.70B.060(5).
(5) 
Public Hearing. A Type III action requires an open record hearing before the hearing examiner.
(a) 
At least 14 calendar days before the date of the hearing, public notice of the hearing shall be provided consistent with the requirements of POMC § 20.25.050.
(b) 
The director's recommendation shall be made available on the date the hearing notice is issued.
(c) 
SEPA appeals for Type III decisions may be consolidated with a public hearing as provided for in POMC § 20.160.240(5).
(d) 
The burden of proof shall be on the applicant to demonstrate that the proposal conforms to applicable codes and standards; except that for any SEPA DNS appeal, the burden of proof is on the appellant.
(e) 
The public hearing shall be conducted pursuant to the hearing examiner's adopted rules and procedures and shall be recorded on audio or audiovisual tape. The hearing examiner may remand an application to staff at their discretion to allow staff to administratively address an issue or irregularity with the application or the processing thereof.
(6) 
Decision.
(a) 
A written decision for a Type III action shall be issued by the hearing examiner within 14 calendar days after the date the record closes, and not later than 170 calendar days after the issuance of the determination of technical completeness pursuant to POMC § 20.24.110, whichever is earlier, unless the applicant has consented in writing to an extension of this time period. The hearing examiner's decision shall include the following information:
(i) 
A description of the proposal and a listing of permits or approvals included in the application;
(ii) 
A statement of the applicable criteria and standards in the municipal code and other applicable law;
(iii) 
A statement of background information and facts relied upon by the hearing examiner which show the application does or does not comply with the approval criteria and standards;
(iv) 
A summary of public testimony and public comment received and how the department or the applicant responded to the public testimony and public comments; and
(v) 
The decision to deny or approve the application and, if approved, any conditions of approval necessary to ensure the proposed development will comply with applicable law.
(b) 
Notice of Decision. Public notice of a Type III decision shall be provided pursuant to POMC § 20.24.100.
(7) 
Reconsideration.
(a) 
The hearing examiner may reconsider a Type III decision if a written request for such administrative appeal is filed by a party of record within 14 calendar days of the date of the notice of decision. Grounds for requesting reconsideration shall be limited to the following:
(i) 
The decision or conditions of approval are not supported by facts in the record;
(ii) 
The decision contains an error of law;
(iii) 
There is newly discovered evidence potentially material to the decision which could not reasonably have been produced prior to the open record predecision hearing; or
(iv) 
The applicant proposes changes to the proposal in response to deficiencies identified in the decision.
(b) 
Any request for reconsideration shall be mailed to all parties of record on the same day as the request is mailed or delivered to the hearing examiner.
(c) 
A request for reconsideration shall stop the running of the judicial appeal period on a Type III decision for seven calendar days. During this time period, the hearing examiner shall decide whether reconsideration is appropriate. If the hearing examiner decides to reconsider the decision, the judicial appeal period will be placed on hold until the reconsideration process is complete and a new decision is issued. If the hearing examiner decides to reconsider a decision, all parties of record shall be notified.
(d) 
The hearing examiner shall, by order, set a schedule for other parties of record to respond in writing to the reconsideration request and shall issue a decision no later than 14 calendar days following the due date for submittal of written responses. A new judicial appeal period shall commence from the date of the hearing examiner's decision on reconsideration.
(8) 
Judicial Appeal. Type III decisions, except shoreline conditional use permits and any associated shoreline permits, may be appealed to superior court. Shoreline decisions are appealable to the State Shorelines Hearings Board.
(Ord. 019-17 § 18 (Exh. 1); Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 017-23 § 1 (Exh. A); Ord. 019-24 § 4; Ord. 008-25 § 4 (Exh. C))

§ 20.22.060 Type IV (city council decision, judicial appeal).

(1) 
General. Type IV applications are defined pursuant to POMC § 20.22.020. All Type IV applications must meet all applicable requirements of the POMC in addition to the requirements specified below.
(2) 
Preapplication Conference. Type IV applications are required to have a preapplication conference pursuant to POMC § 20.24.010.
(3) 
Notice of Application. Type IV applications require a notice of application pursuant to Chapter 20.25 POMC.
(4) 
Review of Application.
(a) 
The director shall commence review of the permit application pursuant to Chapter 20.24 POMC. The director shall determine which city departments are responsible for reviewing or commenting on an application and shall ensure the affected departments receive a copy of the application or appropriate parts of the application.
(b) 
Following a determination of technical completeness and determination of consistency pursuant to POMC § 20.24.090, the director shall prepare a written recommendation to the hearing body. The director's recommendation shall provide a description of the proposal, a listing of the permits or approvals included in the application, a statement of the criteria and standards applicable to the proposal, and a review of the background information and facts relied upon by the director for the recommendation. The recommendation shall enumerate any conditions needed to ensure the application meets each of the applicable decision criteria.
(c) 
If a SEPA determination of nonsignificance (DNS) is issued for the proposal, the DNS will be issued in conjunction with the director's recommendation to the hearing body.
(d) 
Within 14 calendar days of holding a public hearing, the hearing body shall issue a recommendation on the application to the city council.
(5) 
Public Hearing. A Type IV action requires an open record hearing for a recommendation before either the hearing examiner or planning commission, pursuant to the requirements of the individual permit application requirements.
(a) 
At least 14 calendar days before the date of the hearing, public notice of the hearing shall be provided consistent with the requirements of POMC § 20.25.050.
(b) 
The director's recommendation shall be made available on the date the hearing notice is issued.
(c) 
SEPA appeals for Type IV decisions may be consolidated with a public hearing as provided for in POMC § 20.160.240(5). The burden of proof shall be on the applicant to demonstrate that the proposal conforms to applicable codes and standards; except that for any SEPA DNS appeal, the burden of proof is on the appellant.
(d) 
The public hearing shall be conducted pursuant to the hearing body's adopted rules and procedures and shall be recorded on audio or audiovisual tape.
(6) 
Decision. Following receipt of a recommendation from the hearing body, the city council shall approve, approve with conditions, or deny a Type IV application by ordinance. Pursuant to POMC § 20.24.110, the city council's decision must be issued within 170 calendar days of the issuance of the determination of technical completeness, unless the applicant has consented in writing to an extension of this time period.
(7) 
Administrative Appeal. There is no administrative appeal of Type IV decisions.
(8) 
Judicial Appeal. A Type IV decision may be appealed to superior court.
(Ord. 019-17 § 18 (Exh. 1); Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 019-24 § 5; Ord. 008-25 § 4 (Exh. C))

§ 20.22.070 Type V (legislative actions).

(1) 
General.
(a) 
Type V actions are defined pursuant to POMC § 20.22.020. All Type V proposals are legislative actions, but not all legislative actions are Type V decisions. Legislative actions involve the creation, amendment, or implementation of policy or law by ordinance. In contrast to other types of actions, legislative actions apply to large geographic areas and are of interest to many property owners and citizens.
(b) 
Type V actions are not subject to the application procedures in Chapter 20.24 POMC, unless otherwise specified.
(2) 
Public Hearing.
(a) 
The planning commission shall hold a public hearing and make recommendations to the city council on Type V actions. A notice for the public hearing shall be provided pursuant to POMC § 20.25.050.
(b) 
The city council may hold a public hearing on Type V actions prior to passage of an ordinance or entry of a decision.
(c) 
The planning commission and/or city council may require more than one public hearing for Type V actions.
(d) 
Notice of a public hearing shall be provided to the public at least 14 calendar days prior to the hearing by publishing notice as provided for in POMC § 20.25.050. In addition to publishing notice and posting notice at City Hall, at least 14 calendar days prior to the hearing the city shall mail notice of the public hearing to the applicant, relevant government agencies, and other interested parties who have requested in writing to be notified of the hearing. If the legislative action is for a comprehensive plan amendment, notice of the public hearing shall also be posted and mailed pursuant to Chapter 20.04 POMC. The city may also provide optional methods of public notice as provided in Chapter 20.25 POMC.
(3) 
Review. Review of Type V actions shall be pursuant to the applicable POMC chapter for each action.
(4) 
Decision. The city council shall issue a final decision on all Type V actions by passage of an ordinance.
(5) 
Appeals. A Type V decision may be appealed to the Growth Management Hearings Board pursuant to the regulations set forth in RCW 36.70A.290.
(6) 
Legislative Enactments Not Restricted. Nothing in this section, chapter, or Chapter 20.24 POMC shall limit the authority of the city council to make changes to the city's comprehensive plan, as part of a regular revision process, or to make changes to the city's municipal code.
(Ord. 019-17 § 18 (Exh. 1); Ord. 029-18 § 2; Ord. 011-19 § 5 (Exh. 2); Ord. 008-25 § 4 (Exh. C))

§ 20.24.010 Preapplication conference.

(1) 
The purpose of a preapplication conference is to discuss the nature of the proposed development; application and approval requirements, fees, review process, and schedule; and applicable policies and regulations. As appropriate, the director shall invite representatives of affected agencies, such as other city departments and special purpose districts, to attend any preapplication meeting. The preapplication conference may be recorded.
(2) 
Requests for scheduling a preapplication conference shall be submitted on forms provided by the city along with payment of the associated fee pursuant to the city's current fee schedule.
(3) 
Potential applicants or their designees are encouraged to request and attend a preapplication conference with city staff for all Type II, Type III, and Type IV land use actions. When a preapplication conference is requested, the applicant shall meet with the director and any other staff members, as appropriate, to discuss the proposed development.
(4) 
Applicants may also request an optional preapplication conference if not otherwise required.
(5) 
Whether the preapplication conference is mandatory or requested by the applicant, the following information shall be provided to the city by the applicant at least 14 calendar days prior to the date of the preapplication conference:
(a) 
Identification of the subject property;
(b) 
Description of the type of planned development, including proposed uses, estimated density; and
(c) 
Identification of any requests for deviation from code requirements.
(6) 
Failure of the director or any city staff member to provide any of the information required by this section shall not constitute a waiver of any of the standards, criteria, or requirements for the application. Any discussion at the preapplication conference is for the purpose of acquainting the applicant with the known requirements for an undefined proposal. As a result, the discussions shall not bind the city in any manner or prevent the city's future enforcement of all applicable codes, plans, and regulations.
(Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3; Ord. 019-24 § 6)

§ 20.24.020 Master permit required.

(1) 
A master permit application is required for all land use and development projects and shall be submitted in conjunction with the associated permit application(s) required for the project. The master permit application may not be submitted alone.
(2) 
The director shall establish and may revise at their discretion submittal requirements for the master permit application. At a minimum, the master permit application shall require the following:
(a) 
Name and contact information of applicant;
(b) 
Signature by the property owner or person having authorization to sign on behalf of the property owner;
(c) 
List of all project permit applications submitted with the master permit;
(d) 
List of any permits or decisions applicable to the project proposal that have been obtained prior to filing the application or that are pending before the city or any other governmental entity;
(e) 
Indication of whether review under the State Environmental Policy Act (SEPA) applies to the project, or if the project is categorically exempt, pursuant to Chapter 20.160 POMC; and
(f) 
Indication of whether stormwater drainage review applies to the project pursuant to Chapter 20.150 POMC.
(3) 
For purposes of this subtitle, all references to an "application" refers to both the master permit and associated permit application(s).
(Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3; Ord. 017-23 § 1 (Exh. A))

§ 20.24.030 Submission requirements.

(1) 
The director shall establish and may revise at their discretion submittal requirements for each type of land use and development permit application required under this title. The submittal requirements shall be in the form of a counter-complete checklist. The requirements shall be made available to the public in a form that clearly explains what material must be submitted for an application to be considered complete, including type, size, detail, and number of copies for each item.
(2) 
At a minimum, the following shall be completed and submitted by the applicant for all land use and development applications:
(a) 
Master permit application form, pursuant to POMC § 20.24.020;
(b) 
Appropriate application form, provided by the department, for each permit submitted with the master permit, including all required items stated therein;
(c) 
Payment of any and all applicable permit fees pursuant to this title and the city's current fee schedule at the time of application;
(d) 
Environmental checklist (if not exempt from SEPA review pursuant to Chapter 20.160 POMC) and any requirements for SEPA review, when applicable; and
(e) 
Applicable signatures, stamps, or certifications, and attestation by written oath of applicant to the accuracy of all information submitted for an application.
(f) 
Requirements for related permits shall also be provided when applicable.
(3) 
The director may require additional material when the director determines, after a determination of technical completeness pursuant to POMC § 20.24.050, that such information is needed to adequately assess the proposed project.
(4) 
When not required by law, submittal requirements may be waived by the director, in writing, only if the applicant can demonstrate that normally required information is not relevant to the proposed action and is not required to show that an application complies with applicable city codes and regulations.
(5) 
The city's acceptance of documents from an applicant using a counter-complete checklist is used only for purposes of documenting what was submitted by the applicant; it is not a technical review for completeness or compliance with state or local laws and regulations. See POMC § 20.24.040 for the counter-complete review process.
(Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3; Ord. 017-23 § 1 (Exh. A))

§ 20.24.040 Counter-completeness.

(1) 
Applications may be submitted to the city in any of the following manners: electronically, mailed to the city, or brought in person to the city. All three of these systems are acceptable methods for counter-complete review. However, in no case will an application be deemed counter-complete until such time as the submission requirements listed in POMC § 20.24.030, including the minimum required application fees, are received by the city.
(2) 
An application is counter-complete if the director finds that the application purports and appears to include the information required by the master permit application and associated permit application(s) and all required fees have been paid; provided, no effort shall be made to evaluate the substantive adequacy of the information in the application(s) in the counter-complete review process. No effort shall be made to determine ownership of land as part of the counter-complete review process.
(3) 
Timing of Counter-Complete Determination.
(a) 
For applications submitted electronically or mailed to the city, within two business days of receipt of the application, the director shall either: (i) determine that the application is counter-complete if the requirements of subsection (2) of this section are met; or (ii) determine that the application is not counter-complete if the requirements of subsection (2) of this section are not met, in which case the director shall reject and return the application and identify in writing what is needed to make the application counter-complete. If the city does not provide a counter-complete decision for an electronically submitted or a mailed application within two business days of receipt, the application shall be deemed counter-complete as of the third business day from receipt; provided, that all required application components and fees are included with the application. If the city determines that an electronically submitted or a mailed application is not counter-complete and informs the applicant in writing what is needed to make the application counter-complete, the application shall be determined or deemed to be counter-complete within five business days of the notification only if the missing application components and all required application fees are received by the city no later than four business days following the notification to the applicant.
(b) 
For applications brought in person to the city, the director shall make a counter-complete determination while the applicant is present. If the director decides that the application is counter-complete in accordance with subsection (2) of this section, then the applicant shall pay the appropriate fees at the time of submittal. If the director determines that the application is not counter-complete, then the director shall reject and return the application and identify in writing what is needed to make the application counter-complete.
(4) 
Notwithstanding the foregoing, no application shall be automatically deemed counter-complete due to the passage of time unless the submission requirements listed in POMC § 20.24.030, including the application fees, are timely received in accordance with this section.
(Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3; Ord. 011-23 § 2; Ord. 019-24 § 7)

§ 20.24.050 Application review.

Within five business days of determining an application as counter-complete, the director shall transmit a copy of the application, or appropriate parts of the application, to each affected government agency and city department for review and comment to determine technical completeness of the application. The affected agencies and city departments shall have 15 calendar days from the date of the transmittal to comment on whether the application is technically complete and to provide a list of missing information if it is not complete. The agency or city department is presumed to have no comment if comments are not received within this 15-calendar-day period from application transmittal. The director shall grant an extension of time only if the application involves unusual circumstances, provided comments are received at least three business days prior to the 28-day deadline for determining technical completeness.
(Ord. 056-19 § 3)

§ 20.24.060 Technical completeness.

(1) 
Within 28 calendar days of determining an application as counter-complete, the director shall provide a written determination as to whether the application is technically complete. A project permit application is technically complete for purposes of this section when it meets the submission requirements of this chapter as well as the submission requirements contained in other applicable sections of the code. This determination of technical completeness shall be made when the application is sufficient for continued processing even though additional information may be required or project modifications may be subsequently undertaken.
(a) 
The written determination shall state either (i) that the application is technically complete, or (ii) that the application is incomplete and that the procedural submission requirements have not been met, in which case the determination shall outline what information or steps are necessary to make the application procedurally complete.
(2) 
A determination of technical completeness shall not preclude the city from requesting additional information or studies either at the time of the notice of completeness or at some later time. Such new information may be required to establish whether the proposal meets applicable city codes and regulations, whether additional environmental study is required, or, more generally, when there are substantial changes in the proposed action.
(3) 
The city may determine that a counter-complete application is not technically complete because the information submitted is not sufficient for further processing, is incomplete, or is factually incorrect. If the applicant receives a written determination from the city that an application is not technically complete, the applicant shall have up to 90 calendar days to submit the necessary information to the city. Within 14 calendar days after an applicant has submitted the requested additional information, the city shall determine whether the application is technically complete.
(4) 
If an applicant either refuses in writing to submit additional information or does not submit the required information within 90 calendar days, the application shall be terminated.
(5) 
If the director does not provide a written determination that an application is technically incomplete within the 28-day period, the application shall be deemed technically complete for processing as of the twenty-ninth calendar day following the determination of counter-completeness. If the director does not provide a written determination that an application is technically incomplete, the city may still seek additional information or studies as provided in this section.
(Formerly 20.24.050; Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3; Ord. 019-24 §§ 8, 9)

§ 20.24.070 Project review – Public notice.

(1) 
Within 14 calendar days of determining an application as technically complete, and before making a decision on the application, the director shall issue a notice of application as set forth in POMC § 20.25.010. The director shall grant an extension of time only if the application involves unusual circumstances.
(2) 
Except when a land use action is categorically exempt from SEPA, environmental review shall be conducted concurrently with review of other proposed land use actions requested by an applicant. When a proposed development requires more than one land use action, the applicant may request concurrent review of all proposed land use actions.
(Formerly 20.24.080; Ord. 019-17 § 18 (Exh. 1); Ord. 002-19 § 2; Ord. 056-19 § 3; Ord. 019-24 § 10)

§ 20.24.080 Required corrections.

(1) 
Following a determination of technical completeness and the commencement of project review, the director may make a determination in writing that some information is incorrect or that additional information is required. The applicant shall have up to 90 calendar days to submit corrected/additional information.
(2) 
Within 14 calendar days of receiving corrected/additional information, the director shall determine whether the information, plans, or other review materials are now correct and sufficient for further review. If the city determines that the information submitted by the applicant is insufficient, or if additional information is required, the city shall notify the applicant of the deficiencies and the procedures of this section shall apply as if the city made a new request for information.
(3) 
If an applicant either refuses in writing to submit additional information or does not submit the required information within 90 calendar days, the application shall be canceled.
(Formerly 20.24.060; Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3)

§ 20.24.090 Revisions.

(1) 
If, in the judgment of the director, the content of an application is so substantially revised by an applicant, either voluntarily or as corrections, that such revised proposal constitutes a substantially different proposal than that originally submitted, the director shall deem the revised proposal to be a new application.
(2) 
In reaching a decision whether a revision is substantial, the director shall consider the relative and absolute magnitude of the revision, the environmental sensitivity of the site, any changes in location of significant elements of the project and their relation to public facilities, surrounding lands and land uses, and the stage of review of the proposal. Lesser revisions that would not constitute substantial revisions during early stages of review may be substantial during later stages due to the reduced time and opportunity remaining for interested parties to review and comment upon such changes.
(3) 
Written notice of such determination of substantial revision shall be provided to the applicant and all parties of record.
(4) 
A determination that any revision is substantial shall result in the time periods mandated by the Regulatory Reform Act, Chapter 36.70B RCW, and set forth in this title to reset and start from the date at which the revised project application is determined to be technically complete.
(5) 
A revised project application shall be subject to all laws, regulations, and standards in effect on the date of receipt of such technically complete substantial revision.
(Formerly 20.24.070; Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3)

§ 20.24.100 Decision criteria.

The criteria set forth below shall apply to all Type I through IV land use and development permit applications:
(1) 
Determination of Consistency. The applications are reviewed by the city to determine consistency between the proposed project and the applicable land use and development regulations and the comprehensive plan. A proposed project's consistency with the city's land use and development regulations shall be determined by consideration of:
(a) 
The type of land use;
(b) 
The level of development, such as units per acre or other measures of density;
(c) 
Availability of infrastructure, including public facilities and services needed to serve the development; and
(d) 
The character of the development, such as development standards.
(2) 
Upon review of an application, the decision-maker shall also determine whether the building and/or site design complies with the following provisions:
(a) 
The comprehensive plan;
(b) 
The applicable provisions of this title;
(c) 
The Washington State Environmental Policy Act (SEPA), pursuant to Chapter 20.160 POMC, if not otherwise satisfied;
(d) 
The city's public works design standards.
(3) 
Additional Review Criteria. Additional review criteria appear in each chapter or section of the POMC relating to the development regulations for an individual project permit application or other approval. All of the criteria in this section and the criteria relating to the individual application(s) must be satisfied in order for the city to make a determination of consistency and issue an approval.
(4) 
Limitations on Review. During project review, the city shall not reexamine alternatives to or hear appeals on the review requirements of this section except for issues of code interpretation.
(5) 
Burden of Proof. The burden of proof for demonstrating that the application is consistent with the applicable regulations is on the applicant.
(Formerly 20.24.090; Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3)

§ 20.24.110 Notice of decision.

(1) 
Contents. The notice of decision issued by the director for Type I and II actions, and the findings of fact and conclusions of law issued by the hearing body on Type III and IV actions shall include the following, as a minimum:
(a) 
A list of all project permits included in the decision, including all permits being reviewed through the consolidated review process;
(b) 
Date and description of the decision;
(c) 
Statement of any threshold determination made under SEPA (Chapter 43.21C RCW);
(d) 
Procedures for an administrative appeal, if any;
(e) 
Statement that the affected property owners may request a change in property tax valuation notwithstanding any program of revaluation by contacting the Kitsap County assessor;
(f) 
Duration of the permit approval and a statement summarizing the permit expiration and extension procedures (if any); and
(g) 
Statement that the complete project permit file, including findings, conclusions, and conditions of approval, if any, is available for review. The notice shall list the place that the file is available and the name and telephone number of the city representative to contact about reviewing the file.
(2) 
Persons Entitled to Receive Notice of Decision. A notice of decision, or the written findings of fact and conclusions, shall be provided to the applicant, to any person who submitted written comments on the application (other than a signed petition), to any person who testified at the hearing or any person who requested in writing a copy of the decision, and to the Kitsap County assessor.
(3) 
For project permit applications, the city shall issue a notice of decision within the following timelines, unless the time period has been modified pursuant to RCW 36.70B.080 or 36.70B.140, or unless the applicant has agreed to a different deadline:
(a) 
For project permits which do not require public notice of application under RCW 36.70B.110, the city must issue a final decision within 65 days of issuance of the determination of technical completeness on the application;
(b) 
For project permits which require public notice of application under RCW 36.70B.110, the city must issue a final decision within 100 days of the determination of technical completeness on the application; and
(c) 
For project permits which require public notice of application under RCW 36.70B.110 and public hearing, the city must issue a final decision within 170 days of the determination of technical completeness on the application.
(4) 
In calculating the time periods for issuance of the notice of decision, the number of days shall be calculated by counting every calendar day and excluding the following periods:
(a) 
Any period between the day that the director has notified the applicant, in writing, that additional information is required to further process the application and the day when responsive information is resubmitted by the applicant to the city;
(b) 
If the director determines that the information submitted is insufficient, the applicant shall be informed of the particular insufficiencies and the procedures set forth in POMC § 20.24.060 for calculating the exclusion period shall apply;
(c) 
Any period during which an environmental impact statement (EIS) is being prepared pursuant to Chapter 43.21C RCW and Chapter 20.160 POMC;
(d) 
Any period after an applicant informs the city, in writing, that they would like to temporarily suspend review of the application until the time that the applicant notifies the city, in writing, that they would like to resume the application;
(e) 
Any period after an administrative appeal is filed until the administrative appeal is resolved and any additional time period provided by the administrative appeal has expired; provided, that the city may set conditions on the temporary suspension of a permit application;
(f) 
Any extension of time mutually agreed to in writing by the director and the applicant; and
(g) 
If, at any time, an applicant informs the director, in writing, that the applicant would like to temporarily suspend the review of the project for more than 60 consecutive days, or if an applicant is not responsive for more than 60 consecutive days after the city has notified the applicant, in writing, that additional information is required to further process the application, an additional 30 days may be added to the time periods for the city to issue a final decision on the application. Any written notice from the director to the applicant that additional information is required to further process the application must include a notice that nonresponsiveness for 60 consecutive days may result in 30 days being added to the time for review. For purposes of this section, "nonresponsiveness" means that an applicant is not making demonstrable progress on providing additional requested information to the local government, or that there is no ongoing communication or willingness to provide the additional information.
(5) 
The time limits established in this section do not apply to applications that:
(a) 
Are not project permit applications (such as amendments to the comprehensive plan or a development regulation);
(b) 
Require siting approval of an essential public facility;
(c) 
Are substantially revised by the applicant, in which case the time period shall start from the date that a determination of completeness for the revised application is issued by the director.
(Formerly 20.24.100; Ord. 019-17 § 18 (Exh. 1); Ord. 056-19 § 3; Ord. 033-20 § 4; Ord. 019-24 § 11)

§ 20.25.010 Notice of application.

(1) 
The purpose of the notice of application is to give nearby property owners and other interested persons the opportunity to submit written comments about the application before the decision on the application is made. The goal of this notice is to invite people to participate early in the decision-making process.
(2) 
Within 14 calendar days after the city has made a determination of technical completeness, and before making a decision on an application, the director shall issue a notice of application to:
(a) 
All owners of record of real property within a minimum of 300 feet of the subject site. However, if the owner of the real property which is the subject of the application owns another parcel or parcels of real property which lie adjacent to the real property included in the application, notice under this subsection shall be given to owners of real property located within 300 feet of any portions of the boundaries of such adjacently located parcels of real property owned by the owner of the real property included in the application;
(b) 
All city-recognized neighborhood groups or associations whose boundaries include the subject site;
(c) 
Any person who submits a written request to receive a notice; and
(d) 
Any government agency that is entitled to notice or that is affected by the application.
(3) 
Except as otherwise provided herein, the notice of application for a pending application shall:
(a) 
Provide a specific calendar day period for submitting written comments before a decision is made on the permit, and state the place, date, and time the comments are due, and the person to whom the comments should be addressed. For all applications except a shoreline permit, the public comment period for a notice of application shall be a minimum of 14 calendar days. For shoreline permits under the purview of the city's shoreline master program (SMP), the public comment period for a notice of application shall be not less than 30 calendar days. For all decisions to be made by the hearing examiner, all comments on a notice of application shall be submitted in writing before or at the public hearing;
(b) 
Identify the date of submission of the initial application, the date of the notice of technical completeness, and the date the notice of application was issued;
(c) 
Describe the street address or other easily understandable reference to the location of the site;
(d) 
Include the name and telephone number of a contact person regarding the application;
(e) 
Describe the proposal and identify all project permits requested in the application, and list all studies requested by the city;
(f) 
List the relevant approval criteria for the permit applied for, by name and number of code sections;
(g) 
Describe existing environmental documents that evaluate the proposed project, and, if not otherwise stated on the notice of application, the location where the application and any studies can be reviewed;
(h) 
State that any person may comment on the application, receive notice of and participate in any hearings and request a copy of the decision on the application, and describing any appeal rights;
(i) 
Identify the date, time, place, and type of hearing, if a hearing has been scheduled when the date of notice of application is issued;
(j) 
If made at the time the notice of application is prepared, the notice of application shall include a summary of the preliminary determination of consistency required by POMC § 20.24.090;
(k) 
Include any other information determined appropriate by the director, such as the SEPA responsible official's SEPA threshold determination, if complete at the time of issuance of the notice of application.
(4) 
The following shall also be required for preliminary plat applications:
(a) 
For a preliminary plat adjacent to or within one mile of the municipal boundaries of any city, which contemplates the use of any city utilities, mailed notice shall be given to the appropriate city authorities;
(b) 
Notice of the filing of a preliminary plat of a proposed subdivision adjoining the boundaries of the county shall be given to the appropriate county officials; and
(c) 
Notice of the filing of a preliminary plat of a proposed subdivision located adjacent to the right-of-way of a state highway or within two miles of the boundary of a state or municipal airport shall be given to the State Secretary of the Department of Transportation.
(Ord. 019-17 § 18 (Exh. 1); Ord. 019-24 § 12)

§ 20.25.020 Published notice of application.

(1) 
Public notice of an application shall be published in the city's official newspaper or in a newspaper of general circulation within 14 calendar days after the city has made a determination of technical completeness on the application or in the first available paper beyond 14 calendar days (recognizing that the paper is a weekly publication and that there are publication deadlines).
(2) 
The published notice shall contain at a minimum:
(a) 
The project location by street address or other means of ready identification;
(b) 
A description of the proposal;
(c) 
Identification of the permit applications submitted;
(d) 
The public comment period deadline;
(e) 
The location where comments may be sent and location where application materials may be reviewed.
(3) 
The department shall be responsible for preparing the published notice of application including the project description.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.25.030 Posted notice of application.

Public notice of an application shall be posted by the applicant at the applicant's cost on one or more notice boards as follows:
(1) 
The posted notice board shall:
(a) 
Include the words "Public Notice – Notice of Application" in (minimum) four-inch lettering across the top of the sign;
(b) 
Meet the following lettering standards:
(i) 
Helvetica or similar standard typeface, or, hand written block letters;
(ii) 
Include the project title in three-inch capital letters;
(iii) 
Include the proposal description in two-inch capital letters;
(iv) 
All other letters shall be one-and-one-half-inch upper and lower case;
(c) 
Measure at least 14 square feet; and
(d) 
Include all of the same information as found in the published notice prepared by the city pursuant to POMC § 20.25.020.
(2) 
The notice board shall be installed within 14 calendar days after the city issues the notice of complete application, and shall be placed:
(a) 
At the midpoint of the street fronting the site or as otherwise directed by the director for maximum visibility;
(b) 
No more than five feet inside the street property line, except where the board is structurally attached to an existing building; provided, that no notice board shall be placed more than five feet from the street without approval of the director;
(c) 
With the top of the notice board between five and nine feet above grade; and
(d) 
Where it is completely visible to pedestrians.
(3) 
Additional notice boards may be required when:
(a) 
The site does not abut a public road;
(b) 
A large site abuts more than one public road; or
(c) 
The director determines that additional notice boards are necessary to provide adequate public notice.
(4) 
Notice boards shall be maintained in good condition by the applicant during the application review period until the final decision issues.
(5) 
Removal. It is the applicant's responsibility to remove the public notice sign at the following times, as applicable:
(a) 
Fourteen days after the director's decision has been issued (21 days after receipt of the shoreline packet by DOE) and no appeal has been filed or the project is withdrawn or canceled; or
(b) 
If the director's decision has been appealed, the day after the appeal is resolved by either the hearing examiner or city council; or
(c) 
If the decision is made by the hearing examiner or city council, the day after final city council action on the proposal.
The applicant shall submit an affidavit of posting to the director at least 10 calendar days prior to the public hearing on the application or the deadline for public comments. If an affidavit is not filed as required, or if the notice board is removed during this time period, any scheduled hearing or deadline for public comments shall be postponed until the applicant complies with this requirement.
(6) 
Notice boards shall be constructed and installed in accordance with the city's building code and the department's specifications, if any. Alternatively, the city may make available public notice signs which can be purchased from the city upon payment of a fee to be set by resolution.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.25.040 Optional public notice of application.

(1) 
The director, in their discretion, may:
(a) 
Notify the public or private groups with known interest in a proposal or type of proposal;
(b) 
Notify the news media;
(c) 
Place notices in appropriate regional or neighborhood newspapers or trade journals;
(d) 
Publish notice in agency newsletters or send notice to agency mailing lists, either general lists or lists for specific proposals or subject areas; and
(e) 
Mail notice to neighboring property owners.
(2) 
The director's failure to provide optional notice, as described in this section, shall not be grounds for invalidation of any permit decision.
(Ord. 019-17 § 18 (Exh. 1); Ord. 017-23 § 1 (Exh. A))

§ 20.25.050 Notice of public hearing.

(1) 
Mailed Notice of Public Hearing. The city shall use the records of the Kitsap County assessor's office as the official records for determining ownership of property. The director shall mail notice of the public hearing as follows:
(a) 
At least 14 calendar days before the hearing date, notice shall be mailed to:
(i) 
The applicant and all owners or contract purchasers of record of the property that is the subject of the application;
(ii) 
All property owners of record within 300 feet of the site;
(iii) 
Affected governmental agencies as determined by the city;
(iv) 
Any neighborhood or community organization whose boundaries include the property proposed for development, and which has requested notice;
(v) 
Any person who submitted written comments on the application (other than a signed petition);
(vi) 
Any person who submits a written request to receive notice; and
(vii) 
For appeals, the appellant and all persons who provided testimony in the original decision.
(2) 
Affidavit of Mailed Notice of Public Hearing. The director shall have an affidavit of mailed notice of public hearing prepared and made a part of the administrative record. The affidavit shall be a sworn statement stating the date that the notice of public hearing was mailed to the persons who must receive notice, as identified herein.
(3) 
Published Notice of Public Hearing. At least 10 calendar days before the hearing, notice of the hearing shall be printed in the city's official newspaper (a newspaper in general circulation in the city). The newspaper's affidavit of publication of the notice shall be made part of the administrative record.
(4) 
Content of Notice of Public Hearing. The notice of public hearing shall contain:
(a) 
The name and address of the applicant and the applicant's representative;
(b) 
A description of the subject property reasonably sufficient to inform the public of its location, including, but not limited to, a vicinity location or written description, a map or postal address, and a subdivision lot and block designation, but need not include a legal description. A legal description alone does not meet this requirement;
(c) 
The date, time, and place of the public hearing;
(d) 
The nature of the application and the proposed land use or uses that could be authorized for the property;
(e) 
A statement that all interested persons may appear and provide testimony;
(f) 
The sections of the code that are pertinent to the hearing procedure, including, but not limited to, the codes describing the applicable criteria and development standards that apply to the application;
(g) 
The threshold determination made under SEPA (WAC 197-11-330), if any;
(h) 
A statement describing when the information in the administrative record may be examined by the public and when and how written comments addressing findings required for a decision by the decision-maker(s) may be admitted;
(i) 
The name of a city representative to contact and the telephone number where additional information may be obtained;
(j) 
A statement explaining that a copy of the application, all documents relied upon by the applicant, and a list of the applicable criteria for the application are available for inspection by the public at no cost and that copies will be provided at the requestor's cost; and
(k) 
A statement explaining that a copy of the staff report will be available for inspection at no cost at least seven calendar days prior to the hearing and that copies will be provided at the requestor's cost.
(5) 
Final notice of decision for project permits not requiring a public hearing shall be mailed to the applicant in accordance with POMC § 20.24.110.
(Ord. 019-17 § 18 (Exh. 1); Ord. 033-20 § 5)

§ 20.26.010 Purpose and authority.

The purpose of this chapter is to authorize the use of development agreements, consistent with RCW 36.70B.170 through 36.70B.210. The city may, but under no circumstances is required to, enter into a development agreement with a person having ownership or control of real property within the city. The development agreement may address such project elements as those set forth herein, pursuant to RCW 36.70B.170B(3). The development agreement shall be consistent with the applicable development regulations of the city. The consideration provided by the property owner for the city's decision to enter into the development agreement may vary, depending on the benefit the development agreement will provide to the city and/or the public in general.
(Ord. 019-17 § 18 (Exh. 1); Ord. 030-20 § 3)

§ 20.26.020 Form of agreement, effect and general provisions.

(1) 
Form. A development agreement shall set forth the development standards and other provisions that apply to and govern and vest the development, use, and mitigation of the development of the real property for the duration specified in the agreement.
(a) 
For the purposes of this chapter, "development standards" may include, but are not limited to:
(i) 
Project elements such as residential densities, nonresidential densities and intensities or building sizes;
(ii) 
The amount and payment of impact fees imposed or agreed to in accordance with any applicable provisions of state law, any reimbursement provisions, other financial contributions by the property owner, inspection fees, or dedications;
(iii) 
Mitigation measures, development conditions, and other requirements under Chapter 43.21C RCW;
(iv) 
Design standards such as maximum heights, setbacks, landscaping, and other development features;
(v) 
Affordable housing;
(vi) 
Parks and open space preservation;
(vii) 
Phasing;
(viii) 
Review procedures and standards for implementing decisions;
(ix) 
A build-out or vesting period for applicable standards; and
(x) 
Any other development requirement or procedure deemed appropriate by the city council.
(b) 
In order to encourage innovative land use management and provide flexibility to achieve public benefits, a development agreement adopted pursuant to this chapter may impose development standards that differ from the following development regulations of this code; provided, that any development standards imposed by the development agreement shall be consistent with the comprehensive plan:
(i) 
Chapter 20.08 POMC, Vesting;
(ii) 
Chapter 20.12 POMC, Definitions;
(iii) 
Chapter 20.30 POMC, Introduction to Zoning, Land Uses, and Building Types;
(iv) 
Chapter 20.32 POMC, Building Types;
(v) 
Chapter 20.33 POMC, Greenbelt District;
(vi) 
Chapter 20.34 POMC, Residential Districts;
(vii) 
Chapter 20.35 POMC, Commercial and Mixed Use Districts;
(viii) 
Chapter 20.36 POMC, Industrial Districts;
(ix) 
Chapter 20.37 POMC, Civic and Open Space Districts;
(x) 
Chapter 20.38 POMC, Overlay Districts;
(xi) 
Chapter 20.39 POMC, Use Provisions;
(xii) 
Chapter 20.40 POMC, Site and Lot Dimensions;
(xiii) 
Chapter 20.41 POMC, Transfer of Development Rights Program;
(xiv) 
Chapter 20.54 POMC, Nonconformities;
(xv) 
Chapter 20.68 POMC, Accessory Dwelling Units;
(xvi) 
Chapter 20.80 POMC, Subdivisions – General Provisions;
(xvii) 
Chapter 20. 82 POMC, Administration and Enforcement;
(xviii) 
Chapter 20.84 POMC, Boundary Line Adjustments;
(xix) 
Chapter 20.86 POMC, Short Subdivisions;
(xx) 
Chapter 20.88 POMC, Subdivisions – Preliminary Plats;
(xxi) 
Chapter 20.90 POMC, Subdivisions – Final Plats;
(xxii) 
Chapter 20.94 POMC, Binding Site Plans;
(xxiii) 
Chapter 20.96 POMC, Vacation and Alteration of Final Plans and Short Plats;
(xxiv) 
Chapter 20.98 POMC, Improvements;
(xxv) 
Chapter 20.100 POMC, Development Standards – Subdivision Design;
(xxvi) 
Chapter 20.120 POMC, Development Standards – General Provisions;
(xxvii) 
Chapter 20.122 POMC, Building Elements;
(xxviii) 
Chapter 20.124 POMC, Development Standards – Parking and Circulation;
(xxix) 
Chapter 20.127 POMC, Design Standards;
(xxx) 
Chapter 20.128 POMC, Landscaping;
(xxxi) 
Chapter 20.129 POMC, Significant Trees;
(xxxii) 
Chapter 20.132 POMC, Sign Code;
(xxxiii) 
Chapter 20.139 POMC, Residential Design Standards;
(xxxiv) 
Chapter 20.162 POMC, Critical Areas Regulations;
(xxxvi) 
Chapter 20.182 POMC, Impact Fees.
(c) 
A development agreement shall not modify any provision of this code that is not identified in subsection (1)(b) of this section.
(d) 
A development agreement may modify the provisions of this code only if the city council determines that the requested modifications are necessary to provide flexibility to achieve public benefits and provide superior outcomes than those that would result from strict compliance with the other applicable development standards.
(e) 
Any approved development standards that differ from those other applicable development standards shall not require any further zoning reclassification, variance from city standards or other city approval apart from development agreement approval.
(f) 
Subsequently adopted standards which differ from those in the development agreement shall apply to the subject site where necessary to address a serious threat to public health and safety or where the development agreement specifies a time period or phase after which certain identified standards may be modified. Building permit applications shall be subject to the building and construction codes in effect when the building permit application is deemed complete.
(2) 
Decision Type. Development agreements are a Type V action and shall be reviewed and approved pursuant to the procedures in Chapter 20.22 POMC and this chapter, except that if the development agreement is consolidated with a new or pending Type I, II, III or IV project permit application as defined in RCW 36.70B.020, the city council's decision to approve, deny, or modify the development agreement may be appealed pursuant to Chapter 36.70C RCW.
(3) 
Effect. Development agreements are not project permit applications and are not subject to the permit processing procedures in Chapter 36.70B RCW or Chapter 20.24 POMC. A development agreement shall constitute a binding contract between the city and the property owner and the subsequent owners of any later-acquired interests in the property identified in the development agreement. A development agreement governs the project identified in the development agreement during the term of the development agreement, or for all or that part of the build-out period specified in the development agreement, and may not be subject to an amendment to a zoning ordinance or development standard adopted after the effective date of the agreement, except as set forth in this chapter. A permit or approval issued/granted by the city after execution of a valid development agreement must be consistent with the development agreement.
(4) 
Limitations.
(a) 
A development agreement shall be limited to a 20-year term if any provision of the agreement requires the city to:
(i) 
Refrain from exercising any authority that it would have otherwise been able to exercise in the absence of the development agreement;
(ii) 
Defer application to the subject property of any newly adopted development regulations that would otherwise apply to the property identified in the agreement; or
(iii) 
Allow vesting beyond the applicable deadlines for a phased development.
(b) 
The development agreement shall also contain a proviso that the city may, without incurring any liability, engage in action that would otherwise be a breach if the city makes a determination on the record that the action is necessary to avoid a serious threat to public health and safety, or if the action is required by federal or state law.
(c) 
The full costs of drafting and processing the development agreement shall be reimbursed by the owner or applicant prior to final city council action on the agreement to the extent such costs exceed the initial application fee.
(5) 
Developer's Compliance. The development agreement shall include a clause stating that the city's duties under the agreement are expressly conditioned upon the property owner's substantial compliance with each and every term, condition, provision and/or covenant in the development agreement, all applicable federal, state, and local laws and regulations and the property owner's obligations as identified in any approval or project permit for the property identified in the development agreement.
(6) 
No Third Party Rights. Except as otherwise provided in the development agreement, the development agreement shall create no rights enforceable by any party who/which is not a party to the development agreement.
(7) 
Liability. The development agreement shall include a clause providing that any breach of the development agreement by the city shall give right only to damages under state contract law and shall not give rise to any liability under Chapter 64.40 RCW, the Fifth and Fourteenth Amendments to the U.S. Constitution, or similar state constitutional provisions.
(8) 
Termination, Modification and Extension. Every development agreement shall have an identified, specific termination date. Upon termination, any further development of the property shall conform to the development regulations applicable to the property at the time of permit application. The city shall not modify any development agreement by extending the termination date unless the city council makes legislative findings that the additional benefits to the city provided by the developer in exchange for such extension of the development agreement outweigh the impacts from the development authorized by the extension. In no case shall an extension include the extension of provisions that are inconsistent with state or federal law at the time of such extension. Any request for a modification shall be consistent with the city's development regulations applicable to the property at the time of the request, not the original execution date of the development agreement. Any extensions granted shall be for no more than a length of 10 years. No more than two extensions of up to 10 years shall be granted. Extensions may not be granted unless an application for an extension is made no later than 180 days prior to the termination date in the development agreement or prior to the termination of any extension of a development agreement.
(Ord. 019-17 § 18 (Exh. 1); Ord. 030-20 § 3; Ord. 010-23 § 2)

§ 20.26.030 Application requirements.

Any owner of real property may, personally or through an agent, apply for a development agreement by filing with the department of community development the following:
(1) 
Name, address, telephone number and email address (if any) of the property owner. If the applicant is not the property owner, the applicant must submit a verified statement from the property owner that the applicant has the property owner's permission to submit the application;
(2) 
Address, parcel number and legal description of the property proposed to be subject to the development agreement;
(3) 
Recent title report confirming that the property identified in the application is owned by the applicant/property owner;
(4) 
Identification of any application (project permit application, comprehensive plan amendment application, development regulation amendment application) that is related to the proposed development agreement;
(5) 
SEPA checklist, if applicable;
(6) 
Two sets of stamped envelopes, and a list of the same, labeled with the name and address of all current owners of real property, as shown in the records of the county assessor for the subject property, within 300 feet of each boundary of the subject property;
(7) 
A copy of the county assessor's map identifying the properties specified in the preceding subsection;
(8) 
A completed application form and the application fee established by the city for this purpose; and
(9) 
Any other information requested by the community development director relevant to the processing of the development agreement.
(Ord. 019-17 § 18 (Exh. 1); Ord. 030-20 § 3)

§ 20.26.040 Phasing.

(1) 
In order to phase a project to extend the vested rights associated with an underlying project permit application, a development agreement is required. This ensures the availability of public facilities and services to all of the property in the identified individual phases, allows tracking of the available capacity of public facilities and utilities during each phase of construction, and with the extension of the vested rights associated with the project, provides certainty to the developer in the subsequent development approval process.
(2) 
The deadlines in the city's code relating to each type of project permit application must be consulted to establish the baseline vesting period. The city is not required to extend the vesting period. If the city decides to do so through a development agreement, it must be in exchange for the property owner's provision of corresponding benefits to the city in the form of, for example, contributions to public facilities and amenities over and above what would normally be required. In any event, the city shall not allow vesting to extend beyond the established 20-year period after approval of the project permit application unless the development agreement is extended in accordance with POMC § 20.26.020(8).
(3) 
A development agreement for a phased development (such as a subdivision) shall include (in addition to all of the information in POMC § 20.26.030), all of the following:
(a) 
Identification of the phasing schedule;
(b) 
Identification of the number of phases and all lots included in each phase;
(c) 
Identification of the approximate dates for construction of public streets, public utilities and other improvements in each phase;
(d) 
Identification of the approximate dates for commencement of development of each lot, lot sales and building occupancy;
(e) 
Identification of the benefits that the property owner will provide to the city in exchange for permission to phase the development according to the proposed schedule;
(f) 
Establishment of the deadline for the property owner to submit development applications, including building permit applications, for each phase;
(g) 
A description of the manner in which each phase is designed such that all site requirements are satisfied independently of phases yet to be given final approval and constructed;
(h) 
A description of the manner in which the property owner will ensure that adequate public facilities are available when the impact of development occurs. The property owner shall acknowledge in the development agreement that if the demand for public facilities or services needed to accommodate a subsequent development phase increases following the issuance of a development permit for a prior phase in the approval process, or if public facilities or services included in a concurrency or SEPA determination are not constructed as scheduled in the city's capital facilities plan, final development approval may have to be delayed for future phases pending the achievement of the adopted levels of service.
(Ord. 019-17 § 18 (Exh. 1); Ord. 030-20 § 3)

§ 20.26.050 Processing procedures and appeals.

(1) 
Development agreements are not "project permit applications" as defined in RCW 36.70B.020(4). Therefore, there is no deadline for processing a development agreement.
(2) 
A development agreement may be submitted for review in conjunction with a land use and development permit for the underlying project. The development agreement application may be consolidated for processing with the underlying project permit application or other application for approval. Any development plan accompanying the development agreement shall be subject to the applicable project permit/approval application process set out in this title. The application shall not be deemed complete until a draft development agreement has been prepared and a development proposal conforming to the parameters of the development agreement and meeting all pertinent requirements has been submitted. If the development agreement is consolidated with a project permit application, the property owner must agree to waive the deadline in RCW 36.70B.080 and POMC § 20.24.110 for issuance of a final decision on the underlying application, as well as the prohibition of no more than one open record hearing and one closed record hearing on the underlying project permit application in RCW 36.70B.060(3).
(3) 
Public Notice and Public Hearing.
(a) 
Notice of the public hearing shall be provided pursuant to POMC § 20.22.070.
(b) 
If the owner of the real property which is the subject of the development agreement owns another parcel or parcels of real property which lie adjacent to the real property included in the development agreement, notice under this subsection shall be given to owners of real property located within 300 feet of any portion of the boundaries of such adjacently located parcels of real property owned by the owner of the real property included in the development agreement.
(c) 
The hearing on the development agreement shall be held pursuant to POMC § 20.22.070, except that when the development agreement is processed as a legislative matter (i.e., not consolidated with a project permit) the city council shall conduct the hearing itself and forgo a hearing and recommendation by the planning commission. Any requests associated with the project-specific development proposal requiring a public hearing by the hearing examiner shall be heard by the hearing examiner prior to city council action on the development agreement. While the director or hearing examiner may provide a recommendation on a development agreement (even if the director or hearing examiner makes the final decision on the underlying project permit application), the city council shall make the final decision whether to approve a development agreement by ordinance after the public hearing.
(d) 
Modifications to a development agreement shall be in writing, signed by the duly authorized representatives of the parties, be consistent with this chapter and, where considered substantive as determined by the director, follow the same procedures set forth in this chapter.
(4) 
Appeal. A development agreement associated with an underlying project permit application may be appealed in the same manner and within the same deadline as the underlying project permit application. A development agreement associated with a legislative approval, such as a comprehensive plan amendment, may be appealed in the same manner and within the same deadline as the legislative approval. A modification of a development agreement pursuant to POMC § 20.26.020(8) that is consolidated with a new or pending Type I, II, III, or IV project permit application may be appealed pursuant to Chapter 36.70C RCW.
(5) 
Recording Against the Property. The city shall record the development agreement against the property with the real property records of the Kitsap County auditor. During the term of the agreement, it is binding upon the owners of the property and any successors in interest to such property.
(Ord. 019-17 § 18 (Exh. 1); Ord. 030-20 § 3)

§ 20.26.060 Discretionary legislative action.

The decision of the city council to approve or reject a request for a new development agreement, a modification to an existing development agreement, or grant an extension of an existing development agreement, shall be a discretionary, legislative act and an exercise of the city's police power and contract authority.
(Ord. 030-20 § 3)

§ 20.26.070 Unauthorized fees prohibited.

Nothing in this chapter is intended to authorize the city to impose impact fees, inspection fees, or dedications or to require any other financial contributions or mitigation measures except as expressly authorized by other applicable provisions of law.
(Ord. 030-20 § 3)

§ 20.28.100 Purpose.

The purpose of a variance is to provide a means whereby the literal terms of the city's zoning code need not be applied, if circumstances or conditions not created by, or not within the property owner's control, have created practical difficulties or unnecessary hardships that undermine the spirit of these regulations or undermine public safety and welfare. A variance cannot authorize a change to an allowed use or required density limitations. In sum, the variance procedures provide relief from specific dimensional standards in the code (e.g., setbacks) when they have the unintended effect of preventing reasonable development in conformance with all other codes. Variances are not favored and are intended to allow relief in circumstances in which the zoning code requirements significantly diminish the value of a specific property.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.110 Applicability.

(1) 
Deviation from Land Use Regulations Only. The variance procedures provided for in this chapter are for the consideration of deviations from only the city's land use regulations provided for under this title;
(2) 
Shoreline Variances. For properties located within the city's shoreline zone, a deviation from the standards and regulations of the city's shoreline master program requires a separate shoreline variance pursuant to the procedures under Chapter 20.164 POMC;
(3) 
Exceptions and Modifications Versus Variances. A code standard or approval criterion ("code section") may be modified without approval of a variance if the applicable code expressly allows exceptions or modifications. If the code section does not expressly provide for exceptions or modifications, then a variance is required to modify that code section and the provisions of this chapter apply;
(4) 
Types of Variances. There are three types of variances: administrative (1 and 2) and quasi-judicial. The type of variance required depends on the extent of the variance request and the discretion involved in the decision-making process;
(5) 
Prohibitions. The city will not grant any variance that will allow the establishment of a use which:
(a) 
Is not otherwise permitted in the zone;
(b) 
Would result in the extension of a nonconforming use or structure; or
(c) 
Would change the development regulations in the zone applicable to the subject property;
(6) 
A variance will not result in violation(s) of any other adopted ordinance or code standard; each code standard to be modified shall require a separate variance request;
(7) 
An application for an administrative Type 1 variance may only apply to a single lot/parcel or a single identified development project; and
(8) 
No more than three administrative Type 1 variances may be approved for one lot or parcel.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.120 Administration of administrative variance.

The director is authorized and directed to administer the provisions of this chapter relating to administrative variances. There is no public hearing, and after issuance of the final decision, the hearing examiner has the authority to hear and issue a decision on an appeal in an open record hearing.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.130 Procedure for administrative variance.

Administrative variance applications are processed pursuant to Chapter 20.24 POMC.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.140 Requirements for a complete application.

A complete application for either an administrative or quasi-judicial variance application shall include the items listed below. Refer to the relevant city application form for numbers of copies of each item that must be included and the type of accompanying electronic submittal that is required (if relevant).
(1) 
Application form. Seven copies of a completed application form (including all supporting documents);
(2) 
Date, name, address, telephone number and email of the applicant;
(3) 
Name, address, telephone number and email of the owner of the property identified in the application;
(4) 
Legal description of the subject property;
(5) 
Description and photographs of existing site conditions, any plans and/or relevant information to the proposed variance;
(6) 
A site plan and building elevation drawings of all structures proposed to be developed on the subject property. More specific architectural drawings may be required depending on the content of the variance request;
(7) 
Identification of all sections of the city's zoning code from which the applicant seeks the variance and a complete description of the requested variance from such section(s);
(8) 
Description of any proposed development of the property, applying the proposed variance from the identified code section(s);
(9) 
An explanation of the rationale for the proposed variance;
(10) 
The applicant's narrative statement describing the manner in which the application satisfies the criteria for variance approval in POMC § 20.28.150 or § 20.28.180 depending on the type of variance;
(11) 
A SEPA checklist (unless categorically exempt);
(12) 
Concurrency determination (water, sewer and traffic if applicable);
(13) 
The application fee established by the city;
(14) 
Any other required information as indicated by city staff in a preapplication meeting.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.150 Administrative variances – Definition and criteria for approval.

(1) 
Administrative Variance Type 1.
(a) 
A Type 1 administrative variance is defined as:
(i) 
Front Yard Setbacks. Up to a 10 percent reduction to the front yard setback standard in the applicable land use zoning district.
(ii) 
Interior Setbacks. Up to a 10 percent reduction of the dimensional standards for the side and rear yard setbacks required in the applicable land use zoning district.
(iii) 
Lot Coverage. Up to a 10 percent increase of the maximum lot coverage required in the applicable land use zoning district.
(iv) 
Landscape Area. Up to a 10 percent reduction in landscape area (overall area or interior parking lot landscape area).
(v) 
Building Height. Up to a 10 percent increase in maximum building height in the applicable land use zoning district, except within any land use zoning district or overlay district with view protection regulations.
(b) 
A Type 1 administrative variance may be approved if the applicant demonstrates all of the following:
(i) 
There is no presumption of validity favoring the action of granting a variance;
(ii) 
The variance requested is required due to the lot configuration, or other conditions of the site;
(iii) 
The variance does not require the removal of any trees within a critical area or its buffer, designated greenbelt, or habit conservation area; or it is proposed in order to avoid or reduce impact to floodplains, significant trees, wetlands, or other natural features. Modification of the standard shall not be more than is necessary for the preservation of the natural feature to be preserved or protected;
(iv) 
The subject property cannot be reasonably used under the city's land use regulations as written.
(2) 
Administrative Variance Type 2.
(a) 
The following Type 2 administrative variances may be approved on individual platted and recorded lots only. The administrative variance procedure shall not be used to modify a standard for lots yet to be created through a platting process under Chapter 20.86 or 20.88 POMC.
(i) 
Variance to Parking Standards. A variance may be approved to the minimum or maximum standards for off-street parking (quantities and dimensions of parking spaces) if the applicant demonstrates all of the following:
(A) 
There is no presumption of validity favoring the action of granting a variance;
(B) 
The individual characteristics of the use at that location require more or less parking than is generally required for a use of this type and intensity, or modified parking dimensions, as demonstrated by a parking analysis or other facts provided by the applicant;
(C) 
The need for additional parking cannot reasonably be met through provision of on-street parking or shared parking with adjacent or nearby uses; and
(D) 
All other code standards are met in conformance with the underlying zoning district and design standards.
(ii) 
Variance to Bicycle Parking Standards. There is no presumption of validity favoring the action of granting a variance. A variance may be approved to reduce the number of required bicycle parking standards required in Chapter 20.124 POMC if the applicant can demonstrate that the proposed use by its nature would be reasonably anticipated to generate a lesser need for bicycle parking.
(iii) 
Variance to Vehicle Stacking Area. There is no presumption of validity favoring the action of granting a variance. A variance may be approved to reduce the amount of vehicle stacking area required for drive-through facilities if such a reduction is deemed appropriate after analysis of the size and location of the development, limited services available and other pertinent factors.
(iv) 
Variance to Loading Area Standards. There is no presumption of validity favoring the action of granting a variance. A variance may be approved to modify the loading area standards if such a reduction is deemed appropriate after analysis of the use, anticipated shipping or delivery traffic generated by the use and alternatives for loading/unloading, such as use of on- or off-street parking areas during nonbusiness hours; provided, that traffic, pedestrian access, and circulation standards are not impeded.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.160 Administration of quasi-judicial variances.

The community development director is authorized and directed to administer the provisions of this chapter relating to quasi-judicial variances. The authority to hold an open record hearing and provide a final decision on variances is granted to the hearing examiner and the city council has the authority to make a decision on appeal after a closed record hearing.
(Ord. 019-17 § 18 (Exh. 1); Ord. 017-23 § 5 (Exh. A))

§ 20.28.170 Procedure for quasi-judicial variance approval.

Quasi-judicial variance applications are processed pursuant to Chapters 20.20, 20.22, 20.24 and 20.25 POMC.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.180 Quasi-judicial variances – Definition and criteria for approval.

(1) 
Quasi-Judicial Variances – Definition. Any request for a variance under the city's zoning code that does not meet the definition of an administrative variance above shall be processed as a quasi-judicial variance.
(2) 
Approval Criteria. There is no presumption of validity favoring the action of granting a variance. The hearing examiner may not approve a quasi-judicial variance unless the applicant demonstrates that all of the following criteria are satisfied:
(a) 
That, because of special circumstances applicable to the property, including its size, shape, topography, location or surroundings, the strict application of these regulations will deprive such property of privileges enjoyed by other property in the same vicinity and zone as the subject property;
(b) 
That a grant of a variance will be subject to conditions to ensure that the adjustment authorized is the minimum variation needed and that it will not constitute a grant of special privilege(s) inconsistent with the limitations upon other properties in the vicinity and zone in which such property is located;
(c) 
The special circumstances applicable to the property are not self-imposed by any person having an interest in the property; and
(d) 
The variance will not allow the establishment of a use which: (i) is materially detrimental to the public welfare or injurious to the property or improvements in the vicinity and zone in which the subject property is situated; (ii) is not otherwise permitted in the zone; (iii) would result in the extension of a nonconforming use or structure; or (iv) would change the terms of the zone applicable to any or all of the subject property.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.190 Conditioning.

Issuance of a variance may be made subject to such conditions as are necessary to carry out the purpose of this code and ensure that the variance authorized shall not constitute a granting of special privilege inconsistent with the limitations upon other properties in the vicinity and zone in which such property is located. Conditions serving to prevent or minimize adverse effects upon other property in the neighborhood shall include, but shall not be limited to: limitations on size and location, hours of operation, requirements for landscaping or buffer yards, lighting and ingress and egress.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.200 Deadline for final decision.

A variance application (either administrative or quasi-judicial) shall be approved, approved with conditions or denied within 120 days after the application has been determined complete, unless the applicant consents in writing to a longer processing time period.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.210 Effect of approval.

Issuance of a variance shall be deemed to allow variation from the code section identified in the approval only to the extent authorized in the decision. Development of the property subject to the variance shall not be carried out until the applicant has secured all other permits and approvals required by the city, or any applicable regional, state and federal agencies. Approval of a variance shall not be a precedent for the approval of other variances in the zoning district.
(Ord. 019-17 § 18 (Exh. 1))

§ 20.28.220 Expiration.

A variance approval shall become null and void three years after the effective date, unless one of the following has occurred:
(1) 
A building permit has been issued and construction begun and diligently pursued;
(2) 
An extension has been granted by the planning director. Such extension shall be for a maximum of one year, and no extension may be granted which would extend the validity of the variance more than five years beyond the effective date of the variance. No extension will be granted if it necessitates modification of any condition of approval.
(Ord. 019-17 § 18 (Exh. 1))