Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Land Use Site Plan topic

No spam. Unsubscribe anytime.

Planning board backs streamlined site-plan rules, asks for clearer 'security plan' language and council discretion on step-backs

Planning and Zoning Board · December 4, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The Planning and Zoning Board unanimously recommended City Council approve Ordinance 08-2025 to streamline site-plan reviews, replacing 'security system' with 'security plan,' adding finished-road grade language, and changing mandatory step-back language to allow council discretion.

The City of Cape Canaveral Planning and Zoning Board on Dec. 3 voted unanimously to recommend City Council approve Ordinance 08-2025, a package of code changes intended to streamline site-plan review and to clarify when projects must return to other review bodies.

Staff said the ordinance differentiates minor site-plan review (handled by staff through building permits for single-family and duplexes) from regular site-plan review for larger developments, aligns review windows with recent Florida legislation and standardizes concurrent consideration of stormwater and subdivision requirements. "This ordinance was brought about to kind of streamline the development process to revise, you know, procedures, just because they were a little bit counterintuitive at times," the Planner said.

Why it matters: Under the proposed changes, certain height increases that previously were considered separately by the Community Appearance Board would be reviewed concurrently with site plans by City Council, reducing sequential hearings developers and staff called inefficient.

Board members focused on three specific edits during discussion. First, members questioned the insertion of the word "testing" and the phrase "security system" into review criteria, warning those terms could be interpreted to impose costly, undefined requirements on applicants. The Staff member explained the intent: "Testing was added because there may be ... some situations where the particular development project requires, as a condition of approval, some level of ongoing testing and monitoring in order to alleviate any adverse effects," and staff agreed the draft should use "security plan" rather than "security system" to avoid implying review of electrical or plumbing systems.

Second, a member proposed adding the phrase "finished grades for adjoining roads" after references to "10 inches of adjoining property" to address repeated flooding and concerns about emergency vehicle access along North Atlantic Avenue. The Planner said that insertion "is logical" and noted it aligns with existing parcel and neighbor information requested in site-plan submissions.

Third, the board debated mandatory step-back requirements for buildings exceeding 45 feet. One member cautioned that the current "shall provide a step back" wording could unnecessarily constrain design and reduce developable units, citing several downtown properties without step backs. The board discussed phrasing that would allow the City Council to require height mitigation measures when warranted as part of site-plan approval. The Planner summarized the compromise: height mitigation measures "may be required" by City Council in conjunction with site-plan approval, preserving discretion.

Outcome: After those edits were identified, a motion to recommend the ordinance to City Council with the technical changes (change "system" to "plan," add finished grades language, and change the step-back requirement to discretionary language tied to council approval) was made and carried on a unanimous roll-call vote. Staff said the ordinance will go to City Council for two readings, beginning Dec. 16.

What’s next: The board’s recommendation and staff revisions will appear at the City Council meeting on Dec. 16 for first reading and subsequent consideration.