Laserfiche WebLink
PLANNING COMMISSIONERS JOURNAL / NUMBER 78 / SPRING 2010 <br />language. Such an ordinance will be easi- <br />er to administer and amend. <br />1. Make it Clear <br />There are several principles of clear <br />writing. Writing in the active voice – <br />using action verbs – is arguably the most <br />important. The active voice makes it <br />clear who is to perform the action <br />required. For example, an ordinance in <br />passive voice might say “The application <br />must be approved.” In active voice it <br />would say “The administrator must <br />approve the application.” <br />Here are some other suggestions: <br />• Use action verbs that are shorter <br />and more direct. For example, change <br />“make payment” to “pay” or “is con- <br />cerned with” to “concerns.” <br />• Be direct, especially when describ- <br />ing procedures and lists of duties. For <br />example, say “Sign all copies.” <br />• Similarly, convert phrases to simpler <br />terms. Instead of saying “failed to comply <br />with,” use the word “violated.” Substi- <br />tute simple words where possible. For <br />example, instead of “construct” or “fabri- <br />cate” use the word “make,” instead of <br />“initiate” or “commence” use “begin.” <br />• Short, compact paragraphs work <br />best. Each paragraph should deal with a <br />single topic. Lengthy, complex, or tech- <br />nical provisions should be presented in a <br />series of related paragraphs. This will <br />help readers understand the relationship <br />of the provisions. <br />• Watch out for commas. The place- <br />ment of one little comma can sometimes <br />make a big difference in meaning.1 <br />• Draft your ordinances in the present <br />tense. <br />• If you have a choice between writing <br />either positively or negatively, use <br />positive language. For example, instead <br />of saying “The City Manager may not <br />approve signage in the right-of-way <br />unless he or she has determined that <br />there is no public safety impact from <br />such signage,” use “The City Manager <br />may approve signage in the right-of-way <br />when he or she determines that there is <br />no public safety impact from such <br />signage.” <br />• Similarly, avoid negative words or <br />phrases. For example, don’t say “A pro- <br />ject will not be approved unless all appli- <br />cation requirements are met.” Instead, <br />say “A project will be approved only if <br />the applicant meets all requirements.” <br />• Simple illustrations can clarify <br />terms or concepts – and are found in a <br />growing number of ordinances. But first <br />check with your municipal attorney on <br />whether you can do this. If you include <br />graphics, make sure they are clear and <br />legible. <br />2. Language in an Ordinance Should <br />be Consistent <br />Don’t use different words to denote <br />the same thing just for the sake of varia- <br />tion. Using different words rather than <br />repeating the same term simply confuses <br />the reader and may provide opportuni- <br />ties for misinterpretation and litigation. <br />For example, don’t say “Each motor <br />vehicle owner must register his or her <br />car.” Instead, say “Each automobile <br />owner must register his or her auto- <br />mobile.” <br />3. Do Your Lists Right <br />Lists should be clear and use parallel <br />structure. List each item so that it makes <br />a complete thought when read with the <br />introductory text. <br />If the introductory text is a complete <br />sentence, end the introduction with a <br />colon and make each item in the list a <br />separate sentence. If the introductory <br />language for the list is an incomplete sen- <br />tence, end the introduction with a dash <br />and end each item in the list except the <br />last item with a semicolon. <br />After the semicolon in the next to the <br />last item in the list, write “and” or “or” as <br />appropriate and end the last item in the <br />list with a period. Listing in this manner <br />7 <br />can help avoid problems of ambiguity <br />caused by the words “and” and “or.” <br />When using lists it is also helpful to <br />have the introductory text say “at least <br />one of the following” or “all of the fol- <br />lowing.”2 <br />4. Be Considerate <br />Ordinances should avoid gender-spe- <br />cific terminology. For example, “drafts- <br />man” becomes “drafter,” “foreman” <br />becomes “supervisor,” and so on. In <br />addition, instead of using phrases such as <br />“the administrator or his designee,” sub- <br />stitute “the administrator or the adminis- <br />trator’s designee.” Similarly, avoid archaic <br />or potentially offensive terms. <br />5. Be Careful When Defining Terms <br />For zoning ordinances in particular, <br />the best way to avoid the time and <br />expense of a lawsuit is to make sure that <br />all important terms are defined and every <br />definition is clear and unambiguous. <br />In interpreting zoning ordinances, <br />courts will attempt to find the plain and <br />ordinary meaning of the terms. Any <br />ambiguous language will usually be <br />interpreted in favor of the landowner. <br />In Minnesota, the courts have been asked <br />to interpret undefined terms such as <br />“lawn and garden center,” “accessory,” <br />“subordinate,” “incidental,” “main,” and <br />“structure.” <br />IT’S WORTH THE WORK <br />The tips in this article can help you <br />draft a clear, legally-defensible ordi- <br />nance. It may seem like a lot of work. It <br />is. However, taking the extra time as you <br />draft the ordinance will likely save your <br />community even more time and <br />resources when you administer and <br />enforce it. ◆ <br />Carolyn Braun, AICP, is <br />Planning Director for the <br />City of Anoka, Minnesota, <br />and past President of the <br />Minnesota Chapter of the <br />American Planning Associa- <br />tion. She has written two <br />prior articles for the PCJ: <br />“What Planners Do” (Summer 2004) and “Plan- <br />ning from Different Perspectives” (Fall 1996). <br />1 I was reminded of this in a comment by planner <br />Vicky Newson on a draft of this article. As she <br />explained: “Many times the placement or omission of <br />a comma can change the interpretation of a code sec- <br />tion. I always use the example of ‘I have several dress- <br />es. They are red, green, blue, orange and yellow’ <br />versus ‘I have several dresses. They are red, green, <br />blue, orange, and yellow.’ In each case it says the same <br />thing, but how many dresses do I have? In the first <br />example, the last dress could be an orange and yellow <br />dress, but in the second example it is clear that they <br />are two separate dresses.” <br />2 Thanks to Davis, California, Community Develop- <br />ment Director Katherine Hess for this suggestion.