AI in Public Services: Where It Helps Citizens and Where It Shouldn't
There are two ways for a city to get AI wrong. The first is to ban it out of fear and keep making residents wait six weeks for a permit a system could handle in a day. The second is to deploy it carelessly and quietly automate bad decisions at a scale no human bureaucracy could ever match. Both are failures. The job is to find the line between them — and that line is clearer than most of the debate suggests.
The simplest rule: AI is excellent at the work that's high-volume, low-stakes, and repetitive, and dangerous at the work that's consequential, contested, or irreversible for a specific person. Government has plenty of both. Sort the work correctly and AI is one of the best things to happen to public service in a generation. Sort it wrong and it's a liability with a logo.
Where AI clearly helps
- Answering routine questions. "What documents do I need for a permit? When is bulk pickup? How do I appeal a parking ticket?" Residents ask the same questions millions of times. An AI assistant that answers instantly, 24/7, in multiple languages, is a massive quality-of-life win and frees staff for work that needs a human.
- Routing and triage. A pothole report, a code complaint, a service request — AI can read it, categorize it, and send it to the right department instantly, instead of letting it sit in a general inbox for a week.
- Processing paperwork. Extracting information from forms, checking applications for completeness, flagging what's missing before a human ever looks. This is where the six-week permit becomes a three-day permit.
- Translation and access. Making every public document and service available in the languages residents actually speak, instantly. AI makes genuine multilingual government affordable for the first time.
- Finding patterns in operations. Where do service requests cluster? Which intersections generate the most complaints? Which processes have the longest delays? AI surfaces the patterns; humans decide what to do about them.
Notice what these have in common: they speed up access and surface information, but a human still makes any decision that affects a specific person's rights, money, or case. That's the safe zone — AI as the fast clerk and the tireless analyst, never the judge.
Where AI should not be making the call
- Decisions about individuals' rights or benefits. Who gets approved, denied, investigated, or penalized. The moment AI decides a specific person's outcome, a wrong answer is a wrong answer at scale, and the person on the receiving end has no one to reason with.
- Anything where the training data is biased. If historical data reflects historical unfairness, an AI trained on it will automate that unfairness and dress it up as objective math. In public services that's not a bug — it's a civil-rights problem.
- High-stakes, irreversible actions. Enforcement, removals, anything that's hard to undo. The cost of a confident mistake is too high to remove the human.
- Anything the public can't inspect. Government decisions have to be explainable and appealable. A black-box model that can't show its reasoning has no business making public decisions, however accurate it looks on average.
The guardrails that make it safe
The difference between helpful and harmful isn't the technology — it's the guardrails around it. Four are non-negotiable:
- A human owns every consequential decision. AI prepares, recommends, and accelerates. A named human decides anything that affects a person's rights, money, or case, and is accountable for it.
- Everything is explainable and appealable. If a resident is affected, they must be able to learn why and contest it with a person. "The system decided" is never an acceptable answer in public service.
- It's tested for bias before and after launch. Not once — continuously. Check whether outcomes differ across groups in ways that aren't justified, and fix them.
- It's transparent that it exists. Residents should know when they're interacting with AI and have a clear path to a human. Trust dies the moment people feel tricked.
Why this matters more for government than business
A business that automates a bad decision loses a customer. A government that automates a bad decision can deny someone housing, benefits, or due process — and they can't take their business elsewhere. There's only one city hall. That asymmetry is exactly why government should be more aggressive about AI in the safe zone (residents deserve fast, accessible service) and more conservative about it in the consequential zone (the cost of error falls on people with no alternative).
The cities that get this right won't be the ones that moved fastest or slowest. They'll be the ones that sorted the work honestly — automated the clerk-work without hesitation, kept humans firmly on the judgment, and were transparent about both. That's not a technical achievement. It's a governance one, and it's available to any city willing to think clearly about where the line is.
Modernizing how your city serves residents?
I help public-sector organizations deploy AI where it genuinely helps — routing, access, paperwork, analytics — with the guardrails that keep consequential decisions human. Let's map what's safe to automate first.
See the Packages →