Laserfiche WebLink
2 <br />1 hour at the end of the meeting to allow questions and comments from all attendees. These <br />questions and comments must be accurately recorded by the developer and brought to the second <br />meeting. At the second meeting, the developer will provide a draft of its application for plan <br />approval, a detailed description of the project, an accurate description of any impacts on or benefits <br />to the public, the record of oral and written public comments made at previous meeting(s), and a <br />description of the ways in which it has incorporated input received from the public into its plans for <br />the project. <br />3. To maximize community involvement, the community meetings must be held within 3 miles of the <br />development site and on a weekday between 6 pm and 8 pm or Saturday between 9 am and 5 pm. <br />4. The developer will create an accurate record of public comments made during the public meetings <br />and will make that record available to the City and any member of the public upon request. <br />5. Not less than 14 days prior to a public meeting, the developer will provide notice by direct mailing of <br />the time and place of the public meeting in English and the primary languages of the residents <br />impacted by the development project to all persons including businesses, corporations, or other <br />public or private entities owning real property or residing within 1000 feet of the development <br />project and to any person who requests such notice. The notice shall include any materials that the <br />developer will provide to the public at the meeting, including any project description. <br />6. Not less than 14 days prior to a public meeting, the developer will advertise the public meeting in at <br />least two local newspapers in English and two in the primary languages of the residents impacted by <br />the development project; city web-site; the local station, channel 3; and at local schools within the <br />impact zone,. <br />7. The developer will ensure contemporaneous language interpretation at the community meetings in <br />the primary languages of the residents impacted by the development project. The developer will <br />create and keep attendance records with the names of the persons that attended the community <br />meetings. The developer shall submit an affidavit under penalty of perjury that the required <br />community meetings were held in compliance with this section and will submit copies of the <br />advertisements, attendance records of the community meetings, and the record of the public <br />comments made at the community meetings with application for plan approval. <br />GOAL 11 <br />The City should conduct hearings and give better notice about the hearings to the public on all projects <br />that require a pre-application meeting. The developer should hold a pre-hearing meeting similar to the <br />pre-application meeting 15-21 days before the hearing. <br />EXISTING LAW/POLIGY <br />Hearing is required only for certain projects. Only 5 days notice is required for property owners within <br />300 feet of the development (SAMC 41.672). The developer is not required to hold a pre-hearing <br />meeting with the public. <br />E'I OPO sE'D POLICY FOR DEVEE.OPINIENI PROJECT HEARINGS <br />1. A public hearing shall be held for all development projects that require a pre-application meeting. <br />The city will give notice of the hearing by mail 14 days prior to the hearing to all person who <br />reside or own property within 1000 feet of the development <br />2. For development projects that must comply with the pre-application meeting requirement, the <br />developer must hold an additional public meeting that complies with the requirements of the <br />pre-application meeting requirements, 15-21 days before the hearing. At this public meeting the <br />WSA-19