Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, April 1, 2015 <br />Page 6 <br />In his attendance at numerous developer open houses, Member Daire advised that they <br />250 <br />varied among developers as to their intent for a site, or if it was simply to provide <br />251 <br />information on the number of proposed lots or price points and not much information on <br />252 <br />the actual concept for the development. Member Daire asked if it was the expectation at <br />253 <br />these open houses that the developer would talk about their concept with visuals. <br />254 <br />Mr. Lloyd advised that existing requirements for open houses are space as to the type or <br />255 <br />number of materials for the developer to make available, and in what level of finality they <br />256 <br />were presented. Mr. Lloyd advised that part of this lack of guidance was intentional to <br />257 <br />remove a perception that plans had already been presented to the City in some form or <br />258 <br />fashion and was in process at the staff, Planning Commission, or City Council level and <br />259 <br />therefore perceived to already be in the process of approval. Therefore, Mr. Lloyd <br />260 <br />advised that the open house was geared toward alerting citizens that the application was <br />261 <br />not yet in process with the City, but seeking their feedback as an important part of a <br />262 <br />future application, but no other specifics were provided. Mr. Lloyd noted that the purpose <br />263 <br />of the open house was to let the neighborhood see the initial concept and provide their <br />264 <br />feedback and form their own opinions. <br />265 <br />Mr. Lloyd observed that staff was hearing more and more that there is a desire to <br />266 <br />standardize the content of that initial developer open house mailing, with staff involved in <br />267 <br />language requirements as well as arranging meeting space for consistency and in <br />268 <br />reviewing the nature of materials to be discussed. Therefore, Mr. Lloyd suggested it may <br />269 <br />be necessary to revise language consistently across City Code related to open houses <br />270 <br />and the process for approval moving forward as well. <br />271 <br />Mr. Paschke suggested that staff’s intent for the open house would be if the developer of <br />272 <br />a residential subdivision showed the proposed arrangement of lots compared to the <br />273 <br />existing parcel, public and/or private roads proposed, preliminary information related to <br />274 <br />drainage and grading, and some level of detail allowing residents to discuss and <br />275 <br />comment on, as well as any preliminary tree preservation plans, or an aerial photo of <br />276 <br />existing trees and lot lines, proving for some level of detail versus just a general <br />277 <br />discussion. Mr. Paschke opined that this would serve to meet expectations of residents <br />278 <br />for a proposed project, allowing the developer to receive good feedback to bring to their <br />279 <br />engineers and surveyors to move forward in line with City Code while address any <br />280 <br />concerns or input from residents, with staff subsequently receiving that product at the end <br />281 <br />of that initial process. <br />282 <br />Attachment B, Page 7, Lines 233 – 234 (Summary) <br />283 <br />Regarding the written summary of open houses created and presented as part of the <br />284 <br />application by the developer, even if they have the best interest of truth at heart, Chair <br />285 <br />Boguszewski noted that he who controls the delivery process controlled the message. <br />286 <br />Therefore, Chair Boguszewski suggested that developers be required to provide their <br />287 <br />contact information for citizens, providing an opportunity for their summary of the <br />288 <br />meetings outside of mandating those viewpoints. <br />289 <br />Referencing previous Commission discussions on this topic, Mr. Lloyd pointed out that <br />290 <br />language had been revised to consider once the summary is prepared, the developer <br />291 <br />was required to include that as part of their formal subdivision application materials, as <br />292 <br />well as mailing a copy of that summary to open house attendees who provided their <br />293 <br />addresses to the developer to do so. Mr. Lloyd noted proposed subdivision code <br />294 <br />language now reads that open house attendees are encouraged to submit their versions <br />295 <br />of the meeting summary. <br />296 <br />Chair Boguszewski opined that this could serve to trigger an analysis by those attending <br />297 <br />as to the developer’s accuracy of what occurred at the meeting; but there needed to be <br />298 <br />identification of where to send thoughts for those attending the open house. Chair <br />299 <br />Boguszewski noted that, if the sketch plan and substitute were separated out, lines 235 <br />300 <br />and 236 would be removed, duly noted by staff. <br />301 <br /> <br />