Whitepaper

Governing AI for Better City Operations

A Municipal Framework for Accountability, Innovation, and Public Trust.

Key Definitions

The following terms are used throughout this document with the meanings set out below.

TermDefinition
Artificial Intelligence (AI)Machine-based systems that can, for given objectives, make predictions, recommendations, decisions, or generate content. Aligned with the OECD AI Principles (2024) and NIST AI RMF (2023).
Automated Decision System (ADS)Any algorithmic or AI-based system used to make or substantially inform a decision about an individual with limited or no meaningful human review prior to effect.
Generative AIAI systems capable of producing novel text, images, code, audio, or other content in response to prompts. Introduces distinct risks around factual accuracy, data leakage, and intellectual property.
Shadow AIAI tools adopted and used by department staff outside of formal IT governance, procurement, or legal review processes — the most unmanaged risk category in most municipal portfolios.
Algorithmic Impact Assessment (AIA)Structured pre-deployment evaluation of an AI system’s potential effects — covering accuracy, disparate impact, privacy, explainability, and accountability.
Model DriftDegradation of an AI model’s performance over time as real-world conditions diverge from training data. Core post-deployment monitoring obligation for all high-risk systems.
Responsible-Party GapThe structural condition in which the entity that bears legal and political accountability for an AI system’s outcomes (the deploying city) does not control the system’s design, training, update cadence, or explainability features. Governance frameworks are specifically designed to manage this gap.
Deployer AccountabilityThe obligations borne by an institution that activates and operates AI systems procured from commercial vendors — covering procurement due diligence, pre-deployment review, human oversight, ongoing monitoring, and public transparency — regardless of whether the institution designed or built the system.

Why AI Governance Is an Executive Management Issue

Artificial intelligence is no longer solely a technology issue. For large municipal governments, AI is now an enterprise management challenge that directly affects operational performance, fiscal stewardship, procurement accountability, public trust, and executive leadership credibility.

The City’s Role in the AI Ecosystem

Understanding why AI governance is an executive management issue begins with understanding what kind of institution a city actually is in the AI landscape. A large city occupies at least seven distinct roles in the AI ecosystem simultaneously: it is a buyer of vendor AI systems; a deployer of those systems in service of residents; a steward of sensitive personal data those systems consume; a service provider with equity obligations; a regulated entity subject to civil-rights law; an employer whose hiring and scheduling may be AI-assisted; and a public-trust institution accountable in ways private companies are not.

Each role creates distinct governance obligations. No single existing city function spans all seven. This distinction matters more than it may initially appear. Unlike a private organization using AI to improve its own operations, a municipal government deploys AI with binding service obligations, democratic accountability, and civil-rights exposure that private entities do not face at the same scale. The city does not design the systems it uses — but it owns the consequences of deploying them. Governance is how the city manages that responsibility.

How the Gap Emerges

In many cities, AI adoption is already occurring across departments without centralized executive visibility. Individual business units may independently procure or activate AI-enabled tools through existing software platforms, vendor upgrades, or commercial subscriptions — without formal enterprise review.

The Visibility Gap

Executive leadership can become responsible for institutional and political consequences without having a complete inventory of where AI is currently being used. The absence of governance does not eliminate executive accountability. It concentrates accountability after failures occur.

This creates four immediate executive risks that go well beyond the technology department:

  1. Fragmented Operational Decision-Making Departments may adopt overlapping or inconsistent AI systems with different standards for security, privacy, data retention, procurement terms, auditability, and resident protections. Without enterprise governance, cities risk duplicated spending, inconsistent vendor standards, and unmanaged operational complexity.
  2. Political and Reputational Exposure

When AI failures occur, accountability rarely remains isolated within departments. Issues involving wrongful enforcement actions, discriminatory outcomes, surveillance concerns, cybersecurity incidents, or procurement failures quickly escalate to mayoral and city manager leadership — regardless of where they originated.

  1. Fiscal and Procurement Risk AI procurement decisions increasingly involve opaque vendor systems, unclear data rights, uncertain performance guarantees, evolving compliance obligations, and long-term vendor lock-in risks. Strong governance improves procurement discipline and vendor accountability while reducing the likelihood of costly failed deployments.
  2. Public Trust and Institutional Legitimacy Cities operate on public trust. Residents expect that technologies affecting access to services, public safety, housing, employment, benefits, and privacy will be governed responsibly and transparently. A visible AI governance framework demonstrates that the city is modernizing responsibly rather than deploying powerful technologies without oversight.

Executive Implications of Unmanaged AI

Without formal governance, cities face increasing exposure to: litigation and civil-rights claims; procurement waste and failed deployments; cybersecurity incidents involving sensitive data; inconsistent departmental AI practices; public backlash and media scrutiny; loss of resident trust; regulatory remediation costs; and executive accountability after deployment failures — often simultaneously.

Executive Summary

Artificial intelligence is already transforming municipal operations. AI-enabled systems now support functions ranging from resident service delivery and permitting to budgeting, public safety, infrastructure management, and workforce operations. In many large cities, AI adoption is accelerating faster than the governance structures needed to oversee it. This creates a critical leadership challenge for mayors and city managers. The issue is no longer whether cities will use AI. The issue is whether cities will govern AI proactively — before operational failures, legal exposure, cybersecurity incidents, or public trust breakdowns force reactive intervention. Central to that challenge is a structural reality every city deploying AI must confront: the city does not build the systems it uses. It procures them from commercial vendors, activates them in service of residents, and bears full legal and political accountability for their behavior — including for design decisions it did not make and cannot fully audit. Well-designed governance is how the city manages that accountability gap, not just as a compliance exercise, but as a core discipline of responsible public administration. This white paper proposes the establishment of a formal AI Governance Board for large municipal government. The Board is designed to enable responsible innovation, improve operational coordination, reduce enterprise risk, strengthen procurement accountability, support regulatory compliance, and protect residents and public trust. Importantly, the governance model is intentionally risk-tiered: low-risk operational AI tools can proceed rapidly through streamlined review, while higherrisk systems affecting resident rights, public safety, or civil liberties receive proportionate oversight. Research covering 170 local governments worldwide found fewer than 16% had published AI governance policies as of May 2023.[2] State and federal expectations are tightening: at least 16 states have enacted laws specifically governing government-agency AI use[3] and all 50 states introduced AI legislation in 2025.[4] Federal agencies including the FTC,[7] EEOC,[8] HUD,[9] and DOJ have made clear that existing civil-rights and consumer-protection laws apply when automated systems shape decisions about people.

The Objective

The objective is not to slow modernization. The objective is to create the institutional confidence necessary to modernize responsibly at scale — enabling cities to pursue highvalue AI use cases confidently while demonstrating accountability to residents, employees, elected officials, and external partners.

Summary of Recommendations

  • Formally establish an AI Governance Board by resolution or ordinance with a defined charter.
  • Appoint cross-functional Board membership spanning IT, Legal, HR, Civil Rights, Public Safety, Finance, and resident representation — with clearly defined decision-making, review, and advisory roles.
  • Adopt a tiered AI risk classification system to calibrate oversight proportionally, preserving operational agility for low-risk tools.
  • Require pre-deployment Algorithmic Impact Assessments for all Tier 1 and Tier 2 AI systems, using a deployer-focused Deployment Accountability Assessment framework.
  • Establish an AI Procurement Standard addressing the responsible-party gap: audit rights, performance benchmarks, model versioning notifications, data portability, vendor succession provisions, and indemnification.
  • Establish ongoing audit, monitoring, and incident response obligations.
  • Track and align city policy with evolving state AI legislation and federal agency guidance.
  • Develop a public transparency framework to maintain resident trust.

The AI Landscape in Large Municipal Government

Large cities are among the most sophisticated — and most consequential — deployers of artificial intelligence in the public sector. The scale, diversity, and public impact of municipal AI use demand governance commensurate with that responsibility.

1.1 How AI Has Entered City Operations

AI adoption in municipal government has occurred largely through three pathways: deliberate procurement of AI-native platforms; incremental introduction of AI features within legacy software systems; and organic adoption by department staff using commercial AI tools. The third pathway — sometimes called “shadow AI” — is frequently invisible to IT and legal leadership and represents the most unmanaged risk.[2] Across a typical large city, AI-powered systems now touch virtually every major operational domain:

City FunctionAI Applications Present
Public Safety & Law EnforcementPredictive policing models, facial recognition, gunshot detection, license plate readers, risk assessment tools used in arrest or sentencing contexts.
Permitting & Land UseAutomated permit review, zoning compliance scanning, computer vision for inspection documentation.
Resident Services & 311AI chatbots, intelligent call routing, automated case classification and triage.
Finance & ProcurementFraud detection, vendor risk scoring, invoice processing automation, budget forecasting.
Public HealthDisease surveillance modeling, resource allocation algorithms, social services eligibility determination.
Infrastructure & UtilitiesPredictive maintenance for water and transit systems, traffic signal optimization, smart grid management.
Human ResourcesResume screening, employee performance analytics, workforce scheduling optimization.
CommunicationsAutomated content generation, sentiment analysis of resident feedback, social media monitoring.

1.2 AI Adoption Without Executive Visibility

In many municipalities, executive leadership is already responsible for AI-related operational and legal exposure without having comprehensive visibility into where AI is being used. Departments may activate AI functionality through software updates, vendor add-on services, commercial generative AI tools, workflow automation platforms, and embedded analytics systems — without formal enterprise review. This creates an environment in which AI deployment can expand organically across city operations while governance mechanisms remain fragmented or absent. The resulting gap is not merely technological. It is managerial, operational, legal, and political.

1.3 The Pace of Change Is Accelerating

The municipal AI landscape of 2024 is qualitatively different from that of 2022. The widespread availability of large language models through commercially accessible APIs means that any department with a software subscription can now activate or deploy AI-powered workflows — without writing a line of code. The barrier to AI deployment has collapsed; the barrier to responsible AI deployment has not. The critical implication for governance is this: the risk is not that staff are building sophisticated AI systems. The risk is that non-technical staff are consenting — on behalf of the city — to third-party data terms, model outputs, and liability exposure without any institutional authorization or review. That is an administrative and procurement risk, not a technology risk, and it requires an administrative solution.

Benchmark Finding

Research covering 170 local governments worldwide identified hundreds of AI deployments but found that fewer than 16% had published AI governance policies as of May 2023.[2][18] Leading U.S. cities — including Seattle,[13] New York City,[14] Boston,[15] and San José[16] — have begun publishing governance plans, demonstrating that formal municipal AI governance is both feasible and increasingly expected.

1.4 What Is at Stake

  • Resident harm: Algorithmic errors in benefits determination, child welfare risk scoring, or law enforcement decision support can directly harm the most vulnerable residents — often without any notice or meaningful right of appeal.
  • Civil liability: In Detroit, a wrongful facial-recognition arrest led to a policy settlement and compensation on the order of hundreds of thousands of dollars.[10] In Pasco County, Florida, a predictive-policing program resulted in a six-figure civil settlement.[11]
  • Security incidents: AI systems that integrate with sensitive city data create new attack surfaces. Emerging research documents AI-enabled attacks that are faster, more targeted, and more difficult to attribute.[12]
  • Erosion of public trust: When AI failures become public — as they increasingly do — the damage to institutional credibility compounds. Trust, once lost, is costly to rebuild.
  • Regulatory exposure: At least 16 states have enacted laws specifically governing government-agency AI use,[3] and all 50 states introduced AI legislation in 2025.[4]

The Governance Gap: Why Most Cities Are Unprepared

The absence of AI governance in large municipalities is not a consequence of indifference — it is a structural gap that has emerged from the speed of AI adoption, fragmented departmental decision-making, and the absence of clear ownership over AI as a cross-cutting enterprise concern.

The Responsible-Party Gap

The vendor controls training data, model design, update cadence, and explainability features. The city controls none of that. But in a wrongful-arrest lawsuit, a disparate-impact complaint, or a civil rights investigation, the city is the defendant — not the vendor. Governance is how the city manages the space between operational dependency and legal accountability. This structural condition — the responsible-party gap — is the core problem a municipal AI governance framework is designed to address.

2.1 How the Gap Forms

In most large cities, AI adoption has been department-driven rather than enterprise-directed. A public safety department adopts a predictive analytics platform. A permitting office integrates an AI document review tool. An HR team subscribes to a resume screening service. Each decision is made within the department’s procurement authority, evaluated primarily against operational criteria — does it work? — rather than enterprise risk criteria.

2.2 The Limitations of Existing Structures

Existing FunctionGap in AI Governance Coverage
IT / CIO OfficeWell-positioned on infrastructure and security, but typically lacks authority over procurement decisions made in line departments, and may lack civil rights or legal expertise needed for high-risk AI evaluation.
City Attorney’s OfficeEssential for legal review but is reactive by nature; engages when issues are identified, not proactively during deployment planning.
Procurement / FinanceCan enforce contract requirements, but lacks technical and ethical evaluation capacity for AI-specific risks.
HR / Civil Rights OfficeCritical for employment-related AI and bias review, but not engaged in public-facing or infrastructure AI deployments.
Department DirectorsAccountable for outcomes within their domain but have no mechanism or mandate to evaluate cross-departmental AI risk.

No single existing function spans the full risk surface of enterprise AI deployment. The solution is not to retrofit AI governance onto an existing function; it is to create a purpose-built, cross-functional body with an appropriate mandate.

2.3 The Fiscal Cost of Fragmented AI Adoption

Fragmented AI adoption creates operational inefficiencies that extend beyond governance risk. Without centralized standards and inventory management, municipalities may experience:

  • Duplicated software purchases and overlapping AI capabilities across departments
  • Inconsistent vendor terms, data governance practices, and cybersecurity protections
  • Incompatible procurement language and uneven audit rights
  • Duplicated training costs and inconsistent acceptable-use standards

A governance framework enables cities to treat AI as an enterprise capability rather than a collection of isolated departmental tools — improving purchasing leverage, operational coordination, and long-term scalability.

2.4 The Cost of Waiting

  • AI harms often accumulate silently. Biased algorithms may make thousands of erroneous decisions before the pattern becomes visible. By the time harm is recognized, the remediation cost is compounded.
  • Governance established under pressure is governance established poorly. The urgency created by a crisis produces frameworks that are reactive, incomplete, and organizationally resisted.
  • The regulatory environment is moving rapidly. Federal agency guidance from the FTC,[7] EEOC,[8] HUD,[9] and DOJ each carries compliance implications. State-level legislative activity is underway in every region.[3][4]

Regulatory Context (May 2026)

The current U.S. regulatory landscape for municipal AI is a mosaic: federal agency enforcement; state algorithmic accountability legislation now active in at least 16 states;[3] civil-rights law as interpreted through agency guidance; and the NIST AI RMF.[1][6] The EU AI Act — which entered into force in August 2024 — is a useful comparative model for risk-tiering, though it is not a direct U.S. compliance obligation.[5]

Governance as an Innovation Accelerator

A common concern among municipal leaders is that governance structures may slow innovation. Well-designed AI governance has the opposite effect. Clear standards reduce uncertainty. Departments can move more confidently when expectations are defined before deployment rather than enforced after an incident.

3.1 How Governance Enables Faster, More Confident Deployment

For a municipal deployer, the speed benefits of governance are concrete and specific. Procurement expectations are defined before a vendor relationship begins. Approval pathways are predictable and documented in advance. Legal review criteria are established so departments do not rediscover them mid-contract. AI-specific contract templates are ready for execution rather than drafted under time pressure. And security and acceptable-use standards are clear before deployment rather than applied retroactively after an incident. The delays that governance is sometimes assumed to create are, in practice, the delays that its absence produces — the ad-hoc negotiations, legal interruptions, emergency reviews, and post-deployment restrictions that occur when governance questions arise after a system is already running.

The Governance Paradox

Cities that deploy AI without oversight frequently encounter public controversy, emergency policy restrictions, legal intervention, council resistance, and stalled modernization initiatives — all of which create far greater delays than a structured pre-deployment review. Governance protects the momentum of innovation.

3.2 What Governance Prevents

The reactive shutdowns that follow unmanaged AI failures are far more disruptive — and expensive — than the structured reviews governance requires. Consider the pattern that plays out without governance:

Illustrative Scenario: What Happens Without Governance

A department independently activates an AI-enabled resident screening feature through an existing software vendor — without enterprise security review, legal evaluation, civil-rights assessment, or executive visibility. Months later, residents report inconsistent outcomes. Advocacy groups raise concerns about bias. Local media requests records. City leadership discovers there is no formal AI inventory. Vendor contracts lack audit rights. Departments disagree on who owns accountability. The issue escalates into legal review, emergency policy development, council scrutiny, public criticism, and operational disruption — all of which could have been prevented by a structured pre-deployment review that takes weeks, not months.

3.3 Governance as a Leadership Posture

Governance should be understood not as an innovation constraint, but as the operational framework that makes sustainable innovation possible. Cities that establish formal governance structures are better positioned to:

  • Pursue high-value AI use cases with institutional confidence and documented accountability
  • Negotiate stronger vendor contracts from a position of informed standards rather than reactive necessity
  • Demonstrate to grantmakers, regulators, council members, and residents that modernization is being managed responsibly
  • Build the institutional trust that allows future AI deployments to move forward without public controversy.

The real strategic choice is not between innovation and caution. It is between deploying AI with discipline or deploying it in a way that creates avoidable cost, controversy, and remediation later.

Risk Domain Analysis

The AI governance challenge in large municipal government spans four interconnected risk domains. Because cities are deployers of vendor systems rather than builders, the procurement domain is foundational: it is the point at which the city can most directly shape its exposure across all other risk areas. Effective governance must address each domain with specificity while maintaining a coherent enterprise-level framework.

4.1 Procurement & Vendor Due Diligence

The Structural Accountability Problem

Most AI systems deployed by large cities are procured from commercial vendors. This creates the defining structural tension in municipal AI governance: the vendor controls the system’s design, training data, update cadence, and explainability features. The city controls none of that. Yet in a wrongful-arrest lawsuit, a disparate-impact complaint, or a civil rights investigation, the city is the defendant — not the vendor. This is not a theoretical risk. It is the operating condition of every AI procurement the city executes. Standard government contracts were written to govern software availability and response time — not AI accuracy, fairness, or drift. Closing that gap through procurement governance is therefore one of the highest-leverage actions a city can take, and it is why procurement is addressed first among the four risk domains.

The Risk Landscape

  • Black-box vendor systems: Many commercial AI products do not provide explainability or auditability features, making it impossible to evaluate how decisions are made or identify sources of error.
  • Inadequate performance accountability: Systems can degrade significantly over time without triggering contractual remedies, and performance benchmarks are often absent from standard contracts entirely.
  • Vendor lock-in and data portability: Without data portability requirements, the city may be unable to switch vendors without losing access to historically important operational data.
  • Subprocessor and model provenance opacity: Vendors may use third-party models or data sources without disclosure, creating legal and reputational exposure for the city as the deploying entity.
  • Silent model updates: Vendors can update their underlying model without notifying the city. The Deployment Accountability Assessment conducted before deployment may be evaluating a materially different system six months later. Contracts must include explicit notification requirements when underlying models are materially changed, and must define a re-review trigger.
  • Vendor succession and continuity: The vendor you contracted with may be acquired, pivot, or sunset its product before your contract term ends. Without specific continuity provisions, the city may lose audit access, data portability, and contractual protections through a transaction it had no role in. Contracts must address what happens to city data, audit rights, and service obligations when the counterparty changes.

Governance Response

The Governance Board should maintain a Municipal AI Procurement Standard establishing minimum contractual requirements: model explainability and audit access; performance benchmarks with remediation obligations; data portability and exit provisions; subprocessor and training data disclosure; explicit model versioning notification and re-review triggers for material changes; vendor succession and continuity protections; indemnification for AI-related claims; and post-deployment monitoring obligations.

4.2 Security & Data Privacy

The Risk Landscape

AI systems in municipal government invariably interact with sensitive data: PII, PHI, financial records, law enforcement data, and infrastructure operational data. The integration of AI with these data stores creates new exposure vectors that traditional IT security frameworks were not designed to address.

  • Model inversion and data extraction attacks: Adversarial techniques can extract training data from deployed models, potentially exposing sensitive resident data.
  • Third-party AI vendor risk: Vendor security posture, data retention practices, and subprocessor relationships introduce supply chain risk requiring specific contractual and technical controls.
  • Large language model data leakage: Staff use of commercial generative AI tools creates risk that sensitive city data is transmitted to external systems outside normal review channels.
  • AI-enabled cyber threats: Emerging research documents AI-enabled attacks that are faster, more targeted, and more difficult to attribute.[12]

Governance Response

Effective governance requires: a mandatory AI system data inventory; vendor security assessment requirements specific to AI workloads; acceptable use policies for generative AI and commercial LLM tools; contractual data handling standards; and integration with the city’s existing cybersecurity incident response framework.

4.3 Ethics & Civil Rights

The Risk Landscape

AI systems trained on historical data inherit historical patterns — including patterns of discrimination and bias. In a municipal context, where AI makes or supports decisions directly affecting residents’ access to services, their interactions with law enforcement, and their economic opportunities, algorithmic bias is a civil rights issue, not merely a technical one.

  • Disparate impact in automated decision-making: Systems used in benefits eligibility, child welfare, or criminal justice contexts may systematically disadvantage protected classes. EEOC guidance establishes AI’s intersection with employment discrimination law;[8] HUD guidance addresses algorithmic tools in housing.[9]
  • Facial recognition and biometric systems: Documented accuracy disparities across demographic groups create direct civil rights exposure. The Robert Williams case in Detroit resulted in policy settlement and compensation on the order of hundreds of thousands of dollars.[10]
  • Predictive policing and risk scoring: The Pasco County predictive-policing program resulted in a six-figure civil settlement.[11]
  • Resident-facing automated decisions: AI systems that deny or delay benefits, permits, or services without human review or meaningful appeal mechanisms may violate due process requirements.

Civil Rights Standard

No AI system may be deployed in a context affecting resident rights or access to services unless it has been evaluated against disparate impact standards and the evaluation results disclosed to the Governance Board. This is not a higher standard than the law already requires[8][9] — it is a mechanism for meeting that standard proactively and documentably.

4.4 Policy & Regulatory Compliance

  • Federal agency guidance: The FTC,[7] EEOC,[8] HUD,[9] and DOJ each maintain active AI enforcement and guidance portfolios. OMB M-25-21 (April 2025) provides the current framework for responsible AI use in the executive branch.[6]
  • State legislation: At least 16 states have enacted laws specifically addressing government-agency AI use,[3] and all 50 states introduced legislation in 2025.[4]
  • Civil rights law: The ADA, Fair Housing Act, Title VI of the Civil Rights Act, and the Equal Credit Opportunity Act each apply to algorithmic decision-making through agency guidance and case law.[8][9]
  • International comparison: The EU AI Act — in force August 2024 — establishes a well-developed risk-tiering model U.S. cities can study as a comparative framework, though it is not a U.S. compliance obligation.[5]

The Fiscal Case for AI Governance

Municipal AI governance is not solely a compliance initiative. It is a fiscal management strategy. Cities that govern AI effectively reduce the likelihood of the costly outcomes that plague unmanaged deployments — while improving their ability to realize the operational benefits that justify AI investment in the first place.

5.1 The Cost of Ungoverned Deployment

The absence of governance increases the likelihood of: failed procurements and duplicated technology spending; litigation exposure from civil-rights violations; emergency remediation costs when systems fail publicly; cybersecurity response expenses; vendor lock-in that forecloses competitive renewal; and operational disruption that undermines the value of the original investment.

Cost Perspective

For context: the Robert Williams facial-recognition case in Detroit resulted in compensation and legal costs measured in the hundreds of thousands of dollars for a single incident.[10] The Pasco County predictive-policing case produced a six-figure settlement before trial.[11] Both arose in the absence of structured pre-deployment review. A governance function that prevents a single comparable incident would recover its annual operating cost many times over.

5.2 The Return on Governance Investment

Governance ActivityFiscal Benefit
Centralized AI inventoryEliminates duplicated software purchases and overlapping vendor relationships across departments.
Standardized procurement requirementsImproves contract terms, audit rights, and performance guarantees — reducing the likelihood of costly failed deployments.
Pre-deployment reviewIdentifies high-risk systems before investment is made, avoiding expensive remediation or system abandonment post-launch.
Vendor accountability standardsCreates leverage for renegotiation; reduces lock-in risk at contract renewal; includes protections against vendor succession events.
Post-deployment monitoringDetects model drift and performance degradation early, before errors accumulate into liability.
Transparency reportingReduces public controversy and council resistance, enabling faster future deployments.

For city managers and finance leadership, AI governance should therefore be viewed as a form of enterprise risk management and operational oversight — an investment in institutional resilience that pays returns across the entire AI portfolio.

Workforce and Organizational Implications

AI adoption affects municipal workforce operations as much as technology operations. A governance framework that addresses only procurement and legal risk — without addressing the people and organizational dimensions — is incomplete.

6.1 The Workforce Governance Gap

Without clear governance and communication, employees may use AI tools inconsistently, expose sensitive information to external systems, misunderstand acceptable use boundaries, distrust modernization initiatives, or fear workforce displacement. These outcomes undermine both the operational value of AI investments and the institutional trust that governance is designed to build.

6.2 Key Workforce Governance Priorities

PriorityWhat It Covers
Acceptable-use policies for generative AIClear rules on which data can be used with external AI tools; what requires internal review; and what is prohibited.
Employee training and AI literacyBaseline education for all staff on how AI tools work, where they are being used in city operations, and what responsible use looks like.
Human oversight requirementsExplicit standards for which decisions require human review before action — preventing over-reliance on automated outputs.
Labor transparency and communicationProactive communication with employees and labor partners about where AI is being used, what it is used for, and what safeguards are in place.
Workforce augmentation standardsClear policy that AI is deployed to support employee effectiveness and productivity — not to eliminate accountability or remove necessary human judgment from public service delivery.
Role-specific governance guidanceTailored guidance for departments with elevated AI exposure: law enforcement, social services, HR, and resident-facing operations.

The city should clearly communicate that AI deployment is intended to support operational effectiveness and employee productivity — not to reduce the human judgment and care that characterize effective public service. This framing reduces employee resistance and builds the organizational trust that sustained AI adoption requires.

The Proposed AI Governance Board

The AI Governance Board is envisioned as a standing, cross-functional body with a formal charter, clear decision-making authority, and defined accountability to the Mayor and City Manager. It is not an advisory committee — it is a governing body designed to enable confident, responsible innovation at scale.

7.1 Mission Statement

The AI Governance Board exists to ensure that artificial intelligence is deployed across city government in a manner that is safe, ethical, accountable, and aligned with the interests of residents. The Board exercises oversight authority over the city’s AI portfolio, establishes standards and policies for AI development and procurement, evaluates risks, and promotes the responsible use of AI to improve the quality and efficiency of city services.

7.2 Board Composition

The Board’s composition should reflect the cross-cutting nature of AI risk. Roles are classified by function: decision-makers with approval authority, mandatory reviewers who must sign off for specific risk categories, and subject-matter advisors who participate when a use case falls within their domain. This role clarity distinguishes a workable governance body from a notional committee.

RoleDepartmentFunction TypePrimary ExpertiseTerm
Chair (AI Governance Director)Mayor’s / City Manager’s OfficeDecision-makerEnterprise governance, strategic leadershipPermanent — senior appointment
Chief Information Officer (CIO)IT DepartmentDecision-makerTechnology architecture, securityStanding member
Chief Information Security Officer (CISO)IT / SecurityMandatory reviewer — all tiersCybersecurity, data protection, incident responseStanding member
City Attorney / Deputy City AttorneyCity Attorney’s OfficeMandatory reviewer — Tiers 1 & 2Legal, regulatory, civil liabilityStanding member
Civil Rights DirectorCivil Rights / Human Rights CommissionMandatory reviewer — Tier 1; advisor — Tier 2Equity, disparate impact, civil libertiesStanding member
Chief Procurement OfficerFinance / ProcurementMandatory reviewer — all vendor contractsContracts, vendor management, procurement lawStanding member
HR DirectorHuman ResourcesMandatory reviewer — employment AIEmployment law, workforce AI policyStanding member
Public Safety RepresentativePolice / Fire / Emergency MgmtAdvisor — public safety AI use casesLaw enforcement AI applicationsRotating — 2 years
Resident Services Representative311 / Social Services / HealthAdvisor — public-facing AI use casesBenefit systems, service delivery equityRotating — 2 years
Records & Privacy OfficerIT / LegalMandatory reviewer — Tiers 1 & 2Public-records law, data governance, state privacy obligationsStanding member
Independent Technical AdvisorExternal — academic or nonprofitAdvisorThird-party vendor system evaluation; bias audit design and interpretation; AI accuracy and fairness assessment for procured systems; ability to assess vendor claims about model performance independently of vendor documentation2-year renewable term
Resident Representatives (2)Community — appointed by MayorAdvisorPublic accountability, lived experience2-year term — staggered

Note: Decision-makers hold formal approval authority. Mandatory reviewers must sign off on any use case touching their domain before Board approval is granted. Advisors provide domain expertise when relevant and may escalate concerns but do not hold blocking authority.

7.3 Decision Velocity and Administrative Efficiency

The Board’s governance structure is intentionally designed to preserve operational agility. The tiered model allows low-risk operational tools to proceed rapidly through streamlined review, moderate-risk systems to receive targeted technical evaluation, and high-risk systems affecting resident rights or public safety to receive comprehensive review — concentrating oversight resources where consequences are greatest.

Measuring Governance Effectiveness

Governance effectiveness should be measured not by how many systems are delayed, but by how consistently the city deploys AI safely, responsibly, and efficiently. The right metric is the ratio of high-confidence deployments to avoided incidents — not processing time alone.

7.4 AI Risk Classification Framework

Not all AI systems present the same risk profile. Objective triggers define threshold criteria for each tier — not just descriptive labels — so that triage is consistent and defensible.

Tier / Risk LevelObjective Triggers / CharacteristicsGovernance Requirements
Tier 1 — CriticalAffects legal rights, physical liberty, physical safety, or protected-class equity. Includes: law enforcement decision support, benefits eligibility, child welfare risk scoring, housing access, sentencing or parole tools.Full AIA required; Board approval; mandatory Civil Rights and Legal sign-off; public disclosure; human review mandate for every consequential decision; annual audit.
Tier 2 — HighSignificant resident impact on access to services or economic opportunity. Includes: permitting, health services, financial determinations, employment screening. Affects 1,000+ residents/year OR decisions that can be appealed.AIA required; Board review; Legal and Privacy mandatory review; annual performance audit; department head sign-off.
Tier 3 — ModerateOperational efficiency tools with limited direct resident impact. Includes: infrastructure optimization, internal analytics, workflow automation, procurement tools.IT security review; privacy impact assessment; department director approval; inventory registration.
Tier 4 — LowIncidental AI features embedded in standard software. Includes: spellcheck, scheduling assistants, basic FAQ chatbots, document summarization for internal use.Standard procurement review; IT approval; acceptable-use policy acknowledgment; inventory registration.

7.5 Municipal AI Governance Lifecycle

Every proposed AI deployment moves through a defined intake and review workflow, regardless of risk tier. The workflow below provides operational structure for how a use case moves from proposal through approval to ongoing monitoring and public reporting.

Municipal AI Governance Lifecycle Steps

StepGovernance Action
1. Department proposes AI use caseSubmits standard intake form to city AI inventory.
2. Register in City AI InventoryCIO office logs system, vendor, data accessed, deployment context, population affected.
3. Risk triageAssign Tier 1–4 per classification framework; low-risk tools proceed immediately.
4a. Tier 3–4 — Streamlined ReviewIT security review + department director approval; fastest path to deployment.
4b. Tier 2 — Standard ReviewLegal, Privacy, Civil Rights, Procurement, Security sign-off + AIA required.
4c. Tier 1 — Full Board ReviewComprehensive AIA + mandatory Civil Rights/Legal sign-off + public disclosure + human oversight mandate.
5. Conditional or Full ApprovalDeploy with documented human-oversight controls and vendor obligations.
6. Post-Deployment MonitoringOngoing audit, drift detection, incident reporting, periodic re-review; re-review triggered by material model updates.
7. Annual Transparency ReportPublic disclosure of AI inventory, governance activities, and safeguards.

7.6 Core Governance Processes

Pre-Deployment Review

Before any Tier 1 or Tier 2 AI system is deployed, the responsible department must submit a Deployment Accountability Assessment to the Board (see Appendix D). The assessment documents what the city knows about the system, what the vendor has disclosed, what the city has independently verified, how the city can explain a decision to a resident or regulator, and what monitoring and re-review obligations apply. The Board approves, conditionally approves with required mitigations, or rejects.

Ongoing Monitoring and Audit

Approved systems do not receive permanent clearance. All Tier 1 and Tier 2 systems are subject to annual performance audits evaluating accuracy, fairness, security posture, model drift, and continued alignment with the approved assessment. Material deviations — including vendor notification of model updates — trigger mandatory Board review.

Incident Response

The Board maintains an AI Incident Response Protocol integrated with the city’s broader IT and emergency response frameworks. Significant incidents — including system failures causing resident harm, security breaches involving AI-processed data, and civil rights complaints related to AI decisions — are escalated to the Board within defined timeframes.

Annual Transparency Report

The Board publishes an annual AI Transparency Report documenting the city’s AI inventory, governance activities, incident summary, and policy updates — publicly available on the city’s website and presented to City Council. This is the primary mechanism for maintaining public trust.

Implementation Roadmap

Standing up an AI Governance Board requires deliberate sequencing. The following phased roadmap delivers early value — demonstrating governance capability and reducing immediate risk — while building toward full operational maturity over an 18-month horizon.

Phase 1: Foundation (Months 1–3)

Establish the Legal and Organizational Framework

  • Draft and adopt an AI Governance Board Charter by mayoral executive order or city council resolution.
  • Appoint standing Board members from existing departmental leadership; assign Decisionmaker, Mandatory reviewer, and Advisor roles per Section 7.2.
  • Designate an interim Board Chair or assign to the CIO or Deputy City Manager pending a permanent hire.
  • Conduct a city-wide AI inventory: catalog all current AI systems by department, vendor, data accessed, deployment context, and population affected.
  • Classify inventoried systems against the Tier 1–4 risk framework using objective triggers in Section 7.4.
  • Identify the two to three highest-risk deployed systems for immediate evaluation.

Quick Win

The AI inventory exercise almost universally surfaces shadow AI deployments — tools being used without IT or legal knowledge. The act of conducting the inventory itself provides immediate risk reduction and sends a clear organizational signal that AI use is a governed enterprise activity.

Phase 2: Operational Build-Out (Months 4–9)

  • Develop and publish the Municipal AI Use Policy — governing acceptable AI use, including generative AI and commercial LLM tools, across all departments.
  • Publish the Municipal AI Procurement Standard and update standard contract templates to include model versioning notifications, vendor succession protections, and re-review triggers.
  • Develop the Deployment Accountability Assessment template and process (per Appendix D).
  • Conduct assessments on all Tier 1 systems identified in Phase 1.
  • Launch a department AI liaison program — a designated point of contact in each major department.
  • Recruit independent technical advisor and resident representatives.
  • Deploy an AI governance tracking system for intake, review workflow, and inventory management.

Phase 3: Full Operation and Continuous Improvement (Months 10–18)

  • Complete assessments for all Tier 2 systems.
  • Conduct first-cycle performance audits on all Tier 1 systems.
  • Publish the city’s first Annual AI Transparency Report.
  • Deliver AI governance training to department heads and procurement staff.
  • Establish relationships with peer city governance programs — Seattle, NYC, Boston, and San José.
  • Begin drafting a proposed AI Governance Ordinance for City Council consideration.
  • Evaluate the Board’s effectiveness and issue a Year One Assessment.

8.1 Resource Requirements

ResourceNotes
AI Governance Director (new FTE)Senior leadership position; may be phased — assigned to existing executive for Phase 1, dedicated hire for Phase 2+.
Technical Analyst / AI Auditor (1–2 FTEs)Conducts assessments, performs system evaluations including vendor claim verification, manages inventory and tracking.
Policy/Legal Coordinator (0.5 FTE or shared)State/federal regulatory tracking, policy drafting, contract review support.
Independent Advisor ContractsExternal technical reviews and bias audits — estimated $80K–$150K annually depending on scope.
Governance PlatformIntake management, inventory, and reporting — may be addressed through existing GRC tooling.
Training ProgramDepartment-wide AI literacy and governance training.

The resource investment required to stand up an AI Governance Board is modest relative to the city’s overall technology budget — and dramatically lower than the cost of a single significant AI-related adverse event. One avoided settlement, failed procurement, or serious cybersecurity incident could repay the annual governance investment many times over.

Operational Value and Service Delivery Opportunity

Well-governed AI can improve municipal operations across a wide range of service areas. The objective of governance is not to prevent cities from pursuing these efficiencies — it is to ensure that operational benefits are achieved responsibly, transparently, and sustainably.

9.1 AI Operational Benefit Map

City Function Potential Operational Benefit Governance Tier
311 ServicesFaster routing and case classification; reduced call-handling time; 24/7 resident self-serviceTier 3–4
PermittingReduced backlog and document review time; faster approvals for standard applicationsTier 2–3
ProcurementFraud detection and vendor risk analysis; automated invoice processingTier 3
UtilitiesPredictive maintenance and outage prevention; reduced emergency repair costsTier 3
Traffic ManagementCongestion optimization and signal coordination; improved emergency response routingTier 3
FinanceBudget forecasting and anomaly detection; audit efficiency improvementsTier 3
HRImproved recruiting workflows and administrative efficiency; scheduling optimizationTier 2–3
CommunicationsResident engagement analysis and multilingual support; sentiment monitoringTier 3–4
Public SafetyOperational dispatch optimization; evidence management workflowsTier 1–2 (with full assessment)
Social ServicesCaseload management and triage supportTier 1–2 (with full assessment)

Strategic Positioning

Cities that govern AI effectively will be better positioned to modernize services, improve operational performance, strengthen cybersecurity resilience, protect public trust, and responsibly lead through one of the most consequential technological transitions in modern public administration — while competing successfully for innovation partnerships and federal funding opportunities.

9.2 Building Public and Institutional Trust

Large cities are, at their core, trust institutions. Residents must trust that the city will use its powers — including data collection, surveillance, and automated decision-making — fairly, lawfully, and with their interests at heart. A visible, accountable AI Governance Board, with resident representation and public reporting obligations, is a tangible demonstration of that commitment.

9.3 Peer City Momentum

Several major U.S. cities have established formal AI governance structures and are increasingly recognized as national leaders. Seattle has a formal Responsible AI program with a published policy and 2025–2026 AI Plan.[13] New York City has published an AI Action Plan and subsequent guidance.[14] Boston has an innovation and technology governance function with AI oversight responsibilities.[15] San José has an AI policy, handbook, and AI inventory review process, and participates in the GovAI Coalition.[16] Cities that move now join that cohort; cities that wait respond to standards set by others.

Conclusion & Call to Action

Artificial intelligence will shape the next decade of municipal operations. The cities that govern AI effectively will be better positioned to modernize services, improve operational performance, strengthen cybersecurity resilience, protect public trust, and responsibly lead through one of the most consequential technological transitions in modern public administration.

This white paper has made the case across nine dimensions: the breadth of AI already embedded in municipal operations; why governance is an executive management issue, not just a technology issue; how the responsible-party gap — the distance between who controls AI systems and who bears accountability for them — is the defining structural challenge for cities as deployers; how governance accelerates rather than constrains innovation; the compounding risks in procurement, security, ethics, and compliance; the fiscal management rationale; the workforce and organizational dimensions; the architecture and authority of an effective AI Governance Board; a practical implementation roadmap; and the operational value that responsible AI deployment can deliver.

The window for proactive governance is present — but it is not permanent. The pace of AI adoption, the evolution of the regulatory environment at both the state and federal agency levels, and the accumulation of risk in currently deployed systems all create time pressure. Cities that establish governance frameworks now do so from a position of strategic choice; cities that wait increasingly do so from a position of reactive necessity.

Recommended Next Steps for City Leadership

  • Direct the City Attorney and CIO to jointly draft an AI Governance Board Charter for executive adoption within 60 days.
  • Authorize an immediate city-wide AI inventory, led by the CIO’s office, to be completed within 90 days.
  • Designate an interim Board Chair from existing senior leadership to coordinate the Phase 1 buildout.
  • Include a dedicated AI Governance function in the next annual budget cycle.
  • Schedule a City Council briefing on AI governance to begin building legislative support for a permanent ordinance.

Closing Statement

Governance is not the obstacle to innovation. It is the institutional foundation that allows innovation to succeed responsibly, sustainably, and at public scale. The opportunity before city leadership is therefore larger than compliance — it is the opportunity to establish a durable framework for responsible modernization, one that enables cities to adopt transformative technologies while preserving the accountability, transparency, and public trust upon which effective government ultimately depends.

Appendix A: Regulatory & Policy Landscape Map

SourceTypeMunicipal Obligation
FTC AI Guidance (2023–2025)Federal agency enforcement — unfair or deceptive AI practices; consumer protectionMonitor for applicable enforcement actions; review public-facing AI.
EEOC AI Guidance (2022–2024)Federal agency enforcement — AI in employment screening, promotion, and workforce decisionsMandatory review for any employment-facing AI; assessment required.
HUD AI Guidance (2023)Federal agency enforcement — Fair Housing Act applied to algorithmic tenant screening and housing advertisingMandatory review for any housing-related AI; assessment required.
OMB M-25-21 (April 2025)Federal policy / benchmark — responsible AI use, governance structures, human oversight, public trustVoluntary for cities; strong alignment recommended.
NIST AI RMF (2023)Voluntary framework — risk management across the AI lifecycleVoluntary; referenced in federal grant programs and OMB guidance.
State AI Legislation (16+ states)State law — varies by state — government-agency AI use; automated decision-making; algorithmic accountabilityBinding where enacted in city’s state; review state-specific requirements.
Civil Rights Laws (ADA, FHA, Title VI, ECOA)Binding federal law — disparate impact in automated decisions; accessibility; non-discriminationBinding; assessment must address applicable doctrine by use case.
EU AI Act (2024)International — comparative model — risk-tiering, documentation, conformity assessment for high-risk AINot binding on U.S. cities; useful comparative model for tier framework design.

AI Procurement Red Flags Checklist

The following indicators should trigger elevated procurement scrutiny or mandatory Governance Board review before any contract is executed:

  • Vendor refuses to disclose training data sources or data provenance
  • No audit rights are provided in the contract
  • No explainability or interpretability features are available
  • Vendor will not disclose subprocessors or third-party model providers
  • No data portability provisions exist — city cannot extract its data if it changes vendors
  • No performance benchmarks are contractually defined
  • No bias testing documentation or disparate impact analysis is available
  • Data retention terms are unclear or grant vendor broad rights to retain city data
  • Vendor reserves rights to use city data for model training without explicit consent
  • Security certifications are absent, outdated, or not applicable to the deployment context
  • Human oversight mechanisms are undefined or discretionary
  • Incident reporting obligations are unclear or exclude AI-specific failure modes
  • Contract does not include notification requirements for material model updates or version changes
  • Vendor does not provide a designated point of contact or escalation path for AI-related resident complaints
  • Data retention terms do not specify what happens to city data upon contract termination or vendor transition

Glossary of Key Terms

TermDefinition
Algorithmic Impact Assessment (AIA)Structured pre-deployment evaluation of an AI system’s potential effects on individuals, groups, and operations, covering accuracy, bias, privacy, and accountability.
Automated Decision System (ADS)Any algorithmic or AI-based system used to make or substantially inform a decision about an individual with limited or no meaningful human review prior to effect.
Bias AuditIndependent evaluation of an AI system’s outputs to identify systematic errors, disparate impacts, or deviations from expected performance across demographic groups.
Deployer AccountabilityThe obligations borne by an institution that activates and operates AI systems procured from commercial vendors — covering procurement due diligence, pre-deployment review, human oversight, ongoing monitoring, and public transparency — regardless of whether the institution designed or built the system.
Disparate ImpactLegal standard under civil rights law where a facially neutral policy or practice disproportionately harms a protected class, regardless of intent.
ExplainabilityThe degree to which an AI system’s decision logic can be understood and communicated in human-interpretable terms.
Generative AIAI systems capable of producing novel text, images, code, audio, or other content in response to prompts. Includes large language models.
Model DriftDegradation of an AI model’s performance over time as real-world conditions diverge from those present in training data.
NIST AI RMFThe National Institute of Standards and Technology AI Risk Management Framework — voluntary guidance for managing AI risk across the AI lifecycle.
Responsible-Party GapThe structural condition in which the entity that bears legal and political accountability for an AI system’s outcomes (the deploying city) does not control the system’s design, training data, update cadence, or explainability features. Governance frameworks are designed to manage this gap through contract standards, pre-deployment review, and ongoing audit obligations.
Shadow AIAI tools adopted and used by department staff outside of formal IT governance and procurement processes.
Tier ClassificationRisk-based categorization of AI systems used to calibrate the level of governance oversight required prior to and following deployment.

Deployment Accountability Assessment — Required Elements

The Deployment Accountability Assessment (DAA) replaces the traditional developer-oriented Algorithmic Impact Assessment for municipal AI governance. Because cities are deployers — not builders — of AI systems, the assessment is framed around what the deploying city knows, what the vendor has disclosed, what the city has independently verified, and what the city can explain and defend to a resident, a court, or a regulator. The DAA does not ask how the system was built; it asks whether the city has exercised appropriate diligence in deploying it.

  1. System Identification Name, vendor, product version, deployment date, responsible department, and Board intake reference number.
  2. Purpose and Scope Intended use case; decision context; populations affected; estimated volume of decisions per year; whether the system makes final decisions or provides recommendations subject to human review.
  3. Data Inputs Description of all data sources; data quality assessment; data governance controls; what data the vendor receives and retains; any data the city provides that may be used for vendor model training.
  4. Vendor Disclosures What the vendor has formally disclosed about system design, training data, model architecture, and performance — and the basis for those disclosures (contractual obligation, voluntary representation, or third-party audit). Document what was requested but not disclosed.
  5. Independent Verification What the city independently assessed or had third-party audited prior to deployment. What performance claims were verified by means other than vendor documentation. What material aspects of the system could not be independently verified, and the city’s rationale for proceeding despite that limitation.
  6. Performance Documentation Accuracy, precision, recall, and F1 scores as provided by vendor or independently verified. Performance metrics across demographic subgroups. Baseline benchmarks against which post-deployment drift will be measured.
  7. Disparate Impact Assessment Evaluation methodology; who conducted it; what populations were analyzed; results; and any mitigations required before or during deployment. Must specify which civil rights doctrines apply and how compliance is demonstrated. Document whether the vendor conducted its own disparate impact testing and whether those results were made available.
  8. Human Oversight Plan Description of human review processes; override mechanisms; accountability assignments; minimum review requirements for consequential decisions; and escalation procedures when automated outputs are questioned.
  9. Resident Notification and Appeal

Whether and how affected individuals are notified that an AI system contributed to a decision affecting them. Available appeal, correction, or reconsideration mechanisms. Legal basis for notification standards.

  1. Explainability Standard What explanation can the city provide to an affected resident about how a decision affecting them was made? What explanation can be provided to a court, a regulator, or a council member? If the system does not support explanation at the decision level, document how the city has mitigated that limitation through human oversight requirements.
  2. Contract Summary Key protections in the vendor contract: audit rights; performance benchmarks and remediation obligations; model versioning notification requirements; re-review triggers for material updates; data portability and exit provisions; subprocessor disclosure; vendor succession and continuity protections; indemnification for AI-related claims.
  3. Monitoring Plan Post-deployment performance tracking methodology; audit schedule; drift detection approach; designated responsible party; reporting cadence to the Governance Board.
  4. Re-Review Triggers Conditions that will automatically trigger Governance Board re-review before the next scheduled audit: material model update notification from vendor; significant performance degradation beyond defined thresholds; civil rights complaint related to system outputs; security incident involving AI-processed data; vendor acquisition, merger, or product succession event.
  5. Board Attestation Signature of department director and Records & Privacy Officer attesting to DAA completeness and accuracy. Signature of Civil Rights Director (Tier 1 systems) and City Attorney (Tier 1 & 2 systems) attesting that applicable legal standards have been addressed.

Reference Frameworks and Standards

  • NIST AI Risk Management Framework (AI RMF 1.0), January 2023. https://www.nist.gov/itl/airisk-management-framework
  • OMB M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 2025. Current federal AI governance benchmark.
  • OECD Principles on Artificial Intelligence (updated 2024)
  • EU AI Act (Regulation (EU) 2024/1689), entered into force August 1, 2024. Comparative model; not a U.S. federal compliance obligation.
  • FTC Guidance on AI and Consumer Protection (2023–2025 series)
  • EEOC Technical Assistance on AI and the ADA/Title VII (2022–2024)
  • HUD Guidance on Algorithmic Tools in Housing (2023)
  • CDT: “Regulating Public-Sector AI: Emerging Trends in State Legislation” (2025)
  • NCSL: “Artificial Intelligence 2025 Legislation” — state-by-state tracker.
  • De Arteaga et al., “Artificial Intelligence in Local Government Services,” Smart Cities 7(4), 2024 (MDPI).
  • National League of Cities: “AI in Local Government: Lessons from 2025 and Emerging Cyber Threats in 2026,” March 2026.

Notes and References Inline citations appear as superscript [n] markers. Full sources are listed below.

[1] National Institute of Standards and Technology, AI Risk Management Framework (AI RMF 1.0), January 2023. https://www.nist.gov/itl/ai-risk-management-framework [2] De Arteaga et al., “Artificial Intelligence in Local Government Services,” Smart Cities 7(4), 2024 (MDPI). Research covering 170 local governments worldwide found fewer than 16% had published AI policies as of May 2023. https://www.mdpi.com/2624-6511/7/4/64 [3] Center for Democracy & Technology, “Regulating Public-Sector AI: Emerging Trends in State Legislation,” 2025. At least 16 states had enacted laws specifically addressing government-agency AI use. https://cdt.org/insights/regulating-public-sector-ai-emerging-trends-in-state-legislation/ [4] National Conference of State Legislatures, “Artificial Intelligence 2025 Legislation.” All 50 states introduced AI legislation in 2025; 38 states adopted or enacted roughly 100 measures. https://www.ncsl.org/technology-and-communication/artificial-intelligence-2025-legislation [5] EU AI Act (Regulation (EU) 2024/1689), entered into force August 1, 2024. Staged compliance: prohibited-practices provisions applied from February 2, 2025; broader high-risk provisions apply from August 2, 2026. Comparative model only — not a U.S. federal compliance obligation. https://eurlex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32024R1689 [6] Executive Order 14110 revoked January 20, 2025. OMB M-25-21 (April 3, 2025) is the current federal AI governance benchmark. https://www.whitehouse.gov/presidential-actions/2025/01/initialrescissions-of-harmful-executive-orders-and-actions/ [7] Federal Trade Commission, AI enforcement and guidance portfolio, 2023–2025. https://www.ftc.gov/industry/technology/artificial-intelligence [8] U.S. EEOC, “What is the EEOC’s Role in AI,” April 2024. https://www.eeoc.gov/sites/default/files/2024- 04/20240429_What%20is%20the%20EEOCs%20role%20in%20AI.pdf [9] U.S. Department of Housing and Urban Development, guidance on algorithmic tools in housing advertising and tenant screening, 2023. [10] ACLU, Final Order of Dismissal and Settlement Agreement, Robert Williams facial-recognition wrongful-arrest case, Detroit, 2024. https://assets.aclu.org/live/uploads/2024/06/Final-Order-of- Dismissal-and-Settlement-Agreement.pdf [11] Pasco County (FL) predictive-policing program: six-figure civil settlement with a sheriff’s office. https://apnews.com/article/821d260e932a4582a6a912dd61fde157 [12] National League of Cities, “AI in Local Government: Lessons from 2025 and Emerging Cyber Threats in 2026,” March 2026. https://www.nlc.org/article/2026/03/27/ai-in-local-government-lessonsfrom-2025-and-emerging-cyber-threats-in-2026/ [13] City of Seattle, Responsible Use of Artificial Intelligence program and 2025–2026 AI Plan. https://www.seattle.gov/tech/data-privacy/the-citys-responsible-use-of-artificial-intelligence [14] City of New York, AI Action Plan and subsequent AI guidance and principles. [15] City of Boston, Office of Innovation and Technology. https://www.boston.gov/government/cabinets/innovation-and-technology

[16] City of San José, AI policy, AI handbook, inventory and review materials, and participation in the GovAI Coalition. [17] OMB M-24-10, March 2024. Rescinded and replaced by M-25-21, April 2025. [18] QUT research summary: “Local governments are using AI without clear rules or policies.” https://www.qut.edu.au/news/realfocus/local-governments-are-using-ai-without-clear-rules-or-policiesand-the-public-has-no-idea