If you’ve ever read a Council document and thought, that doesn’t quite say what it’s pretending to say, you’re not imagining things.
This is what my experience working with my local council has taught me, first as a civics reporter and now as a citizen journalist. I have written this post to help people feel confident engaging, asking questions and standing up for their community.
Having been in the firing line myself, there are a few patterns you start to recognise.
First, process is not the same as truth. When councils say a matter has been reviewed or investigated, what that usually means is that procedures have been checked. It does not mean all relevant voices were heard, all facts were tested, or the full context was examined. A process can be followed perfectly and still leave the real questions untouched.
Second, reassurance is not the same as accountability. Communities are often told nothing is wrong, it’s only procedural, or there will be consultation later. Those statements may be technically accurate, but they don’t explain what decisions have already been made, what limits are already set, or how much influence the community will actually have. Reassurance can close a conversation without resolving it.
Third, councils work hard to control the narrative. Key decisions are wrapped in calming language, framed as minor steps, or buried in long reports and attachments. The important details sit in technical documents, footnotes, or papers released late, when attention has already moved on. By the time the implications are clear, momentum is well underway. Once you see this pattern, you start reading past the headlines and paying close attention to the words being used.
Why this matters to me
I didn’t learn how Council processes work by accident. I learned by living through one.
In my case, a court case was underway involving a development where the community stood to receive close to one million dollars in contributions under a Section 7.11 agreement that the developer had already entered into. While that case was still before the court, Council withdrew the 7.11 and shifted to a Section 7.12 contributions framework.
Because of that timing, the judge could only assess the development under the 7.12 system. The result was that the community lost around $970,000 in developer contributions.
When Council later reviewed the matter, what they examined was whether they were permitted to change from 7.11 to 7.12. What was not examined was when the change was made, how it intersected with an active court case, or the financial impact that timing had on the community.
That experience taught me a lasting lesson. Processes can be followed, reviews can be completed, and yet the outcome can still fall well short of what the community reasonably expected.
It’s why I pay close attention to how decisions are framed, when changes are made, and what questions are – and aren’t – being asked. I want other community groups to understand these dynamics early, so they can advocate with their eyes open and not mistake procedural compliance for genuine accountability.
Finally, this is why community advocacy matters. Formal processes happen behind closed doors. Advocacy keeps issues visible. It creates space for questions, brings in expertise, and helps people engage at the point when it still matters. When communities understand how these systems operate, they are far better equipped to stand up for themselves and for the places they care about.
Good governance depends on more than process. It relies on clarity, honesty and a community that feels confident enough to ask questions and expect real answers.
Once you’ve seen how the language works, you can’t unsee it. And that awareness makes all the difference.
#Kiama #LocalGovernment #CommunityVoice #PlanningTransparency #CivicEngagement #PublicInterest #GoodGovernance #CitizenJournalism #KiamaCommunity #Accountability
One thought on “When Council reassurance isn’t the same as explanation”
Comments are closed.