From the Local Government edition of September 22, 2026
Centralia unanimously adopts staff generative-AI ordinance requiring verification
City of Centralia · Small-city internal AI governance and workforce policy · Centralia, Missouri, United States
- Publisher
- KBIA
- Original publication
- September 22, 2026 KBIA public-radio report on Monday ordinance vote
- Source retrieved
- 2026-09-23
- Event date
- 2026-09-21
What happened
On Sept. 22, 2026 KBIA reported Centralia’s Board of Aldermen unanimously passed an ordinance Monday regulating city staff use of generative AI. Staff must verify accuracy of any generated content; supervisors decide how far each department may use AI; unauthorized use can bring discipline or termination; AI-generated videos, images, and audio for city business require written supervisor permission; and protocols aim to stop confidential information from being entered into AI tools. City Administrator Tara Strain said AI has helped with paperwork and Facebook posts but will never replace police or manual labor. The piece cites a Tyler Technologies survey that only about a third of public-sector leaders have a defined AI policy, and quotes academic experts on legitimacy and scale-of-error risks.
Why it matters
Same-day small-city AI acceptable-use adoption—useful control checklist beside larger-city inventories and chatbot launches.
Evidence and measured results
KBIA Sept 22: unanimous ordinance; verification mandate; supervisor discretion; discipline; generative media permission; confidential-data protocols; Strain quotes; Tyler one-third citation.
Limitations and uncertainty
Article summarizes ordinance; full legal text not attached; Tyler survey is secondary.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Staff already use generative AI for paperwork and public posts while hallucination and confidential-data risks lack clear local rules.
- Stakeholders
- Board of aldermen
- City administrator
- Department supervisors
- Police/public safety
- Communications
- Discovery questions
- Which tools are authorized per department?
- How is verification evidenced?
- What counts as confidential input?
- How are generative media approvals logged?
- Value hypothesis
- A lightweight ordinance plus supervisor discretion can reduce uncontrolled shadow AI if training and enforcement are real—without proving productivity gains.
- Potential engagement
- Policy drafting, allowlist, and supervisor training package for a small city—no automation platform sale required.
- Unsupported claims
- AI replaces police/manual labor
- Guaranteed productivity savings
- Tyler survey equals Centralia measurement
- Ordinance eliminates hallucination risk
Pre-sales engineering
Role takeaway
- Fit
- Acceptable-use controls for staff generative AI with verification and confidential-data prohibitions.
- Architecture and integration
- Supervisor-authorized tools → staff draft → mandatory human verification → optional written approval gate for AI media → publish/retain records.
- Prerequisites
- Written policy/ordinance
- Tool allowlist
- Training materials
- Incident/discipline process
- Constraints
- Small-city IT capacity
- Article is secondary to full legal text
- Department-by-department variability
- Consumer tools hard to monitor fully
- Security
- Prohibit confidential inputs to public models; require verification before external use; gate synthetic media.
- Proof of value
- Training completion
- Exception/incident log trend
- Sample of verified outputs
- Supervisor approval records for AI media
Delivery
Role takeaway
- Work
- Translate ordinance into SOPs, train all staff, and stand up supervisor approval and audit sampling.
- Dependencies
- Legal/ordinance text
- HR/discipline procedures
- IT allowlisting
- Communications norms
- Ownership
- City Administrator owns policy; supervisors own day-to-day authorization.
- Skills and adoption
- Teach staff to verify facts and never paste confidential data into public AI.
- Governance checkpoints
- Effective-date briefing
- 30-day compliance sample
- Quarterly policy refresh
- Incident review
- Acceptance criteria
- Staff acknowledge policy
- Verification expectation documented
- Confidential-data ban communicated
- AI media permission path exists
- Risks
- Uneven enforcement
- Shadow AI persists
- Over-blocking low-risk uses
- Public messaging errors if verification skipped
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?
Prioritize allowlisting and DLP-style confidential-prompt bans before broad Copilot rollouts.
Governance
Who approves, reviews and stays accountable for outcomes?
Pair ordinance text with training and sampled verification evidence—passage alone is not control maturity.
Security and privacy
What data, permissions and controls need testing?
Confidential-input bans and media-approval gates are the operational core of the reported ordinance.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Policy should not freeze helpful drafting aids if verification and non-digital service capacity (e.g., police staffing) remain explicit.
Procurement
What should contracts, pricing and exit terms secure?
Small cities may buy policy/training help before enterprise AI platforms.
Operating model
Which teams own the service once it runs?
Supervisor-scoped rules require consistent management capacity across departments.
Publication history
- 2026-09-22Local Government · Issue 174 resources
Stable resource ID: centralia-staff-ai-ordinance-20260922