FRANKSTON Council will undertake a feasibility study to look into how it could move forward its net zero emissions target.

At their August meeting, Frankston councillors agreed to investigate ways to move their net zero target from the 2024/2025 financial year to 2023/2024.

Cr Claire Harvey proposed the move. She told the meeting that “councillors are being called upon by residents to lead by example in our action on climate change at the level of local government.”

“While it’s my personal opinion that we are probably a couple of decades late, and acknowledging the wisdom of going hard and going early to borrow from a now widely understood COVID catchphrase, we do have a choice now to step up as ambitious leaders in our local community and provide a clear message to the state and federal governments.”

All councillors approved the move with the exception of Crs Steven and Liam Hughes. Cr Liam Hughes said “to say this notice of motion will have an impact on the fight to stop climate change is a complete over-exaggeration.”

“I love the environment. I know what you’re thinking – Liam is saying ‘we should quit, we should quit this target and just give up’ – and you’re right! We should quit, but we should quit believing we can stop climate change. We can not,” he said. “What we should focus on is the future. We need to be proactive, let’s spend the money we would on the notice of motion on services that keep Frankston going when severe weather events happen.”

Cr Steven Hughes raised concerns about the cost of the move to the budget. “Council is nowhere near achieving zero emissions, this will mean we will have to use carbon offsets as an option. This means that the resident’s rates will be increased to foot this bill. If the costs exceed the rate cap then services will potentially have to be cut to support carbon offsets.”

First published in the Frankston Times – 7 September 2021

Share.
Leave A Reply

Currently you have JavaScript disabled. In order to post comments, please make sure JavaScript and Cookies are enabled, and reload the page. Click here for instructions on how to enable JavaScript in your browser.

Exit mobile version