Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Technology Policy topic
No spam. Unsubscribe anytime.
Sterling Heights rolls out Gov AI across city staff and plans public‑facing chatbot with data protections
Summary
City administration described its AI task force decision to adopt Gov AI as a productivity tool (160 active users, 6,000+ prompts since launch) and previewed a public chatbot tied to sterlingheights.gov; officials emphasized an Acceptable Use Policy and Data Shield protections to reduce PII exposure and model hallucinations.
Sterling Heights officials described the city’s approach to artificial intelligence, emphasizing an internal productivity rollout and data safeguards. Assistant City Manager Dale Jawadzikowski said the administration’s AI task force selected Gov AI to support internal work and that an acceptable‑use policy (finalized November 2025) requires human review of AI outputs.
Jawadzikowski said Gov AI went live Feb. 9 and has reached roughly 160 active users with more than 6,000 prompts submitted for drafting memos, summarizing meetings and other routine tasks. "AI is not intended to replace staff judgment, but rather support it," he said, adding that staff are using the tool for drafting, research and communication.
Officials outlined plans to develop a public‑facing chatbot that will be grounded to city sources such as sterlingheights.gov and (if added) the city charter and code. He said the chatbot will query a curated set of city documents rather than the open web, reducing the risk of hallucinations. Administration also highlighted Gov AI’s Data Shield feature, which scans queries for personally identifiable information and can mask or warn users before submission.
Councilmembers asked for training and clarity on how the chatbot is grounded; Jawadzikowski said the back end can be configured to use only city documents so the assistant should not hallucinate from general web content. The city will provide additional briefings and training to council and staff.
Next steps: staff will continue user training, deploy the internal chat features more broadly, and develop the public‑facing chatbot if budget authorization for the proposed tool is finalized.
