From the Local Government edition of September 23, 2026
UNC Coates’ Canons issues 14 recommendations for local-government AI use policies
UNC School of Government (Coates’ Canons) · Local-government law guidance and administrative policy · North Carolina / United States local governments
- Publisher
- Coates’ Canons (UNC School of Government)
- Original publication
- September 9, 2026 Coates’ Canons blog post by Kristi Nickodem
- Source retrieved
- 2026-09-24
What happened
On Sept. 9, 2026 UNC School of Government’s Coates’ Canons published Kristi Nickodem’s updated 14 recommendations for local-government AI use policies. The post argues many units still lack guardrails despite shadow AI: it cites a 2025 KPMG/University of Melbourne survey that 58% of employees intentionally use AI regularly and 70% of those use free public tools. Recommendations include: don’t copy-paste policies; define covered technology; require IT review for new software/subscriptions; set agentic-AI boundaries; prohibit improper confidential disclosures; require fact-checking and accountability for outcomes (noting LLM hallucinations); consider department-specific rules; remind staff of public-records duties; address transcription/notetaking/recording; state prohibited uses; calibrate transparency; involve the right people; review policies at least annually; and test whether employees can understand/apply the policy. Why-now for the 2026-09-23 edition: same-day Raleigh stop decision and Colorado Springs go-live make written fact-check, IT-approval, and prohibited-use rules immediately operational for peers.
Why it matters
Actionable local-gov policy checklist newly salient beside same-day production go-live and cautionary non-retention stories; fills the controls gap when cities buy voice AI or $3k LLMs.
Evidence and measured results
Coates’ Canons Sept. 9, 2026: 14 recommendations listed; shadow-AI rationale with 58%/70% survey cite; fact-checking/hallucinations; IT approval; confidential disclosures; agentic boundaries; annual review; employee understandability test.
Limitations and uncertainty
Guidance blog, not an empirical evaluation of any city’s outcomes; survey statistics are secondary citations from 2025; older than last edition but included with explicit why-now beside 2026-09-23 deployments.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Employees already use public AI tools while many local governments still lack usable AI policies.
- Stakeholders
- City/county attorney
- Manager/administrator
- IT
- HR
- Department heads
- Elected officials
- Discovery questions
- Which AI tools are already in shadow use?
- Who approves new AI software or subscriptions?
- What fact-checking is required before external use?
- When was the AI policy last reviewed?
- Value hypothesis
- A tailored, understandable AI use policy reduces confidential disclosures and hallucinated communications if training and IT gates are real.
- Potential engagement
- Policy gap assessment and drafting workshop mapped to the 14 recommendations—no vendor accuracy claims.
- Unsupported claims
- Policy alone stops all misuse
- Survey percentages prove local conditions
- Any specific vendor is endorsed
- One copied template fits every charter city
Pre-sales engineering
Role takeaway
- Fit
- Control framework requirements for generative and agentic tools used by local-government staff.
- Architecture and integration
- IT service catalog allowlist → approval ticket → configured tenant/logging → human fact-check before external send.
- Prerequisites
- Tool inventory
- Data classification
- Records guidance
- Training plan
- Constraints
- Guidance not empirical outcomes
- Secondary survey citations
- Must be localized to law
- Older than last edition without why-now would be weak
- Security
- Prohibit confidential inputs to public tools; govern transcription/recording; review agentic write actions.
- Proof of value
- Share of AI tools IT-approved
- Training completion
- Fact-check spot audits
- Annual policy review completed
Delivery
Role takeaway
- Work
- Localize the 14 recommendations into a short policy, train, and set an annual review calendar.
- Dependencies
- Legal
- IT
- HR
- Department champions
- Ownership
- Manager/attorney owns policy; IT owns technical gates.
- Skills and adoption
- Tabletop with employees to test whether rules are understandable before publishing.
- Governance checkpoints
- Draft legal review
- Adoption
- 90-day comprehension check
- Annual update
- Acceptance criteria
- Covered technology defined
- IT approval required for new AI software
- Fact-checking required for external outputs
- Annual review scheduled
- Risks
- Unreadable copy-paste policy
- Shadow AI continues unchecked
- Transcription creating unexpected records
- Agentic tools acting without oversight
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Policies should distinguish chatbots, agentic tools, and transcription products so technical controls match risk.
Governance
Who approves, reviews and stays accountable for outcomes?
Fact-checking, IT approval, prohibited uses, and annual review are minimum operating controls for both go-lives and stop decisions.
Security and privacy
What data, permissions and controls need testing?
Ban confidential pastes into public tools; treat transcription/recording features as records and privacy events.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Policies should be understandable to front-line staff, not only attorneys, or shadow AI will continue.
Procurement
What should contracts, pricing and exit terms secure?
Route new AI subscriptions through existing IT acquisition gates; ban silent personal accounts for work data.
Operating model
Which teams own the service once it runs?
Pair go-lives and stop decisions with written fact-check and prohibited-use rules so accountability stays with humans.
Publication history
- 2026-09-23Local Government · Issue 184 resources
Stable resource ID: unc-coates-local-ai-policy-recs-20260909