Amending Chapter 21 South Bend Municipal Code Planned Unit Development Districts

Home Browse Search

(1) Permitted Uses. (A) Primary uses in the PUD District shall be any use or range of uses specified in the PUD District Ordinance establishing such District. (B) Accessory uses, home occupations or temporary uses, unless otherwise specified in the PUD District, shall be permitted in a manner customarily associated with the primary use specified in the PUD District Ordinance. (2) Development Standards. (A) The PUD District shall specify development standards applicable to each permitted use in the PUD District and, at a minimum, shall adopt or include a variation of each development standard that is applicable to each such use in the district in which each such use is first permitted. (B) In any case in which an applicable development standard has not been specified in the petition for zone map change to the PUD District, the development standard shall be that which is specified in the district in which the use is first permitted. (c) PROCEDURE FOR APPROVAL OF A PLANNED UNIT DEVELOPMENT. (1) General. (A) The complete review and approval process for a PUD consists of three (3) components: Submittal of a Concept Plan per §21 -05 (c) (2) Concept Plan; ii. Submittal of a Petition for zone map change per §21 -05 (c) (3) Petition for Zone Map Change to PUD District; and, iii. Submittal for Secondary Approval per §21 -05 (c) (7) Secondary Approval. (B) A petitioner may elect to proceed with Petition for Zone Map Change to PUD District and Secondary Approval separately, or may elect to combine them for joint approval as set forth in § 154.227 (c) (5) (B), below. (C) If filed separately, the procedure for filing for approval of a zone map change shall be the same as that required for any other petition for zone map change before the Area Plan Commission, except as otherwise provided for in this chapter. (2) Concept Plan. (A) The filing of a Concept Plan is required. The review of the Concept Plan by the Staff will create an understanding between the Staff and the developer which may help to alleviate future misunderstandings and extensive revisions.