Atlanta's vacant-property security proposal is on Oct. 13 agenda

A proposal to require security measures on certain unimproved vacant properties is listed on Atlanta's Oct. 13 Community Development/Human Services Committee agenda. The measure would give owners 60 days after registration to secure covered property—but it would not make fencing the only option.⁠[1]

Councilmember Byron D. Amos's ordinance, 26-O-1441, would require either a barrier or a qualifying alternative designed to restrict unauthorized access. A physical barrier would have to be continuous and at least six feet high. Alternatives could include monitored surveillance, regular security patrols or dense landscaping installed for that purpose.⁠[1]

Those alternatives would not be an unrestricted menu. Both barriers and other security measures would have to meet specifications issued by the police chief, published on the Atlanta Police Department's website and delivered to the municipal clerk. The proposal also preserves zoning restrictions on walls and fences: where zoning prohibits a compliant barrier, an owner would have to use an alternative.⁠[1]

The added requirement targets unimproved vacant property subject to the city's vacant-property registration provisions. That qualification matters; this proposal alone does not establish which individual parcels would be covered. Its penalty provision specifies a $500 fine per noncompliant property, not an expressly stated daily fine.⁠[1]

The legislation remains held. Its history records a Sept. 29 committee hold and an Oct. 5 City Council return as held. The Oct. 13 agenda carries it among held papers, rather than presenting an adopted requirement. Although the draft says it would take effect immediately upon adoption, the scheduled checkpoint is not a promise of passage or a final vote.⁠[1]

The committee meeting is scheduled for 1:30 p.m. Oct. 13 in the Larry M. Dingle Committee Room at Atlanta City Hall. For property owners, the distinction is practical: the draft describes what compliance could require if adopted, not a new security deadline already in force.⁠[1]