Lifetime Citizen Portal Access — AI Briefings, Alerts & Unlimited Follows
Ordinance Committee sends fiscal‑impact proposal to public hearing after debate over scope and form
Loading...
Summary
The Norwalk Ordinance Committee voted unanimously to send a draft ordinance requiring fiscal‑impact statements for many ordinances to public hearing, after members debated whether the requirement should be automatic, how to handle departmental review when the finance department is the subject, and the CFO’s role in standardizing the process.
The Norwalk Ordinance Committee voted June 21 to send a draft fiscal‑impact ordinance to public hearing after an extended discussion about scope and implementation.
Brian Candela, the city attorney, told the committee that most department heads had no substantive objections but that the chief financial officer had endorsed the concept because it would help five‑year planning. Candela said the draft would require written assessments in many cases but allow departments to state when an ordinance has no fiscal impact.
Council members pressed staff on section 3(e), which says the council cannot vote on an ordinance unless certain requirements are satisfied, and on a separate clause that says errors or inaccuracies do not invalidate an ordinance. Council member (speaker 7) framed the concern as a tension between preventing substantive omissions and treating fiscal estimates as reasonable projections rather than guarantees. Candela and the chair responded that the intent is to distinguish substantive omissions from non‑substantive errors and that fiscal impact statements are best‑effort estimates.
Committee members also discussed whether the ordinance should prescribe a standard form. Some said the CFO should help define standard questions departments answer; others warned the ordinance should not hard‑code a form that the city would have to change administratively. Candela said administrative flexibility would allow the CFO to shape the implementation over time.
After further procedural discussion, the committee (on a motion moved by Council member Buckalow, per the chair) voted unanimously to send the draft fiscal‑impact ordinance to public hearing. The chair and staff said the public hearing will be scheduled so the council and committee can receive public comment and further refine implementation details.
The committee recorded no public comments on the matter during the meeting. The ordinance’s final language, required thresholds, and any standardized questions will be developed with input from the CFO before a final council vote.
