Laserfiche WebLink
the daitv administration of the old zoning code through a <br />collaborative group review process. Research the work. of other <br />planning agencies for good examples, and determine if their <br />approach is applicable. A caretul diagnosis of these problems <br />should be prepared, and the team responsible (or the update <br />should be charged with correcting them. <br /> <br />Techniques for Better Readability <br />Word Processi,g. Computers and word processing software are <br />essential (or a major zoning code update. The speed, flexib ry, <br />file management, and editing capabilities of word processing <br />makes its use a clear choice. Most planning agencies now have <br />this because J~ is a cos~-effectJve investment. Laser printing will <br />help yield professional results. <br /> Appearance of the Code. Overall appearance affects how the <br />new zoning code is written and should be decided eariv on. A <br />code should have a thematic look from cover to cover with <br />uniX'lng elements consisting of its cover, paper color, type sD, lc, <br />and text layout. A professional appearance will more likdy have a <br />positive impact. <br /> Some communities use the same cover designs, loges, and <br />paper as the zoning code's companion documents, such as a <br />comprehensive pian. This helps to establish a relationship <br />between these documents. Gimmicks, however, undermine the <br />confidence created by a simple, straightforward appearance. <br /> Don't use brightly colored paper that will detract from the <br />zoning code. Also, some colors do not photocopy well. Use a <br />muted color cover stock and white paper for the text. Some <br />codes use colored paper to separate certain sections. <br /> General Organization. Start by grouping related provisions. <br />The organization and order of zoning codes ,,,an',. but usually <br />include general provisions, zoning district standards, special <br />deveiopment regulations, administration, and definitions. <br /> Grouping related t~rovisions will improve readabiiirv. Readers <br />can find information quickiy if they know that specific provisions <br />are grouped together. Some cities randomiy piace provisions in <br />the code based on their order of adoption or `.vhere space permits. <br />Finding regulations becomes difficult as readers must scan the <br />entire code to be sure there are no other related regulations. <br /> However, there are exceptions, h is easier to have certain <br />special development standards and definitions in the same major <br />division. For exampte, use of the term "home occupations" may <br />occur onh, in the speciai deveiopment standards division on <br />home occupations. It would be inconvenient to include this <br />definition in the definitions division. Converseb,, the term <br />"dwelling" may be found throughout the code, in which case its <br />definition should be located in the definitions division. <br /> Landscaping is a troublesome subject in most zoning codes. <br />Should there be a special section for landscaping, or should <br />landscaping provisions be located throughout the code? Many <br />codes do both. It may be logical to have a general landscaping <br />section applicable to all zoning districts and have specific standards <br />applicable to a specific section. For example, there should be <br />landscaping standards in the parking section because they are <br />frequent})' used together. However, general landscaping provisions <br />such as types of plant materials, irrigation, and maintenance that <br />apply to both zoning districts and parking lots should be located in <br />the code's special development standards division. <br /> Another organizational issue invoh,es writing standards and <br />procedural sequences that follow the same general order. ]f <br />tables are used to show development standards for each zoning <br />district, the standards should appear in nearly identical order for <br />each zoning district, and the tables should have the same general <br /> <br />design. Rezonings, variances, conditional use permits, and <br />architectural review should also follow the same procedural <br />sequences and use the same words to the extent possible. This <br />wilt make it easier for staff to memorize procedures and will <br />make procedural differences more noticeable. <br /> Decide early whether to incorporate laws, regulations, and <br />standards by reference or tn include the text of standards <br />adopted by other governing bodies that affect zoning <br />regulations. Some would argue that it is better to incorporate by <br />reference because the taws or regulations being referenced <br />frequently change. The guide here should be- common sense. If <br />the outside regulation is used infrequently and is lengthy, <br />incorporate it by reference onh'. Generalh'. it is better to <br />monitor changes outside the local jurisdiction and amend the <br />zoning code than to endure the inconvenience of having to use <br />the zoning code in conjunction with other reference sources. <br /> <br />Maior <br />Division Description Examples <br /> <br /> General <br />Provisior~s <br /> <br />Zoning <br />D~slrict <br />Regulations <br /> <br />Special <br />Developmenl <br />Standards <br /> <br />Administration <br />and <br />Enforcement <br /> <br />Definitions <br /> <br />Contains provisions <br />apphcable lo the <br />entire zoning cede. <br /> <br />Includes alt zoning <br />districl and overlay <br />dist'nct regulations. <br /> <br />Includes specific <br />develo0ment stan- <br />dards applicable to <br />one or more uses <br />or dislr~ClS. <br /> <br />Procedural require- <br />ments lot all <br />administrative and <br />legislative reviews, <br />appeals, enforce- <br />ment, and penalties. <br /> <br />Definitions of lerms <br />used throughout <br />Ine zoning code. <br /> <br />Tille; purpose; authorily; <br />applicability of zoning code; <br />estabhshment el zoning <br />districts: rules of inter- <br />pretation: severabihty. <br /> <br />Agr¢cullural; resioentdal; <br />commercial; industrial; <br />hoodpiain overlay. <br /> <br />Parking; signs; noncon- <br />forming uses and struc- <br />tures; home occupations: <br />recycling facilities; bed and <br />breaklast inns. <br /> <br />Site p~an review: conditional <br />use permits and variances; <br />architectural review: zoning <br />coda amendmenls and <br />rezonmgs; filing el appeals; <br />enforcement and revocation <br />o~ permits and penalties. <br /> <br />"DweDng unit," 'structure." <br />"lot," "yard." Terms used only <br />m the special development <br />standarps (e.g., sign. salellite <br />d~sh antenna, bed and ureak- <br />fasL etc.) ShOUld be totaled <br />only m lhose sections. <br /> <br />Format. Format includes the adopted standard for the <br />appearance of each page. A consistent format is easier to use. <br /> Lega] publishing requirements often dictate page layout. The <br />zoning code is usually part of an agency's general code, which <br />may have an established format. Consult early with your legal <br />counsel to see if changes in format are possibie. <br /> If the esrablJshed format is unworkable, you may be relegated <br />to keeping a separate "unofficial" version that would nor be <br />codified in the agency's general code. in this case, a disclaimer <br />in the unofficial version should state that the official version is <br />included in the general code. An unofficial version lets the <br />planning agency make formatting changes without having re <br />formally amend the zoning code. <br /> Format inciudes a number of elements that should combine to <br />give each page an uncomplicated appearance. The most obvious Js <br /> <br /> <br />