Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Development Code topic
No spam. Unsubscribe anytime.
Walton County planning staff present broad LDC cleanup; legal limits of SB180 flagged
Summary
Planning staff proposed a package of Land Development Code cleanup amendments intended to codify long‑standing practices on inspections, surveys, notice and procedural clarity; staff warned several provisions likely raise SB180 legal concerns and may be deferred pending legal review.
Walton County planning staff on [date not specified] presented a wide‑ranging Land Development Code (LDC) revision at a special planning commission workshop intended mainly to codify existing practice, tighten notice and sign rules, and clarify procedures for conditional uses and development orders.
The package covered dozens of edits, from Section 1080 language that would allow “county personnel, including but not limited to department heads, development order inspectors, engineers, project managers, and code compliance officers may enter onto properties” where development approvals exist, to codifying the county’s pre‑construction meeting and a requirement for a signed, sealed boundary/topographic survey within one year for development applications, Planning staff Stephen said. He told commissioners he had flagged several provisions in the packet for "SB180 concerns" and that legal review could recommend postponing vote on provisions that may be deemed more burdensome under the law.
Why it matters: The draft aims to reduce recurring procedural problems — late continuances tied to insufficient notice, disputes over sign removal timing, and inconsistent approaches to surveys and inspections — by formally enshrining practices staff has followed. The SB180 caveat, however, means some substantive items could be delayed or trimmed after counsel reviews whether the revisions increase burdens on applicants.
Key proposals and debate: Commissioners broadly accepted a staff clarification on inspection authority, while the packet’s notice and sign changes drew more questions. Staff proposed that mailing receipts and public notice timing mirror the staff report publication (one week before a scheduled hearing) to reduce late continuances. On multifrontage sites, staff suggested requiring signs on each frontage and additional signs for frontages over 750 linear feet; planners said the rules would codify a 14‑day sign‑removal requirement that is already practiced.
Other technical changes included limits and clarification for conditional‑use review (distinguishing minor director review from major Board review), a director’s deviation process permitting very limited setback encroachments for survey or construction errors, and an exception process clarifying when site‑development and floodplain review is or is not required.
Quotes and attribution: Planning staff Stephen summarized some edits as “cleanup” but warned that the left column of the draft contained entries flagged as SB180 concerns and that legal staff may advise, “board, you shouldn’t vote on this currently.” Commission discussion focused on whether the proposed timing, signage, and survey requirements would be more burdensome in practice than staff intended.
Next steps: Commissioners and members of the public asked staff to refine ambiguous language — especially where numerical thresholds occur — and to return with targeted workshops on high‑conflict topics. Staff said it will coordinate with county legal counsel on SB180 risks before bringing the packet back for formal action.
