[Ord. No. 4190, 2-1-2021; Ord. No. 4668, 8-19-2024]
A. Preapplication Staff Meeting.
1. Purpose.
a. The preapplication staff meeting is intended to provide an opportunity for the applicant to meet with City staff to discuss submittal requirements, review procedures, and to identify any issues associated with the proposed development concept.
2. Applicability.
a. A preapplication staff meeting may be requested by an applicant for any application type and shall be required for applications as indicated in
Table 405.010,
Summary Table of Application Procedures.
b. The preapplication staff meeting requirements may be waived by the Community Development Director if the Director determines that the proposal would not have significant impacts on the surrounding properties, environment, or infrastructure.
3. Procedure.
a. The applicant shall submit a request for a preapplication meeting to the Community Development Director.
b. At least seven (7) days prior to the scheduled preapplication meeting, the applicant shall submit the following materials at a minimum:
(1) A written description of the proposed project;
(2) Conceptual drawings showing the location, layout, and primary elements of the proposal; and
(3) Proposed uses, location of uses, and densities.
4. Effect.
a. Any information or discussions held at the preapplication staff meeting shall not be binding on the City or the applicant.
b. Discussions of potential conditions to mitigate impacts do not reflect actions by the decision-making body until and unless a decision-making body takes formal action.
B. Preapplication Neighborhood Meeting.
1. Purpose.
a. A preapplication neighborhood meeting is intended to allow residents, businesses, and organizations in the area surrounding a proposed development an opportunity to learn about the project details and to provide feedback to the applicants.
2. Applicability.
a. A preapplication neighborhood meeting is required for applications as indicated in
Table 405.010,
Summary Table of Application Procedures.
b. The preapplication neighborhood meeting requirements may be waived by the Community Development Director if the Director determines that the proposal would not have significant impacts on the surrounding properties, environment, or infrastructure.
3. Notice.
a. The applicant shall be responsible for providing notice by mail to all owners of record within five hundred (500) feet of the boundaries of the property.
b. Notice shall be provided at least fifteen (15) days prior to the meeting date and shall include the meeting date, time, location, address of the proposed development and short description of the proposed project.
c. The applicant shall also provide notice to the Community Development Director and the Aldermen of the Ward in which the project is located.
4. Meeting Specifics.
a. The meeting shall be organized by the applicant.
b. City staff are not required to plan, organize, attend or participate in the meeting.
c. The applicant shall present, at a minimum, proposed land uses, a conceptual site layout of buildings, parking and vehicle access, and the preliminary design concept. Engineered plans are not required.
d. The applicant shall provide an opportunity for attendees to provide feedback and ask questions.
e. As part of the application submittal, the applicant shall submit a summary of the meeting, list of attendees, copy of the presentation and proof of notification.
f. The applicant is required to host one (1) preapplication neighborhood meeting, but may agree to conduct additional meetings before or after filing an application.