Council debates planned developments, nonconformities and design exceptions as staff begins text‑amendment cycle

A broad workshop discussion on January 28 focused on the city’s use of planned developments (PDs), repeated requests for exceptions to zoning and the ongoing rewrite of the Land Development Code. Council members, staff, developers and neighborhood speakers debated whether the PD process has become the default mechanism to secure relief from multiple code standards and what changes the forthcoming code rewrite should deliver.

Councilmember Clendenin opened the item by saying she believed PDs were now too often used as a way to obtain broad waivers and higher density in otherwise stable neighborhoods. “A PD was originally intended to be more larger scale, more transformational projects,” she said. “But instead they go through this because this is the path of least resistance.” Several council members echoed concerns about predictability for homeowners and whether PD approvals had produced massing and stormwater outcomes they did not expect.

Staff and industry representatives described the practical reasons PDs are common. Steve Michelini, speaking for builders, said many administrative routes and prior relief options had been removed over the years, leaving applicants no practical way to resolve spacing, setback and other minor conflicts except by pursuing a PD. “What used to be a safety valve has become the norm,” he said. Staff noted complexity: some waivers are hardship‑based (variance criteria); other approvals test compatibility and intent (PD criteria). The recent code structure and discretions available across multiple departments have sometimes made Euclidean zoning harder to implement without special approvals.

Staff presented a package of proposed text amendments separate from the long‑term code rewrite. Among the concepts: (a) consolidating and clarifying design exception rules and adding notice requirements; (b) codifying minimum site plan submittal standards for administrative processes; (c) streamlining appeals of certain administrative decisions to appropriate advisory boards; (d) aligning accessory dwelling and extended family residence language; and (e) clarifying tree‑protection, buffering and equipment setback standards. Staff said these are “concept” proposals that will be shaped during public workshops and formal drafting.

Council actions and directions

- West Tampa overlay: Council voted to delay proposed minor edits to the West Tampa overlay (item listed as section 27‑241) until the land development code rewrite is further along. A motion to delay was made and seconded and approved by voice vote.

- Text‑amendment follow‑up: Council asked staff for more detailed written language on two specific concept areas — the consolidated design‑exception approach and the site‑plan/submittal standards for variances and administrative reviews (staff references: concept sections 2760 and 2771). After discussion about timing, the council set a deadline for a written staff report on March 6, 2025.

Why it matters: The long discussion underlined the tradeoffs between flexibility for redevelopment and predictability for neighborhoods. The city’s land‑use rules determine where density and building massing are appropriate across neighborhoods, corridors and downtown; how those rules are written affects litigation risk, developer certainty and neighborhood character.

What’s next: Staff will hold public workshops as part of the text‑amendment cycle and incorporate input; drafts will then travel to the planning commission for recommendation and return to council for first and second reading. Council also scheduled Clarion (the code‑rewrite consultant) to brief council on March 6 so members can align the short‑term amendments with the longer rewrite.