statement in Article 1 that states: Any reference to day or days regarding timelines shall mean calendar days unless otherwise specified.

Transcription

1 As part of the Unified Development Code (UDC) project, numerous changes are presented in the formal draft document. While the below table does not summarize all proposed changes, the intent of the summary below is to orient the reader to significant changes for consideration. 1. General General Changed references from individual departments, divisions, or business centers to County, as applicable. Since titles and responsibilities change frequently, better to use the general term County. 2. General General Added section titles when the UDC references different sections. For clarity and ease of use. 3. General General Updated references to outdated survey datum requirements. To update outdated standards. 4. General General Struck specific references to fee amounts throughout the different sections and replaced with adopted fee resolution or fee policy. Fee amounts change frequently. They can be referenced and amended annually. 5. General General Struck specific time review requirements for all development reviews. Review timelines will be determined and maintained administratively, which can then be updated from time to time as workload demands, levels of service, customer expectations, etc. change. 6. General General Standardized terminology, outline numbering, capitalization, To ensure consistency and eliminate typos. punctuation, table formatting, etc. 7. General General Replaced any images or drawings that were unclear or poor quality. To minimize vague or unclear standards. 8. General General Struck all references to calendar and working days and provided a To ensure consistency in timeline/deadline expectations. statement in Article 1 that states: Any reference to day or days regarding timelines shall mean calendar days unless otherwise specified. 9. General General Struck all references to calendar and working days and provided a To ensure consistency in timeline/deadline expectations. statement in Article 1 that states: Any reference to day or days regarding timelines shall mean calendar days unless otherwise specified. 10. General General Struck commentary comments or clarified via code language. To clarify code requirements. 11. General General Changed all references to Zoning Atlas to Zoning Map. DRC requested change 12. None Article 1, Added meaning of text and graphics. To clarify the use of terms and graphics. 13. None Article 1, Granted authority to administer the UDC to the Administrator (designee). Since LDR and Zoning is now unified, there will now be a centralized Administrator responsible for development responsibilities, who can delegate as needed Article 2, and 12 Clarified purposes and intent. To clarify purposes and intent of consolidated regulations. 15. None Article 3, Added language for continuity for approvals, enforcement, applications To clarify expectations and applicable requirements. being reviewed, etc a Article 3, Removed district conversion table as it no longer applies. No longer applicable. 17. None Article 3, 124, 21 Expanded Vested Rights language. To clarify how the UDC recognizes vested rights. Page 1 of 5 7/6/2018

2 18. 74, Article 4, through 31 Consolidated and updated development review authorities for decision-making, particularly clarifying the Administrator of the UDC. Updated for consistency with UDC framework and delegation of authority Article 4, Replaced Development Review Committee with Development Review Coordination (team). To better reflect that this group is a technical working group that reviews plans, and not an appointed committee. Shifted duty to the Administrator who can coordinate with technical experts , Article 4, and 31 Changed the process for Myakka River Relief from Committee to Administrator Article 4, Updated summary of authority table Updated for consistency with UDC framework and delegation of authority. 22. Various Article 5, various Organized and compiled all Development Procedure Types and their To provide a centralized location for all development provisions into one Article. review procedures for ease of use and navigability. 23. Various Article 5, various Specified common component parts of all procedures and deleted Increase user-friendliness. duplicative procedure types (e.g. public hearing, notification, etc.) Article 5, 124- Clarified that the Board can continue a public hearing or remand an Clarified public hearing processes. 36(c)(6)c application back to the PC Article 5, 124- Clarified that the PC can continue a public hearing. Clarified public hearing processes. 36(c)(6)c a Article 5, Added annual cycle process for UDC amendments. Creates a formal review process for publicly and privately initiated amendments, which provides for improved workload management and policy considerations Article 5, Clarified that a rezone plan or a specific element of the plan may be Not all elements of a plans are required to be binding. binding , Article 5, Consolidated the Subdivision Plan and Site/Development Plan processes into one process. Similar review processes and creating one process is more user-friendly , Article 5, Added ability for applicants to meet with the Development Review Coordination (DRC) team during application review, rather than just meeting with the DRC during pre-application Article 5, Updated the application process for submitting Building Permit applications in relation to Final platting Article 5, Clarified that a special exception plan or a specific element of the plan may be binding. Improved communication and facilitation of the development review process. Process improvement. Not all elements of a plans are required to be binding. Page 2 of 5 7/6/2018

3 32. Road Construction Article 5, Clarified Right of Way Permit requirements for damaged or broken infrastructure. Creates enhanced mutual understanding of existing damaged or broken infrastructure. Technical Manual Article 17, 3 Clarified how technical, non-technical, and undefined terms are used in Clarifications. the code Article 17 Clarified and updated terms, as well as added new definitions. Clarifications and new terms as needed. 35. Various Article 17 Relocated land use definitions (Former 5.2) from Zoning Regulations All definitions in one location. into the definitions Article 5, (b)(2)c Extended the deadline that an application can be withdrawn from prior to public hearing notification to up until the close of the public hearing and up until a final decision is made when no public hearing is required. Requested by OCA to be consistent with applicable law (a)(4)a & b.1.ii Article 5, (c)(5)c.1.ii (a)(4)a Article 5, (c)(5)c.1.v b.1.v Article 5, (c)(5)c.1.vii (a)(4)a Article 5, (c)(5)c c. & 74- Article 5, (a)(3) 36(c)(5)b (a)(4)b Article 5, (c)(5)c.2 Struck a land development regulation that required a mailed notice to properties within 500ft of the subject property for watercourse buffer variances, a minimum of 30 days prior to the public hearing. Retained the zoning regulation that requires a 750ft and 15-day notice as the general standard. A mailing notice requirement to individual multifamily dwelling units that applies to properties seeking a watercourse buffer variance has been expanded to apply to all development procedures that require a public hearing. Also clarified that this applies to individually owned unit, rather than apartment tenants. Struck language requiring mailing notification for properties seeking relief of the Myakka River Standards. Stuck the minimum 5-day timeframe requirement that the mailing notice affidavit be submitted prior to public hearing. Struck a land development regulation that required a published notice 15 days prior to public hearing. Retained the zoning regulation that requires consistency with Florida Statutes. Struck posted notice requirements that only applied to watercourse buffer variances in the land development regulations these processes under the UDC All property owners, including condo unit owners, within 750ft of a subject property should be notified of public hearing. Since authority is being delegated to the Administrator, no public hearing is required. DRC requested this change LDR and Zoning processes under the UDC. The County can still require publication 15 days prior, but cannot be less than what the state requires which varies depending on the type of enactment LDR and Zoning processes under the UDC. Page 3 of 5 7/6/2018

4 (a)(2) & Article 5, 124- Struck language regarding public hearing requirements that was either OCA requested this change b.2. i (a) and (b) 36(c)(5) redundant or conflicting b. 3&4 Article 5, (c) Struck requirement for mandatory preapplication conference for PDD and TDR application. Also added Subdivision or Site Development Plan process. To remove a redundancy: PDD and TDR applications are subsets of the Rezoning application process, and To clarify in Article 5 that a preapplication conference is required for a Subdivision or Site Development Plan application consistent with current LDR requirements in e Article 5, (c)(3) Added new language that specifies that a new Preapplication Conference is required if an application is not submitted within a year, or if the application deviates substantially from plans submitted at the initial Preapplication Conference. Added new language establishing an annual cycle for private text amendments. Added language establishing when a Rezoning application is deemed open, closed and withdrawn. Struck Special Exception Planning Commission Findings of Fact and added reference to Board Findings of Fact a. Article 5, (c)(2) 47. None Article 5, (c)(3) b1-8 Article 5, (c)(4) (b) Article 5, (c) Struck 60-day timeframe for Administrative Adjustment decision and added that the timeframe will be established by Administrative Policy (b)(3) & Article 5, 124- Struck current provision that delegated authority to the Board to waive 74-63(a)(8) 46(c)(5) or defer the construction of sidewalks (Article 12) and retained Article 5, (b)(5) 52. None Article 5, (b)(2)c Article 5, (d)(3) 54. Article 5 Article 4, (a)(7) b Article 5, (c)(3) provision delegating that authority to the Administrator (Article 5) Struck requirement for right-of-way use permit for subdivision entry signs. Added private roads or streets to the list of uses/activities exempted from having to obtain a Right-of-Way Use Permit Struck language regarding the issuance of identification tags for signs requiring a sign permit. References to payment of fees for application processing stricken. Added language (Article 4) that states that the Board shall prescribe or amend fees under this UDC by resolution and the applicant shall by the amount(s) established by the resolution. Struck 20-day review deadline for (Zoning) Administrator to review Temporary Use Permit application To establish expiration criteria and ensure that information provided at the Preapplication Conference is accurate given any plan changes To streamline the text amendment process so impacts can be assessed and considered simultaneously To clarify the process for determining Rezoning application sufficiency Language is duplicated. Review times will be established administratively. To correct conflicting regulations. ZA requested change PW/T team requested change Electronic submittal and acceptance of plans negates the need for a tag. To have one centralized reference to fee schedule information. Review times will be established administratively. Page 4 of 5 7/6/2018

5 # Current Code b.1(i)- (vii) UDC Change Reason Article 5, (b) Struck list of substantial modifications that may be approved by (Zoning) Administrator and added them to the Binding Development Concept Plan Modification Table. To consolidate all conditions related to modification of Binding Development Concept Plans. 57. None Article 17, List of acronyms added To provide clarity and ease of use a.ii Article 17, Method of measuring fences and walls added Consistency with the rest of the UDC 59. Various Article 17, Revised names of definitions to reflect changes in other articles these definitions under the UDC Article 17, Added measurement standards of definitions Consistency with the rest of the UDC Article 17, Group categories added to definitions Consistency with the rest of the UDC 62. Various Article 17, Revised definitions to be consistent with the comprehensive plan To ensure definitions are consistent with the comprehensive plan 63. Various Article 17, Struck duplicated or conflicting definitions these processes under the UDC 64. Various Article 17, Consolidated and compiled all definitions in one location. To provide a centralized location for all definitions for ease of use and navigability Page 5 of 5 7/6/2018