Loading...
HomeMy WebLinkAbout2026/09/23 - ADMIN - Agenda Packets - Community Technology Advisory Commission - Regular Community technology advisory commission meeting September 23, 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 – Aug. 19, 2026 3. Presentations - none 4. Business a. Recap Sept. 14 annual meeting with city council (10 minutes) b. Signal items (30 minutes) i. Exploration: ALPRs and data centers ii. Review: Drones as first responders, data privacy iii. October signal assignments c. Review final AI whitepaper (10 minutes) 5. Communications and announcements (5 minutes) a. Staff b. Commission members 6. Adjournment Future meeting/event dates:  Oct. 21, 6 p.m., regular meeting  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 August 17, 2026 6 p.m. Community technology advisory commission Minutes Present: Commission Member Slaats (Chair), Commission Member Dyer (Vice Chair), Commission Member Bulliner, Commission Member Keogh, Commission Member Straus, Commission Member Reid Anderson, Commission Member Elsa Anderson (Youth Member), Ms. Smith (Staff Liaison), Council Member Jim Engelking (Council Ambassador) Absent: Commission Member Stautz, School District Liaison Marble Prior to the formal call to order, members introduced themselves to Council Member Jim Engelking, who was present in his new role as City Council Ambassador to the Commission. 1. Call to order – roll call It was moved by Commission Member Slaats, seconded by Commission Member Dyer, to call the meeting to order at 6:04 p.m. The motion passed. Council Member Engelking introduced himself as a retired IT consultant serving Ward 2, and the newly assigned ambassador to the Commission through the City Council's ambassador program. He explained that the program was created to improve the flow of information between advisory commissions and the City Council. He noted that the Council has members with varying levels of technical background and expressed that he sees strong opportunity for the Commission to provide strategic policy guidance, including helping Council members understand what questions to ask when technology decisions arise. He cited license plate reader technology as an example of a high-interest topic among his constituents. Commission Member Slaats noted that the Commission has been working to shift its focus from a tactical, staff-augmenting role toward a more strategic policy-advisory function and that Council Member Engelking's perspective aligned well with that direction. 2. Approval of minutes – July 15, 2026 It was moved by Commission Member Slaats, seconded by Commission Member Bulliner, to approve the minutes of the July 15, 2026 meeting. The motion passed. 3. Presentations – none 4. Business a. Review submitted signal items Commission Member Slaats introduced the Commission's new signals process, explaining that signals are emerging topics members identify as potentially relevant to the City Council. He outlined four evaluative questions for each signal: what is happening, why it might matter to St. Louis Park, what policy or strategic question it could raise for Council, and how the Commission might be useful. Signal: AI Use in Schools (submitted by Commission Member Elsa Anderson) Commission Member Elsa Anderson presented her signal on artificial intelligence use in schools. She described a growing disconnect between students using AI tools and teachers struggling to keep pace with guidelines and expectations. She noted that this tension was intensifying and would likely become more prominent in the coming school year. She acknowledged uncertainty about whether this was a school board or city council matter. Commission Member Dyer noted that the school board is a separate entity with jurisdiction over curriculum and suggested that if the Commission explored the topic further, findings could be shared with Council who might then pass them along to the school board in an advisory capacity. Council Member Engelking described an existing parent community group in St. Louis Park focused on finding the appropriate balance between digital and traditional learning. He also raised the broader issue of screen time across all age groups and suggested the city could explore initiatives to promote in-person interaction. Commission Member Keogh drew a connection between the signal and the theme of over- reliance and declining quality of work, noting that this concern appears across both school and government technology use. She suggested that AI presents a particular challenge in educational settings because school is fundamentally about developing one's own thinking. Commission Member Bulliner suggested taking a holistic view of how AI education could be communicated to the broader community, including through parks and recreation programs, and recommended the signal be retained. Commission Member Keogh suggested that boosting AI literacy among residents would benefit the community broadly and that the city could explore what programming or resources it might offer. Commission Member Elsa Anderson suggested the city could provide an accessible online resource on AI for teachers and community members in professions where AI has developed faster than people can keep up. Commission Member Stautz also recommended that while the school-specific aspect of the signal may be too narrow for the Commission's jurisdiction, the broader AI trend it represents could be absorbed into other signals and explored collectively. Commission Member Slaats agreed and moved to hold the signal for future consideration, noting that it connects well to the AI white paper discussion. Next steps: Commission Member Slaats summarized that the signals process would continue to be developed and that signals would be accumulated over time. He noted that Commission Member Keogh and he had also submitted signals that would be taken up in future meetings. September signal assignments: No formal signal assignments were made at this meeting. The Commission agreed to continue building its signal backlog and to revisit assignments at a future meeting. b. Review AI Whitepaper Commission Member Slaats opened discussion of the Commission's AI white paper, intended as guidance for the City Council and senior city leadership on artificial intelligence policy considerations. Commission Member Bulliner recommended that the white paper include a more formal definition of artificial intelligence and distinguish between its various forms, such as generative AI, agentic AI and computer vision applications. He noted that without a defined scope, the term becomes too broad to be actionable. Commission Member Keogh praised the section providing broad policy questions for evaluating AI tools. She emphasized that AI should be framed as a tool to solve a problem rather than a goal in itself, and that this message should be made explicit for council members who may be less familiar with technology. She noted that AI products are not deterministic and therefore require a different evaluative approach than standard software. Commission Member Reid Anderson offered overall positive feedback on the document and echoed questions about two specific recommendations: the AI readiness assessment and the equity measurement framework. He noted that both are important concepts but that the white paper does not clearly define what the output of either would look like. Commission Member Straus suggested that the equity measurement recommendation could be treated as policy guidance to consider equity at the decision-making level while leaving implementation details to individual use cases. He also recommended adding a self-education component to the recommendations, emphasizing that decision makers who have not personally engaged with AI tools may not fully absorb the paper's content. Commission Member Straus further proposed that the executive summary be strengthened to serve as a standalone takeaway for readers who may not engage with the full document. He suggested the summary could be structured to highlight the most critical points regardless of the reader's prior AI experience. Commission Member Bulliner noted that references to how other cities are using AI are a strength of the document because the white paper's purpose is to prompt new thinking rather than provide definitive answers. Ms. Smith offered staff perspective, noting that the city has taken meaningful steps on AI governance. She referenced internal generative AI guidelines for staff adopted a couple of years ago, a set of vendor questionnaire questions specifically addressing AI use including data storage and whether generative AI is used, and a recent budget request to implement Microsoft Copilot within the government cloud as a controlled environment for employee AI use. She encouraged the Commission to acknowledge these existing efforts in the white paper so the Council understands the city is not starting from zero. Commission Member Straus suggested that some of these existing practices could be highlighted in the executive summary to demonstrate St. Louis Park's competency and to reassure readers that responsible practices are already in place. Commission Member Dyer recommended explicitly calling out the vendor due diligence process as a highlighted practice. Commission Member Keogh raised the broader question of public trust and data governance, referencing the example of third-party data platforms that aggregate city data and make it available for commercial resale. She suggested that as AI and data tools expand, the city may want to consider when and how to engage residents before significant technology contracts are executed. She noted that some cities have proactively involved residents in conversations about data use. Council Member Engelking described a deep dive he and another council member conducted into the Flock license plate reader system, including questions about data security and storage. He noted that while the answers were reassuring, many constituents expressed a desire to ask those questions directly of the police department. He observed that constituent appetite for direct engagement on technology decisions is significant. Commission Member Keogh raised the question of whether the city has a public feedback mechanism before technology contracts are signed, and whether an evolving data governance model might be worth exploring. Ms. Smith acknowledged that most technology contracts do not reach the council approval threshold and therefore do not have a structured public input stage. She noted that larger contracts do go before the council and are visible in public meeting packets. She also shared that the city is undertaking a broader data governance project for internal data. Council Member Engelking mentioned that the City Council has a study session scheduled for September 28, 2026, to examine drone technology, which he noted will raise similar privacy and policy questions. Commission Member Straus noted that he had planned to submit signals on both drones and Flock cameras and saw an article where Ms. Smith was quoted on the license plate reader topic, which he described as a positive indicator of the city's engagement on these issues. Commission Member Slaats summarized feedback and proposed the following revisions to the white paper: add a formal definition distinguishing types of AI; emphasize that AI is a tool not universally appropriate for every situation; add attribution identifying the Commission as authors; clarify the AI readiness assessment recommendation; address the equity measurement question at the policy level while deferring implementation specifics to use cases; add a self- education recommendation for decision makers; beef up references to what the city is already doing on AI governance; and revise the language around the council review recommendation to include the option of public forums for AI tools that affect resident rights or services. c. Prep for Sept. 14 annual meeting with city council Ms. Smith confirmed that Commission Member Slaats and Commission Member Dyer would lead the presentation to the City Council at the September 14, 2026, annual study session. She noted that all commission members are welcome to attend and that the Commission has approximately 30 minutes. She indicated she would revise the work plan summary slides including updating the white paper projecctc status to reflect that it is in progress. Commission Member Straus suggested presenting the executive summary content at the meeting rather than submitting the full document in advance, as a live summary would be more likely to generate engagement from council members with varying levels of interest in reading longer documents. Commission Member Keogh agreed and observed that a presentation format similar to one recently delivered to the Council by another body generated productive back-and-forth conversation. She noted that a brief presentation on key AI considerations could be particularly effective given that technology may not be in every council member's area of expertise. Council Member Engelking recommended that the presenters introduce each commission member in attendance at the start of the presentation. He also suggested the Commission describe its signals process as part of the presentation, both to help Council understand how the Commission generates work and to open the possibility of Council submitting signals of its own. He further suggested the Commission offer a foundational technology primer to the Council, a brief educational session covering how technology works and what types of questions elected officials should be asking about technology the city is proposing to implement. Commission Member Slaats responded positively to the primer idea and noted it builds on feedback the Commission received at the previous annual meeting, when Council members expressed uncertainty about where to start on technology topics. Commission Member Slaats indicated that the presentation would also address the work plan item on assessing the city's customer response management tool. He noted that with a former commission member's departure that work had stalled and that the Commission had discussed repivoting the question to a broader strategic framing around what principles the city should use to determine whether a resident-facing digital service provides sufficient public value. He recommended presenting that reframe to the Council rather than striking the item. Commission Member Keogh agreed that reframing the question would be more meaningful and noted that Council would likely not remember the original item in detail. 5. Communications and announcements Ms. Smith announced that the city's new website design will launch in the coming weeks. She clarified that the update is primarily a refresh focused on accessibility, mobile responsiveness and improved search functionality rather than a full redesign. Commission Member Slaats raised the question of whether the September 16, 2026 regular meeting should be moved given its proximity to the September 14 City Council study session. It was moved by Commission Member Bulliner, seconded by Commission Member Straus, to move the September 16, 2026, meeting to September 23, 2026. The motion passed. Council Member Engelking expressed enthusiasm for the ambassador role and noted his intention to attend more frequently than the minimum required commitment. He acknowledged that the program is new and that the role will evolve, and invited feedback from the Commission if his participation begins to look more like that of a committee member than an external liaison. 6. Adjournment It was moved by Commission Member Slaats, seconded by Commission Member Straus, to adjourn the meeting. The motion passed and the meeting was adjourned at 7:20 p.m. These minutes were created with the assistance of a generative AI transcript service, then edited and finalized by a city staff person. Konnor Slaats - 9/14/26 city council meeƟng takeaways These are notes only and are not the official record of the council meeƟng.  Brausen: like the working model. Personally interested in data centers. o Nobody’s proposed one in SLP, but might be one worth talking with environmental/sustainability commission, whether net gain is worth the investment o Keller: the planning commission would also have a role in this. Would want a nuanced approach to what data storage would look like. o You can’t have AI without data centers. But do we need AI right away? Will AI kill us? Are data centers worth the resources you put into them? o Brausen: what’s the basic educaƟonal level? What’s the resource drain? o Are they an absolute necessity? Is it a risk?  Baudhuin: another one: ALPR technology. Was a great study session on this, but it’s disƟnctly technological. How are we viewing that? o There’s a disƟncƟon between Flock and ALPR, focus on broad view of the technology and security issues that come along with it. Also how different companies have different levels of security. o Bashore: diƩo, interested in that.  Bashore: also data privacy pracƟces. What are some of the best pracƟces we should be taking to ensure security/privacy/safety? Can we do some research and make some recommendaƟons? o Brausen: some of it is determined by Legal. Would we need to do in coordinaƟon with city aƩorney? o Mayor Mohamed: expanding to data privacy would be great, important.  When she imagines council/advisory relaƟonship, she imagines it like that—with liƩle fingerprints all over things the city is working on. What’s happening? Automated license plate readers (ALPRs) are becoming an increasingly important part of law enforcement technology in the Twin Cities. St. Louis Park has used stationary Flock ALPR cameras since 2023, in addition to mobile ALPR use in police vehicles. The system records images of passing vehicles along with the time, date, and camera location, and compares plates against law-enforcement “hot lists.” St. Louis Park currently retains ALPR data for 30 days and has restrictions on access, data sharing, and use for immigration enforcement. (St. Louis Park) Recent reporting by the Star Tribune raises a broader question about the governance of these systems. An investigation found that law-enforcement agencies, including agencies working with Immigration and Customs Enforcement (ICE), had searched Flock camera data collected by Twin Cities suburbs for immigration-related purposes. Several cities subsequently restricted access to their systems. In April 2026, St. Louis Park stopped sharing ALPR data with departments that collaborate with ICE, and the city has since emphasized that its system cannot be used for immigration enforcement. (Star Tribune) St. Louis Park has already considered many of these issues. At an April 2026 council study session, council reviewed ALPR deployment, data protections, inter-agency sharing, and auditing. Council supported maintaining the program while ending data-sharing agreements with agencies participating in federal 287(g) immigration-enforcement agreements. Council also supported making audit information available outside the police department and increasing public education about how ALPRs operate. (Laserfiche) Why might this matter to Council? ALPRs illustrate a broader technology-governance issue: the risks associated with a technology may depend not only on how the city operates it, but also on how data can be accessed, shared, or repurposed by other organizations. St. Louis Park has established safeguards including required law-enforcement purpose codes, logging and auditing of searches, restrictions on external agencies, 30-day data deletion, and technical controls blocking immigration-purpose searches. The city also states that its ALPR data is not shared with federal agencies or agencies that have immigration-enforcement agreements with ICE. (St. Louis Park) The recent experience of neighboring communities suggests that continued attention may be warranted as Flock and similar systems expand. The relevant question may not be whether St. Louis Park should have ALPRs, but whether its governance, transparency, auditing, and data-sharing practices remain appropriate as the technology and regional ALPR network evolve. What policy or strategic question could this eventually create for Council? What ongoing governance and transparency practices should St. Louis Park maintain for ALPR technology to ensure that its data is used only for authorized purposes, particularly when data may be accessed by other law-enforcement agencies? Why might CTAC be useful? CTAC could help monitor emerging ALPR governance practices and compare St. Louis Park’s approach with peer cities, particularly around data sharing, auditing, retention, transparency, and vendor capabilities. A potential exploration could identify a small set of governance principles for surveillance and data- collection technologies that could apply beyond ALPRs. This could complement the Commission’s existing interest in responsible data stewardship and surveillance creep. Alternatively, because St. Louis Park has already undertaken a substantial policy review and implemented several safeguards, CTAC could simply continue to watch developments rather than initiate additional work at this time. September 2026 Signal - DFR - Straus What’s happening? Drone use by Minnesota law enforcement is expanding, with several Twin Cities departments moving toward Drone as First Responder (DFR) programs. These systems can send a drone to certain 911 calls ahead of officers, providing live video and potentially helping determine what response is needed. Minnetonka launched Minnesota’s first DFR program in 2025, and Edina and Bloomington have been testing or evaluating similar systems. (Star Tribune) St. Louis Park already uses drones for police operations, including assisting with searches. The larger trend is therefore less about whether SLP should have drones and more about how the city should govern their use as the technology becomes more capable and more routinely integrated into public safety. There is also a useful statewide dataset for understanding this trend. Minnesota law requires law- enforcement agencies using UAVs to report their warrantless deployments, dates, authorized uses, and total program costs to the BCA. The BCA publishes the data annually. In 2024, 119 agencies reported 6,603 warrantless UAV uses, up 50% from 2023, with total program costs of $1.97 million, up 85%. (DPS Assets) Why might this matter to Council? DFR technology could provide real public-safety benefits: faster situational awareness, improved officer safety, and potentially fewer unnecessary officer dispatches. But increasing use also raises questions about how frequently drones are deployed, what they capture, how long data is retained, and whether uses expand beyond the purposes for which the program was originally established. The BCA reporting requirement provides an opportunity to evaluate these questions with actual data rather than speculation. What policy or strategic question could this eventually create for Council? As drone technology becomes more widely used in public safety, what governance and transparency practices should St. Louis Park use to ensure that the benefits of the technology are balanced with privacy and community-trust considerations? Why might CTAC be useful? CTAC could compare St. Louis Park’s drone use with peer cities using the BCA’s publicly available data, including deployment frequency, authorized uses, and program costs. It could then examine how communities such as Minnetonka, Edina, and Bloomington are approaching newer DFR capabilities. This could help answer a narrower question: Should SLP’s existing drone governance be updated as the technology and regional use evolve, or is the city’s current approach sufficient? The growing importance of AI- and data-driven technology in city technology means that responsible data stewardship is becoming core to good, transparent governance.City government plays a critical role in re-establishing trust in government overall. If residents do not trust how their data is handled by the city, it leads to more distrust in government and overall dissatisfaction. Common solutions used by cities, especially in the surveillance/policing space, gather and share more data than ever with outside parties. Once data is collected by these sources, how the data is used & accessed can be a black hole or pose a risk to the safety of the community, depending on who gets access to the data. However, some cities take a community-centered, transparent approach to solutions that gather & process resident data, which both mitigates risk of data misuse, unwarranted surveillance, and improves community trust. Trends ● Privacy/security concerns ○ Flock: West St Paul, Burnsville, Duluth, Isanti county all have ended or chose to not enter into an agreement with Flock, citing privacy concerns & spuriousness about Flock’s behavior as a vendor partner ○ Unwarranted/rampant usage of data by ICE during the federal invasion to intimidate observers and community members - sourced from tools such as Accurint ○ Backlash against Skydio drones in minneapolis ● High-profile problems lead to distrust of AI-driven systems, wasting community resources and underscoring the need to build trust through other mechanisms ○ 1.4 billion bad notifications a month lead to unnecessary traffic stops or effort ○ Flock: LA saw massive accuracy issues, leading them to end their pilot ○ Plymouth man pulled over by four cops due to a plate read error ○ Tennessee woman wrongfully jailed for six months based on AI facial recognition Potential policy question: How should St Louis Park evolve its data usage & sourcing practices to achieve its strategic vision, particularly around good governance & creating a welcoming, safe community? CTAC could: ● Propose a framework for gathering resident input to study the topic further ● Investigate strategies, principles, and risks for current & future resident-facing technology and data collection Sources: https://www.govtech.com/transportation/for-cities-collecting-visual-data-brings-privacy-concerns 䅵杵獴 https://www.brookings.edu/articles/how-citizens-and-local-governments-can-advance-data-drive n-policymaking-together/ https://mcity.umich.edu/wp-content/uploads/2023/03/Privacy-Frameworks-for-Smart-Cities_Whit e-Paper_2023.pdf 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 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. August 2026 Signal from Konnor Slaats https://www.lmc.org/news-publications/magazine/july-august-2026/letter-of-the-law-july-2026/ What’s happening? The League of Minnesota Cities ’July–August 2026 guidance says information entered into AI systems, AI-generated outputs and associated system data may qualify as government data under the Minnesota Government Data Practices Act. It warns that putting nonpublic information into third-party AI tools could constitute a data breach and that prompts or outputs may need to be retained, searched and disclosed. Why might this matter to council? SLP already has a GenAI use policy that prohibits use of medium-to-high risk data in GenAI tools (March 18 packet). SLP also already urges compliance with the Minnesota Government Data Practices Act, which the League article is referencing. Is the League guidance going further by saying all inputs/outputs may be government data and need to be tracked? Is that something SLP and other cities are tracking today, or are they just tracking final outputs? What policy or strategic question could this eventually create for Council? Does the city’s current approach account for prompts, input histories, intermediate outputs, and other AI system data, or primarily final documents? If the city’s current policy covers these, this signal may not require further action. If a gap exists, Council could eventually consider whether the city needs clearer standards for retaining, retrieving, and classifying AI-related records. Any policy change would likely be narrow. Why might CTAC be useful? CTAC could help if staff identifies an unresolved policy question. Potential work could include comparing how peer cities treat prompts, intermediate outputs, and AI metadata under public- records requirements. Otherwise, the League guidance could validate St. Louis Park’s existing approach rather than justify additional CTAC work. From Konnor Slaats, July 15, 2026: I reflected on our work plan and progress since our Council meeƟng last April, especially as we prepare to welcome several new members. I’ve been thinking about how we could build on our exisƟng working structure and create a more consistent cycle of discussion and output that Council finds valuable. I’m wondering if we could pilot some documented working norms for the remainder of the year. This is similar to how we’ve operated over the past year, but with clearer stages and expectaƟons. Because technology quesƟons likely won't arrive as clearly defined asks from Council, I think CTAC can serve as both a technology-sensing and advisory body: idenƟfying emerging issues, framing the quesƟons that may eventually maƩer to Council, and then focusing our deeper work on a small number of validated prioriƟes. At a high level: Commissioners surface signals → CTAC frames potenƟal quesƟons → Council validates and prioriƟze major work → a small number become acƟve advisory projects. For Signals, ExploraƟon, and acƟve work, commissioners would route them through the staff liaison for advance distribuƟon and pre-reading. Stage 1 (Signals): commissioners periodically bring forward a short, half-page summary of technology- related work they think CTAC should be aware of like:  Emerging technology trends  Something a peer city is doing  Emerging policy or resident-impact quesƟon The summary would answer:  What's happening?  Why might this maƩer to St. Louis Park?  What policy or strategic quesƟon could this eventually create for Council?  Why might CTAC be useful? In-meeƟng, we'd spend no more than 10-15 minutes discussing these items and decide to watch, explore, or close them. Items worth watching could remain on a simple backlog for the future. We could try rotaƟng responsibility so 2 commissioners bring signals monthly and adjust the approach over Ɵme. Stage 2 (ExploraƟon): CTAC decides that a signal needs more invesƟgaƟon, so one or two commissioners do a limited amount of research to answer: is there a meaningful and ac Ɵonable quesƟon here? The output would be no more than one page, with the primary goal of framing a clear problem statement. For example: "What principles should SLP use to determine whether a resident-facing digital service provides sufficient and disƟnct public value?" Checkpoint: before recommending deeper work, we check against four criteria  Is there a real public or city decision underneath it?  Does CTAC add something that staff might not naturally provide?  Is this appropriately strategic rather than operaƟonal?  Will this be relevant to Council or another commission QuesƟons that pass this test could be added to the exisƟng backlog as high-potenƟal future work. We could then periodically bring the highest-priority quesƟons to Council (through our annual check-in, or through the formal communicaƟon process) to understand which quesƟons Council would find most valuable for CTAC to pursue. Stage 3 (AcƟve work): AcƟve work would have a clear problem statement, a deliverable, a target date, a lead commissioner and contributors. The output would vary depending on the quesƟon. Some might warrant larger advisory papers, while others may only need a short briefing or response. For a large project, I think we can use a model similar to what we're doing:  One lead/editor: keeps the work moving by outlining the content, integrates the final product, idenƟfies key decisions. They can create some content but shouldn't be expected to do nearly all of it.  Two or three contributors: each own a defined slice of research or analysis Stage 4 (Approval and compleƟon): Full commission can criƟque, debate, and approve the final version to send to Council. Across a three-year term, this would let commissioners rotate through different roles and give us a more formal structure. I would expect us to have only one or two substanƟal projects at a Ɵme, but the exact number and team structure could flex based on the work and commissioner capacity. Board and Commission Annual work plan Presented to council: September 14, 2026 Approved by council: 1 2026 work plan │ Communications and Technology Commission 1 Initiative name: Support citywide Vision 4.0 process Initiative type: ☒ Staff support (review project, policy or program and provide feedback) ☐ Independent research project ☐ Gather community feedback ☐ Lead community event Initiative origin: ☐ Applicant-initiated ☒ Staff-initiated ☐ Commission-initiated ☐ Council-initiated Legally required (e.g. response to Legislative changes or Judicial decisions)? ☐ Yes ☒ No Commissioner lead(s) name(s): None, all will be involved. If joint commission initiative, list other board or commission: Is this an established work group? ☐ Yes ☒ No Initiative description: Support the citywide Vision 4.0 process by participating directly and/or encouraging others to participate, and by sharing information with other community members about the process. Strategic Priority: ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☒ 5 ☐ N/A Deliverable: ☐ Research report ☐ Summary of community input ☒ Other ☐ N/A Target completion date: 3Q 2025 This section to be completed by staff: Council request (if applicable): ☐ Review and comment or reply ☐ Review and decide ☒ Informational only – no response needed Budget required: None Staff support required: Communication from staff liaison about opportunities with Vision 4.0 Liaison comments: Plan to keep the commission informed about opportunities to assist with the citywide Vision 4.0 process.  Commission members received information from the community engagement coordinator throughout the Vision 4.0 process, including invites to participate in surveys and to host community meetings. Board and Commission Annual work plan 2  Commission member Benjamin Straus hosted a community meeting at his apartment complex.  Commission members reviewed the Dec. 8, 2025, Vision 4.0 council report presented to the city council, to inform CTAC additional workplan goals for 2026. 2 Initiative name: Participate in city website redesign review process Initiative type: ☒ Staff support (review project, policy or program and provide feedback) ☐ Independent research project ☐ Gather community feedback ☐ Lead community event Initiative origin: ☐ Applicant-initiated ☒ Staff-initiated ☐ Commission-initiated ☐ Council-initiated Legally required (e.g. response to Legislative changes or Judicial decisions)? ☐ Yes ☒ No Commissioner lead(s) name(s): None, all members or a small group will be involved. If joint commission initiative, list other board or commission: Is this an established work group? ☐ Yes ☒ No Initiative description: While the exact process for the redesign has yet to be determined, we plan to draw on the expertise of the CTAC by involving members, or a small group of members, in potential user group testing or other review of a draft redesign of the city website. Strategic Priority: ☒ 1 ☐ 2 ☐ 3 ☐ 4 ☒ 5 ☐ N/A Deliverable: ☐ Research report ☐ Summary of community input ☒ Other ☐ N/A Target completion date: 3Q 2025 This section to be completed by staff: Council request (if applicable): ☐ Review and comment or reply ☐ Review and decide ☒ Informational only – no response needed Budget required: None Staff support required: Staff liaison Liaison comments: The primary goals of the redesign are to ensure compliance with upcoming ADA requirements, ensure mobile accessibility and improve search function. CTAC will be asked to focus on these items in its review.  CTAC members Konnor Slaats and Kayla Stautz each participated in one of two user experience workshops Sept. 9 and 11, both two hours each. Both were provided with recordings of the workshop they didn’t attend, and provided comments on user feedback, as well as suggested wireframe and design elements. Board and Commission Annual work plan 3 3 Initiative name: Stay informed about pending legislation affecting cable and technology Initiative type: ☒ Staff support (review project, policy or program and provide feedback) ☐ Independent research project ☐ Gather community feedback ☐ Lead community event Initiative origin: ☐ Applicant-initiated ☒ Staff-initiated ☐ Commission-initiated ☐ Council-initiated Legally required (e.g. response to Legislative changes or Judicial decisions)? ☐ Yes ☒ No Commissioner lead(s) name(s): None, all will be involved If joint commission initiative, list other board or commission: Is this an established work group? ☐ Yes ☒ No Initiative description: CTAC is asked to stay informed about pending legislation that may affect the city’s cable franchise, or other technologies vital to the community such as broadband. Strategic Priority: ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☒ 5 ☐ N/A Deliverable: ☐ Research report ☒ Summary of community input ☐ Other ☒ N/A Target completion date: Ongoing This section to be completed by staff: Council request (if applicable): ☐ Review and comment or reply ☐ Review and decide ☒ Informational only – no response needed Budget required: None Staff support required: Information and updates from staff liaison Liaison comments: Staff liaison will stay informed of pending legislation through contact with state and national advocacy organizations, as well as through the city’s legislative staff and lobbyists. Information affecting cable and technology will be shared with CTAC members. Board and Commission Annual work plan 4 4 Initiative name: Whitepaper – Future of Generative AI for Cities Initiative type: ☐ Staff support (review project, policy or program and provide feedback) ☒ Independent research project ☐ Gather community feedback ☐ Lead community event Initiative origin: ☐ Applicant-initiated ☐ Staff-initiated ☒ Commission-initiated ☐ Council-initiated Legally required (e.g. response to Legislative changes or Judicial decisions)? ☐ Yes ☒ No Commissioner lead(s) name(s): Konnor Slaats, Kayla Stautz, Benjamin Straus If joint commission initiative, list other board or commission: Is this an established work group? ☐ Yes ☒ No Initiative description: This is a proposed whitepaper seeking to explore the question: how might cities need to adapt to be generative artificial intelligence (AI)-compatible in the future? The whitepaper will explore policy adaptations cities, including St. Louis Park, may need to make in a generative AI-enabled future. Peer cities and use cases for generative AI tech will be explored in areas such as public works, public-facing chatbots, planning and zoning, external resources and coalitions, and public engagement. Strategic Priority: ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☐ 5 ☐ N/A Deliverable: ☒ Research report ☐ Summary of community input ☐ Other ☒ N/A Target completion date: Q3 2026 This section to be completed by staff: Council request (if applicable): ☐ Review and comment or reply ☐ Review and decide ☒ Informational only – no response needed Board and Commission Annual work plan 5 Budget required: Staff support required: Liaison comments: CTAC has reviewed the generative AI guidelines generated in November 2024 for city staff, and is aware of the data assessment project conducted in 2025 to move the city toward the goal of having reliable, organized data to “feed” any future generative AI project. Data cleanup will continue in 2026. 5 Initiative name: mystlouispark (city customer response management system) assessment Initiative type: ☐ Staff support (review project, policy or program and provide feedback) ☒ Independent research project ☐ Gather community feedback ☐ Lead community event Initiative origin: ☐ Applicant-initiated ☐ Staff-initiated ☒ Commission-initiated ☐ Council-initiated Legally required (e.g. response to Legislative changes or Judicial decisions)? ☐ Yes ☒ No Commissioner lead(s) name(s): Rudyard Dyer, Shane Leverenz, Tom Marble (school district staff liaison) If joint commission initiative, list other board or commission: Is this an established work group? ☐ Yes ☒ No Initiative description: The commission team members will conduct an assessment and review of the current MySLP app. We will document the current feature set, capabilities, accessibility (language options), and integrations. Research will be conducted on industry best practices and peer municipality apps to determine if there are any opportunities to expand, further integrate, or modify the existing MySLP app in any way to provide more or better benefits to residents. We will also examine whether the MySLP app is even necessary. The end deliverable will be a report outlining the current condition and capabilities of MySLP with recommendations for any changes, enhancements, or modifications to the platform. Strategic Priority: ☐ 1 ☐ 2 ☐ 3 ☐ 4 ☒ 5 ☐ N/A Deliverable: ☒ Research report ☐ Summary of community input ☐ Other ☒ N/A Target completion date: This section to be completed by staff: Council request (if applicable): ☐ Review and comment or reply ☐ Review and decide ☒ Informational only – no response needed Board and Commission Annual work plan 6 Budget required: Staff support required: Liaison comments: City staff are currently evaluating this product for compatibility with other software being used in the city for tracking work requests internally, in an attempt to eliminate duplicate efforts. Initiative Origin Definitions  Applicant-initiated – Project initiated by 3rd party (statutory boards)  Staff-initiated – Project initiated by staff liaison or other city staff  Commission-initiated – Project initiated by the board or commission  Council-initiated – Project tasked to a board or commission by the city council Strategic Priorities 1. St. Louis Park is committed to being a leader in racial equity and inclusion in order to create a more just and inclusive community for all. 2. St. Louis Park is committed to continue to lead in environmental stewardship. 3. St. Louis Park is committed to providing a broad range of housing and neighborhood oriented development. 4. St. Louis Park is committed to providing a variety of options for people to make their way around the city comfortably, safely and reliably. 5. St. Louis Park is committed to creating opportunities to build social capital through community engagement Modifications  Work plans may be modified, to add or delete items, in one of three ways:  Work plans can be modified by mutual agreement during a joint work session. Board and Commission Annual work plan 7  If immediate approval is important, the board or commission can work with their staff liaison to present a modified work plan for city council approval at a council meeting.  The city council can direct a change to the work plan at their discretion. Future ideas Initiatives that are being considered by the board or commission but not proposed in the annual work plan. Council approval is needed if the board or commission decides they would like to amend a work plan. Initiative Comments