Cities that stop at the policy draft typically face staff confusion, council questions, and public trust problems within 90 days of launch.

A complete city AI policy program is a working package, not one policy document.

A city does not have a complete program if it only has a draft policy. The package also needs review and sign-off logic, staff guidance, training, public explanation, and a named owner after launch. If one of these pieces is missing, the work is still incomplete.

Updated April 18, 2026 by City AI Policy. Use this page to see the full package, open the deeper page for each part, and then move into the repo to build it.

What this page should help a city decide

Use this page to compare what your city has now against the package it actually needs. Then go straight to the deeper page for the missing piece instead of browsing the site without a next step.

These six parts describe what a complete program looks like. For the step-by-step process that builds them, see How It Works.

Rules for use

Clear statements about approved uses, prohibited uses, high-risk work, resident-facing use, vendor use, and update responsibility.

Open the rules page

Review and sign-off logic

Practical routing for legal review, procurement review, operational review, and executive or departmental approval.

See the review path

Staff guidance

Plain instructions for managers and staff using AI tools in real work.

Open staff guidance

Training materials

A short path that tells teams what they need to know before tools are used at scale.

See the training path

Public explanation

Resident-facing material that explains where the city uses AI, what checks exist, and how to ask questions.

Open public explanation

Named owner and update path

A complete program names the sponsor, the maintainer, the update trigger, and the place where new questions or exceptions go after launch.

See ownership and leadership

Once you know the missing piece, go to the repo and build it.

The repo is where your city gets the working files, templates, prompts, and examples behind this package. This page should help you aim. The repo should help you produce the actual materials.

Before the city calls the program complete, make sure these are true

Use this as a quick test when a city thinks it may be close to finished.

  • The city has a policy draft that staff and leadership can both read clearly.
  • The city has a review path for new uses and changes to existing uses.
  • The city has staff guidance that fits day-to-day work and vendor use.
  • The city has a training path for managers and staff.
  • The city has a public explanation or transparency surface.
  • The city knows who owns updates and maintenance after launch.

If the city is missing pieces, do not call the program complete yet.

Open the repo if your team is ready to build the missing parts. If your city has compared the full package and still needs outside help to get it over the line, use the contact path here.

Open the repo path

Work from the files, prompts, examples, and review materials that support the full package.

Open the repo path

Get help

If your city has compared the package and still needs help pulling the missing pieces together, get help here.

Get help