From the Local Government edition of October 7, 2026
Detroit's citywide AI policy allows only Microsoft CoPilot Chat, bans AI in employee evaluations, and requires disclosure and fact-checking
City of Detroit (Department of Innovation and Technology) · Municipal AI acceptable-use policy · Detroit, Michigan, United States
- Publisher
- BridgeDetroit
- Original publication
- October 5, 2026 (BridgeDetroit); summary republished by Detroit Newsroom October 7, 2026
- Source retrieved
- 2026-10-08
What happened
Detroit's AI policy, in effect since this summer for all departments, vendors, interns, consultants and volunteers, permits only Microsoft CoPilot Chat as a text LLM. It bars AI-made images of real events, AI in evaluations of people or programs such as employee reviews, and AI handling sensitive or identifying data without human review; staff must disclose AI use and fact-check outputs. Violations are handled through the employee handbook up to discharge, and new tools go through DoIT review. The CIO's main stated worry is AI literacy.
Why it matters
A large U.S. city chose a single-approved-model policy tied to its surveillance-oversight ordinance, a model other cities with similar ordinances can compare against.
Evidence and measured results
Explainer based on the policy and a CIO interview; no compliance or usage data.
Limitations and uncertainty
Published Oct. 5, before the last run, but not in the archive and amplified Oct. 7; the policy text itself was not opened separately; no audit of compliance.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- The city must keep AI use within one approved tool while vendors add AI features to existing systems.
- Stakeholders
- CIO, Department of Innovation and Technology
- Law Department
- Human Resources
- Procurement
- City Council Legislative Policy Division
- Discovery questions
- Which existing vendor upgrades include AI features?
- How long does DoIT review of a new AI tool take?
- How is AI use disclosed in documents?
- What AI literacy training exists for staff?
- Value hypothesis
- Clearer intake and training could reduce policy violations; no baseline is reported.
- Potential engagement
- An inventory of AI features in current vendor systems mapped to the policy's prohibitions.
- Unsupported claims
- That other LLMs will be approved soon
- Measured productivity gains
- That compliance is currently high or low
Pre-sales engineering
Role takeaway
- Fit
- Fits Microsoft-tenant deployments and products whose AI features can be configured or disabled.
- Architecture and integration
- CoPilot Chat inside the city tenant; DoIT intake for other tools; disclosure labelling and human review for personal data.
- Prerequisites
- Microsoft tenant controls
- Data classification
- DoIT review workflow
- Vendor documentation of AI features
- Constraints
- Single approved LLM
- Surveillance ordinance compliance
- No AI in personnel evaluations
- No AI handling personal data without human review
- Security
- Keep data unsafe for public disclosure out of AI prompts and require human review where personal data is involved.
- Proof of value
- Configure one vendor upgrade with AI features disabled or scoped, and verify
- Test disclosure labelling in a document workflow
- Check logs for use of unapproved AI services
Delivery
Role takeaway
- Work
- Operate the policy: tool intake, vendor AI inventory, disclosure practice and staff literacy.
- Dependencies
- DoIT review capacity
- Vendor cooperation
- HR for enforcement
- Training resources
- Ownership
- Department of Innovation and Technology (CIO).
- Skills and adoption
- Literacy training on fact-checking, disclosure and data limits for employees, vendors and volunteers.
- Governance checkpoints
- New-tool review decision
- Annual policy review
- Council public comment
- Acceptance criteria
- All vendor systems with AI features inventoried
- Median review time for AI requests published
- Share of staff completing AI training reported
- Risks
- Shadow AI use outside CoPilot Chat
- Unreviewed AI features in vendor upgrades
- Literacy gaps among staff and residents
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?
A single approved LLM inside the Microsoft tenant means blocking or discouraging other generative AI services and routing new-tool requests through DoIT.
Governance
Who approves, reviews and stays accountable for outcomes?
Links AI to the Community Input Over Government Surveillance ordinance and employee discipline; drafting involved Law, HR, Procurement, police and fire, and the Council's Legislative Policy Division.
Security and privacy
What data, permissions and controls need testing?
Prohibits sharing data unsafe for public disclosure and AI processing of personal data without human review; 'Detroit's data is Detroit's data.'
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Bans AI in employee reviews; the CIO flags uneven AI literacy among staff and residents.
Procurement
What should contracts, pricing and exit terms secure?
Vendors and consultants are bound by the policy, so contract terms must reflect the disclosure and data limits.
Operating model
Which teams own the service once it runs?
DoIT staff, including the CIO, review each request for new AI tools or AI-enabled upgrades.
Publication history
- 2026-10-07Local Government · Issue 326 resources
Stable resource ID: detroit-citywide-ai-policy-copilot-chat-only-20261005