Citizen Portal
Sign In

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

Get email alerts on the Ordinance Landscaping topic

No spam. Unsubscribe anytime.

Committee continues ordinance on Virginia-friendly landscaping after residents raise equity and implementation questions

Land Use, Housing and Transportation Standing Committee, Richmond City Council · May 19, 2026
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 Land Use, Housing and Transportation standing committee continued Ordinance 2026-113, which would create a Virginia-friendly landscaping exemption to the city’s tall-grass code and rely on third‑party certification, after residents and council members asked staff to clarify setbacks, an 80% native-species threshold, and costs for certification and signage.

The Land Use, Housing and Transportation standing committee continued consideration of Ordinance 2026-113 on a 3–0 vote after weeks of public concerns about enforcement, equity and cost. The proposal would add definitions to the city code to allow properties certified as "Virginia-friendly landscapes" to be exempt from tall-grass citations, using an existing National Wildlife Federation (NWF) third‑party certification and a city registry.

Supporters of native landscaping testified at the committee meeting but asked for clearer rules and lower barriers. "I heartily embrace the move to encourage native plants within the city, but I am concerned with four specific items," said Robin Allman, a 5th District resident, citing the ordinance’s requirements to remove detached limbs and a five‑foot setback from property lines. Libra Olson, a commercial real estate agent, said the NWF certification and signage can be expensive and urged incentives for commercial properties.

Office of Sustainability staff described the ordinance as an "off‑ramp" for residents who are currently cited under the city’s tall‑grass and weeds ordinance. "We wanted to give an off‑ramp that brings benefits to our ecosystem and provides pollinator benefits," Tara Worden of the Office of Sustainability said, explaining the proposal would let property owners apply for NWF certification and then register on a city portal so code inspectors can see which properties are certified.

Daniel Klein, a sustainability coordinator who helped draft the ordinance, said the 80% native‑species target and five‑foot setback were taken from existing city sustainable‑design standards and are negotiable. "Those are fairly negotiable," Klein said; he added that staff could consider 60%–70% thresholds and that setbacks could be refined.

Kevin J. Vonk, director of Planning, Development & Review, told the committee that using the third‑party registry would reduce the training burden on code inspectors and prevent unnecessary citations: "When we go out and somebody calls in tall grass, we can look in our database and say, 'Nope, it's not tall grass — it's a certified pollinator garden.'" Vonk said enforcement is currently a civil penalty issued without a prior warning.

Committee members asked staff to provide data on where tall‑grass citations occur and to work on equity and training issues before the ordinance returns. One councilor noted the need for more time for edits and engagement; another proposed continuity with other commissions but ultimately moved to continue the ordinance for one month to allow staff follow‑up. The committee voted to continue the ordinance to the June 16, 2026 meeting.

The continuation will give staff time to supply citation maps, refine setback and threshold language, and outline training and cost‑assistance options. The committee also asked for a list of quick‑build and pilot programs and for additional outreach to neighborhood groups to reduce barriers for renters and lower‑income homeowners.

If the ordinance returns to committee with edits, staff said they will provide a draft implementation plan, training timeline for code enforcement, and proposed language on which third‑party standards and signage would be acceptable.