Chapter 2.55
ADOPTION OF ORDINANCES AND RESOLUTIONS

Sections:

2.55.010    Purpose.

2.55.020    Use.

2.55.030    Public use or reliance not intended.

2.55.040    Types of county legislative actions.

2.55.050    Workshops on proposed ordinances and resolutions.

2.55.060    Rules for adoption of ordinances and resolutions.

2.55.010 Purpose.

The purpose of these rules is to establish a uniform process for adoption of ordinances and resolutions in Jefferson County. [Ord. 2-24 § 2]

2.55.020 Use.

No authority other than the BoCC, the BOH, or the county administrator may enforce these rules. Failure of the BoCC, the BOH or the county administrator to follow these rules in a particular instance shall not be considered as a waiver. No notice of waiver of these rules by the BoCC, the BOH, or the county administrator need be given. [Ord. 2-24 § 3]

2.55.030 Public use or reliance not intended.

Because these rules are procedural in nature and are designed to assist in the process of adoption of ordinances and resolutions and not to provide substantive rules affecting constituents, it is expressly stated that these rules do not constitute land use regulations, official controls, “appearance of fairness rules,” public hearing rules, or other substantive rules binding upon or to be used by or relied upon by members of the public. These rules do not amend statutory or other regulatory requirements (including in an ordinance). [Ord. 2-24 § 4]

2.55.040 Types of county legislative actions.

(1) Ordinance. An ordinance is a local law (legislative act) prescribing permanent rules of general applicability, including new legislation. Action by the BoCC and the BOH shall be taken by ordinance when required by a Jefferson County ordinance (including one codified in the Jefferson County Code (“JCC”), the Revised Code of Washington (“RCW”), or the Washington Administrative Code (“WAC”)), or where prescribed conduct may be enforced by penalty. All legislative acts should be made by ordinance. Actions relating to subjects of a permanent and general character are usually regarded as legislative.

(2) Resolution. A resolution usually is less formal than an ordinance and is a statement of legislative policy or direction that may concern matters of special or temporary character. Action by the BoCC or the BOH shall be taken by resolution in those instances where an expression of legislative policy more formal than a motion is desired. Resolutions may be adopted without a public hearing, unless a state or local law requires a hearing.

(3) Motion. A motion directs a specific course of action. A motion is less formal, usually unwritten, and once approved and entered into the record, is the equivalent of a resolution in those instances where an ordinance or a resolution is not required.

(4) Order. An “order” is used by a legislative body to direct a specific action be taken on behalf of the county. An order usually is unwritten. Once an order has been complied with, it no longer has effect. [Ord. 2-24 § 5]

2.55.050 Workshops on proposed ordinances and resolutions.

The BoCC or the BoH may discuss drafts of proposed ordinances and resolutions at a regular or special meeting, following all the requirements of the Open Public Meetings Act, Chapter 42.30 RCW, and this chapter. Ordinances or resolutions requiring a hearing shall not be adopted at a workshop, unless proper and timely notice of a hearing has been given prior to the workshop. [Ord. 2-24 § 6]

2.55.060 Rules for adoption of ordinances and resolutions.

The rules for adoption of ordinances and resolutions are as follows:

(1) One Subject Only. No ordinance or resolution shall contain more than one subject, which shall be clearly expressed in the title.

(2) Public Hearing Requirement. An ordinance may be adopted only after proper notice and a public hearing. Notice of the time, place and purpose of any public hearing shall be given by one publication in a newspaper of general circulation in the county and in the official gazette, if any, of the county, at least 10 days before the hearing. Some state statutes and local ordinances require a public hearing for ordinances and resolutions. A public hearing shall be held whenever one is required by state statute or local ordinance. State statutes that require a public hearing are listed in Appendix A to the Municipal Research and Services Center of Washington publication Local Ordinances for Washington Cities and Counties (2016), which can be found at https://mrsc.org/getmedia/44e20d0f-a536-473f-baac-bd7504323330/Local-Ordinances-For-Washington-Cities-And-Counties.pdf?ext=.pdf. For the avoidance of doubt, if the BoCC adopts a planning commission recommendation in full under JCC 18.45.060(3) or 18.45.090(4), a public hearing by the BoCC is not required since the planning commission is required to conduct a public hearing prior to transmission of its recommendation to the BoCC.

(3) Codification of Ordinances. All ordinances of the county of a general and permanent nature shall be incorporated into and become part of the JCC.

(4) Required Format for All Proposed Ordinances and Resolutions.

(a) Each proposed ordinance and resolution shall be in writing in its entirety;

(b) The clerk of the board of county commissioners shall be responsible for numbering each ordinance in the format where the consecutive number adopted each year starting with 01 for the first ordinance adopted, and so on; then, the month and date adopted in the following format: 0103 and so on; and then the year adopted in the following format: Ordinance No. 01-0103-24;

(c) The clerk of the board of county commissioners shall be responsible for numbering each resolution in the same manner as for ordinances in subsection (4)(b) of this section (Resolution No. 01-0103-24);

(d) If an ordinance or resolution is amended either by deleting or adding language or sections, reference shall be made in the title to the amended ordinance or amended resolution and the earlier ordinance’s or resolution’s number, any appropriate code section and, if applicable, the ordinance’s or resolution’s common name (e.g., the Uniform Development Code);

(e) If an ordinance or resolution repeals or replaces an earlier ordinance or resolution, reference shall be made in the title to the repealed or replaced ordinance or resolution and the earlier ordinance’s or resolution’s number, any appropriate code section and, if applicable, the ordinance’s or resolution’s common name;

(f) Each ordinance shall contain the following enactment clause: “Be it ordained by the Board of Health [Board of County Commissioners] of Jefferson County, State of Washington...”;

(g) Each resolution shall contain the following enactment clause: “Be it resolved by the Board of Health [Board of County Commissioners] of Jefferson County, State of Washington...”;

(h) Any definitions shall be in alphabetical order;

(i) Only gender neutral terms shall be used;

(j) If a violation of the ordinance is to be punished by a fine or imprisonment, the penalty shall be stated specifically in the ordinance;

(k) Each proposed ordinance or resolution shall contain the following additional language:

(i) A statement of facts supporting the ordinance or resolution, sometimes referred to as “whereas clauses”;

(ii) The purpose of the ordinance or resolution;

(iii) The detailed requirements of the ordinance or resolution;

(iv) The location in the Jefferson County Code for any ordinance to be codified;

(v) A statement explaining compliance with the State Environmental Policy Act, Chapter 42.21C RCW, or a statement identifying an exemption in WAC 197-11-800 that applies;

(vi) Whether an amended, repealed or replaced ordinance or resolution shall remain in force and effect until the effective date of the newly enacted ordinance or resolution;

(vii) Whether, if any section, subsection, paragraph, sentence, clause, or phrase of the ordinance is declared unconstitutional or invalid for any reason, such decision affects the validity of the remaining parts of the ordinance; and

(vii) Whether the effective date is the date of adoption or some other date.

(5) Public Notice Rules for Ordinances or Resolutions that Require a Hearing. A hearing notice for all proposed ordinances or all resolutions that require a public hearing shall be prepared and transmitted to the BoCC or the BOH, along with an agenda request at least 14 days before the date of any hearing.

(a) The hearing notice shall contain all of the following:

(i) A description of the nature of the proposal under consideration;

(ii) The availability of relevant draft documents and how they may be obtained, including the location(s) where the draft documents can be viewed either in person, on the county website, or both;

(iii) How the public can provide oral testimony and written comments;

(iv) The time, date and location of the hearing; and

(v) The range of alternatives considered or scope of alternatives available for oral testimony or public comment.

(b) The proposed ordinance or resolution described in the hearing notice shall be posted in the location(s) where it can be viewed, as stated in the hearing notice, at least three days prior to publication of the hearing notice.

(c) A hearing notice may be approved for publication by a motion. If such motion fails, the proposed resolution or ordinance shall be considered lost, unless a subsequently adopted motion directs that a revised hearing notice be published.

(6) Approval by the Prosecuting Attorney. The county relies on advice from the prosecuting attorney to ensure that all adopted ordinances and resolutions are in a form sufficient to enforce them and are in compliance with local, state and federal law. Accordingly, all ordinances and all resolutions that require a public hearing must be in a form approved by the prosecuting attorney or their designee:

(a) Before submission to the county administrator as required by subsection (7) of this section;

(b) Before posting a hearing notice in the location where a proposed ordinance or resolution requiring a hearing can be viewed, as required by subsection (5)(c) of this section;

(c) Before any public hearing by the planning commission on a proposed ordinance or resolution; and

(d) Before a recommendation on a proposed ordinance or resolution from the planning commission is submitted to or provided to the board of county commissioners.

(7) Rule Requiring Submission to the County Administrator. All proposed resolutions and ordinances must be submitted to the county administrator for review in the format required in subsection (4) of this section prior to submission to a county legislative authority for consideration or adoption.

(8) Hearing to Consider Adoption of an Ordinance or Resolution at an Open Public Meeting. After compliance with subsections (1) through (6) of this section, the BoCC or BoH may consider the ordinance or resolution at a regular or special meeting, following all the requirements of the Open Public Meetings Act, Chapter 42.30 RCW. The hearing must be held at the time, date and location stated in the hearing notice. [Ord. 2-24 § 7]