§ 32-4-217. COMMUNITY INPUT MEETING.

(a)

Purpose. The purpose of the community input meeting is to provide a forum for:

(1)

Discussion; and

(2)

Resolution of community concerns and developer constraints within the context of this title and county regulations and policies.

(b)

Notice and schedule.

(1)

(i)

Within 10 working days after the concept plan conference, the Department of Permits, Approvals and Inspections shall direct the posting of notice on the property subject to the concept plan.

(ii)

The notice shall include the date, time, and location of the community input meeting.

(2)

The community input meeting shall be held no earlier than 21 days and no later than 30 days after posting.

(3)

The community input meeting shall be held:

(i)

At a site within eight miles of the vicinity of the proposed development, if the proposed development is outside the urban rural demarcation line; or

(ii)

At a site within three miles of the proposed development, if the proposed development is inside the urban rural demarcation line; or

(iii)

In Towson, if no other meeting site can be scheduled.

(4)

The meeting may be held in a school, library, house of worship, community center, or other public place of assembly.

(5)

At the time of posting notice under paragraph (1) of this subsection, the Department of Permits, Approvals and Inspections shall make the concept plan available for inspection and the concept plan and agency comments shall be transmitted to the persons identified under § 32-4-216(b) of this subtitle.

(c)

Attendance at community input meeting by county agencies.

(1)

A representative of the Department of Permits, Approvals and Inspections shall attend the community input meeting.

(2)

(i)

A participant may request to the Department of Permits, Approvals and Inspections or the Department's designee that a representative of a reviewing agency attend the community input meeting in order to respond to comments which may be raised or conditions to the concept plan which may be proposed or requested by a participant.

(ii)

The participant shall make the request to the Department of Permits, Approvals and Inspections or the Department's designee at least 10 days before the community input meeting and shall identify the possible comment or condition.

(3)

The Director of the Department of Permits, Approvals and Inspections may require that representatives of any county reviewing agency attend the meeting in order to respond to comments which may be raised or conditions which may be proposed or requested by a participant.

(d)

Conduct of the community input meeting.

(1)

A representative of the Department of Permits, Approvals and Inspections shall:

(i)

Conduct the community input meeting;

(ii)

Take minutes of the meeting to be placed in the Development Plan file; and

(iii)

Prepare a list of comments or conditions raised by any participant at the meeting and sign the list and place it in the Development Plan file.

(2)

At the community input meeting the applicant shall present the concept plan for comment and discussion by any participant.

(e)

Proposed comments and conditions.

(1)

At the community input meeting, a participant may raise any comment relevant to the concept plan or propose any condition to be imposed by the Hearing Officer on the approval of the Development Plan.

(2)

If a comment or condition is unresolved, the Director of Permits, Approvals and Inspections may require:

(i)

An additional meeting to be held; and

(ii)

Representatives of any county reviewing agency to attend the meeting in order to address the comments or conditions.

(3)

As part of the Development Plan review, the appropriate agency shall:

(i)

Address the comments or proposed or requested conditions that are not resolved through the community input meeting; and

(ii)

Submit the comments or proposed or requested conditions to the Hearing Officer according to § 32-4-226 of this subtitle.

(1988 Code, §§ 26-168, 26-202) (Bill No. 1, 1992, § 2, 3-2-1992; Bill No. 12-93, § 2, 4-5-1993; Bill No. 29-95, §§ 1, 3, 5-21-1995; Bill No. 69-95, § 10, 7-1-1995; Bill No. 89-97, § 2, 10-19-1997; Bill No. 73-00, §§ 3, 4, 9-15-2000; Bill No. 79-01, § 2, 7-1-2004; Bill No. 75-03, §§ 10, 11, 7-1-2004; Bill No. 122-10, §§ 12, 30, 1-16-2011; Bill No. 3-11, § 1, 4-14-2011)

Editor's note:
  Section 12 of Bill No. 122-10 provided that subsection (c)(2)(ii) should be amended to read, in pertinent part, "...or the Divisions's designee..." The change of the word "Department" to "Division" was inadvertent, and the editor has corrected this error so that the word "Department" is retained.