Laserfiche WebLink
Development Review Process - The Bookends <br />Conceptual Review <br />that our system (and yours, too) has leverage <br />points where relatively small changes can cre- <br />ate huge improvement. This leveraging is best <br />identified by the 8o/2o rule, a phenomenon <br />where 8o percent of your system's activity is <br />influenced by 20 percent of the total system. <br />In terms of volume, building permit <br />review consumes the majority of our review <br />activity since it is the back -end process for all <br />projects (nearly 5,00o cases in 2016). In terms <br />of front-end impact, the conceptual review <br />process best ensures a smooth flow with all <br />other functions that operate downstream. <br />Simply put, these are the critical bookends <br />(i.e., the 20 percent). <br />Finding the Value <br />With the two processes identified, we applied <br />our principles for improving each. To illustrate, <br />let's consider conceptual review. We start with <br />value: what is the value of this meeting? We <br />define it from our standpoint as well as the <br />client's: In both instances, value is generally <br />defined by the quality of what we produce and <br />the time in which it is delivered. <br />In terms of quality, the value of these <br />meetings comes not just from the guidance we <br />Subdivision <br />Rezoning <br />Variance <br />Conditional Use Permit <br />Special Use Permit <br />Administrative Waiver <br />Other Review Permits <br />5 <br />provide in the meeting but also, most espe- <br />cially, from the formal comments we provide <br />afterward in document form. These meetings <br />often generate a lot of information for an ap- <br />plicant. It can be hard to follow our message <br />completely in the 3o-minute window we pro- <br />vide. So our staff often tried to consolidate the <br />comments into a document that was sent after <br />the meeting —typically via email. That letter <br />then represents the essential recipe for how <br />the applicant can accomplish the project in <br />accordance with our zoning regulations. <br />So again, the letter is the highest piece <br />of value from this process. For the client and <br />for us. In the past, however, our process didn't <br />ensure that all the proper experts attended <br />the meeting. The idea of "consolidated com- <br />ments" was often a non -starter since we <br />seldom had a building official, engineer, or <br />code enforcement officer in the meeting. Even <br />when members were in attendance, we didn't <br />always ensure that our comments were con- <br />sistent, clear, and in chronological order. So <br />quality was often far less than what we knew it <br />could, and should, be. <br />And as mentioned before, the value of <br />these meetings is also built on time. If we <br />Building Permit <br />failed to send these comments to applicants <br />in a timely fashion, their experiences —and <br />their projects —suffered. Traditionally, we <br />told customers they would receive comments <br />within 14 days. This was the hope but not the <br />internal expectation. Thus the 14 days was <br />seldom met. The time tine was more like 7o <br />days on average, which is embarrassing to <br />consider. There were even instances where we <br />didn't send the comments at all! <br />Mapping the Value <br />On paper, conceptual review is a small pro- <br />cess. But when mapped through the rest of <br />the value chain, it has a tremendous effect on <br />the success of a project. If applicants do not <br />receive a document of consolidated comments <br />in a timely fashion after a conceptual meeting, <br />they often fail to follow the rest of our process <br />effectively. If the applicant does get com- <br />ments, but they are inaccurate or incomplete <br />or inscrutable, the plight is just as bad. <br />In every instance, this creates the classic <br />problem of "garbage in, garbage out." Poor <br />guidance leads to poor submittals and poor <br />outcomes. Every planner is keen to this fact, <br />and it makes more work for everyone. <br />It begs the question: How could some- <br />thing so simple as a conceptual review pro- <br />cess be so inconsistent? Was our staff lazy? <br />Irresponsible? Negligent? Like so many facets <br />of work in large organizations, the truth of the <br />ZONINGPRACTICE 5.17 <br />AMERICAN PLANNING ASSOCIATION Ipage 4 <br />