Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Community Benefits topic
No spam. Unsubscribe anytime.
Flint council rejects Community Benefits ordinance after debate over developer input and resident power
Summary
On a second-reading vote March 10, the Flint City Council rejected a Community Benefits Agreement ordinance intended to give residents a formal role in negotiating developer benefits; the measure failed on a 4–3 vote after public testimony urged clarity and technical edits.
The Flint City Council voted on March 10 on the Community Benefits Agreement ordinance (agenda item 240430.1) after public testimony and technical comments from local advocates. Council members moved to adopt the ordinance on second reading, but the measure failed on a 4–3 vote.
What the ordinance would have done: the ordinance was drafted to require developers seeking certain public incentives to negotiate a proportionate community benefit with the directly affected ward and the citywide advisory council. Supporters said the proposal would return negotiating power to residents and allow communities to define benefits that matter locally, including monetary contributions, volunteer programming, scholarships, cleanups or other services.
Public reaction and technical comments: Joel Arnold, planning and advocacy manager at Communities First, said the draft had improved but urged technical clarifications to avoid capturing small projects and to clarify treatment of nonprofit project structures, recipients of HOME/CDBG funds and the size threshold for coverage; he suggested a threshold around $20 million to avoid burdening small projects. Other public speakers urged clearer language and community town halls before final adoption.
Council debate: proponents on the council said the ordinance was intended to return power to residents and to ensure tax breaks delivered proportional benefits to communities. Opponents and some council members raised concerns, echoing commenters, that the ordinance as written needed technical fixes to avoid discouraging smaller developments or causing unworkable uncertainty for lenders and smaller projects. Council members said the ordinance could be revised and reintroduced if changes were needed.
Final action: the motion for second reading and enactment was put to a roll-call vote and the ordinance failed 4–3. (Council recorded the final tally as 4 yes, 3 no.) The council discussed options to send the draft back for committee consideration and noted a revised version could return with a new ordinance number if further amendments are requested.
Why it matters: the ordinance was intended to create a formal process for neighborhoods to negotiate benefits from developers receiving public incentives, clarifying resident input on projects that may affect neighborhood resources and services.
