HomeMy WebLinkAbout2026/10/21 - ADMIN - Agenda Packets - Community Technology Advisory Commission - Regular Community technology advisory commission meeting
October 21, 2026
6 p.m.
If you need special accommodations or have questions about the meeting, please call Jacque Smith at 952.924.2632 or the
administration department at 952.924.2505.
Community technology advisory commission
The community technology advisory commission is meeting in person at St. Louis Park City Hall,
5005 Minnetonka Blvd., in the Westwood Room on the third floor. Members of the public are
welcome to attend in person.
Visit www.stlouispark.org/government/boards-commissions to view the agenda and reports.
Agenda
1. Call to order – roll call (6 p.m.)
2. Approval of minutes – Sept. 23, 2026
3. Presentations - none
4. Business
a. Signal items (30 minutes)
i. ALPRs: Keogh, Straus
ii. Data centers: E. Anderson, R. Anderson, Bulliner
iii. Drones: Slaats, Straus
iv. Spreadsheet tracker
v. November signal assignments
5. Communications and announcements (5 minutes)
6. Adjournment
Future meeting/event dates:
Nov. 18, 6 p.m., regular meeting
Dec. 16, 6 p.m., regular meeting
CTAC Purpose Statement: The Community Technology Advisory Commission advises the city council and
other city bodies on how technology services can improve resident services and enhance quality of life. By
researching emerging technologies, assessing their potential impact, and recommending solutions
grounded in clearly defined problems, the commission helps ensure that technology decisions support the
city’s long-term strategic goals.
Community technology advisory commission meeting
September 23, 2026
6 p.m.
Community technology advisory commission
Minutes
Present: Commission Member Konnor Slaats (Chair), Commission Member Rudyard Dyer (Vice
Chair), Commission Member Elsa Anderson, Commission Member Reid Anderson,
Commission Member Ed Bulliner, Commission Member Lindsay Keogh, Commission
Member Kayla Stautz, Commission Member Ben Straus, School District Liaison Tom
Marble Ms. Jacque Smith (Staff Liaison)
1. Call to order – roll call
It was moved by Commission Member Dyer, seconded by Commission Member Slaats to call the
meeting to order at 6:02 p.m. The motion passed.
2. Approval of minutes – Aug. 19, 2026
It was moved by Commission Member Slaats, seconded by Commission Member Keogh, to
approve the minutes of the Aug. 19, 2026 meeting. The motion passed.
3. Presentations – none
4. Business
a. Recap Sept. 14 annual meeting with city council
Commission members agreed the annual meeting was successful with a clear discussion and
ideas for items for the commission to look into such as ALPRs and data centers. Commission
Member Slaats suggested creating groups of no more than three commission members to look
into these two items, then create a one-page summary for commission review, then to submit
to the city council. Commission members agreed on this approach.
b. Signal items
i. Exploration: ALPRs and data centers
Commission Members Straus and Keogh agreed to work on the ALPR topic. Commission
Member Keogh stated that the question is not whether ALPRs bring value, but how data
collection and stewardship should be approached. Findings will be brought back to the
commission over the next couple of meetings, with a goal of providing information in a
council advisory form by the end of 2026.
Commission Members Bulliner, Reid Anderson and Elsa Anderson agreed to work on the
data center topic. Commission Member Bulliner suggested approaching it from the
perspective of how the city council should think about data centers more broadly.
ii. Review: Drones as first responders, data privacy
Commission Member Slaats agreed to review the drone information submitted by
Commission Member Straus for crafting into a one-page document, and will provide
feedback before the next regular meeting. The commission can review the document
and decide if it should be sent to council, before spending more time on writing a longer
white paper. Commission Member Straus suggested work on signals should be done
within a quarter to keep items moving. Commission Member Slaats stated that it was
okay if work on various signals are at different stages.
iii. October signal assignments
Assignments for October are for Commission Member Slaats to provide feedback on the
drone signal to Commission Member Straus; for Commission Members Keogh and
Straus to work on the ALPR topic for the October meeting; and for Commission
Members Elsa Anderson, Reid Anderson and Bulliner to work on the data center topic
for the October meeting.
Before moving to the next topic, Commission Members Bulliner and Straus suggested
there should be a way to track the progress and stages of each signal. Commission
members agreed it was important to be able to keep track of those signals that aren’t
formally submitted to council, in case the topic comes up in the future and at that time
can be provided to council. Ms. Smith agreed to create a tracking form in SharePoint.
c. Review final AI whitepaper
Commission Member Slaats said he tried to incorporate everyone’s feedback into the final
product, and he plans to add a table of contents and adjust formatting before formal submission
to council. Commission Member Slaats will also fill out the council advisory form. All members
voted in favor of sending this item to city council for inclusion in a future study session packet.
Commission Member Slaats said the commission should feel good overall about completing this
project. Commission Member Stautz recognized Commission Member Slaats for the signal
system which has helped the commission be more productive.
5. Communications and announcements
a. Staff
Ms. Smith reminded commission members to return completed conflict of interest
disclosure forms by Oct. 5 as directed in the email they received. Ms. Smith also invited
members to attend the Sept. 26 Green Line extension opening day announcement event
hosted by Metro Transit.
b. Commission members
School District Liaison Tom Marble invited members to participate, or invite others to
participate, in a new digital learning advisory committee hosted by St. Louis Park Public
Schools. The first meeting is Oct. 5, 6 – 7:30, with three more meetings planned for the
school year. Anyone interested can visit the school district website for more information
and to sign up. Mr. Marble emphasized they are looking for diverse representation
beyond parents and that the committee will be focused on directed technology use vs.
passive consumption. Commission Member Slaats said this is a great way to follow up
on the AI in schools signal that was submitted by Commission Member Elsa Anderson,
but which the commission agreed was outside their purview.
6. Adjournment
It was moved by Commission Member Slaats, seconded by Commission Member Stautz, to
adjourn the meeting. The motion passed and the meeting was adjourned at 7:10 p.m.
DRAFT: Policy question to explore:
Given rapidly-changing technology and public opinion landscapes, what ongoing transparency,
governance, oversight, and implementation strategies would Council like CTAC to explore to
support future decisions on ALPRs and other data-collection & surveillance technology, in
alignment with the city’s Vision 4.0?
Summary to date:
Earlier this year, St Louis Park implemented changes to its ALPR retention and usage policy to
prevent other law enforcement agencies from unauthorized access. St. Louis Park PD recently
removed written-request requirements for ALPR data access1. Combined with evolving national
trends, this shift highlights governance risks:
● Deepens Racial and Economic Disparities: Nationwide, ALPR deployment is usually
disproportionately concentrated in lower-income and communities of color, amplifying
bias in predictive analytics.2 3 4
● Shifting Legal Consensus: An October 2026 federal ruling in Oklahoma established
that warrantless, prolonged retrospective searches of Flock databases violate the Fourth
Amendment.5
● Data Misuse and Wrongful Targeting: Character misreads and outdated databases
can cause severe harm and wrongful arrests.6 7
● Erosion of Public Trust: Automated surveillance without local oversight or transparency
damages resident confidence in municipal data stewardship.8
● Perception vs. Reality of Safety: While visible tools make residents feel safer,
independent studies note it is difficult to isolate ALPR's direct impact on actual crime
rates. 9
Why this matters to council:
● Alignment with Vision 4.0 Equity Goals: Unchecked data sharing and algorithmic bias
disproportionately harm marginalized communities. Strict surveillance governance is vital
to maintain public trust and honor municipal equity mandates.
● Vendor & Data sovereignty risks: Standard contracts (e.g., Flock agreements) often
grant perpetual data licenses and allow external staff access, driving "surveillance creep"
as local data enters national networks.
● Changing legal landscape: The city’s "reasonable suspicion" threshold may risk
obsolescence following federal rulings against warrantless searches.
If Council would like to explore more, potential topics for CTAC might be:
● CTAC can investigate alternative technical architectures and strategies employed by
other cities, such as in-house or self-hosted ALPR infrastructure, that satisfy public
safety needs and build public trust.
● CTAC can propose a comprehensive "Data Stewardship Framework" for surveillance
and data collection technologies (such as ALPRs) that sets baseline requirements for
any current or future surveillance procurement.
● CTAC could help monitor emerging governance practices and compare St. Louis Park’s
approach with other cities, particularly around data sharing, auditing, retention,
transparency, and vendor capabilities.
1: St. Louis Park Police Department sec. 425.9, “Releasing ALPR data”
2: Study finds Flock cameras disproportionately surveil Black and high-poverty neighborhoods in
Hampton Roads | 13newsnow.com
3: https://osf.io/preprints/socarxiv/5ckgv_v1
4: License Plate Surveillance Logs Reveal Racist Policing Against Romani People | Electronic Frontier
Foundation
5: Flock You and the Horse You Rode In On - Federal Court Rules Flock Violates Fourth Amendment -
Security Boulevard
6: Woman sues Flock, officer after cameras used in alleged mistaken theft charge - ABC News
7: Flock ‘false flags’ lead to frightening motorist encounters with police
8: How citizens and local governments can advance data-driven policymaking together | Brookings
9: San Francisco’s car crime has plunged. How much credit does Flock deserve? : Planet Money : NPR
Citywide drone governance
CTAC research proposal for Council feedback
Building on recent signals, CTAC proposes a policy study of city drone use and seeks Council feedback on relevance
and scope.
Policy ques,on
As drone technology becomes more widely used by ci>es, what governance and transparency prac>ces should St.
Louis Park use, and what use cases might warrant Council review, to ensure that the benefits of the technology are
balanced with privacy and community-trust considera>ons?
Why this could merit explora,on
Minnetonka launched its Drone as First Responder (DFR) program in August 2025 to support emergency calls and
provides a public flight dashboard. [3] Its June 2026 update describes support for both police and fire, and it also has a
full police drone use policy. [9] Edina completed a two-week DFR trial in May 2026. [5] Bloomington’s explora>on
includes public works, infrastructure, and environmental applica>ons. [4] These developments raise ques>ons about
privacy, transparency, and oversight as city uses expand.
Proposed scope
The study would address policy implica>ons across police, fire, public works, u>li>es, engineering, and parks, including
contracted and shared drone services. Poten>al uses would be dis>nguished from current prac>ces.
Survey exis,ng policy and peer approaches. Survey published policies and staff summaries of current prac>ce;
compare peer approaches to iden>fy choices relevant to SLP.
Explore privacy and public accountability. Examine permi]ed purposes, incidental images of residents and homes,
reten>on and sharing, vendor use of data, and public repor>ng. Consider how benefits and community impacts
should inform policy.
Consider review of expanded uses. Iden>fy changes that could warrant Council review or community input, such as
DFR, rou>ne area monitoring, new analy>cal capabili>es, or expanded data sharing.
Roles and deliverable
CTAC would lead policy research and peer comparison. Staff would supply exis>ng informa>on and check factual
accuracy and legal requirements. The Police Advisory Commission could be invited to iden>fy public safety ques>ons
and comment on a dra^; joint work would be agreed separately.
The proposed deliverable is a focused policy white paper, approximately 4–6 pages. It would cover city use cases, peer
approaches, governance principles, tradeoffs, and ques>ons for Council. It could iden>fy areas for further policy
development. Opera>onal assessments, dra^ing proposed policies, and implementa>on planning would remain with
staff.
Council feedback requested
Would this policy white paper topic be useful to Council? Which ques>ons should take priority? What staff input and
PAC consulta >on would be appropriate? How does this topic’s priority compare to other proposed topics (ALPRs and
data centers)?
[3] Minnetonka: Drones as First Responders
[9] Minnetonka: DFR program update (June 29, 2026)
[5] CBS Minnesota: Edina DFR trial (May 19, 2026)
[4] Bloomington: DFR explora>on (May 15, 2026)
Outlook
CTAC Council Advisor y Form, AI Whitepaper, Drones Signal Feedback + Council Proposal
From Konnor Slaats < >
Date Sun 9/27/2026 6:13 PM
To Jacque Smith <jsmith@stlouisparkmn.gov>
3 attachments (525 KB)
B&C Advisory communication template (CTAC AI Whitepaper).pdf; Future of AI for Cities.pdf; CTAC Council Drone Proposal.pdf;
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize
the sender and know the content is safe.
Hi Jacque!
Attached are the filled commission advisory form, updated AI for Cities whitepaper, and my Drones
Signal Feedback for Ben.
Also, just a heads up that I can't make the October 21 meeting because of a prior commitment. I'm
sorry for not realizing it during our past meeting. I thought it was a different week.
Here's my notes from Ben's signal, with a proposed PDF that we could send directly to Council
alongside our other topics (data centers, ALPRs). Happy to tweak this as well, just was reviewing Ben's
amazing signal and figured we'd want to tweak it a bit to be more Council-focused. Pending how we
feel about this, I can also tweak our Exploration phase notes.
Notes on Ben's Signal:
1. Is there a real public or city decision? Yes. Council could decide regulations to cover city drone uses, what public information residents should
receive, and which material expansions require additional review.
2. Does CTAC add something staff might not naturally provide? Yes, if we stay at the policy level. Staff will have operational knowledge and know
legal obligations and existing controls. CTAC can compare practices across departments and peer cities, examine how capabilities and data uses may
evolve, and translate tradeoffs into choices Council can evaluate
3. Is this strategic rather than operational? Yes, with boundaries. Thinking we should focus on permitted drone purposes, collection and data limits,
public accountability, and approval thresholds. Any particular drone procedures or decisions would be left to relevant departments.
4. Is this relevant to Council or another commission? Probably, though it’s unclear how broadly. Council has an interest in citywide consistency, public
trust, resource commitments, and how technology changes services. PAC would be a limited partner for police use and resident engagement.
Recommended framing
As drone technology becomes more widely used by cities, what governance and transparency practices should St. Louis Park use, and what use cases
might warrant Council review, to ensure that the benefits of the technology are balanced with privacy and community-trust considerations?
DFR is a good example: more frequent use could increase times that the public comes in contact with a drone. Similar questions would be raised if
infrastructure imagery is later used for enforcement or shared with another agency. These are just scenarios right now, but show where drone usage could
become more broad.
A useful outcome could be confirmation that existing controls are adequate, clearer public information, targeted improvements, or a common city
framework. The review should remain open to each result.
Let me know if you have any questions, and thank you!!
Konnor
10/15/26, 8:24 AM CTAC Council Advisory Form, AI Whitepaper, Drones Signal Feedback + Council Proposal - Jacque Smith - Outlook
about:blank 1/1
Idea ID Signal Title Submitted By Strategic Priority Owner Stage Priority Status Decision Received Date Stage Start Date Target Due Date Next Step Link to Docs Notes
1 GenAI and government data Konnor Slaats Good Governance Konnor Slaats Approval/completion High Sent to councilApprove 8/10/2026 8/19/2026 10/12/2026 Submit to council Whitepaper being finalized; Konnor completed advisory form; on 10/12/26 council study session as report; no follow ups for CTAC; staff will present more info to council in 2027 as part of Good Governance system
2 ALPRs Ben Straus Good Governance Benjamin Straus Exploration Medium Researching Approve 9/15/2026 9/23/2026 10/21/2026 Move to exploration; discuss in October 2026 meeting20260923 Straus Signal - ALPR.pdf Straus, Keogh researching
3 Data centers CTAC A Welcoming, Safe Community Edward Bulliner Exploration Medium In review Approve 9/14/2026 9/23/2026 10/21/2026 Move to exploration; discuss in October 2026 meetingNone Bulliner, Reid Anderson, Elsa Anderson researching
4 Drones as first responders Ben Straus Good Governance Benjamin Straus Exploration Medium In review Approve 9/16/2026 9/23/2026 10/21/2026 Move to exploration; discuss in October 2026 meeting20260923 Straus Signal - DFR.pdf Slaats provided feedback for Straus; info in 10/21/26 CTAC packet; also discussed at 9/28/26 council study sesssion
5 Gen AI in schools Elsa Anderson A Welcoming, Safe Community Elsa Anderson Signal Low On hold Defer 8/10/2026 8/19/2026 8/19/2026 None 260819 Signal-Elsa Anderson.pdf Declined as city doesn't have authority over the schools. Note: At 9/23/26 meeting the creation of a digital learning advisory committee was announced, hosted by SLP Public Schools.
6 Data stewardship Lindsay Keogh Good Governance Lindsay Keogh Signal Medium Received Pending 8/10/2026 10/21/2026 Review in meeting 260819 Signal-Lindsay Keogh Information applies to other signal topics being reviewed such as AI and ALPRs
7 League of Minnesota Cities AI Data Practices Konnor Slaats Good Governance Konnor Slaats Signal Low Received Pending 8/10/2026 10/21/2026 Review in meeting?260819 Konnor Slaats Signal.docx Konnor purposely sent in a signal that seemed like it should be held to test process; not sure if there's much here. Seems like SLP is well-covered already
1
Advisory communication to council
City Council has provided direction that the primary purpose of advisory boards and commissions is to
assist/advise city council in the policy decision-making process on behalf of the public. Boards and
commissions may also be asked to provide community advice and feedback in a systematic manner.
Please use this form to submit a board or commission-related topic for city council consideration. Note that
use of this advisory communication to council requires a majority vote of a city board or commission prior to
submission.
Decisions on whether to take up an issue will be made by council.
Use the sections below as a guide and omit sections that may be extraneous.
Date:
To:
From:
Subject:
Strategic priority (if applicable):
Approved work plan item? ☐Yes
☐No
Council request: ☐ Review and comment or reply
☐Review and decide (e.g., new work plan item)
☐Informational only – no response needed
Action requested:
What is the commission asking Council to do? For non-work plan items, no action will be taken unless Council
chooses to provide direction or otherwise discuss at a future meeting. If requesting a new work plan item, make
explicit.
1
Background:
Explain the exact circumstances of the situation and provide general information about the topic/issue.
Assessment:
Explanation of the Commission's stance on a particular topic/issue, how it supports existing strategic priorities
and how it advances the purpose of boards and commissions. Include information about whether cross-
collaboration with other boards or commissions is recommended. If action from the council is requested,
provide the justification.
Recommendation:
Recommendations should be included for “review and decide” initiatives. Include clear explanation of
recommendation(s). This section can include a bulleted list of each individual recommendation, etc. Staff will
provide their recommendations on the staff report.
Future of AI for Cities
A Policy White Paper
Prepared by the St. Louis Park Community Technology Advisory Commission
For consideration by the St. Louis Park City Council
2026
Executive Summary.....................................................................................................................3
Defining AI....................................................................................................................................4
Section 1: Risks, Governance, and Guiding Principles...........................................................4
Cross-Cutting Risks.................................................................................................................4
A Governance Framework for Council Questions...................................................................5
Principles for Responsible AI Use...........................................................................................6
Section 2: Internal City Operations............................................................................................7
The Current Landscape...........................................................................................................7
Key Internal Use Cases...........................................................................................................7
Staff Productivity and Writing Assistance..........................................................................7
Grant Writing and Administrative Support..........................................................................8
Permitting and Workflow Acceleration...............................................................................8
Policy Implications for St. Louis Park.......................................................................................8
Section 3: Public-Facing AI and Resident Engagement..........................................................9
Chatbots and Self-Service Assistance.....................................................................................9
Meeting Transparency and Accessibility..................................................................................9
Equity and Participation.........................................................................................................10
Policy Implications for St. Louis Park.....................................................................................10
Section 4: Public Works and Infrastructure Operations........................................................11
Examples from Peer Cities.....................................................................................................11
Potential Applications for St. Louis Park................................................................................11
Risks and Watch-Outs...........................................................................................................12
Policy Implications for St. Louis Park.....................................................................................12
Section 5: Planning, Zoning, and Permitting..........................................................................13
Examples from Peer Cities....................................................................................................13
Potential Applications for St. Louis Park................................................................................13
Risks and Watch-Outs...........................................................................................................14
Policy Implications for St. Louis Park.....................................................................................14
Section 6: Looking Ahead — Agentic AI and the Evolving Landscape................................15
What Agentic AI Means for Cities..........................................................................................15
Implications for St. Louis Park...............................................................................................15
External Resources and Learning Networks.........................................................................16
Conclusion: Toward an AI-Compatible City............................................................................17
Appendix: Key Resources and References............................................................................18
National and State Guidance.................................................................................................18
Peer City Policy Documents..................................................................................................18
Selected Case Study Sources...............................................................................................18
Executive Summary
Artificial intelligence is no longer an emerging technology. Across the United States and
internationally, cities of every size are deploying AI tools to detect potholes, process permit
applications, answer resident questions, translate public meetings, and manage aging
infrastructure. The question for St. Louis Park is not whether AI will affect city government, but
where it provides genuine public value, where simpler approaches remain preferable, and how
any tools the city adopts will be governed responsibly.
This white paper reflects the research, discussion, and recommendations of the St. Louis
Park Community Technology Advisory Commission and is presented to the City Council
for consideration. It explores how cities can adapt their policies, processes, and
governance frameworks for an AI-enabled future. It also draws on examples from peer
cities, national guidance from the National League of Cities (NLC), and the city's own
existing technology posture and policies.
The paper is organized around five topic areas: (1) the cross-cutting risks and governance
principles that apply to all AI use; (2) internal city operations, including back-office tools and
workflow acceleration; (3) public-facing services such as resident chatbots and meeting
transparency tools; (4) public works and infrastructure operations; (5) planning, zoning, and
permitting; and a forward-looking look at agentic AI and what may come next.
Across all areas, the Commission reaches a common conclusion: the value of AI depends on
the quality of underlying data, the clarity of governance structures, the preservation of human
accountability, and a sustained commitment to equity. The Commission therefore recommends
that St. Louis Park formalize a risk-tiered AI governance process and public inventory; evaluate
proposed uses against simpler alternatives; prioritize approved, low-risk internal tools and
hands-on learning; require human accountability, transparency, and equity measurement for
uses that affect residents; and monitor rather than broadly deploy agentic AI in the near term.
St. Louis Park has a meaningful foundation for this work: it has internal generative AI
guidelines, a standard AI vendor questionnaire, proposed additional AI investment for
2027, and a Community Technology Advisory Commission actively engaged in these
questions. The task ahead is extending that framework to cover other AI applications,
including perceptive, analytical, predictive, and agentic systems.
Defining AI
Artificial intelligence (AI) is an umbrella term for computer systems that perform tasks involving
perception, language, pattern recognition, prediction, or decision support. Municipal AI can take
several overlapping forms.
● Perceptive AI, including computer vision, detects or classifies conditions in images,
video, or sensor data, such as potholes or pavement damage.
● Analytical and predictive AI identifies patterns in data to forecast conditions, prioritize
work, or support decisions.
● Generative AI, including large language models (LLMs), creates content such as text,
summaries, translations, images, or code.
○ Unlike a pothole-detection model, which is generally trained to identify a defined
condition in visual data, an LLM generates responses by predicting likely
language and can therefore produce plausible but incorrect information.
● Agentic AI builds on these capabilities by connecting models to tools and workflows to
carry out multi-step tasks.
These categories can overlap, and all require appropriate testing, human accountability, and
governance.
Like any technology, AI is not inherently the right tool for every problem; the city should use it
only when it offers a clear advantage over simpler, more transparent, or less costly approaches.
Section 1: Risks, Governance, and Guiding Principles
Before evaluating individual AI applications, the Commission believes it is important to establish
a shared governance vocabulary and identify the risks that apply across all municipal AI use
cases. This section frames the core issues that should inform every subsequent decision the
city makes about AI.
Cross-Cutting Risks
AI Slop and Hallucination. Generative AI systems can produce confident, fluent, and entirely
incorrect answers. A prominent municipal example: in 2024, New York City's MyCity chatbot
advised business owners that they could legally reject Section 8 housing vouchers and that
serving cheese bitten by a rat was permissible. Deploying AI tools that interact directly with the
public without rigorous accuracy review creates real reputational and legal exposure.
Resident Data and Privacy. Public AI models may retain user inputs for training. Staff using
unapproved tools can inadvertently expose resident financial records, health information, or
other protected data. In early 2026, the acting director of the U.S. Cybersecurity and
Infrastructure Security Agency reportedly triggered internal security warnings after uploading
sensitive government documents into a public ChatGPT instance. Third-party contractors may
also process city data through unauthorized AI systems without the city's knowledge.
Surveillance Creep. Camera networks, mounted sensors, and detection tools deployed for
narrow purposes such as pothole detection can be tempting to repurpose for enforcement,
public safety monitoring, or behavioral surveillance. Governance frameworks should establish
clear use-case boundaries and require Council review before any expansion.
Equity in Service Delivery. AI tools trained on complaint data may prioritize areas where
residents are more likely to report problems, systematically underserving neighborhoods with
lower reporting rates, language barriers, or lower institutional trust. Cities must actively monitor
whether AI improves or exacerbates service equity.
Unpredictable Costs. Operational costs for AI can fluctuate by orders of magnitude based on
small changes in how systems are prompted or how often they self-correct. Without hard
spending limits and performance boundaries, AI tools can quietly become fiscal liabilities.
Vendor Dependence and Data Lock-In. Many AI tools are embedded in proprietary platforms.
Cities should evaluate whether they can export their data, audit model performance, switch
vendors, and integrate tools with core systems before signing contracts.
Records and Legal Obligations. Images, videos, work orders, and resident reports may
become government records. Under the Minnesota Government Data Practices Act, data
created with AI assistance may need to be retained and produced in response to public data
requests.
A Governance Framework for Council Questions
The National Institute of Standards and Technology (NIST) AI Risk Management Framework
provides a useful foundation. The Commission has distilled its core functions into four questions
that Council members and staff can apply to any proposed AI deployment:
NIST Function Council Question What to Look For
Govern Who is ultimately accountable if
this fails and responsible for
associated costs?
A specific human owner or
position, not just an IT vendor.
Map What specific problem does this
solve, what data does it touch,
and how is it paid for?
A clear use case with strict
boundaries on what resident
data is involved. Control
mechanisms to prevent runaway
costs.
NIST Function Council Question What to Look For
Measure How will we prove this system is
unbiased, accurate, and
cost-constrained?
Pre-deployment testing plan,
ongoing performance audits,
and consistent cost
measurement.
Manage What is the human fallback plan
when the AI makes a mistake or
is unavailable?
A documented mitigation
strategy and a clear off-switch if
things go wrong.
These four questions do not resolve every governance challenge, but they ensure that each AI
deployment has a named human owner, a defined problem scope, a measurement plan, and a
documented fallback. The Commission recommends that St. Louis Park require documented
answers to these questions before approving any new AI system.
Principles for Responsible AI Use
Drawing on NLC guidance and peer city experience, the Commission recommends the following
principles for all AI activity in St. Louis Park:
• AI should support human decisions, not replace them. Staff, commissioners, and Council
should retain accountability for all interpretations, recommendations, and approvals.
• AI should be attached to defined operational problems, not deployed speculatively.
Before adopting AI, the city should compare it with simpler, more transparent, and less
costly alternatives.
• All AI tools should go through IT and legal review before deployment, including free and
pilot products.
• AI-generated content in public-facing channels should be disclosed and cite authoritative
sources.
• Performance should be measured against equity metrics, not just efficiency metrics.
• The city should maintain a public inventory of AI systems in use, consistent with best
practices from cities like San Jose and Lebanon, NH.
St. Louis Park's existing internal generative AI guidelines already reflect many of these
principles, and the city plans to evolve these guidelines into a formal policy in early 2027. The
task ahead is extending that policy to cover operational, perceptive, and predictive AI
applications as they emerge.
Section 2: Internal City Operations
City employees across departments increasingly interact with AI tools in their daily work,
whether the city has sanctioned those tools or not. A proactive strategy for internal AI use
reduces risk, improves consistency, and creates opportunities to demonstrate AI's value to staff
and elected officials before expanding into higher-stakes resident-facing applications.
The Current Landscape
Cities are deploying AI for internal operations in three broad categories: productivity tools for
individual staff, workflow acceleration across departments, and data analysis and decision
support.
San Francisco has led among peer cities, adopting Microsoft Copilot for writing city reports,
analyzing data, and summarizing documents across departments. San Jose issued an RFP in
2025 for a city-wide generative AI platform for employee use. Seattle and Boston have each
published internal generative AI policies governing staff use of tools like ChatGPT, Gemini, and
Copilot.
According to a 2025 global study of 250 cities, 56 percent are actively piloting or using AI to
upgrade government operations and services, and 83 percent plan to do so within three years.
The trend is clear: cities that establish governance frameworks now will be better positioned to
adopt tools responsibly as they mature.
St. Louis Park has already taken a meaningful step by publishing internal generative AI
guidelines and a standard AI vendor questionnaire. The next phase is building on that
foundation by clarifying which tools are approved, how staff are trained, and how the city will
evaluate and expand internal AI use over time.
Key Internal Use Cases
Staff Productivity and Writing Assistance
AI copilot tools integrated with productivity suites (Microsoft 365, Google Workspace) can help
staff draft reports, summarize meeting notes, respond to routine correspondence, and search
internal knowledge bases. Early research suggests these tools are especially helpful for newer
or less-experienced employees. The risk is over-reliance on AI-generated content that has not
been fact-checked or verified against authoritative sources.
Peer example — Chattanooga, TN: The city created a “Prompt Library” of pre-written prompts
to guide generative AI tools for specific staff tasks, standardizing outputs and reducing errors
across departments.
Grant Writing and Administrative Support
AI can assist staff with grant research, identifying eligible programs, drafting application
narratives, and checking compliance with grant requirements. This has particular value for
smaller cities where grant-writing capacity is limited.
Permitting and Workflow Acceleration
Several cities have integrated AI into permitting workflows to reduce review cycles, catch
incomplete applications early, and improve consistency across staff reviewers.
Peer example — Hamilton, ON: The city used AI to scan first-stage building permit
applications for compliance with city rules, building codes, and zoning requirements, achieving a
60 percent decrease in permit processing time and a 70 percent decrease in overall review time
from application receipt to conditional approval.
Peer example — Los Angeles Planning: The Planning Department uses AI to analyze land
use regulations and zoning data to proactively identify issues before formal permit application
review begins, reducing back-and-forth between applicants and staff.
Peer example — Honolulu: CivCheck, an AI-guided permit preparation tool, helps applicants
check for code compliance and required documents before submission, reducing review time by
catching problems upstream.
Policy Implications for St. Louis Park
For internal operations, the Commission recommends the following:
• Extend the existing generative AI guidelines/future policy to cover productivity tools,
copilots, and any AI embedded in core software platforms such as the city’s permitting or
work-order systems.
• Establish an approved tools list. Following Seattle’s model, require that all AI software,
including free and pilot products, go through IT and legal review before staff use.
• Continue investing in practical AI literacy. Provide structured, hands-on opportunities for
staff and Council members to use approved AI tools with public, nonsensitive
information.
• Partner with the League of Minnesota Cities, MNIT, or local educational institutions
where appropriate.
• Create a feedback channel for staff to surface AI use cases, identify problems, and
share what is working across departments.
• Set spending controls. Any AI tool with usage-based pricing should have a hard
spending cap and monitoring process in place from day one.
Section 3: Public-Facing AI and Resident Engagement
Public-facing AI applications carry higher reputational and governance stakes than internal tools
because errors affect residents directly and can undermine trust in city government. At the same
time, well-designed resident-facing tools can meaningfully improve access to services, reduce
barriers for non-English speakers, and extend the city’s reach outside business hours.
Chatbots and Self-Service Assistance
AI-powered chat interfaces are increasingly common in city government. When well-governed,
they can handle routine informational inquiries, help residents navigate city services, submit
service requests, and identify the right staff contact for complex issues. When poorly governed,
they produce incorrect guidance with high confidence, as New York City’s MyCity chatbot
demonstrated in 2024.
The key design principles for safe resident-facing chatbots are: ground responses in
authoritative city documents and ordinances; include clear disclaimers; provide a path to human
review for any consequential decision; and disclose that the user is interacting with an AI.
Ann Arbor, MI "Ask Ann" provides 24/7 chat assistance in 71 languages, helping residents
find city services, submit requests, and contact staff. Unresolved questions
are escalated to staff during business hours.
Dearborn, MI AI translation and virtual chatbot tools serve a community where more than
half of 110,000 residents speak a language other than English at home.
Atlanta, GA ATL311 chatbot handles routine service requests and common questions,
reducing call-center volume and improving after-hours responsiveness.
Midland, TX "Ask Jacky" is integrated with SeeClickFix to allow residents to report issues
and track status via an AI-powered chat interface.
Kelowna, BC Building permit chatbots had over 5,000 weekend conversations and 6,500
after-hours conversations in the first six months of 2024, reducing routine
staff inquiries.
Meeting Transparency and Accessibility
AI tools for meeting accessibility address two related challenges: making government
proceedings understandable to residents who cannot attend in person, and serving residents
who do not read or speak English fluently.
Meeting agenda explainers: Saratoga, CA deployed an AI tool called Hamlet that summarizes
council agendas, supporting documents, and meeting recordings in plain language. Government
Technology reports that several cities are using similar tools to improve transparency and
resident engagement.
AI translation and captioning: Sunnyvale, CA provides real-time translation and captioning at
city council meetings. Smart Cities Dive reports growing use of AI captioning tools like Wordly
for public hearings to serve non-English speaking residents. The NLC notes that Dearborn’s AI
translation services have significantly improved information access for its large Arabic-speaking
population.
Open data and civic intelligence: Washington, D.C. piloted DC Compass, a generative AI
assistant integrated with the city’s open data portal, allowing residents to ask questions about
datasets, generate visualizations, and understand neighborhood-level statistics without
specialized technical knowledge.
Equity and Participation
AI-assisted public engagement tools have genuine potential to improve equity by reaching
residents who cannot attend meetings, do not speak English fluently, or are unfamiliar with
government processes. But they can also replicate or amplify existing inequities if deployment is
not thoughtful.
Digital access remains a prerequisite for many of these tools. Residents without smartphones,
reliable internet, or digital literacy may be excluded from AI-mediated engagement channels.
The city should monitor whether AI tools improve participation among historically
underrepresented groups or consolidate engagement among those already most engaged.
Policy Implications for St. Louis Park
• Any resident-facing chatbot should be grounded in authoritative city documents, updated
regularly, and subject to accuracy review before launch and on an ongoing basis.
• AI-generated responses in public channels must disclose AI involvement and provide a
clear path to human review.
• Meeting accessibility tools should be evaluated for translation quality across the
languages most spoken by St. Louis Park residents.
• The city should monitor whether public-facing AI tools improve participation and access
for underserved residents, not only convenient metrics like total interactions.
• All resident-facing AI applications should be included in a public AI inventory.
Section 4: Public Works and Infrastructure Operations
Public works may be the most operationally mature area for municipal AI because the work is
data-rich, repetitive, and highly visible to residents. Streets, sidewalks, snow removal, sewer
systems, waste collection, traffic signals, and resident-reported issues all generate information
that can be used to detect problems earlier, prioritize work more effectively, and improve service
delivery consistency.
The strongest AI applications in public works are not AI replacing staff. They are tools that help
staff convert messy, high-volume real-world inputs—photos, sensor readings, service requests,
inspection notes, and asset data—into structured information that supports better decisions. The
city still needs public works professionals to validate conditions, authorize work, understand field
constraints, and communicate tradeoffs.
Examples from Peer Cities
San José, CA Vehicle-mounted cameras identify potholes (97% accuracy) and trash/debris
(88% accuracy) in real time. The city is expanding the pilot to bike lanes and
sidewalks, and also captures parking violations and lived-in
vehicles—raising surveillance creep concerns.
Memphis, TN AI analyzes video from city vehicles to identify potholes and property blight,
combining footage with existing data sources to predict areas at risk of
urban decay before residents report them.
Eagan, MN A second-ring Twin Cities suburb with 244 centerline miles of streets uses
LiDAR and AI for pavement condition scoring, producing dashboard-ready
condition maps and data downloads for capital planning.
Cranberry Twp., PA A pavement sensor and forecasting system providing localized 72-hour
pavement temperature forecasts saved $160,000 in winter maintenance
costs by reducing unnecessary road salting.
Montreal, Canada AI analyzes dump truck images to verify snow levels and prevent contractor
fraud without capturing license plates or other identifying information.
Seattle, WA Participates in Google’s Project Green Light, using AI and Google Maps
data to identify inefficient signal timings. Early results show potential to
reduce stops by 30% and CO2 emissions by 10%.
Potential Applications for St. Louis Park
For St. Louis Park, the most relevant public works applications would likely be incremental and
workflow-driven rather than large “smart city” transformations. The city’s existing MySLP/Accela
platform, with 17,288 subscribers and over 6,000 service requests submitted since 2014,
provides a foundation that AI can build on rather than replace.
• Converting resident service requests, photos, and notes into standardized categories,
locations, urgency levels, and routing queues.
• Using camera or inspection data to identify potholes, pavement markings, sidewalk
obstructions, illegal dumping, waste overflow, or snow-related conditions.
• Supporting pavement, sewer, and asset-management planning by combining inspection
data, condition ratings, historical repairs, and GIS.
• Helping field staff retrieve internal knowledge, prior work orders, maintenance history,
and standard operating procedures while in the field.
• Summarizing public works trends for staff and Council, such as recurring hotspots,
seasonal patterns, response times, and service-level performance.
Risks and Watch-Outs
Public works AI can appear operationally low-risk but still raises serious governance questions.
Surveillance creep is a particular concern: the same camera network used for pothole detection
can be repurposed for monitoring people, encampments, or behavior. Equity in service
prioritization is another: AI trained on complaint data may systematically underserve
neighborhoods with lower reporting rates. And AI outputs should always be treated as signals
for human review, not final determinations—false negatives in public safety contexts can miss
genuine hazards.
Policy Implications for St. Louis Park
• Continue starting with defined operational problems. Attach AI to specific service
goals—faster pothole identification, improved snow response, better asset
planning—rather than deploying speculatively.
• Prioritize integration before automation. If resident reports, work-order systems, and GIS
are disconnected, AI will add complexity rather than reduce it.
• Require human review for any consequential action. AI can flag, sort, summarize, or
recommend; it should not independently authorize repairs, enforcement, or billing
decisions.
• Draw clear surveillance boundaries. Establish policy on what camera networks can and
cannot be used for, and require Council approval before expanding use cases.
• Measure service equity. Evaluate AI tools by neighborhood-level response times,
complaint resolution rates, missed issues, and whether benefits are distributed fairly.
Section 5: Planning, Zoning, and Permitting
Planning, zoning, and permitting are among the most promising municipal AI use cases
because the work is complex, document-heavy, rules-based, and highly consequential.
Residents, builders, developers, board members, and elected officials must navigate zoning
ordinances, building codes, application requirements, site plans, variances, setbacks, design
standards, and public hearing processes. These systems are difficult for non-experts to
understand, and delays can affect housing production, economic development, and resident
trust.
AI can help by searching large bodies of rules, identifying missing documents, summarizing
applications, comparing submissions against requirements, and providing clearer guidance to
applicants and staff. The strongest use case is not having AI approve development; it is using AI
to reduce avoidable back-and-forth, improve completeness at submission, and help staff focus
on judgment-heavy issues.
Examples from Peer Cities
Hamilton, ON AI-assisted site plan review for non-profit development projects produced a
60% decrease in review days and 70% decrease in overall processing time.
Kelowna, BC Building permit chatbots launched in 2023 guide homeowners and builders
through permit applications, reducing routine staff questions and extending
service to evenings and weekends.
Austin, TX Beta-testing an AI Pre-Check tool for residential zoning review, allowing
applicants to identify zoning compliance issues before formal submission.
Honolulu, HI CivCheck helps applicants verify code compliance, permitting requirements,
and required documents before submission, reducing review cycles.
Sacramento, CA AI roadmap identifies electronic plan check as a near-term priority to
automate code compliance and design validation.
Los Angeles, CA Planning Department uses AI to analyze land use and zoning data to
proactively identify issues during the permit review process.
Potential Applications for St. Louis Park
The most relevant near-term applications fall into four categories:
1. Applicant self-service. AI can help residents, small businesses, and property owners
understand basic rules such as setbacks, fences, accessory dwelling units, signage, and
parking—and help them determine whether a permit is likely needed—outside of business
hours. Tools must cite authoritative ordinances and provide links to current sources.
2. Submission completeness checks. AI can review application packages for missing
documents, incomplete fields, conflicting information, or obvious inconsistencies before staff
begins formal review.
3. Staff copilots. AI can help staff summarize application materials, prior permits, property
history, relevant ordinances, variances, and public comments, reducing administrative time while
preserving staff judgment.
4. Policy and scenario analysis. AI can help staff, boards, and Council summarize how peer
cities handle zoning questions, identify common ordinance language, or model high-level
implications of proposed zoning changes.
Risks and Watch-Outs
Planning and zoning AI carries higher governance risk than public works triage because
land-use decisions affect property rights, housing, and neighborhood change. Due process and
transparency require that residents and applicants understand how AI was used in any decision
affecting them. Incorrect legal interpretation by a chatbot or copilot can cause residents or
applicants to spend money, delay projects, or misunderstand their rights. And tools trained on
historical permitting data may perpetuate patterns of unequal access or enforcement.
A specific technical risk worth noting: applicants could embed hidden or misleading text in PDFs
or plan documents to attempt to manipulate AI summaries or reviews. This “prompt injection”
risk is a real procurement and security consideration for any document-review AI tool.
Policy Implications for St. Louis Park
• AI should not make binding land-use decisions. Staff, boards, commissions, and Council
remain accountable for interpretations, recommendations, and approvals.
• AI-generated guidance should cite current ordinances, city webpages, application forms,
and relevant policies. Residents must be able to verify the source of any guidance they
receive.
• Residents and applicants should always have a path to human review. AI should make
the process easier, not create a barrier that residents cannot understand or challenge.
• The city should preserve records of AI use in planning and permitting decisions
consistent with public records requirements.
• Continue using and strengthening procurement guidelines. They should require vendors
to explain what data the tool uses, how it interprets city rules, how often it is updated,
and how the city can test for errors.
• Performance metrics should include application completeness, number of correction
cycles, total review time, applicant satisfaction, and equity of access across applicant
types.
Section 6: Looking Ahead — Agentic AI and the
Evolving Landscape
The AI use cases described in this white paper are largely assistive: AI that flags, summarizes,
translates, or classifies information for human review. The next wave of AI technology—already
emerging in enterprise and government contexts—is agentic AI, in which multiple AI agents
work together to automate and coordinate multi-step tasks with minimal human intervention at
each step.
What Agentic AI Means for Cities
The National League of Cities describes agentic AI this way: “Agentic AI can coordinate the
actions of several business processes, from checking applications for errors or missing
information to validating plans and generating compliance reports and then notifying applicants
of approvals and collecting applicable fees.”
In practical terms, agentic AI could eventually handle workflows that today require multiple staff
handoffs: receiving a permit application, checking it for completeness, routing it to the
appropriate reviewer, generating a compliance checklist, sending the applicant a status update,
and processing payment—all without human intervention at each step.
This is not science fiction. Agentic AI capabilities are being built into enterprise platforms today,
and cities that have strong data foundations and well-defined workflows will be first in line to
benefit. But the governance implications are significantly greater than for assistive AI, because
agentic systems can take consequential actions on behalf of the city without a human reviewing
each one.
Implications for St. Louis Park
The Commission does not recommend that St. Louis Park deploy agentic AI broadly in the near
term. However, the city should be aware of this trajectory and begin laying the governance and
data foundations that will make responsible agentic adoption possible when the time comes.
Specifically, this means:
• Establishing clear workflow documentation so that any AI system—agentic or
otherwise—can be configured against defined, auditable processes rather than informal
practices.
• Ensuring that AI governance frameworks explicitly address autonomous action: under
what circumstances can an AI system take an action without human review, and who
bears accountability when it errs?
• Maintaining a human-in-the-loop requirement for all decisions that affect resident rights,
benefits, or obligations until the city has sufficient experience, audit capability, and public
trust to consider exceptions.
• Watching peer cities that are piloting agentic workflows in lower-stakes
contexts—scheduling, document routing, status notifications—to learn from their
experience before adopting similar tools.
External Resources and Learning Networks
St. Louis Park does not need to navigate this landscape alone. The following networks and
resources provide valuable guidance, peer learning, and policy models:
National League of Cities (NLC). NLC’s AI in Cities Report and Toolkit, City AI Governance
Dashboard, and AI Policy Dashboard provide case studies, readiness assessment tools, and
examples of city AI policies from across the country.
League of Minnesota Cities (LMC). LMC has published guidance on AI use consistent with the
Minnesota Government Data Practices Act, and its frameworks for data classification and risk
management are already referenced in St. Louis Park’s internal guidelines.
MNIT (Minnesota IT Services). MNIT guidance on AI risk classification and data governance
provides a state-level framework that St. Louis Park can align with.
Bloomberg Philanthropies / City AI Connect. A global learning community for cities exploring
generative AI in public services, providing peer exchange, expert access, and a shared
resource hub.
AI4Cities (European). A collaborative project involving Helsinki, Amsterdam, Copenhagen,
Paris, Stavanger, and Tallinn using pre-commercial procurement to develop AI solutions for
mobility and energy, offering useful models for collaborative AI procurement.
Global Observatory of Urban Artificial Intelligence (GOUAI). Supported by UN-Habitat,
GOUAI maintains the Atlas of Urban AI, a repository of ethical AI initiatives and projects from
cities worldwide.
Conclusion: Toward an AI-Compatible City
The question this white paper set out to answer is how cities need to adapt to become
AI-compatible—not just technically, but in terms of governance, culture, and policy. The
Commission’s answer, drawn from peer city experience and national guidance, is that AI
compatibility is less about adopting any particular technology and more about building the
underlying conditions that make AI trustworthy and useful.
Those conditions include: clean, integrated data that AI systems can act on reliably; clear
governance structures that assign human accountability for every AI system; staff and elected
officials who understand both the capabilities and the limitations of the tools they use;
procurement practices that require vendors to be transparent and auditable; and a commitment
to measuring whether AI improves service equity, not only efficiency.
St. Louis Park has a meaningful foundation for this work: it has internal generative AI guidelines,
a standard AI vendor questionnaire, proposed additional AI investment for 2027, and a
Community Technology Advisory Commission actively engaged in these questions. The work
ahead is to extend and deepen that foundation—incrementally, measurably, and with residents
at the center.
The Commission recommends that the city:
• Formalize a public AI inventory and governance process, requiring council review and
public feedback for any AI tool that affects resident rights or services.
• Evaluate AI readiness (data quality, workforce capability, system integration, and
cybersecurity posture) and compare proposed AI uses with simpler, less costly, more
transparent tools before adopting new AI tools in any department.
• Prioritize internal productivity tools like Microsoft Copilot and low-risk pilot applications
linked to defined problems in the near term, using those experiences to build institutional
knowledge before moving to higher-stakes use cases.
• Require appropriate human review, public-facing transparency, and equity measurement
for AI uses that can materially affect residents, with ongoing performance monitoring.
• Stay connected to the NLC, LMC, and peer city networks to monitor how the
technology—and the governance approaches to it—continue to evolve.
An AI-compatible city is not one that uses AI everywhere, but one that knows when AI
adds value, when it does not, and how to govern it when used. By investing in
governance, data, and human capacity, St. Louis Park can use AI selectively to deliver
more efficient, equitable, and transparent services.
Appendix: Key Resources and References
National and State Guidance
• National League of Cities — AI in Cities: Report and Toolkit (2024)
• National League of Cities — City AI Governance Dashboard:
nlc.org/resource/city-ai-governance-dashboard/
• National League of Cities — Use AI to Transform City Operations (2025):
nlc.org/article/2025/07/31/use-ai-to-transform-city-operations/
• League of Minnesota Cities — AI guidance aligned with Minnesota Government Data
Practices Act
• MNIT — Minnesota AI risk classification guidance
• NIST AI Risk Management Framework: nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf
Peer City Policy Documents
• City of Seattle — Generative Artificial Intelligence Policy
• City of Boston — Interim Guidelines for Using Generative AI (2023)
• City of San Jose — AI Handbook / Digital Privacy Office (2024)
• City of Tempe — Ethical Artificial Intelligence Policy (2023)
• City of Lebanon, NH — AI Registry
• New York City — Artificial Intelligence Action Plan (2023)
• City of Chattanooga — AI Prompt Library
Selected Case Study Sources
• Sacramento 2025–2028 AI Strategy and Roadmap
• Hamilton, ON — Bloomberg Harvard City Program All4One Pilot
• APWA / Eagan, MN — AI for Pavement Assessment Case Study
• Google Research — Project Green Light: sites.research.google/greenlight/
• Bloomberg Philanthropies / Johns Hopkins — City AI Connect: cityaiconnect.jhu.edu
• Global Observatory of Urban Artificial Intelligence — Atlas of Urban AI:
gouai.cidob.org/atlas/
• Eurocities — Algorithmic Transparency Standard: algorithmregister.org
This white paper was prepared by the St. Louis Park Community Technology Advisory
Commission. It draws on publicly available municipal policy documents, the NLC’s AI in Cities
Report and Toolkit, the Sacramento and Hamilton AI strategy documents, and reporting from
Government Technology, Smart Cities Dive, and other municipal technology publications.