What staff need to know
Where AI can be used, where it cannot, when human review is required, how to ask questions, and what to do before something risky becomes normal practice.
See the rules staff need to followPolicy without training stays a document. This is where it becomes practice.
A city policy only works if staff know what it means, managers know what to reinforce, and everyone knows what to do when a tool or request falls outside the approved path. This page should make it clear that the repo is not just for drafting policy. It should help your city build the workforce guidance and training materials that make the policy usable in daily work.
What this page should help a city do
This page should help your city see that policy is not enough on its own. The real test is whether the rules can be taught, reinforced, escalated, and used by actual staff in actual departments.
Use the repo when your city is ready to turn the policy into staff guidance, manager talking points, training outlines, and practical materials that teams can follow without guessing.
What managers need to reinforce
How to supervise approved uses, catch drift, document concerns, and keep teams from normalizing unreviewed shortcuts that later create legal, operational, or trust problems.
See the review path managers supportWhat the repo should help you build
Staff guidance, manager prompts, training outlines, escalation language, and examples your city can adapt instead of writing every piece from scratch.
Open workforce working filesWhat good looks like
Staff know the boundaries, managers know how to respond, and training makes the policy easier to use instead of harder to remember.
See where workforce guidance fits in the full packageWhat residents notice later
Strong staff guidance improves public consistency. The city answers questions more clearly because the workforce is acting from one shared playbook.
Open public explanationUse the repo when your city is ready to make the rules teachable.
The repo should help your team move from policy language to usable workforce materials. That means guidance staff can read, training managers can run, escalation paths teams can follow, and examples your city can adapt quickly.
- Open the repo when your city needs the actual workforce files, not more explanation.
- Use the prompts and examples to draft the training layer faster.
- Bring the finished materials back through review before rollout.
Before you hand this to real teams, make sure these are true
Use this to test whether the city’s guidance is practical enough to hand to staff and managers.
- It explains approved uses and prohibited uses clearly.
- It shows when human review is required.
- It tells staff where to escalate uncertain requests.
- It explains documentation expectations in simple language.
- It gives managers a short training path they can actually run.
- It gives the city a repeatable way to onboard new staff later.
If you want the policy to work, do not stop at the policy.
Use the repo to build the workforce layer that makes the rules usable. If your city is trying to do that work and still needs outside help pulling the training package together, get help at the end of the process.