Use plain notices
Tell residents when AI is part of a city process and what role it is actually playing.
Residents and council who discover AI use before the city has a prepared explanation create credibility problems that are harder to manage than the original policy work.
Public transparency should explain city AI use without hiding behind jargon.
Residents should not need a technical background to understand where the city is using AI, why it is using it, what checks exist, and where to raise concerns. This page is about that public-facing layer.
Publish a public explanation
Describe how the city reviews tools, what oversight exists, and who owns the work.
Make questions easy
Give residents a clear way to ask what is being used, where, and how it affects them.
What good public transparency usually includes
Not every city needs a large public registry on day one. Every city does need honest and usable explanation.
- A short city explanation of what AI tools are in scope and why the city chose them.
- A plain description of review, oversight, and who keeps the material current.
- Resident-facing notices for tools that affect service delivery, communication, or access.
- An easy route for residents to ask questions, request clarification, or report concerns.
What this layer needs to do inside the city
Public transparency has to work for leadership, program owners, and outside readers at the same time. If it only sounds good on the page, it will not hold up once questions start.
Protect public confidence before confusion starts
The city does not need a long technical explanation. It needs a clear public story, a named owner, and a simple way to answer the first serious questions well.
Keep the public explanation tied to the real review path
Transparency should come out of the same workflow that sets the rules, review triggers, and ownership. If it is written separately, it will drift away from how the city actually governs use.
Make the work legible from outside the building
Researchers, journalists, civic groups, and residents should be able to see what is in scope, what oversight exists, and where the city wants questions to go without guessing at the structure behind it.
Toolkit and working files for this page
The public-facing copy should come from the same working bundle the city uses to draft notices, explanations, and the question route.
- Public explanation templates help staff write the city story in plain language without overexplaining the internals.
- Resident notice language gives a direct, usable explanation when AI affects service delivery or communication.
- Question-routing guidance shows who answers, where questions go, and how concerns are tracked.
When your team is ready to draft, the toolkit is the front door and the working files are the materials behind it.
Public transparency should end in publishable files and a clear help path.
Use the repo when your city is ready to draft the resident-facing page, notices, FAQs, and question-routing language. If the local context is politically exposed, sensitive, or hard to explain cleanly, get help before the public page turns into a guess.