Citizen Portal
Sign In

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

Get email alerts on the Tree Protection topic

No spam. Unsubscribe anytime.

Olivette planning commission reviews tree‑protection draft, clarifies review procedures

5763606 · July 24, 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

At a work session in Olivette, commissioners and city staff reviewed a draft tree‑protection ordinance, clarified the commission’s role in land‑use approvals, and explained staff review timelines; no formal actions were taken.

At a work session in Olivette, commissioners and city staff reviewed a draft tree‑protection ordinance, clarified the commission’s role in land‑use approvals, and explained staff review timelines; no formal actions were taken.

The meeting opened with public comment in support of stronger protections for the city’s urban canopy. "One of the great aspects of living in Olivette is the trees that we have," said Martha Turner, a resident of 706 Ellington Lane, who told commissioners that recent teardown construction nearby removed mature trees and altered neighborhood shade and character.

Commissioners and staff said the topics matter because tree loss, design review and site‑plan practice affect neighborhood character, stormwater and future development timelines. "You are stewards of the comprehensive plan," Carlos Trejo, the city’s planning director, told the commission, summarizing the commission’s long‑range role in translating the plan into review practice.

City Attorney Stephanie Carr gave legal guidance intended to reduce later litigation risk by distinguishing two kinds of action the commission takes. "When you are acting legislatively, you have a broad discretion," Carr said; that includes recommending text amendments such as a new tree ordinance or rezoning. By contrast, she explained, when the commission acts administratively — applying existing code to a specific development or site plan — the body must show how a petition does or does not meet the ordinance standards, because courts review administrative decisions against the written code.

Carr illustrated the legal difference with a recent out‑of‑state example in which officials denied a subdivision plat that complied with ordinance text, a decision that invited litigation and damages for delay; she used that to urge commissioners to articulate specific reasons when denying an administratively reviewable application.

Staff then outlined the project review workflow and minimum submission requirements. Planning and zoning administrator Jack Carswell and planner Jack (staff) described a two‑step internal timeline: a 15‑day completeness review after a petition is filed and a 30‑day window for applicants to submit corrected materials. When revisions arrive, staff will place the petition on the next meeting agenda within 30 days of receiving those revisions.

Jack summarized the typical completeness checklist items petitioners must provide: site and existing conditions plans, proposed improvement plans, setback information, scaled cross sections, a concept stormwater management plan, landscape and tree protection plans, and architectural elevations. Staff use an internal calculation sheet for lot coverage, setbacks and other numeric checks and flag missing items in the staff report that accompanies every petition.

Commission members asked how to build a defensible administrative record. Carr and staff emphasized practical steps: commissioners should state the reasons for approval or denial on the record, reference code standards where relevant, and rely on staff analysis included in the packet. Carr recommended limiting back‑and‑forth engagement with members of the public during comment periods; she cautioned commissioners that extensive, informal exchanges can create evidence of bias in later litigation.

The group also reviewed procedural issues frequently raised by residents and applicants: how guidelines differ from code, when a variance or special land‑use permit is appropriate, how precedent does (and does not) constrain future decisions, notice requirements, and the distinct legal roles of homeowners’ association covenants vs. municipal code (staff and the city attorney said property owners must comply with both but that the city enforces municipal code while HOAs enforce their covenants).

Staff reported the tree‑ordinance draft posted for commissioners is a June 26 version and said additional work‑session time will be scheduled; commissioners and staff agreed to continue the tree discussion at a focused work session (staff indicated August 7 as the next work session date to address trees). No ordinance text was adopted at the meeting.

Separately, staff gave a short development update: review work is moving for the Olive Crossing lot (retail tenants discussed by staff included preliminary mentions of Paris Baguette and a Brass Tap), and the Irvington Place apartment project is proceeding toward a planned 2026 occupancy date; staff said 34 townhouses have active reviews for a Dealman area site. Those project notes were informational only and not acted on by the commission.

What's next: staff will post an updated tree draft and proposed changes to minimum submission requirements for petitioners, and the commission will continue the tree ordinance discussion at a subsequent work session. The commission made no formal motions or votes on the ordinance or code changes at this meeting.