Citizen Portal
Sign In

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

Get email alerts on the Property Taxes topic

No spam. Unsubscribe anytime.

Lynchburg council agrees to seek ordinance change after dispute over ‘perpetual’ real‑estate tax language

5334393 · July 9, 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

After a contentious public exchange about ordinance language that some council members called a “magic” tax increase, the council directed the city attorney to prepare a new ordinance to remove perpetual tax‑increase language and return with it at the August 26 meeting for formal consideration.

Lynchburg City Council members spent more than two hours on procedural arguments and policy claims over language in an ordinance that some members said would allow an automatic, recurring real‑estate tax increase.

The debate centered on language in Ordinance 025‑055 that, as written, said the real‑estate tax rate would continue “each and every fiscal year thereafter beginning July 1 and ending June 30 of each such year unless otherwise changed by council.” Council members including Chris Feraldi called that a “magic tax increase” and urged the council to remove it so the council must vote a rate each year.

The dispute touched on state law. Council Member Tammer (identified in the meeting as Council Member Timmer) read aloud Code of Virginia section 58.1‑3321, which describes how a locality should reduce its levy when reassessments would otherwise increase total levies by 1% or more and how the governing body may, after a public hearing, increase the rate above the reduced rate if necessary. Timmer said, “the way that this is written violates the state code,” and supported striking the perpetual‑increase language.

The city attorney advised council members that the technically correct way to change text in an already‑adopted ordinance is to bring a new ordinance showing the proposed amendment rather than to attempt to re‑write a signed ordinance on the dais. The attorney told the council, “If a majority wants to go this road…do a new ordinance instead of revisiting a signed ordinance because the public should be able to have the right to see what we’re presenting at a meeting.”

Council members debated procedure and motives. Feraldi, speaking repeatedly during the discussion, said the text risked removing public accountability: “If we’re gonna go forward with this ordinance the way it is…you’re voting to take away your power to have any influence over it going in the future,” he said. Other members argued the language had long existed in city code and that a new ordinance should be drafted carefully to preserve continuity if necessary.

After extended discussion, Council Member Feraldi withdrew an immediate motion to reconsider the adopted ordinance and instead moved that the council return in August with a properly drafted ordinance to strike the perpetual tax language. Council members agreed to direct the city attorney to prepare a proposed ordinance for consideration at the council’s next regular meeting on August 26, 2025. The city attorney reiterated that the proposed amendment should be presented as a stand‑alone ordinance so that the public can see the exact text being changed.

The council’s debate included a separate procedural vote earlier in the meeting to take up a related calendar item; later in the session the council adopted its calendar item for general business unanimously and confirmed the next scheduled meeting for August 26 at 4 p.m.

The council did not adopt the substance of a new ordinance at this meeting; it instructed staff to prepare and present a draft ordinance for a future vote. Formal change to the ordinance will require an ordinance ordinance vote after the text is published and the public has had an opportunity to review it.