RS9 SystemsRS9 Systems Pty Ltd, Sydney

Council AI policy: what it should actually cover

A council AI policy that is any use does four jobs. Everything else is decoration.

The four jobs

1. It says what gets logged

If AI touches something a resident could complain about (a reply, a decision, a priority, a letter), someone should be able to open a record later and see what went in, what came out, which tool, which version and who was there. Not "we keep logs somewhere." Where, for how long, and who can pull them when the Ombudsman or a councillor asks. Work out whether it's a public record while you're at it. Most of it will be.

2. It names the human who signs off

"A human is in the loop" means nothing. A named role is. For each use: who reads the output before it goes anywhere, what they're checking for, and what they can do when it's wrong. If the answer is "the same person who clicked generate, in a hurry," that's not sign-off.

3. It says what counts as an incident, and how fast you hear about it

Wrong address in a letter. Resident data pasted into a public tool. A chatbot that told someone something it shouldn't. Write down what counts, who gets told, and the time limit. A policy with no clock on incidents is a suggestion.

4. It's clear about data

What can never go into a public tool. What can go into the council's own approved tools, and under what conditions. What the vendor is allowed to keep, train on, or send offshore, and what happens to it when the contract ends. Staff should be able to find this answer in under a minute, not in a 40 page framework.

Two things people forget

  • Contractors and suppliers. Your staff aren't the only ones using AI on your work. The policy should say what a supplier has to tell you.
  • Software that already has AI in it. A lot of councils will find AI in tools they bought years ago. The policy should cover what you buy, not just what staff type into.

How RS9 can help

Two ways, and you can take the first without ever talking to us.

Free: the checklist. One page. Twelve questions you can answer in a meeting, covering the four jobs above, suppliers and embedded AI. Download it, run it against your draft policy or the one you already have, and keep it. No email gate.

Download the checklist (PDF)

Paid: a policy review. If you'd like a second pair of eyes, we'll read your draft or adopted AI policy against that checklist and the frameworks you're already pointing to (the NSW AI Assessment Framework, the Australian Voluntary AI Safety Standard and the like), and write back what's missing, what's vague and what's hard to apply on a Monday morning. A written review. We'll tell you if we think you don't need it. Contact us for pricing.

If you do hire us, we won't use the review to sell you software. If your answer is "buy RS9," we've done it wrong.

Dale
RS9