Residents look up the same things every week: bin days, rates, dog registration, consents. More and more, the first answer comes from Google, ChatGPT or Claude, not from the council. I check what they're told, where each answer comes from and who needs to fix it, and give independent advice on AI projects.

Where councils feel it

What I check for the questions residents ask most, and what you get back.

A resident asks Google

“When's my rubbish collected over Christmas?”

What I check
Whether Google's AI Overview, ChatGPT, Claude and your own site search give this year's dates, and which page each answer comes from.
What you get
The old page behind any wrong answer, and who updates or redirects it.

A resident asks ChatGPT

“How much is dog registration this year?”

What I check
Whether the answer quotes this year's fee, last year's, or a neighbouring council's.
What you get
The pages AI tools draw on, and what to change so the current fee is the one they find.

A resident searches your site

“building consent for a deck”

What I check
Whether site search and Google find the right step across the main site, the consents portal and the district plan.
What you get
A fix list naming who acts: web team, platform owner, comms, customer services or your CMS vendor.

A first answer review

A findability audit built around residents' questions. I ask the questions people actually ask, in their words, check the first answer from Google, AI assistants and your own site search, and trace each wrong answer back to its source. That's rarely just the main website: consultation sites, the district plan, library and pool sites, map listings and outside sites all feed the answers. The review covers:

  • What residents are told about rates, rubbish, consents, dog registration and other high-volume services, checked against your own information.
  • Where the answers come from, including sources you didn't expect.
  • Search visibility and broken inbound links, including old addresses left over from restructures.
  • AI crawler access, so blocking is a decision, not an accident.
  • Map listings for offices, libraries, pools and facilities: hours, holiday hours, address and phone, and who manages each one.

You get a written report and a fix list that names who acts: your web team, a platform owner, comms, customer services, IT or your CMS vendor. More on the findability audit.

From your team it takes a scoping call at the start and one hour to go through the findings. I work from the outside, with no access to your systems.

What a review finds

Three examples from checks of council information, with the names and figures left out:

  • A payment page quoted a late fee that isn't in this year's fee schedule. AI tools repeated it.
  • One page said two things about a discount deadline: pay on the day and get the discount, and pay on the day and get the late fee.
  • After water services moved to a new organisation, three pages each said something different about who bills residents for water.

Findings go only to your council. I never name organisations in anything I publish. Some checks start with a scan of public pages: about the scanner.

Advice on AI projects in local government

  • Staff use of AI. Which tasks are worth it, a safe-use policy people can follow, and what privacy and LGOIMA mean for what goes into a prompt.
  • A chatbot or AI search for residents. Whether it's worth doing, what it should answer, and testing it with real questions before launch.
  • Choosing a vendor. Requirements you can take to market, and a comparison on your own content rather than the vendor's demo.

I advise, specify and test; your team or your vendor builds. More on AI project consulting.

What I don't do

I don't build, host, redesign or maintain websites, so I work alongside your website partner, not in place of them. Where a fix is theirs, it goes on their list.

Try it yourself

Ask Google, ChatGPT and Claude five questions residents often ask you, such as bin days, dog registration or when rates are due, and compare each answer with your own information. If some are wrong or come from sources you didn't expect, a first answer review works out why and what to fix first.

Further reading

Common questions

Isn't this something our website vendor does?

Your vendor builds and looks after the site, which I don't do. The review looks at the answers residents get, which also come from other council platforms and outside sites. The fix list includes work for your vendor where it's theirs to do.

Can you work across several councils in our region?

Yes. A regional review asks the same questions for each council and shows where the answers get mixed up between them.

How does procurement work?

A short call, then a written quote with the scope and a fixed price, agreed before any work starts. It's sized to fit within the single-quote limit in most councils' procurement policies.

Can you look at our staff use of Copilot, ChatGPT or Claude?

Yes. That's often where AI work in local government starts: which tasks are worth it, a safe-use policy people can follow, and how to check what the tools produce.

Talk about your council

Send a few lines through the contact form or call (027) 450 5720.

Discuss a review