ARTICLE 3: GENERAL PROCEDURES
Section
3.1.   PURPOSE OF ARTICLE
3.2.   GENERAL REQUIREMENTS
   3.2.1.   Pre-Application Conference
   3.2.2.   Neighborhood Meeting
   3.2.3.   Application Requirements
   3.2.4.   Public Notice
3.3.   ZONING COMPLIANCE REVIEW PROCEDURES
   3.3.1.   Purpose
   3.3.2.   Review Procedures
   3.3.3.   PDSD Approval Procedure
   3.3.4.   100' Notice Procedure
   3.3.5.   400' Notice Procedure
   3.3.6.   Zoning Administrator Approval Procedure
   3.3.7.   Historic Preservation (HPZ) Design Review Procedure
   3.3.8.   Neighborhood Preservation (NPZ) Design Review Procedure
3.4.   SPECIAL EXCEPTION
   3.4.1.   General
   3.4.2.   PDSD Special Exception Procedure
   3.4.3.   Zoning Examiner Special Exception Procedure
   3.4.4.   Mayor and Council Special Exception Procedure
   3.4.5.   Findings
   3.4.6.   Conditions of Approval
3.5.   REZONING (CHANGE OF ZONING)
   3.5.1.   General
   3.5.2.   Types of Rezoning Ordinances
   3.5.3.   Zoning Examiner Legislative Procedure
   3.5.4.   Change in Conditions of Approval and Completion of Conditions
   3.5.5.   Planned Area Development (PAD)
   3.5.6.   Planned Community Development (PCD)
3.6.    PLAN ADOPTION AND AMENDMENT PROCEDURES
   3.6.1.   Purpose
   3.6.2.   Applicability
   3.6.3.   Initiation
   3.6.4.   Pre-Application Conference Required
   3.6.5.   Public Outreach and Neighborhood Meetings
   3.6.6.   Application
   3.6.7.   Staff Review and Recommendation
   3.6.8.   Planning Commission Public Hearing Required
   3.6.9.   Planning Commission Recommendation and Reconsideration
   3.6.10.   Mayor and Council’s Public Hearing and Decision
   3.6.11.   Re-Application
3.7.    TEXT AMENDMENT PROCEDURE
   3.7.1.   Purpose
   3.7.2.   Applicability
   3.7.3.   Initiation
   3.7.4.   Development of a Text Amendment
   3.7.5.   Planning Commission Public Hearing Required
   3.7.6.   Planning Commission Recommendation and Reconsideration
   3.7.7.   Mayor and Council’s Public Hearing and Decision
3.8.   LAND DIVISION AND
3.9.   APPEALS
   3.9.1.   Design Review Board (DRB) Appeal Procedure
   3.9.2.   Mayor and Council Appeal Procedure
   3.9.3.   Takings and Exactions Appeal Procedure
3.10.   BOARD OF ADJUSTMENT APPEALS AND VARIANCES
   3.10.1.   General Board of Adjustment Procedures
   3.10.2.   Appeals
   3.10.3.   Variances
3.11.   ADMINISTRATIVE MODIFICATIONS
   3.11.1.   Design Development Option (DDO)
3.12.   MISCELLANEOUS PERMITS AND APPROVALS
   3.12.1.   Architectural Documentation Prior to Demolition of Historic
   3.12.2.   
3.1.   PURPOSE OF ARTICLE
   This article describes zoning and review procedures related to activity in the City of Tucson.
3.2.   GENERAL REQUIREMENTS
   This section establishes general requirements pertaining to pre-application conference, neighborhood meeting, public notice, public comments, application completeness, and other rules for processing applications after they are accepted for review. Individual review procedures and their specific requirements are set forth in this Article.
3.2.1.   PRE-APPLICATION CONFERENCE
   A.   Purpose
   The pre-application conference is designed to assist the applicant by providing as much information as possible regarding regulations and requirements and how they may affect the proposed ’s scope and design, prior to submission of a formal application.
   B.   Applicability
   A pre-application conference is required in accordance with the applicable procedure detailed in this Article. Table 3.2-1 sets forth the procedures for which a pre-application conference is required.
   C.   Requirements
   At the pre-application conference, the applicant shall describe to the PDSD the general goals, uses, and characteristics (e.g., size, location, , etc.) of the proposed in sufficient detail to enable the to identify potential code or plan compliance issues and discuss design issues and options. Depending upon the level of detail of the information provided for the proposed or the need to include other departments in the preliminary discussions, the PDSD may request additional pre-application conference(s).
   D.   Effect
   Review is on a conceptual basis, therefore, comments made at this conference are advisory and do not constitute approval or denial of the .
Loading...