A change in circumstances or conditions may warrant a change to development regulations. The purpose of this chapter is to establish the provisions to amend development regulation text, including Title 11, Zoning, Title 12, Subdivisions, Title 14, Development Permit Procedures and Administration, Title 15, Development Standards, and Title 16, Enforcement and Violations, when the change would be consistent with the goals, objectives, policies, and designations of the county comprehensive plan and the intent of this title.
(Res. 2004-85 (part), 7/27/04; Res. 2007-55 (part), 3/27/07; Res. 2012-78 (part), 8/14/12)
Proposed text amendments to Chelan County development regulations identified above may be initiated for review by the board of Chelan County commissioners, the Chelan County planning commission, Chelan planning staff, or by application by a member of the public or an authorized agent. Such amendments shall be consistent with the intent, goals, policies, and land use designations contained in the county comprehensive plan. If the proposed amendment is inconsistent with the provisions of the comprehensive plan, approval of an amendment to the county comprehensive plan consistent with the provisions contained in Title 14, Chapter 14.14, of the Chelan County Code is required prior to authorizing the amendment.
(Res. 2004-85 (part), 7/27/04; Res. 2007-55 (part), 3/27/07; Res. 2012-78 (part), 8/14/12)
Emergency amendments may be initiated by the board of county commissioners, outside of the normal amendment review cycle, upon a finding that a situation necessitates expeditious action to preserve the health, safety or welfare of the public. Staff shall immediately evaluate and analyze the emergency amendment and forward it to the planning commission for review at a public hearing. After the public hearing, the planning commission shall make a recommendation on the proposed amendment(s) to the board of county commissioners.
(Res. 2004-85 (part), 7/27/04; Res. 2007-55 (part), 3/27/07; Res. 2012-78 (part), 8/14/12)
The approval, modification or denial of a development regulation amendment application shall be evaluated on, but not limited to, the following criteria:
(1) 
The amendment is necessary to resolve a public land use issue or problem.
(2) 
The amendment is consistent with goals of the Growth Management Act, Chapter 36.70A RCW.
(3) 
The amendment complies with or supports comprehensive plan goals and policies and/or county-wide planning policies.
(4) 
The proposed amendment does not adversely affect lands designated as resource lands of long-term commercial significance or critical areas in ways that can-not be mitigated.
(5) 
The amendment is based on sound land use planning practices and would further the general public health, safety and welfare.
(Res. 2004-85 (part), 7/27/04; Res. 2007-55 (part), 3/27/07; Res. 2012-78 (part), 8/14/12)
Applications shall contain the information necessary to review the proposal as set forth in the provisions contained in Chapter 14.06 of this title and such other information as is needed to determine conformance with this title and the comprehensive plan. Additional information may be requested by the administrator at any time during the review process, and must be provided in a timely manner. The application shall be filed with the community development department along with the appropriate fee. Applications for development regulation text amendments will be reviewed in conformance with Section 14.10.050 of this title.
(Res. 2004-85 (part), 7/27/04; Res. 2007-55 (part), 3/27/07; Res. 2012-78 (part), 8/14/12)
Pursuant to RCW 36.70A.106(3), the department shall notify and transmit copies of proposed regulation amendments to the appropriate Washington State agencies as required by law, or successor agency at least sixty calendar days prior to anticipated action on recommendations of the planning commission. The department shall also transmit to agencies as required by law regulation amendments adopted by the board of county commissioners, within ten calendar days of adoption.
(Res. 2004-85 (part), 7/27/04; Res. 2007-55 (part), 3/27/07; Res. 2012-78 (part), 8/14/12)