Skagit County planning commission reviews major rewrite of Title 14 development code

The Skagit County Planning Commission on April 22 reviewed a proposed, county-led reorganization of Skagit County Code Title 14 intended to make the development code easier to read and administer and to streamline residential permitting.

The draft ordinance, presented remotely by Ryan Walters, would reorganize the current Title 14 into divisions and new chapters, standardize definitions and terminology, convert long text lists into comparison tables, and move non-development items out of Title 14. "We are at work in reorganizing the county's development code, Skagit County code title 14," Walters said, adding the rewrite aims to "make it more user friendly and usable and easier to administer." The commission also welcomed new member Jed Holmes before taking up the presentations.

Why this matters: Planning staff told commissioners the reorganization should reduce internal inconsistencies, make use standards and permitted‑use tables easier to compare across zones, and shorten the time planners spend resolving ambiguous language. Walters said the approach emphasizes plain language, unifies terms (for example, standardizing varied historical usages such as "zoning district," "classification," and "district" to simply "zone"), and preserves many existing rules while improving organization.

Major elements explained by Walters include: - A division-based structure that breaks the existing long zoning chapter (current 14.16) into multiple chapters (examples shown as 14.10–14.19) grouped by zone types (rural, resource, UGA/Bayview Ridge, overlays) and an independent chapter for use standards so a user can find rules for an identified use in one place. - Standardized chapter/section headings (purpose, applicability, application requirements, review criteria) to align with state procedure language and to improve clarity for applicants and staff. - Moving non‑development items such as tax provisions out of Title 14 (to Title 3) so the development code contains only development regulations. - Limited substantive changes where staff judged necessary: middle‑housing is allowed in the RVR zone (updated table reference 14.11.020), vehicle‑charging stations were added to certain zone tables, the UGA would allow two accessory dwelling units (ADUs) rather than one, and a new type of land division—unit lot subdivisions—was added (standards in proposed 14.76 in the draft). Walters also noted an exemption from impact fees for ADUs beyond the 50% state minimum (the draft provides a full exemption for ADUs). - Administrative clarifications, including moving terminology from "administrative official" to "director" and integrating (later draft) director interpretations into the code so they receive consistent public review.

Walters emphasized the draft is mainly reorganization with "limited rewriting," and that some chapters received heavier substantive editing, such as setbacks, natural resource lands, and land divisions. He also described a new front‑end chapter (proposed 14.01) to guide users in navigating the reorganized code.

Commissioners asked for clarifications on how the director's role will operate in practice and where substantive changes were being proposed. Walters and staff said the schedule includes a public hearing on May 6 and deliberations May 20, and any Planning Commission recommendations that change the draft would likely trigger a second public comment period when the package goes to the Board of County Commissioners.

Walters: "We want to improve its readability ... and streamline residential permitting requirements." The commission agreed there will be opportunities for follow‑up questions and feedback as the review advances.

Looking ahead: staff told the commission the reorganization draft was published the day before the April 22 meeting and that the public hearing is scheduled for May 6, with commission deliberations planned for May 20. Any changes forwarded to the Board of County Commissioners will be re‑noticed for public comment as required.