Laserfiche WebLink
<br />Zoning Bulletin <br /> <br />Scope of Requirements-County denies permit <br />on grounds that -applicant could not meet llall <br />requirements" of county code <br /> <br />Applicant argues "all requirements" included aiternatives <br />articulated in the code <br /> <br />Citation: Griffinv. Thurston County, 2008 WL 4938899 (Wash. 2008) <br /> <br />WASHINGTON (11/20/08)-jeff Griffin owned a small waterhont <br />lot in the county. He wanted to build a house on the lot. R~lated to that <br />goal, he submitted an on-site sewage system ("OSS") permit application <br />to the county's Health and Social Service~ Department (the "Depart- <br />ment"). Griffin's lot was less than one-quarter the size normally tequired <br />for an OSS. His OSS application included six OSS components that re- <br />quired either modified setback distances or "waivers" of the county's san- <br />itary code (the "Code"). A health officer approved all six of the compo- <br />nents. However, after neighbors appealed, the county's Board of Health <br />(the "Board") denied Griffin's ass permit. Section 21.4.5.3 of the Code <br />required a proposed OSS on an undersized lot meet "all requirements of <br />[the Code] other than minimum land area:" The Board concluded that <br />because Griffin's OSS design required "a substantial number of waiver <br />requests, and horizontal setback reductions," Griffin could not meet "all <br />requirements" of the Code. ' <br />Griffin appealed the Board's denial. He argued that: other provisions <br />of the Code offered alternative setbacks and standards; his proposed OSS <br />met those alternatives; and therefore he met "all requirements." <br />The superior court agreed with Griffin. It reversed the Board and or- <br />dered the county to issue Griffin the OSS permit. <br />The county appealed. The court of appeals reversed the superior court <br />and upheld the Board's deniai of the permit. It reasoned that "[i]f 'all <br />requirements' included waivers and setbacks, the ['all requirements'] Jan- <br />guage would be meaningless and superfluous." <br />Griffin appealed. <br /> <br />DECISION: Affirmed on other grounds. <br /> <br />The Supreme Court of Washington agreed with Griffin that the "all <br />requirements" language of ~ 21.4.5.3 included the alternatives provided <br />in other provisions in the Code. However, the court concluded that Grif- <br />fin was not entitled to an OSS permit because one of his six OSS compo- <br />nents" failed to meet a Code requirement or Code-articulated alternative. <br />rId reaching its conclusion as to how ~ 21.4.5.3's "all requirements" <br />language should be interpreted, the court said that it interpreted local <br />ordinances in the same way that it interpreted statutes: it looked first to <br /> <br />4 <br /> <br />@ 2008 Thomson Reuters/West <br /> <br />60 <br /> <br />I <br />I <br />I <br />i <br />i <br />I <br />I <br />i <br />I <br />I <br /> <br />\ ' <br />