State and Local Government AI Policy

Learning Objectives

After completing this lecture, you will be able to:

• Understand the key concepts of state and local government ai policy in a government context
• Connect state and local government ai policy to your agency's AI initiatives
• Identify next steps for applying these concepts in your role

Key Topics Covered

-
Local government considerations

-
Federal preemption

-
Multi-jurisdiction coordination

Why This Matters for Government

Government agencies face unique challenges when it comes to AI adoption. This lecture addresses these challenges head-on by providing cios, chief ai officers, agency technology leaders with the knowledge and frameworks needed to navigate AI in the public sector responsibly and effectively.

As part of the L4 (AI Architect) curriculum, this lecture builds on the foundational principle that every AI system in government ultimately serves citizens. Whether you are working with AI tools daily or setting strategy for your agency, understanding state and local government ai policy is essential for responsible, effective government AI adoption.

Lecture URL: https://skill.re/learn/govt/state-and-local-government-ai-policy.php

======================================================================

TRANSCRIPT: State and Local Government AI Policy

======================================================================

You will understand the unique challenges of state and local AI governance, including the fragmented

regulatory landscape, divergent state laws, local implementation challenges, and federal-state-local

coordination mechanisms. You will learn how to design AI policies that align across jurisdictional

boundaries, manage conflicting requirements, and coordinate multi-jurisdiction AI initiatives. By the

end, you'll be able to navigate federalism complexities, design policies that work across jurisdictions,

and build coalitions for collaborative governance.

If you think federal AI governance is complex, try managing AI policy across 50 states, thousands of cities

and counties, and multiple sovereign tribal nations. The United States has no single AI governance framework.

Instead, we have a patchwork of federal requirements, state laws that sometimes conflict with each other,

local ordinances that can be stricter or looser than state law, and tribal nations with their own governance

authority.

This creates a compliance nightmare for organizations operating across jurisdictions. A data use case that's

legal in one state may be illegal in another. A vendor that meets federal procurement requirements may not

meet specific city requirements. An AI system that complies with federal guidance may violate state law.

This session walks you through the state and local AI governance landscape. We'll examine the major state laws

currently in effect. We'll explore local governance mechanisms. We'll show you strategies for managing conflicts.

And we'll discuss approaches to multi-jurisdiction coordination and alignment.

The core insight: State and local AI governance is real, evolving rapidly, and creating compliance burdens

for organizations. Understanding and navigating this landscape is essential.

UNDERSTANDING MULTI-JURISDICTION AI GOVERNANCE

The U.S. constitutional structure allocates authority to federal, state, and local governments. Each level

has power to regulate AI within its jurisdiction. This creates overlapping, sometimes conflicting governance

frameworks. Your job is to understand this structure and navigate it strategically.

WHY THIS MATTERS FOR GOVERNMENT

The stakes are high. Non-compliance with state law can result in civil suits, state attorney general actions,

reputational damage, and loss of trust. Non-compliance with local requirements can result in permit denial,

fines, or business interruption. Managing multi-jurisdiction compliance requires understanding not just what

each jurisdiction requires, but how to design systems and policies that satisfy multiple jurisdictions

simultaneously.

THE STATE AI GOVERNANCE LANDSCAPE

As of early 2026, the state AI governance landscape is fragmented but rapidly developing. Different states

are taking different approaches.

STATES WITH COMPREHENSIVE AI GOVERNANCE LAWS

California has led the way with multiple pieces of legislation:

• Algorithmic Accountability Act (proposed): Requires impact assessments for automated decision systems
• Bot Disclosure Requirements: Requires disclosure when users interact with bots
• AI Transparency Requirements: Requires disclosure of AI use in government

California's approach is Rights-focused. Systems affecting fundamental rights require assessments, transparency,

and human oversight. This approach is stricter than federal requirements.

Colorado has enacted AI governance legislation:

• Focus on bias testing and fairness requirements
• Requirements for human review of algorithmic decisions
• Transparency and disclosure mandates

Other states with AI legislation include New York, Illinois, Massachusetts, and Texas. Each has slightly

different requirements.

STATES WITH SECTOR-SPECIFIC AI REQUIREMENTS

Some states have AI requirements in specific domains:

• Healthcare: Many states have requirements for AI use in medical contexts
• Criminal Justice: States have requirements for AI use in risk assessment, sentencing recommendations
• Employment: States have requirements for AI used in hiring and workplace decisions
• Housing/Finance: Some states have requirements for AI used in lending and housing decisions

STATES WITH MINIMAL/NO AI GOVERNANCE

Many states have not yet enacted comprehensive AI governance. However, this is changing rapidly. Expect

more states to enact AI governance laws over the next 1-2 years.

IMPLICATIONS FOR FEDERAL AGENCIES

Federal agencies operating in states with AI requirements must comply with state law. This includes:

• State requirements for bias testing apply to federal systems operating in those states
• Transparency requirements apply
• Human oversight requirements apply
• Data protection requirements apply (some states have stricter requirements than federal)

Managing this means:

• Assess which states have AI governance requirements relevant to your systems
• Determine whether federal systems must comply with state requirements
• Consult with agency legal counsel about state law compliance obligations
• Design systems to satisfy the most stringent state requirement where multi-state operations occur

LOCAL AI GOVERNANCE AND ORDINANCES

Cities and localities are increasingly establishing AI governance requirements through ordinances.

MUNICIPAL AI GOVERNANCE APPROACHES

Major cities implementing local AI governance:

• San Francisco: Has restricted facial recognition use by government; requires algorithmic bias audits
• New York City: Has requirements for AI transparency and accountability in hiring and benefits determination
• Boston: Has focused on algorithmic discrimination and impact assessment requirements
• Cities like Portland, Seattle, Denver: Have passed algorithmic accountability measures

Local governance typically focuses on:

• Algorithmic bias and discrimination
• Transparency and disclosure to residents
• Human oversight of algorithmic decisions
• Impact assessments for high-risk systems
• Resident right to explanation and appeal

TRIBAL SOVEREIGNTY AND AI GOVERNANCE

Tribal nations have sovereign authority to govern AI within their territories. Some tribes are developing

AI governance frameworks. This is an emerging area, but tribes have authority to:

• Restrict AI deployment affecting tribal members
• Require data sovereignty (tribal data stays on tribal lands)
• Require consultation with tribal governments before AI deployment
• Establish tribal AI governance standards

Implications for federal agencies:

• Tribal consultation is required for AI systems affecting tribal nations
• Tribal data must be handled according to tribal governance requirements
• Federal agencies cannot override tribal governance authority

CONFLICTS BETWEEN FEDERAL, STATE, AND LOCAL REQUIREMENTS

When federal, state, and local requirements conflict, which prevails?

SUPREMACY OF FEDERAL LAW

Federal law is supreme. When federal law conflicts with state or local law, federal law prevails. However,

this principle is limited:

• States can impose stricter requirements than federal law (in general)
• States cannot prevent federal agencies from complying with federal law
• The question is whether federal requirements preempt state/local requirements

PREEMPTION DOCTRINE

Preemption occurs when federal law explicitly prevents state/local regulation OR when federal law is so

comprehensive that state/local regulation would interfere. In AI governance, preemption is rare because:

• Federal AI requirements are still developing
• Congress has not explicitly preempted state AI regulation
• Most federal and state requirements are complementary rather than conflicting

PRACTICAL IMPLICATIONS

When federal, state, and local requirements conflict:

• Design systems to satisfy the most stringent requirement
• If requirements are fundamentally incompatible, consult with legal counsel
• Document your compliance approach and reasoning
• Consider whether different approaches are needed in different jurisdictions

Example: A federal AI system needs to retain log data for security purposes (federal requirement).

California law restricts data retention (state requirement). Solution: Design separate data handling for

California that satisfies both requirements (e.g., higher security walls, more restricted access,

automatic deletion after shorter period).

DESIGNING MULTI-JURISDICTION COMPLIANT SYSTEMS

Overview

How do you design systems that work across multiple jurisdictions with different requirements?

APPROACH 1

Design your system to satisfy the most stringent requirement across all jurisdictions. This means:

• Conduct impact assessments even if only some jurisdictions require them
• Implement transparency mechanisms even if not all jurisdictions require them
• Implement human oversight even if not uniformly required

Advantage: One system design works everywhere. Disadvantage: May be overly restrictive for jurisdictions

with minimal requirements.

APPROACH 2

Design systems with modular components that can be configured differently for different jurisdictions:

• Data handling modules that can be configured for different state data protection requirements
• Transparency modules that can be enabled/disabled based on jurisdiction
• Oversight modules that can vary by jurisdiction
• Bias testing modules that can be adjusted for different standards

Advantage: Tailors systems to each jurisdiction. Disadvantage: More complex to maintain and test.

APPROACH 3

Establish governance structures that coordinate across jurisdictions:

• Multi-jurisdiction AI governance board that includes representatives from different jurisdictions
• Shared documentation and compliance evidence
• Coordinated impact assessments covering multiple jurisdictions
• Joint training and capability building

Advantage: Builds shared understanding and coordination. Disadvantage: Slow and requires significant coordination effort.

FEDERAL-STATE-LOCAL COORDINATION MECHANISMS

Effective multi-jurisdiction governance requires coordination mechanisms.

ROLE OF PROFESSIONAL ASSOCIATIONS

Professional associations play a critical role in information sharing and norm-setting:

• National Association of State CIOs (NASCIO): Provides forums for state CIO coordination on AI governance
• International City/County Management Association (ICMA): Facilitates local government coordination
• Council of State Governments (CSG): Works on interstate policy coordination

Agencies can participate in these associations to:

• Learn about emerging state/local requirements
• Participate in standard-setting efforts
• Influence state and local policy development

FEDERAL GRANT PROGRAM COORDINATION

The federal government uses grant programs to incentivize state/local compliance with federal priorities:

• Grant requirements may include AI governance expectations
• Federal agencies can condition funding on compliance with federal AI requirements
• This creates incentive alignment

STATE-TO-STATE COORDINATION

States are coordinating with each other on AI governance:

• Multi-state model legislation efforts
• Regional coordination on AI governance standards
• Information sharing about emerging requirements and implementation challenges

Agencies can participate by:

• Sharing information about federal requirements and guidance
• Helping states understand compliance implications
• Supporting state coordination efforts

MANAGING REGULATORY FRAGMENTATION

Overview

How do you manage a situation where multiple jurisdictions have different AI requirements?

CENTRALIZED COMPLIANCE MANAGEMENT

Create a centralized function responsible for managing multi-jurisdiction compliance:

• Track requirements across all relevant jurisdictions
• Maintain current inventory of requirements
• Identify conflicts and gaps
• Coordinate across internal teams to implement compliance

FEDERATED RESPONSIBILITY

Distribute compliance responsibility while maintaining coordination:

• Each regional office/agency is responsible for compliance in their jurisdiction
• Centralized function provides guidance, training, and coordination
• Regular meetings to share challenges and solutions
• Shared compliance documentation

STAKEHOLDER ENGAGEMENT

Engage with state and local governments to:

• Clarify requirements when they're ambiguous
• Request relief when requirements create genuine conflicts
• Participate in requirement-setting processes
• Build relationships that make compliance easier

ANTI-PATTERN 1

Description: Assuming that federal requirements supersede all state/local requirements, so you only need

to comply with federal law.

Risk: You fail to comply with binding state/local requirements. This can result in state attorney general

actions, civil litigation, or reputational damage.

What goes wrong: Your agency deploys an AI system in California without California-required impact

assessment. California's attorney general office discovers this. Your agency now faces investigation,

required remediation, and public criticism.

How to avoid: Conduct systematic assessment of which state/local requirements apply to your systems.

Consult with legal counsel. Design systems to satisfy applicable requirements. Don't assume federal

requirements are sufficient.

ANTI-PATTERN 2

Description: Attempting to comply with every local requirement by creating unique system configurations

for each locality.

Risk: System complexity becomes unmanageable. You have dozens of system variants, each with different

configurations. Testing, maintenance, and updates become prohibitively expensive.

What goes wrong: You decide that every city where you operate will have a different data handling

configuration. You end up with 200 system variants. When you discover a security vulnerability, you

need to patch all 200 variants. Your engineering team is paralyzed.

How to avoid: Distinguish between truly unique requirements and variations that can be managed with

modular design. Where possible, satisfy the most stringent requirement. Use configuration management

to handle jurisdictional variations without creating separate code branches.

ANTI-PATTERN 3

Description: Assuming that different state and local governments will coordinate with each other, so

you don't need to worry about conflicts.

Risk: Conflicts remain unresolved. You're caught between incompatible requirements from different

jurisdictions.

What goes wrong: California requires one approach to algorithmic bias testing. Texas prohibits that

approach (for different reasons). You don't know how to design a system that satisfies both. You end

up not complying with one jurisdiction.

How to avoid: Actively engage in state/local coordination. Join professional associations. Participate

in multi-jurisdiction forums. Share information about conflicts. Help jurisdictions understand

implications of their requirements for multi-jurisdiction operations.

ANTI-PATTERN 4

Description: Applying standard state/local compliance processes to tribal nations, treating tribal

governance as a special case rather than as sovereign authority.

Risk: You fail to respect tribal sovereignty. This damages relationships with tribal nations and may

violate legal obligations.

What goes wrong: You deploy an AI system on tribal lands without tribal consultation. The tribe views

this as a violation of sovereignty. They demand the system be shut down. Your agency now faces tribal

government opposition and reputational damage.

How to avoid: Understand tribal sovereignty. Establish consultation processes with tribal governments.

Build tribal governance into your compliance framework from the beginning. Invest in relationships with

tribal leadership.

PROMPT 1

Your agency operates AI systems in 10 states. Develop a process that:

a) Identifies AI governance requirements in each state

b) Assesses which requirements apply to your systems

c) Identifies conflicts between federal and state requirements

d) Prioritizes compliance work

e) Assigns responsibility for monitoring and compliance

PROMPT 2

Your agency's AI system is required to:

• Retain detailed logs for federal security audits (federal requirement)
• Delete personal data within 30 days (California requirement)
• Provide real-time data to law enforcement (Texas requirement)

These requirements conflict. How would you:

a) Assess whether all requirements actually apply?

b) Identify the fundamental conflicts?

c) Design an approach that satisfies all requirements?

d) Document your reasoning?

PROMPT 3

Your agency wants to deploy an AI system in a region with significant tribal population. Design a

tribal engagement process that:

a) Respects tribal sovereignty

b) Incorporates tribal requirements into system design

c) Builds ongoing relationships with tribal governments

d) Addresses tribal data sovereignty concerns

e) Creates feedback mechanisms for tribal input

PROMPT 4

Design a modular architecture for an AI system that operates across multiple jurisdictions with

different requirements. Include:

a) Which components should be jurisdiction-specific?

b) Which components should be shared?

c) How would you manage configuration across jurisdictions?

d) How would you test system variants?

e) How would you handle security patches across variants?

PROMPT 5

Design a governance structure for your agency that manages AI compliance across multiple jurisdictions:

a) Centralized vs. federated responsibility approach?

b) How to coordinate across regional offices?

c) How to engage with state/local governments?

d) How to monitor regulatory changes?

e) How to resolve conflicts when they arise?

• Multi-jurisdiction AI governance is complex. Federal, state, local, and tribal authorities each have

power to regulate AI. You must understand requirements across all relevant jurisdictions.

• State AI governance is evolving rapidly. More states are enacting AI requirements. Plan ahead and

monitor emerging requirements in states where you operate.

• When requirements conflict, design systems to satisfy the most stringent requirement. This simplifies

compliance and avoids jurisdictional conflicts.

• Tribal nations have sovereign authority. Treat tribal governance as binding, not optional. Invest in

tribal relationships and engagement.

• Use modular system design to manage jurisdictional variations without creating unmaintainable system

complexity.

• Engage actively in state/local coordination. Join professional associations. Participate in forums.

Help jurisdictions understand implications of their requirements.

• Decentralized compliance responsibility requires strong centralized coordination. Establish clear

mechanisms for tracking requirements, identifying conflicts, and resolving them.

PREEMPTION

Legal doctrine that federal law supersedes state/local law when there's a conflict. In AI governance,

federal preemption is rare; states generally can impose stricter requirements than federal law.

TRIBAL SOVEREIGNTY

Authority of tribal nations to govern within their territory. Tribes are recognized as distinct political

entities with powers comparable to states. Tribal law applies to tribal members and on tribal lands.

STATE ATTORNEY GENERAL

Chief legal officer for a state, responsible for enforcing state law. Can bring civil actions against

entities violating state law, including AI governance requirements.

ALGORITHMIC ACCOUNTABILITY

Principle that entities deploying AI systems should be accountable for AI decisions and their impacts.

Increasingly embedded in state and local requirements.

DATA RESIDENCY

Requirement that data stays within a specific geographic location. Common in state and local AI governance

to address data protection and sovereignty concerns.

State and local AI governance is not a distant concern. It's real, binding, and evolving rapidly. Organizations

operating across multiple jurisdictions must understand the governance landscape in each jurisdiction and

design systems that satisfy multiple requirements simultaneously.

This is complex work. It requires:

• Systematic assessment of requirements across jurisdictions
• Modular system design that can accommodate jurisdictional variations
• Centralized coordination with federated responsibility
• Active engagement with state and local governments
• Respect for tribal sovereignty

Agencies that excel at this treat multi-jurisdiction compliance as integral to AI governance, not as

an obstacle to operations. They design systems that work across jurisdictions. They build relationships

with state and local partners. They participate in coordination efforts. They anticipate emerging

requirements rather than reacting to them.

Take 25 minutes to answer these questions:

• What states and localities are most relevant to your agency's operations?
• What AI governance requirements exist in those jurisdictions?
• Where are the biggest compliance gaps?
• How does your agency currently track state/local regulatory changes?
• How could your agency participate more effectively in state/local coordination?

The U.S. federal system means that AI governance will always be fragmented. Different jurisdictions will

have different requirements. This is a feature, not a bug--it allows experimentation and localization. Your

job is to understand this landscape, design systems that work across jurisdictions, and build relationships

that make compliance easier. Smart agencies do this. Less organized agencies get caught flat-footed when

new requirements arrive.

Government AI CLUB Certification Program

Level 4: AI Architect | State and Local Government AI Policy | Lecture 4.2.3

A GOVT.CLUB initiative.

<- 4.2.2 Navigating the Federal AI Landscape
4.2.4 International AI Governance ->

Start Your CLUB Certification

This lecture is part of L4: AI Architect -- 120 hours of comprehensive government AI training.

Explore CLUB Certification

Related Lectures

L4
4.2.1 -- Drafting Agency AI Policies
180 min - Workshop + Template

L4
4.2.2 -- Navigating the Federal AI Landscape
150 min - Lecture + Tracker

L4
4.2.4 -- International AI Governance
180 min - Lecture + Frameworks