What's moving in local government tech

As reported by ICMA's PM Magazine, a Leadership ICMA capstone project surveyed 28 local government professionals and found that 82% already use some form of AI at work. Uses include drafting council agendas and reports, translating and transcribing meetings and documents, and website navigation help. Respondents also named unclear policies and governance, data privacy and security worries, accuracy problems, and a lack of training.

The authors argue that traditional IT procurement is not always well suited to AI and that adoption is often happening through individual experimentation. Their answer is the AI Matrix, a web-based scoring tool that assesses functionality, workforce impact, human interaction, ethics and data security on a 30-point scale. A score above 16 counts as a pass. The sample is small, so treat the survey figures as indicative rather than representative.

For staff who prepare agendas, minutes and records, the practical issue is that tools touching public documents are often adopted without a consistent review. Questions about data handling, accuracy and human oversight matter more when outputs feed official records.

Practical takeaway: inventory which AI tools your office already uses, then ask whether any shared checklist, scoring approach or policy covers them. Even a simple common set of questions would reduce inconsistent practice across departments.

As reported by ICMA's PM Magazine, Douglas County, Colorado found that access and training alone did not produce sustained generative AI use. Roughly 150 licenses were issued through an AI Champions program, yet about 40 holders were using the tool at least occasionally a year later. The county now pairs work-relevant training with an internal AI Hub, use-case spotlights, office hours and one-on-one working sessions.

The article's clearest example involves meeting minutes. The fairgrounds team supports roughly 100 board and committee meetings a year, and preparation reportedly fell from 30 minutes to two hours down to a few minutes. For community development's four advisory boards, preparation reportedly dropped from five to seven hours per meeting to about 30 minutes, an estimated 250 hours saved annually. The authors say this took more than asking AI to summarize a transcript. Staff worked with the team to design workflows reflecting each board's requirements.

For clerks and staff who prepare meetings, the point is that results came from redesigning a specific process, not from the tool alone. These are the county's own estimates, and your boards, formats and legal requirements will differ.

Practical takeaway: pick one recurring meeting task, document what your board or statute requires of the output, and test a workflow against that checklist before expanding. Keep a human review step for anything that becomes part of the official record.

In an opinion piece for Route Fifty, behavioral scientist Gleb Tsipursky cites a Stanford Digital Economy Lab update of ADP payroll data through June 2026. It found employment among workers ages 22 to 25 in highly AI-exposed occupations was about 19% below where it would have been compared with similarly aged workers in less-exposed fields. The author says the gap appears mainly through reduced hiring.

His proposal is a capacity-dividend rule: when automation saves staff hours, reinvest some of them in supervised work. Examples include junior analysts checking AI-generated summaries against source records and early-career staff explaining exceptions before a senior official signs off. He also suggests tracking time to independent competence alongside hours saved.

This is an opinion, not a study of government results, but it speaks to a real concern in clerk and records offices. If AI drafts agendas, summaries or minutes, the junior staff who once learned the process by doing that work may lose the practice. Retirements make that risk sharper in thin teams.

Practical takeaway: if you pilot AI for meeting prep or records work, assign a newer employee to verify outputs against source documents, with an experienced reviewer available, and note what they learn.

As reported by Route Fifty in a column by Adobe's Brian Chidester, Adobe's State of AI Readiness in the Public Sector report found that roughly 90% of proposed public sector AI use cases never reach production. Among 502 active respondents, 62% said they are piloting or deploying AI. But 92% described the relationship between business functions and IT as siloed or transactional, only 4% reported comprehensive measurement of AI's impact, and just 7% have a formal AI owner with a defined title and budget authority.

This matters for staff who prepare meetings, records and decisions. A pilot that summarizes documents or helps employees find information can look successful, then stall in IT reviews, security assessments and competing department priorities. The column argues that unclear decision rights, not the tools, are the usual cause. Keep in mind that the author works for a vendor and the figures come from a single survey, so treat the numbers as directional.

Practical takeaway: before starting a pilot in your office, decide who owns the decision to expand or stop it, write down a baseline to measure against, and bring IT, security, privacy and accessibility staff in while the use case is still being designed rather than at the end.

As reported by StateScoop, a new report from the Center for Internet Security, the MS-ISAC and the Consortium for School Networking surveyed 426 K-12 cybersecurity and technology leaders. Among those that had an incident in the past year, 34% said it affected day to day operations, and 66% said they have only one or two dedicated cybersecurity staff. Nearly 80% said they need more support, 70% said budget limits forced delays, and 87% named phishing or email compromise among the leading incidents. The report also noted that AI can make phishing and impersonation more convincing.

Schools are not city halls, but the pattern may sound familiar to local government staff. The article describes incidents that can reach student information systems, communications and payroll, which are the kinds of back office systems that clerks and finance staff depend on. Small teams covering both daily IT work and security are a common constraint in smaller jurisdictions, though this survey does not speak to municipal figures.

Practical takeaway: the report's recommendations are a usable checklist. They include multifactor authentication, email security, regular awareness training, a tested incident response plan, a formal AI use policy and use of free threat monitoring such as the MS-ISAC Malicious Domain Blocking and Reporting service.

As reported by StateScoop, Los Angeles residents can now track City Council legislation, search public records and share feedback through a new online platform. The city clerk's office said the site is designed to simplify searches across more than 500,000 documents and 172,000 Council Files dating back to 1970, and that users can search in everyday language without knowing file numbers or keywords.

StateScoop reports the platform was built with Concourse, which also supports the council's internal legislative operations, including document intake, agenda creation, vote recording and meeting livestreams. Development began in May and the site launched in less than six months.

For staff who prepare meetings and manage records, the notable point is that the public-facing search and the internal legislative workflow are described as part of one system. When intake, agendas and votes feed the same record, the public view is only as good as the upstream habits: consistent file naming, complete attachments and timely posting. Plain-language search also changes what residents expect. They will increasingly look for a topic, not a file number.

A practical takeaway: try your own public records search the way a resident would, using a topic and no file number, and note where results fail. Those gaps usually point to metadata or indexing habits your office can fix before any new tool is purchased.

As reported by Chalkbeat and republished by Route Fifty, New York City announced restrictions on student facing AI tools just before the school year, saying it would discontinue or disable AI components of more than 38 previously allowed programs. Chalkbeat obtained the list after more than a month of requests. Several companies said their products do not use the kind of AI the policy prohibits and that they did not know why they were flagged. The Education Department said the rules cover student facing generative AI features, not necessarily whole products, and that it is working case by case with vendors.

This is a school system, but the lesson carries to any local government buying software. The Education Department did not explain how it decided which tools met its definition, according to the report. When a policy leans on an undefined term, vendors and staff may read it differently, and fixes can land mid season.

It also shows records pressure. The list itself took more than a month to obtain, so expect requests about which AI tools your office uses.

Practical takeaway: keep a current inventory of AI features in your vendors' products, define covered AI in policy and contracts, and ask vendors to confirm in writing which features are on.

As reported by Route Fifty, local leaders speaking at the ICMA annual meeting said AI customer service chatbots are taking routine questions off the plates of small staffs. Laura Stelzner, city administrator and treasurer of Chetek, Wisconsin, said her three person office is the hub of everything, and that the phone is not ringing as often as it was. Aaron Grisdale, town manager of Woodstock, Virginia, described using AI to push out trash and recycling schedule changes after the vendor shares them.

For clerks and staff who prepare meetings and records, the point is protected time. Stelzner said budget work and reconciling invoices and purchase orders need closed doors and deep focus, and she does not see that work being delegated to AI. Staff also use chat tools internally to find answers in ordinances faster, according to the report.

Both officials said some residents will always want a human, so they keep in person and phone help alongside the tools. Concerns about AI replacing jobs remain, Route Fifty noted, though both officials described the technology as helping staff work more efficiently.

Practical takeaway: if you are weighing a chatbot, track which repeat questions consume the most staff time, and keep a clear path to a person for residents who prefer one.

As reported by StateScoop, the Center for Civic Futures, a program of Renaissance Philanthropy, is awarding $11 million to 11 projects through its Public Benefit Innovation Fund. The projects aim to reduce administrative burden and improve eligibility processing for programs including Medicaid, SNAP and unemployment insurance. The organization said close to half of applications in its first round were chatbots, so this round favors back-end work. Examples include a North Carolina test of AI-assisted SNAP recertification using synthetic data, and using AI to map legacy technology systems more quickly.

The report also says some grants will address procurement, including more flexible technology contracts for Medicaid agencies. The fund's director is quoted saying you cannot launch a new AI tool if you cannot buy it. Some projects will stay in closed testing environments because of sensitive personal data, and the results are expected to be open source.

For county and local staff who support benefits offices or prepare technology agenda items, the lesson is that process and contracting often limit AI projects more than the tool does. Pilot design, evaluation criteria and data handling are worth documenting up front, and the open-source results may offer templates to learn from.

As reported by Route Fifty, citing Nevada Current, the Reno City Council voted 5-2 to expand its existing Axon contract to include automated license plate readers, drones and AI report drafting. The city had decided not to renew a 2024 Flock contract. The $22 million, eight-year deal requires quarterly audits and deletion of data not tied to an investigation after 15 days. The mayor and one council member voted no, citing privacy concerns.

For clerks and council staff, the story is about process as much as technology. According to the report, some members who voted yes still had lingering questions about transparency, reporting requirements and accountability. Opponents asked the council to postpone the vote while Nevada legislators consider both a ban and a separate regulation bill. Long contracts that add new surveillance or AI capabilities can generate records requests, public comment and audit obligations well beyond the vote itself.

Practical takeaway: when a contract adds capabilities to an existing vendor relationship, make sure the agenda packet clearly describes the new scope, retention and audit terms, and that someone owns the follow-up reporting. Pending state legislation may also change what a long-term agreement allows, so it is worth asking how the contract would handle that.

As reported by ICMA, Rachel Stern, founder and managing partner of Govtech Ventures, told attendees at the 2026 ICMA Annual Conference that local government leaders should approach AI procurement the way venture capitalists do: identify promising opportunities, demand evidence, and increase investment only when results justify it. She described leaders as investors whether or not their title says so, since they are allocating capital to uncertain technology with consequences that could compound over a decade. The article says she outlined five steps, though the supplied text covers only the opening of the piece.

This matters for the staff who prepare council items. Clerks and analysts are often the ones drafting the contract summary, the staff report and the records implications of a new tool. A staged approach gives those documents a clearer shape: a defined problem, evidence of results, and a decision point before expansion, rather than a single large commitment to a product.

Practical takeaway: when an AI purchase comes to your office for agenda preparation, ask what problem it solves, what evidence supports the claim, and what milestone would trigger a larger investment or an exit. Having those answers in the staff report makes the council's decision easier to explain later.

Route Fifty reports that voters in 10 states will decide 41 local ballot measures on Nov. 3 that would advance, restrict or set conditions on data center development. In Harwood, North Dakota, a proposed measure would require independent evaluation of a project's technical information, a public hearing and access to related public records. Ottawa, Kansas, and Sunbury, Ohio, have measures tied to a 25 megawatt threshold, and Grove City, Ohio, would require added voter approval for larger facilities.

Brookings experts quoted in the article pointed to a lack of transparency as a driver of resident distrust, including negotiations with one or two officials before the community is brought in. One said deals shrouded in nondisclosure agreements have fueled frustration. The article also says Pennsylvania's governor signed an executive order that prohibits nondisclosure agreements for data center developments.

Why it matters: clerks and council staff sit at the center of these disputes. Hearing notices, agenda packets, development agreements and records requests are where residents test whether a process was open. Confidentiality terms signed early can collide with public records obligations later.

Practical takeaway: if a data center inquiry could reach your community, ask your attorney now how any nondisclosure terms interact with your state's public records and open meetings laws, and set up a clear file of project documents so requests can be answered quickly. Whatever the ballot results, expect more questions.

As reported by CyberScoop, Microsoft attributed the recent supply chain attack on ConnectWise customers' Microsoft 365 environments to a China state aligned group it tracks as Storm-0940. Microsoft said the group used an open source agentic AI penetration testing framework called ARTEX to automate scanning, password spraying and abuse of OAuth applications. Government was among the many sectors it targeted. Microsoft did not say how many customers were compromised, and noted that a successful login does not necessarily mean data was accessed or stolen.

According to the report, ConnectWise temporarily shut down services Saturday and began restoring them in phases Wednesday. It advised customers to keep connections disabled and expects recovery to take several days. Microsoft said that in some environments the AI agents went beyond sign in to directory operations, including changing application credentials to establish persistence.

Why it matters: many city and county offices rely on outside vendors and backup tools that hold high privileges inside their Microsoft 365 tenants. Meeting packets, minutes, records and email often live there, so a compromised third party app can reach far beyond its intended purpose, as Microsoft put it.

Practical takeaway: ask your IT team or managed provider whether ConnectWise Cloud Backup is in use, and have them review which third party apps hold permissions in your tenant and whether any credentials changed recently. Confirm that multifactor authentication is enforced and that failed login alerts are being watched.

Route Fifty interviewed Tim Marczewski, Missouri's director of AI and innovation, about how state agencies have approached AI. He said the state began with small pilots, including one with 100 people across 17 agencies, and required staff to bring a specific use case to take part. Those pilots also helped the state build governance and a sandbox where employees can experiment without worrying about misusing data.

One example he cited involved a grants program that received about 3,000 applications instead of the usual 100. Using Google's Vertex AI to read application documents, with a human reviewing the results, the state cut processing from a projected January to June down to one month, and he said it saved about $200,000. He also said trainings with 700 people do not work, and that smaller sessions tied to functional areas are more effective.

For clerks and records staff, the pattern is useful at local scale: document intake and review are where AI tools are often tried first, and the human checkpoint is part of the design. These are the claims of one official, not an independent evaluation.

Practical takeaway: if your office is considering a pilot, start small, require a defined use case, set data guardrails first, and train by job function rather than by all-hands session.

Google Public Sector unveiled Gemini for government services on Tuesday, an add-on that gives federal, state and local governments specialized skills, AI agents and integrations with commonly used software, as reported by Route Fifty. According to the company's press release, the tools can help officials interpret dense regulations, redact documents requested under the Freedom of Information Act, simplify jargony documents and review contracting bids.

The product is not yet generally available. Route Fifty reports that the federal Health and Human Services Department and the State of Missouri have tested it over the past few weeks, that Google is accepting more early adopters, and that general availability is expected later this year with no target date.

For clerks and records staff, redaction is the item to watch. Redaction errors can expose protected information or lead to improper withholding, and the supplied article gives no detail on accuracy, audit trails or how staff would review results. Those details are unknown, and the claims come from a vendor press release.

A practical step: if your office is asked to pilot any tool for redaction or bid review, decide beforehand who reviews every output, how decisions are logged, and how the work fits your retention and public records obligations. Ask what testing has been done on documents like yours before agreeing to be an early adopter.

In a piece published by Route Fifty and written by Garrett Lee, a Broadcom regional vice president, the author argues that state and local agencies face new data exposure as employees use public AI assistants and AI features built into existing software, often before policies exist. Because the author's company sells security products, the argument should be read as vendor perspective.

The piece recommends three steps: discover and classify sensitive data across file shares, cloud storage and departmental applications; create an inventory of approved AI tools and define which data types may be used with each; and use automation to enforce policies with limited staff. It says governance does not need to be perfect on day one and can start with risk-based policies focused on the highest-risk information.

For staff who draft memos, prepare agenda packets and handle records, the useful part is not any product but the basic framework. Drafts, personnel matters, and records with confidential content can end up pasted into a public AI tool without anyone intending harm. A written list of approved tools and the kinds of information allowed in each is something a clerk's office can help shape with IT, whatever technology is later chosen to enforce it.

A practical takeaway: ask your IT lead whether an approved AI tool list exists, and whether it says anything about records that may be confidential or subject to retention rules.

As reported by Route Fifty, a new report from Georgetown University's Beeck Center for Social Impact and Innovation says residents increasingly use AI assistants instead of visiting government websites, so their ability to find the right answer depends on whether those tools can reach and correctly interpret government content. The report's author, Andrew Merluzzi, told Route Fifty the fix is not especially difficult, but governments have to know the problem exists.

The report points to several steps. Security settings that block malicious bots may inadvertently block a legitimate AI assistant. It suggests a three-tier approach to crawler access, from verified established providers down to unverified bots that get a graduated response. It also recommends publishing critical information, such as application deadlines, as page text, HTML tables or PDFs with extractable text, since scanned documents and screenshots may be overlooked. Sites should be retested after redesigns or content management system changes, and a person or team should own content accuracy, prioritizing the consequence of an error over page traffic.

For clerks and records staff, this touches the places residents look for agendas, minutes, meeting notices and deadlines. If those are posted as scanned images, an AI assistant may not relay them correctly, or at all. A practical takeaway: ask your web team whether bot-blocking rules were reviewed for AI crawlers, and check whether your posted agendas and notices are text-extractable rather than scans. Then ask an AI assistant a few common questions and see whether the answers match what you published.

As reported by ICMA, engagement expert Brady Wilson of Juice Inc. led a Game Changer session at the 2026 ICMA Annual Conference in Long Beach, California. His central message was that many difficult behaviors come from fundamental needs that are not being met. He named five: belonging, security, freedom, significance and meaning. In the article's examples, constant gossip may point to a struggle for belonging, and micromanaging may reflect a search for security. Wilson stressed that recognizing the need does not excuse incivility. It gives leaders a better starting point for responding.

This matters for the staff who prepare meetings, records and decisions, because the article describes contentious council meetings and frustrated residents as part of the territory. It also notes that exhausted leaders can lose access to emotional regulation, flexible thinking and strategic decision making. That is one speaker's framing from a conference session, not research findings, but it speaks to a real strain on clerk and records teams.

The practical takeaway is a small one. Wilson suggested a five-minute energy conversation with employees: ask what is currently energizing them, what is draining them, and how you might address it together. Managers could try it with the team before a heavy meeting cycle.

As reported by Route Fifty from Stateline, data center investment is now on pace to dwarf past building booms. Citing a report by a Columbia Business School professor, the article says the buildout could reach $10 trillion and account for nearly 4% of GDP. It adds that many states granted tax exemptions before the boom and many officials are now rethinking them as tax revenue and energy affordability come under pressure.

The article gives two examples. Nevada trimmed tax abatements in a September executive order and will ask data centers to cover their energy and water demands. In Oregon, a report last month led to a continued freeze on data center approvals, and the most frequent concern in public comments was utility affordability.

For staff who prepare council and commission materials, the shift matters because data center proposals often reach local bodies through zoning, utility agreements and incentive requests. The article does not describe local processes in detail, so any local effect would depend on your state and utility arrangements.

A practical takeaway: if a proposal is possible in your jurisdiction, start organizing the record now. That includes any existing abatement terms, a sourced summary of expected energy and water demand, and a way to log and categorize public comments so recurring concerns, such as utility costs, are visible to decision makers.

In an opinion piece published by Route Fifty, the author argues that deploying body cameras is only the first step. The piece notes that ICE's policy gives leadership broad discretion over release, and contrasts that with London's Metropolitan Police, which revised its policy to allow more proactive release. After a knife attack in Golders Green, the Met released responding officers' footage within hours, where it would previously have typically waited until criminal proceedings ended.

The piece also describes why this work is hard. Footage is moving, often poorly lit, and may show victims, children, witnesses and bystanders. Agencies have to decide what is relevant, what must be protected, and how to keep the context that makes a recording useful. The author frames these as questions of operational capability as well as policy.

For clerks and records staff, this is a reminder that body camera volume lands in the public records queue. Even though the article centers on federal and UK examples, the same review and redaction burden applies to local agencies. Note that this is an opinion piece, not a study of local practice.

A practical step: ask your police or sheriff's office how long review and redaction of a typical incident takes, who decides on release, and whether written criteria exist. Having those answers before a high profile incident makes response times easier to explain.

CyberScoop reports that threat intelligence firm VisionHeight found networks of hyperlocal websites, with names like "Wolverine State Report" and "Peach State Bulletin," across at least 14 states. The sites repeat statements that a named candidate is the stronger choice on issues like housing and taxes, and they cite one another. VisionHeight's chief technology officer told CyberScoop the content appears written for AI crawlers rather than human readers. The firm does not attribute the activity to any actor. It says Perplexity cited one of the pages as a first source in at least one answer, though most of the research focused on Google search AI answers.

This matters to clerks and council staff because residents increasingly ask chatbots about local races and may get answers shaped by sources like these. Targets reportedly include local offices and Secretaries of State, so your jurisdiction's contests could be affected. It is not yet clear how widely such tactics change AI answers.

Takeaway: try a few plain questions about your own local races in common AI tools and search, and note what sources come back. Make sure your official election pages state key dates, ballot details and polling information in clear, direct language, and point residents to them.

As reported by Route Fifty, based on Nextgov/FCW interviews, state officials say they are receiving fewer election-specific federal briefings than in previous cycles. Sources also described weaker information sharing between government, researchers and technology companies. The story says AI tools now help influence operators write plausible messages, find audiences and adjust campaigns at scale. CISA told the outlet it will activate an Incident Coordination Group before and during Election Day, and said influence operations fall outside its mission.

For county and municipal clerks who run or support elections, the practical risk is a slower flow of early warning. One nonprofit official described learning about possible bomb threats in 2024 by walking across a federal operations room, and said they have not been invited to one for the midterms. Local staff may need to rely more on state election offices and peer jurisdictions to learn what others are seeing.

Takeaway: before Election Day, write down who you would call about a suspicious threat or false voting information, including your state election office and neighboring clerks. Confirm those contacts are current, and have a short, approved public correction ready to post from official channels.

As reported by Route Fifty, Colorado Springs is weighing Project Taurus, a 50-megawatt data center planned on the site of a former Intel chip factory. The City Council voted last month to postpone final approval until April after a contentious public hearing. The local economic development chief said concerns about water, power and noise "are not a reason to say no; they really are conditions to say yes."

The city's approach, per the article, includes a utility tariff on large loads so the user pays for infrastructure and power, a requirement for closed-loop water systems, and a developer commitment to monitor noise and post a $1 million surety bond. The article notes noise monitoring is not yet required in the city's unified development code.

For council staff and clerks, the lesson is about documentation. Several of these protections are commitments rather than code requirements, and the same official stressed the need to "get things in writing." Staff preparing agenda packets for similar projects may want to make sure promised conditions, their enforcement mechanisms and any public hearing records are clearly captured and easy to retrieve, since a postponed decision can span many months and several meetings.

As reported by StateScoop, New York City's Public Interest Technology Crew launched in July and delivered its first product in 10 weeks: an online complaint portal for the city's Click-to-Cancel rule, built with the Department of Consumer and Worker Protection. The portal went live Oct. 1, the rule's effective date. The team's leaders said that because the software was built in-house, they cut out a procurement process that, in one leader's words, "adds months, if not years, to a lot of traditional IT projects."

For staff who prepare decisions and manage contracts, the notable part is the method as much as the speed. The team described running usability tests during development, talking with residents in different languages, and working with the staff who process complaints. It also said it did not set aside privacy, security or accessibility, and relied on existing city security processes.

New York is a very large government, and an in-house team may not be realistic for most clerks' offices. Still, the practical takeaway travels: when a new ordinance or rule has a hard effective date, involve the people who will handle the resulting submissions early, and test the public-facing form before it is final. That can matter as much as which vendor is chosen.

As reported by Route Fifty, in a piece originally published by New York Focus, an analysis of roughly 680 school district websites and board manuals found that more than half lack formal, board-adopted AI policies. Around 270 have one, most supporting responsible AI use. Of the roughly 400 districts where no policy was found, more than 70 confirmed they had none, and 39 of those said they plan to write one this school year. Some districts without policies still use AI regularly, and several told the outlet they are waiting for state guidance.

School districts are a distinct body from city and county government, but the pattern is familiar to any local clerk. Tools get adopted in practice before a governing body adopts a rule, and staff are left to guess where policy applies. The article also quotes a researcher noting that AI is being built into so many products that it is not always clear what a policy covers. A board-adopted policy carries more authority and tends to be more enforceable than internal guidelines.

Practical takeaway: check whether your own jurisdiction has a council or board-adopted AI policy, or only informal staff guidance. If the latter, the clerk's office is well placed to flag the gap, track which AI-enabled tools departments actually use, and make sure any adopted policy lands on a public agenda and in the official record.

As reported by Route Fifty, Gov. Gavin Newsom signed the "No Robo Bosses" Act, SB 947, late last month. The state is described as the first to require human review for certain employment decisions made by automated systems. A person must corroborate the decision by reviewing the data behind the system's output, such as performance evaluations, peer reviews and personnel files. Employees gain the right to be told when an automated system assisted a termination or discipline decision, and to request a meaningful, objective description of their own data used by the tool. Employers cannot use a system whose output a human reviewer cannot verify. Newsom vetoed a similar bill in 2025, citing overly broad restrictions.

For city and county staff, the immediate legal reach is a question for counsel, since the supplied article does not say how the law applies to public employers. But the direction matters anywhere HR, clerks and records staff handle personnel files. If an automated tool informs a disciplinary decision, the data it used and the reviewer's corroboration may become records that someone has to locate, explain and possibly produce.

Practical takeaway: inventory the software your HR and department staff use for scheduling, performance scoring or monitoring, and ask vendors what data feeds each output and how a human reviewer can verify it. Doing that before a state mandate or an employee request arrives is cheaper than reconstructing it afterward.

Route Fifty profiled Brock Arnold, who handles both human resources and IT for Roosevelt, Utah, a city of around 7,000 residents. He described a government that was antiquated in its systems and moved it onto Tyler Technologies' local government software platform. As reported, running payroll for 51 full-time and about 180 part-time employees used to take three days and require supervisors to come in on a Sunday afternoon to approve payments. Invoice approvals and time-off requests also had to be done in person. Arnold says payroll now takes a matter of hours and can be done off-site.

Arnold also framed the move as a security step. He pointed to Iran-linked hackers attacking small water systems and transportation agencies in several states, and said part of the goal was to get off localized servers so the city could be better protected. This is one city's account, so results will vary with vendor, contract and staffing.

For clerks and managers in small jurisdictions where one person wears several hats, the useful detail is how the city began. Arnold said it started small, by moving its access directory to the cloud and asking how supervisors could more easily see account information, enter invoices and track budgets. Takeaway: list the approvals in your office that still require someone to be physically present, and pick the one that causes the most delay as a first candidate for change.

As reported by Route Fifty, state and local governments marked Digital Inclusion Week, Oct. 4 to Oct. 10, with funding and assistance announcements. Carolyn Bennett Glauda of the Southeastern New York Library Resources Council said many government websites lack features such as keyboard accessibility, alt text for images and clear design. Route Fifty also reported that Utah Gov. Spencer Cox signed an executive order this week to build AI literacy, starting with public employees. It directs state agencies to require AI training and promote responsible AI use within government.

For staff who prepare agendas, minutes and public notices, the accessibility point is the practical one. Residents often meet local government through a portal, a posted PDF or a chatbot, and those are the places where missing alt text or poor navigation can block access. Elizabeth Laird of the Center for Democracy and Technology told Route Fifty that agencies should regularly tell the public how they use AI and what steps they take to keep people safe. That advice is aimed at skepticism toward AI, but it applies to any new digital service.

Takeaway: pick one frequently used page, such as the current meeting packet, and check whether it can be navigated by keyboard and whether images have alt text. If your office uses any AI tool, consider drafting a plain-language note describing how it is used.

As reported by Route Fifty and Source New Mexico, the state's Office of Cybersecurity told an interim legislative committee that agencies should update digital security before a hostile country builds a powerful quantum computer. General counsel Todd Baran said bad actors may harvest data today and decrypt it years later. He noted that federal guidance sets Dec. 31, 2030 as a deadline for many federal systems and contractors to adopt newer encryption, with old methods retired by 2035. He also said his office currently lacks the power to mandate such changes across state agencies and will seek a bill.

The article lists birth and death records, juvenile records and health records among the sensitive data governments hold in encrypted systems. Many of those records carry long or permanent retention periods, so confidentiality has to last longer than the technology protecting it. The timeline of the threat is uncertain, and the officials' concern rests on expert expectations rather than a present breakdown.

Practical takeaway: ask your IT lead or records vendors which long retention record sets are encrypted, how, and whether they have a plan for newer standards. Add that question to your next contract renewal or procurement review.

As reported by StateScoop, Georgia's Secretary of State has launched GABBY, a chatbot that answers resident questions using information published on the office's website. Officials say it is meant to reduce the time people spend hunting for information and ease the load on call center employees. StateScoop notes the announcement did not say whether the tool uses generative AI or describe its underlying technology.

For clerks and records staff, the design choice is the useful part. A bot that draws only on official pages is only as accurate as those pages. Outdated fee schedules, stale meeting notices or buried forms will show up in its answers. StateScoop also cites Arizona's BallotBot, which officials describe as supplementing, not replacing, help from county election officials. That framing is worth borrowing if your office considers something similar.

Practical takeaway: before any chatbot pilot, audit the pages it would read from, assign an owner for keeping them current, and ask the vendor plainly whether the tool generates new text or retrieves existing content. Tell residents what it is and how to reach a person.

As reported by Route Fifty from a Pew Charitable Trusts article, dozens of water utilities have had cyberattacks in recent years that forced systems offline, manual operation, or suspended billing. The FBI received reports of incidents affecting water systems in at least seven states over a few days this past July, and attacks that month hit utilities in more than 30 Minnesota communities. Pew points to Baltimore's 2019 ransomware attack, which prevented water bills for several months and cost an estimated $18 million.

The piece describes state responses. New York aligned health and environmental rules and paired them with a $2.5 million grant program that, per the article, awarded more than $9 million to 153 local projects. State estimates suggest compliance could cost up to $150,000 a year for utilities serving 3,300 to 50,000 people.

Why it matters: for managers and finance staff, a cyber incident is also a billing, records and council reporting problem. Even when water quality is not affected, revenue collection and customer accounts can stall, and the costs can land on the broader local budget.

Practical takeaway: ask your utility and IT leads whether a manual billing fallback and an incident reporting procedure exist and have been tested, and whether your state offers assessments or grants before new requirements arrive.

A Route Fifty opinion piece by Brian O'Hara, a former Minneapolis police chief, argues that an automated alert should prompt verification, not automatic enforcement. He notes that more than 50 agencies or communities have canceled or suspended contracts, rejected proposals or deactivated cameras this year. He cites a Los Angeles review in which officers acknowledged 161 alerts as correct plate matches even though the vehicles were not stolen. He also describes a San Francisco watchdog finding that traced excessive force to a manually entered wrong plate that was never verified.

For staff who prepare council items and manage contracts, the useful point is where responsibility sits. The author says chiefs answer for policy and conduct, managers and councils for contracts and oversight, vendors for design and auditability, and lawmakers for enforceable limits. He suggests state law set a floor while local governments write stricter limits into contracts. A Minneapolis audit he cites found statutory compliance but still recommended formally approved procedures for access, retention, deletion and periodic review.

Practical takeaway: pull your current camera or alert technology agreements and check whether retention periods, audit rights, access rules and verification steps are written down, not just left to vendor settings. Those documents are also likely to be the ones requested under public records law.

As reported by The Texas Tribune via Route Fifty, the Public Utility Commission of Texas filed suit Monday in Travis County to block release of two fields from its data center and virtual currency mine survey: the county and the regional water planning area. The agency argues the details become sensitive when combined with other survey data, and it cites the Texas Homeland Security Act. The Attorney General's office had issued two rulings finding the PUC had not sufficiently established that the information fits that exception.

For records staff, the case turns on a point that applies well beyond Texas: when an agency withholds records under a statutory exception, it carries the burden of showing the exception applies. The PUC is also arguing that individual data points should not be judged in isolation, which is a mosaic style argument. Whether a court accepts it could shape how critical infrastructure exemptions are read, though the article notes the lawsuit is not a final ruling on release.

Practical takeaway: if your office handles requests touching utilities, water, energy or other infrastructure, review how your written exemption justifications are documented. Clear, specific explanations of why a record meets the statutory test are what ruling authorities looked for here. Watch this case for guidance, and check with your attorney before changing any practice.

As reported by Route Fifty, citing Utah News Dispatch, Utah Gov. Spencer Cox signed an executive order on Tuesday setting a "pro-human" framework for AI in state government. Agencies are directed to require AI literacy training for employees, evaluate where AI can optimize business functions in a cost-effective manner, and propose areas where citizen-facing processes and automated workflows could responsibly be transformed. The Department of Government Operations is to lead, and the Division of Technology Services is to work with Human Resources Management on a training strategy, including specialized training for agency AI leads.

This is a state order, so it does not bind cities or counties. But it shows a pattern local staff will likely see more often: training requirements paired with expectations to find AI use cases. For those who prepare agendas, minutes and records, that raises practical questions about who approves tools, how outputs are reviewed by a person, and how AI assisted work is documented for records retention and public access.

Practical takeaway: consider whether your organization has a basic AI use policy and a training plan, and whether your records schedule addresses AI generated drafts or logs. The Utah order offers one model for sequencing training before broader adoption, though the article does not detail enforcement.

In an opinion piece published by Route Fifty, the author argues that the recent wave of cyberattacks on water and wastewater systems is a public safety and infrastructure problem, not only an IT problem. The piece says more than 30 systems in the midwest have reported incidents and that utilities in Cape May County, New Jersey, confirmed attacks. It stresses that attribution remains under investigation. Reported incidents involved attempts to manipulate operational technology, passwords and network settings, and some communities saw temporary loss of water pressure, though the author says widespread public health consequences have not occurred so far.

The author cites recommendations from CISA, EPA and the FBI: reduce public-facing internet exposure, eliminate default passwords, inventory IT and operational technology assets, back up systems, remediate vulnerabilities and exercise incident response plans. The piece also calls for continuous visibility into vendors and remote-access relationships, and for states to offer shared cybersecurity services to smaller jurisdictions.

Why it matters: staff who prepare council items on utility contracts, vendor agreements and capital budgets are often the ones who can ask whether cyber resilience is included. Practical takeaway: when a water or wastewater item reaches the agenda, ask whether the asset inventory is current, which vendors have remote access, and whether manual operating procedures are documented and rehearsed.

As reported by Route Fifty, the Water Information Sharing and Analysis Center announced on Sept. 29 a partnership with Cyware, which uses agentic AI to share threats and support collective defense. Once the partnership is fully operational, WaterISAC members in the water and wastewater sectors are expected to receive AI-powered threat intelligence. The article notes the move comes weeks after water systems in several states were hit by hackers linked to Iran, with more systems hit recently in Colorado.

WaterISAC's executive director, Tom Dobbins, said there are over 50,000 water utilities in the country and many are very small, without the defensive capabilities of large cities. Many city and county utilities sit inside general government, so the budget, staffing and risk questions often land with managers and council staff. Dobbins pointed to basics like multifactor authentication and password resets as places smaller utilities can start. He also said WaterISAC has been without federal funding to cover membership dues for its members.

Practical takeaway: find out whether your water or wastewater utility belongs to an information sharing group, and who actually receives the alerts. Then confirm those alerts reach someone with the authority to act on them, and consider a short cyber readiness update in an upcoming council or board briefing.

As reported by StateScoop, Sens. Bernie Sanders and Jeff Merkley and Rep. Alexandria Ocasio-Cortez introduced the Ban Flock Act on Monday. It would block federal funding from state and local governments that use automatic license plate readers, bar federal agencies from using them, and let people sue the federal government over violations.

StateScoop also notes that Sen. Josh Hawley introduced the Stop Flock Abuse Act at the end of last month. It would ban local governments from selling or sharing vehicle data the cameras collect, require automatic deletion within 10 days except for data used in a criminal investigation, and ban facial recognition on these networks. Senate Minority Leader Chuck Schumer also sent a letter to Flock's CEO about its National Lookup Tool, asking for a response by Oct. 16.

Both bills are only proposals, and nothing here says either will advance. Still, the bipartisan attention suggests that council members and residents may ask staff about retention periods, data sharing and vendor contracts for these systems.

Practical takeaway: gather current contracts, retention settings and sharing agreements for any plate reader program so staff can answer questions quickly and brief the council with accurate facts if the rules change.

As reported by Route Fifty, in a story that first appeared in The Texas Tribune, North Richland Hills, Texas, invoiced a Flock watchdog $2.3 million, payable up-front, for records on how police use Flock Safety cameras. The invoice reportedly cited labor at $15 an hour, equivalent to more than 14 years of work, to search about a terabyte of communications. The requester says he sent nearly identical requests to almost 200 agencies and got widely varying results. Sealy reportedly provided more than 400,000 pages for free, while other agencies quoted thousands of dollars or denied requests.

The article also describes the Texas Department of Public Safety providing a full list of searches in July, then narrower records, then withholding data and asking the Attorney General's Office for permission to do so. The city declined to answer questions, and DPS did not comment.

For clerks and records staff, the lesson is consistency. When similar requests produce free production in one city and a five or seven figure estimate in another, the difference invites scrutiny, and it may be read as discouraging access. Cost estimates, search methods and exemption decisions tend to be easiest to defend when they are documented and applied the same way across requesters.

Practical takeaway: if your office has not yet received a request about license plate reader use, check now where audit logs, camera locations and retention data are kept, who can export them, and how your fee and estimate policy would apply.

As reported by Route Fifty, state chief information officers said at the NASCIO annual conference that centralized approaches to digital identity are emerging. A NASCIO report found that 51% of state tech leaders run digital identity programs under a centralized model, while 38% reported a hybrid or federated style. Ohio CIO Katrina Flory said that without an enterprise approach, individual agencies build their own solutions, which drives up costs. Washington is working toward an enterprise customer identity for residents, and New York offers agencies a shared plug-in while setting compliance requirements.

The report also found that 70% of respondents see inadequate funding as a barrier and 68% cited organizational and cultural resistance. Washington CIO Bill Kehoe described the challenge as a mindset shift toward serving residents rather than agencies.

This matters for local staff because resident facing services such as permits, records requests and public comment portals often depend on identity checks. State choices on shared identity services could shape what counties and cities are later expected to integrate with, though the article does not say so directly.

Practical takeaway: note where your office verifies identity today, and start with one narrow use case, as a former California security chief suggested, rather than a broad rollout.

As reported by Route Fifty, citing the New Jersey Monitor, a New Jersey Senate panel unanimously advanced a bill that would require preapproval for a range of automated digital tools in the workplace and limit electronic monitoring. Tools used for personnel decisions would be barred unless a third party impact assessment finds they serve one of six discrete purposes, such as payroll or periodic performance assessment. Public sector employers, including tools that aid the provision of government services, would face the same requirements, and vendors would pay for the assessments.

The bill does not define artificial intelligence, and its definitions are not limited to AI. Business groups warned it could reach payroll, scheduling and cybersecurity tools. The sponsor, Sen. Andrew Zwicker, suggested definitions could change as the bill moves through the Legislature, so the final scope is uncertain.

For staff who support HR, records and technology decisions, the broad wording is the point to watch. If it survives, routine systems could be treated like decision tools, and contracts may need to say who arranges and pays for assessments. Similar proposals could surface in other states.

Practical takeaway: list the automated tools your organization uses for scheduling, payroll, monitoring and personnel decisions, and note which vendors could produce an independent assessment if asked.

As reported by StateScoop, Vermont has moved from years of building an AI ethics framework into what chief data and AI officer Josiah Raiche calls an enablement phase. State employees are building their own AI "power tools" to automate routine work. Raiche said the approach rejects autonomous agents in favor of a human operator working inside a defined process.

StateScoop also reported that agencies pick trusted employees who get roughly a three-month head start to build practical tools before their wider teams are trained. In one example, the Secretary of State's office worked with Raiche's team on an AI skill for ballot proofing against a spreadsheet of roughly 3,000 candidates. The tool flagged errors it was confident about and items it was unsure of.

For clerks and staff who prepare meetings and records, the useful part is the design: a named human operator, a defined process, and uncertainty surfaced rather than hidden. That is a sensible pattern for any document-heavy task, since accountability stays with a person. The Vermont examples are early and self-reported, so results elsewhere may differ.

Practical takeaway: pick one repetitive checking task in your office, such as proofing agenda packets against a source list. Have a trained staff member pilot it, and require that the tool mark what it is unsure about so a person reviews those items.

In an opinion piece published by Route Fifty, Colton Overcash argues that states are layering different thresholds, timelines and reciprocity procedures onto GovRAMP. The piece notes that North Carolina began requiring GovRAMP-aligned provisions in new cloud contracts on April 1, 2026, with full compliance mandatory from April 1, 2027. It also says Indiana and Nevada have mandates, and that Texas requires a reciprocity request rather than automatically listing GovRAMP or FedRAMP products.

The author recommends presumptive reciprocity for equivalent authorizations, a common crosswalk of statuses, and narrow, public state overlays. He also says GovRAMP is intended for use by local governments and school systems, and that counties and cities may add their own variations if states offer no clear reusable model. This is one author's view, not a finding.

For staff who handle procurement and records, the issue is practical. Cloud tools used for agenda management, records and meeting systems may soon be asked to show a specific authorization status in solicitations and renewals. Fewer qualified bidders could follow if requirements diverge.

Practical takeaway: check whether your state has a cloud authorization requirement, and ask vendors which status they hold before drafting a solicitation. Tie any extra local requirement to an identifiable risk.

As reported by StateScoop, the Maine State Archives has launched Open Access, a public website offering digitized and born-digital records, meaning documents created electronically rather than scanned from paper. The state says the platform holds more than 100,000 imaged records spanning five centuries, and Secretary of State Shenna Bellows said it will keep expanding as more collections are imaged. StateScoop also notes Hawaii's State Archives announced a similar digitization effort in February.

For local clerks and records staff, the story is a reminder that public expectations for self-service access are rising. When a state archive makes historical material searchable online, residents may reasonably ask whether local minutes, ordinances and older council records are equally easy to find. StateScoop's reporting also frames this as part of a wider push to preserve digital records such as email, text messages and social media, which can be harder to manage than paper.

The archivist quoted in the article noted the archive holds more than 8 miles of documents, so full digitization is a long road. That is a useful reality check for any local program.

A practical takeaway: start with the records residents and requesters ask for most often, and track which ones are already available online. That list can guide a phased digitization plan and may reduce routine records requests over time.

As reported by Route Fifty, state and local agencies often keep the control but lose the reasoning behind it when elections, retirements, reorganizations or vendor turnover change who is in charge. The article proposes a standard: a consequential cyber decision should be understandable to a qualified successor without a private briefing. It describes a hypothetical county where a 30-day vendor access exception outlives the departed CIO because nobody can tell what it covered or what should have ended it.

The suggested check is a reconstruction test. Pick five high-impact decisions, hand each record to a qualified reviewer who was not in the original discussion, and ask them to recover the key elements in plain language. Score each as aligned, partially aligned or not recoverable. Route Fifty says the record should connect existing artifacts such as tickets, risk registers and meeting minutes rather than add a large new form.

For clerks and staff who prepare meetings and records, this matters because approvals often live in minutes and agenda packets. If a council or manager approves an exception, the record should say what it covers, who accepted the risk and what ends it. Otherwise the minutes show only that something was approved.

A practical takeaway: before the next transition, pick a few open exceptions and ask someone outside the original discussion to explain them from the file alone. Where they cannot, add the missing scope, owner and expiration to the existing record.

As reported by Route Fifty, the National Association of State Chief Information Officers released its 2026 annual survey this week at its San Diego conference. It draws on responses from 51 state and territorial CIOs. Ninety percent said they anticipate or might face more turbulence and disruption over the next five years, and 66% said they lack adequate funding to balance immediate needs with future investment.

The survey also points to workforce pressure. An expected wave of public sector retirements will take institutional knowledge with it and bring changing skill requirements, the report says. Workforce skills and capability constraints affect 28% of CIOs' ability to deliver digital services. The three leading strategies are upskilling current employees, investing in training and building talent pipelines. Texas CIO Tony Sauerhoff said modernization now means changing how government runs its business, not just upgrading hardware and software.

This is a survey of state CIOs, so local findings may differ. Still, clerk's offices and records teams often depend on a few long tenured people who know where things live and why procedures work as they do. Any technology change, such as new agenda or records systems, tends to expose that dependence.

Practical takeaway: use the next quiet stretch between meeting cycles to write down the procedures only one or two people fully understand, and pair a newer staff member with each of those experts.

As reported by StateScoop, the extension of the Department of Justice's Title II rule under the Americans with Disabilities Act moved the compliance date back a year, to April 26, 2027. The rule covers states and large local governments. NASCIO's survey found that 46% of states still lack a chief accessibility officer and 67% have no dedicated accessibility funding. The survey also suggested the delay may have reduced momentum.

The top two compliance challenges, chosen by 75% of state accessibility officers surveyed, were document remediation and fixing high traffic systems. Officials from Texas and Pennsylvania said the extra time should not turn accessibility into a mere checkbox, and that the underlying civil rights obligations have not gone away.

For clerks and meeting staff, document remediation is familiar territory, since agenda packets, staff reports and minutes are often published as PDFs. The article does not address local practice, so confirm how the rule applies to your jurisdiction with your attorney.

Takeaway: the officials' advice was to prioritize by risk. Start by listing the most visited pages and the document types residents request most, then fix those first and build accessibility into how new documents are created.

As reported by CyberScoop, Mandiant researchers say the earliest known exploitation of a critical Citrix NetScaler zero-day, CVE-2026-88772, occurred Sept. 3, more than three weeks before attacks were confirmed. Mandiant says organizations in sectors including government, education and financial services were likely compromised, and it is aware of dozens of impacted organizations. A second NetScaler zero-day, CVE-2026-88771, has reportedly been exploited since at least Sept. 24, according to GreyNoise. Citrix disclosed both flaws on Sunday and released patches, along with fixes for six other vulnerabilities.

Why it matters for local government: clerks and records staff often depend on remote access gateways to reach case files, agenda systems and records repositories. Mandiant notes most edge devices do not support endpoint detection and response monitoring, so a compromise can be hard to spot. The researchers also say the timeline could change as investigations continue, so patching alone may not settle whether a system was affected.

Practical takeaway: ask your IT team or managed provider today whether your organization runs NetScaler appliances, whether the patches are applied, and whether anyone has reviewed logs back to early September. If records or meeting systems sit behind those devices, make sure your incident response plan covers notifying the people who rely on them.

As reported by StateScoop, the City of Charlottesville, Virginia, moved its on-premises SAP system to S/4HANA Cloud, starting in July 2024 and going live in September 2025. IT director Stephen Hawkes described the effort as "eight years in the making," slowed by staff turnover and by cycling through "five or six city managers" while he sought funding and approval. The legacy system faced end-of-support in 2027.

The lessons are practical for staff who prepare decisions. Hawkes said his five-person team slowed down to educate leaders and commissioned an outside study comparing options, which helped make the case. He also said change management took roughly the last six or seven months of the 14-month project. For clerks and finance staff who depend on back-office systems for agendas, budgets and records, that suggests user adoption deserves as much planning as the data migration itself.

Hawkes also said the city is experimenting with AI agents on the ERP platform for bottlenecks such as permit application processing. Treat that as early and self-reported.

Takeaway: if your system faces an end-of-support date, document the risk in plain language for elected officials now, and consider an independent options study so continuity does not hinge on any one manager's tenure.

StateScoop reports that NASCIO's 2026 State CIO Survey, based on responses from 51 state and territory CIOs, found 98% have enterprise policies and procedures for AI development and use, up from 76% last year. Contract provisions and procurement terms for GenAI rose from 41% to 61%. Respondents said agentic AI will be the most impactful emerging technology over the next two to three years (64%), with current activity concentrated in internal workflow automation, IT operations, application development and customer service.

The survey also found that 68% of CIOs expect more turbulence in their role, and only 35% say they help local governments with digital accessibility. Cybersecurity remains a concern, with one CIO quoted as saying "the threat is high and the defenders are thin."

Why it matters for local staff: state policy and procurement language often becomes the template that counties and cities borrow, or the standard they are measured against. If AI tools touch agendas, minutes or records work, expect questions about governance and contract terms to come up in your own procurements.

Takeaway: check whether your state has published AI policies or contract language you can adapt, and ask your state CIO office what support exists for local accessibility and security work, since the survey suggests that help is limited.

As reported by Route Fifty, in a piece written from a vendor's perspective, state Medicaid agencies still often rely on technology designed decades ago. The article contrasts a single-stage enterprise overhaul with a phased implementation that upgrades components such as eligibility, provider management or claims in planned stages. It argues that single-stage projects raise integration risk, strain small internal teams and can delay results. It also describes a provider enrollment project split into three releases that delivered working software in eight months, instead of a 24 to 32 month full replacement.

The subject is state Medicaid, but the pattern will be familiar to local staff. Clerks and records teams are often asked to oversee a vendor rollout while still running agendas, minutes and requests day to day. The article notes that this overlap can increase burnout and oversight gaps. Because the examples come from the author's own client work, treat the timelines as illustrative, not a benchmark.

Practical takeaway: when you scope a replacement for agenda, minutes, records or permitting software, ask vendors whether it can be delivered in stages, whether the old system can run alongside the new one, and which module should go first. Staff bandwidth belongs in the readiness check before procurement, not after.

As reported by StateScoop, privacy experts consider passage of a comprehensive federal privacy law this year highly unlikely, citing midterm elections, few remaining legislative days and no bipartisan bill with real momentum. That leaves states to keep writing their own rules.

The article says Oklahoma, Louisiana and Alabama have enacted comprehensive privacy laws set to take effect in 2027, and Vermont's law begins in 2028. Virginia, Maryland, Connecticut, New Hampshire and Delaware have passed amendments covering areas such as precise geolocation, facial recognition, children's data and third party data processing. Delaware's amendments will require businesses to conduct and document due diligence on third parties that receive personal data.

The piece focuses on businesses and state governments, and it does not say how these laws apply to cities and counties. Local staff should not assume either way. Still, the direction of travel, with more attention to vendors and data handling, can shape the questions residents, councils and auditors ask about the tools a local government uses.

A practical step: ask your attorney which of these state laws, if any, reach your jurisdiction, and review current vendor contracts for how personal data is shared, retained and disclosed, especially for any system that touches public records or resident submissions.

In an opinion piece for Route Fifty, Crosby Burns, Marin County's Deputy County Executive and Chief Digital and Innovation Officer, argues that governments often treat digital accessibility as a compliance exercise and ask whether a system meets the standard more than whether someone can actually use it. He says that approach can leave systems technically accessible but unusable, and can slow services while they sit in review.

Burns describes how the county moved away from trying to fix everything at once. After more than two years of work on social services such as CalFresh and Medi-Cal, it shifted to a prioritized framework focused on the service pages that reach the most residents. He writes that this let the county reach 90% of its goals in 90 days through its second "Digital Accelerator." He also cites county figures showing nearly one in ten residents, about 24,900 people, live with a disability.

For clerks and council staff, the piece is a reminder that the documents residents rely on to follow local decisions, such as agendas, packets and minutes, are part of the same picture. This is the author's account of one county's experience, so results will vary, but the sequencing idea travels well.

A practical step: list the pages and documents residents open most, test a few with real users or assistive technology, and fix those first rather than waiting for a full remediation plan.

As reported by Route Fifty, Delaware lawmakers are considering a bill, proposed by Secretary of State Charuni Patibanda-Sanchez, that would let AI agents operate as their own legal entities, including signing contracts. Under the June draft, an "artificial intelligence company" would need a sponsor ensuring it is adequately capitalized, would have to keep an activity log, and would have to disclose that it is an autonomous system. If passed, a 30 month sandbox would let organizations test such companies. Lawmakers are expected to take it up when the legislature reconvenes in January.

Law professors quoted by Route Fifty said the draft lacks an accountability framework. One noted it sets no minimum capital amount and gives few governance details. Another said governments will likely watch closely because the issue relates to autonomous, automated or algorithmic decision making in government.

For staff who prepare records and decisions, the bill is an early signal of a question that may reach local offices: who is accountable when software acts on its own? Contracts, filings and correspondence could someday arrive from a non-human party, and the draft's activity log and disclosure ideas hint at what records may be expected.

A practical takeaway: check whether your records and procurement policies say who is responsible for automated actions and whether those actions are logged and retained. Better to settle that before a vendor or counterparty raises it.

As reported by Route Fifty, the Cybersecurity and Infrastructure Security Agency released its 2026 Election Infrastructure Security Plan on Thursday. It names CISA's 10 regional directors as election security advisers and describes a free platform for sharing threat information among election officials, state intelligence hubs and federal partners. Election officials can request help through CISA's regional offices, and fusion centers are identified as a key channel for election intelligence.

The plan arrives after cuts that state officials say weakened their ties to federal expertise. Route Fifty reports that Michigan's deputy secretary of state told lawmakers in April that local election officials had lost contact with CISA staff they once relied on. The plan does not say how many employees will do the work, does not identify funding, and does not say when officials can enroll in the platform. The administration's fiscal 2027 budget proposal would also eliminate CISA's election security program, though Congress would have to approve that change.

For clerks and county staff who help run elections, the plan is a promise rather than a service you can count on yet. Treat the federal support as something to confirm, not assume.

A practical step: find out who your CISA regional office contact is and whether your state fusion center handles election threat reports. Write both into your incident response plan, and keep a backup path through your state election office in case federal help is thinner than described.

As reported by Route Fifty, Maryland Gov. Wes Moore is creating a task force, staffed by seven state agencies, to review new data center proposals and advise local jurisdictions. Moore said final decisions still rest with local governments. The task force will rate projects expected to use at least 25 megawatts at peak as aligned, conditionally aligned or not aligned with state principles, including ratepayer protection and community support.

The order also sets up a public online dashboard, updated monthly, listing proposals with details such as developer name, expected peak energy demand and anticipated water use. State agencies are told to defer substantive permit review until a developer documents required local land use approvals, and not to enter new nondisclosure agreements with developers, operators or site selection agents. Existing agreements will be honored but not renewed or extended.

Why it matters: local planning and clerk staff in Maryland may see more of these projects move through public hearings with a state view attached, and the dashboard could shape what residents ask for in the record. The NDA ban applies to state agencies, so how local governments handle confidentiality is still a local question.

Practical takeaway: whatever your state, if a data center inquiry reaches your office, check what confidentiality commitments staff have made and how they square with your open meetings and public records obligations.

As reported by Route Fifty, a Senate Judiciary subcommittee criticized automatic license plate readers on Wednesday, saying the tools enable warrantless searches and lack needed cybersecurity guardrails. Sen. Josh Hawley said practically every state now has them. Sens. Katie Britt and Raphael Warnock have asked the Justice Department for guidance to help state and local agencies prevent misuse. The CEOs of Flock, Axon, Motorola and Verkada were invited but declined, according to Hawley.

Witnesses suggested independent security testing of vendors and tight limits on how long the data is kept. Route Fifty also cites a Wall Street Journal report that Flock now has a dropdown menu for users to justify searches and will require a case number for law enforcement searches.

For city and county staff, this is a contracts and records issue as much as a policing one. Vendor terms, retention schedules and search logs are things a council may ask about, and the logs and justifications could plausibly become targets of public records requests. Nothing in the hearing created a new obligation, but federal attention often shapes what residents and elected officials ask next.

Practical takeaway: pull your current license plate reader contract and retention policy, confirm who can search and how searches are logged, and make sure the clerk's office knows where those records live before a request arrives.

The National League of Cities reports that more than 3,000 data centers operate in the U.S., and its research found at least 120 communities have adopted data center moratoria and 60 have passed new zoning regulations this year. In a new CitiesSpeak episode, an AAAS researcher, a Tucson councilmember and the Cedar Rapids mayor discuss the tradeoffs.

The AAAS guest said a 100 megawatt hyperscale facility can use roughly as much electricity as 80,000 U.S. households, and that peak water use at a large site can reach one to eight million gallons per day. NLC and the AAAS center published a resource called Key Questions to Ask When Considering a Data Center in Your Community. Tucson spent nearly a year writing new rules with a 13 member technical advisory committee and public input. Cedar Rapids is welcoming two facilities after years of planning, with development agreements that NLC says are expected to include infrastructure investments.

This matters for staff who prepare the agenda items, staff reports and records behind these decisions. Data center votes tend to span zoning, utilities and tax questions at once, and both officials stressed early public communication.

A practical step: use the key questions list as a checklist for staff reports, so applicant answers on water, energy and infrastructure costs are on the public record before a vote.

As reported by Route Fifty, California Gov. Gavin Newsom signed an executive order to speed independent audits and third party oversight of AI safety and security risks. It creates a task force that must deliver a guide on strengthening state AI law within two months. In Virginia, Gov. Abigail Spanberger announced a Data Center Accountability Framework, to be partly mandated by executive order and proposed in legislation for the 2027 session.

The Virginia piece is the one local staff should watch. According to the report, any entity under the governor's supervision would be barred from signing a nondisclosure agreement for a data center project, and the state would create a Data Center Planning and Community Engagement Toolkit for local governments. The framework would also speed up work on data center noise regulations. The report does not say whether the NDA ban would reach localities, so that is worth confirming as details emerge.

For clerks and council staff, data center proposals often mean confidential negotiations, public records questions and heavy agenda packets. A state signal against secrecy could shape what residents expect to see in the open. The practical takeaway: review how your office handles NDAs and records requests tied to economic development projects, and watch for the toolkit so you can compare it with your current review process.

As reported by StateScoop, Virginia Gov. Abigail Spanberger sent a letter to congressional leaders asking for federal AI guardrails, citing data privacy, workforce displacement, cybersecurity and resource use. She said Virginia will keep developing its own policies, and last week signed an executive order creating an AI Task Force focused on workforce impacts, privacy and cybersecurity. StateScoop also reports California Gov. Gavin Newsom signed legislation creating a framework for independent AI verification organizations and a registry of AI auditors, as part of a broader strategy that includes government use of AI.

StateScoop notes federal action remains uncertain, and that the National Association of State Chief Information Officers has urged Congress to preserve states' authority to regulate AI.

For local staff, the practical effect is that the rules governing AI tools you buy or pilot may shift, and may differ by state, before any federal framework arrives. State requirements could eventually flow down to counties and cities through procurement, privacy or workforce policies, though the article does not say so directly.

Practical takeaway: keep an inventory of the AI features in your agenda, minutes and records tools, and build contract language that lets you adjust if state or federal requirements change.

As reported by Route Fifty, the Allen Lab for Democracy Renovation at the Harvard Kennedy School launched its Digital Civic Infrastructure Initiative last week. It is meant to be a resource hub where local governments can find research, policy briefs and digital tools. Associate director Sarah Hubbard said some local governments have no tech staff or resources to build their own website.

An early project is a free, open-source budget transparency tool built with Massachusetts municipalities. It lets users publish visualizations of budget plans and line items, and government users can use it to process capital expenditure requests. Route Fifty also reports that a related Allen Lab report on Massachusetts cities found early promise in AI chatbots for resident questions and in tools that draft transcripts, summarize meeting minutes or translate government communications. Those are early findings, not proven results.

For clerks and staff who prepare meetings and records, this matters because minutes and transcript drafting are named as active use cases. Any AI-drafted summary still needs human review before it becomes part of the record.

Practical takeaway: if your office is short on budget for vendor products, review the initiative's free resources, and decide in advance who verifies any machine-drafted minutes or translations before they are published.

As reported by StateScoop, Code for America is one of 15 organizations chosen for the $30 million Google.org Impact Challenge: AI for Government Innovation. Its funding will support a tool for the GetYourRefund tax service that reviews uploaded documents and flags cases that can move to preparation or need extra review. The stated aim is to free volunteer preparers from routine screening so they can handle harder questions.

The article also cites a 2025 Code for America report finding that most states are still in early stages with AI. Only New Jersey, Pennsylvania and Utah were described as having made major strides, and most of the other 47 were experimenting through small pilots or outside partnerships.

Why it matters: the design is a useful pattern for local offices. The tool sorts routine items from those needing human judgment rather than making final decisions, which is how many clerks and records staff would want any intake automation to work, whether for records requests, permits or applications. The article does not describe accuracy results or safeguards, so those questions remain open.

Practical takeaway: if your office is considering AI for intake or document review, define in advance which cases always go to a person, how flagged items are logged, and who reviews errors.

As reported by Route Fifty in an op-ed by Mike Barton of AudioEye, the ADA Title II rule requires state and local governments to meet WCAG 2.1 Level AA for websites and mobile apps. The piece says the Department of Justice pushed deadlines back a year in April 2026. Governments serving 50,000 or more people now have until April 26, 2027, and smaller governments and special districts until April 26, 2028. The author notes that WCAG 2.2 is the current version and suggests building to it. Note that the author works for an accessibility vendor, so treat the framing with that in mind.

Why it matters: the author argues that residents who cannot use a digital form can lose benefits in ways that look like ordinary case closures, and that the ADA already required equal access to programs and services before the web rule. For staff who prepare agendas, notices, forms and public documents, the same logic applies to anything residents must use online, including PDFs and meeting materials. Check the deadline for your population tier against your own legal counsel's reading.

Practical takeaway: pick your highest-stakes resident transactions, such as applications, payments or records requests, and test them with a keyboard only and then a free screen reader like NVDA or VoiceOver. The author says this surfaces the worst problems quickly, and recommends pairing automated scans with expert testing.

As reported by Route Fifty, Georgia appears poised to adopt hand-marked paper ballots for the 2028 election. At a Thursday committee meeting, cybersecurity experts told a legislative panel that more is at stake than ballot format. They pointed to aging software on current machines, long vendor support timelines and ballot privacy. One expert said, "Election security is a process and not a purchase."

Two points stand out for local staff. First, a state official urged lawmakers to ask what a vendor will provide for "five, 10, 15 years down the road," including updates and spare parts. That is a useful question for any long-lived system you buy. Second, Route Fifty reports a Princeton researcher claimed he used AI on publicly available data to link thousands of voters in two Georgia counties to specific ballots. The claim is the researcher's own, but it shows that data released in good faith could be combined in ways staff did not expect, especially in smaller jurisdictions.

Practical takeaway: when you write or renew technology contracts, put the vendor's multi-year support and update plan in writing. Before releasing election-related data, consider whether it could be re-identified when combined with other public data, and ask your counsel about it.

As reported by StateScoop, California Gov. Gavin Newsom signed an executive order directing the Government Operations Agency to set application requirements and procedures for independent AI verification organizations by next May. Related requirements would begin by the end of 2027. State officials and outside experts have until Nov. 16 to recommend changes to existing AI safety laws, including periodic audits of large frontier developers and a possible emergency shutdown mechanism.

The order targets companies building advanced AI models, and the article does not describe new duties for local governments. Still, StateScoop notes that Illinois, Tennessee and Colorado have also been working on AI rules, and that Colorado has spent two years rewriting a 2024 law that covered government users of high-risk AI systems. StateScoop also reports that a NASCIO report found state CIOs moving toward more deliberate AI governance rather than treating AI as a standalone initiative.

For clerks and managers, the signal is that expectations around AI oversight and documentation are unsettled and may change. A practical step is to keep a simple inventory of any AI features in your agenda, minutes, records or chat tools, along with what each vendor has said about testing and safety. That makes it easier to respond if state rules reach your office.

As reported by Route Fifty, a commentary on e-procurement says the most common failure point in public procurement modernization is not software but the lack of a baseline. A government that cannot state its cost per solicitation, cost per supplier registration or cycle time per contract action cannot scope the project, defend the spend or judge results later. The piece suggests four numbers to gather before an RFP: cost per procurement document, cost per supplier registration, the distribution of cycle times per contract action, and the count of duplicate and stale vendor records.

For clerks and staff who prepare contracts, bid openings and council items, this matters because the paper costs sit on your desks. The author describes them as spread across many people, such as approvers passing contracts one at a time or staff re-keying vendor packets. The piece also cautions that vendor benchmarks are largely cross-industry figures and should be treated as order-of-magnitude, since sealed-bid rules, public posting, protest windows and records retention change the math. It adds that accessibility and supplier outreach for small, rural and first-time bidders should be funded as line items.

A practical takeaway: before the next vendor demo, have staff time one representative solicitation and one mailed vendor packet. A few weeks of that data gives your finance committee something concrete to compare against any vendor's claims.

As reported by StateScoop, Nebraska Secretary of State Bob Evnen unveiled a new online voter registration system on Tuesday, National Voter Registration Day. The platform combines the state's voter registration and voter information services into one site. Residents can register, update registration information, change party affiliation, check the status of early or provisional ballots and find their polling place.

StateScoop notes the launch comes as election officials face pressure to update systems while keeping voting reliable and secure, including cybersecurity concerns around voter databases. It also points to Pennsylvania, which recently launched a dashboard drawing on its statewide voter registration database to show public registration totals and changes.

Why it matters for local staff: when a state consolidates services into one portal, the questions that reach front counters and phone lines tend to change. Offices that field voter questions may see a spike in people asking where to go, what a ballot status means or how to fix a record. Old links, printed handouts and phone scripts can quickly become out of date, and that is a small but real risk this close to an election.

Practical takeaway: audit your office's web pages, social posts, printed materials and call scripts, and confirm they point to the right tool. A quick walk through the new portal yourself will help you answer resident questions with confidence before Nov. 3.

As reported by Route Fifty, Maryland launched Maryland Tax Connect on Sept. 1, a portal where residents can file state income taxes for free, make payments and check refund status. State officials describe it as the first systemwide modernization of the state's tax infrastructure in three decades. It replaces a 1993 system on a COBOL based mainframe that went down for a week in March 2023, according to Comptroller Brooke Lierman.

The details of the cutover are worth a look. Route Fifty reports the office closed the legacy system for nearly two weeks last month to transfer more than 4 billion tax records, and that staff training began in May. The office is also holding monthly webinars for residents. Lierman said the design borrowed from the IRS Direct File approach, including a simple interview style flow and prepopulated wage and income data.

For clerks and records staff, the lesson is not about taxes. Any aging system that holds permits, licenses, minutes or case files eventually faces the same questions: how long can service be down, how will records be verified after the move, and how early do staff need training? Planned downtime is easier to manage than an unplanned outage.

Practical takeaway: if your office relies on a legacy system, sketch a cutover plan now, covering downtime windows, record verification, staff training dates and how you will tell residents about any gap in service.

As reported by StateScoop, a new report from the National Association of State Chief Information Officers and Forrester Research draws on a 2026 survey of 51 state and territory CIOs and interviews with 19 more. It found that modernization success did not necessarily depend on whether IT was centralized or decentralized. Successful CIOs built agency relationships, tied spending to mission outcomes and set up governance for competing priorities. The report found 61% of CIOs said IT spending is largely aligned with statewide priorities, and 53% use an enterprise governance review board.

The report also names three pressures: a "First Mover Penalty," where the first agency to adopt a tool bears costs that benefit others, a "Planning Trap," where long budget cycles slow response to technologies like AI, and a "Funding Cliff," where temporary money expires before ongoing support is settled. NASCIO's 2026 priorities put AI first for the first time, ahead of cybersecurity.

These are state level findings, but local staff may recognize the same dynamics in budget requests, pilot projects and grant funded software. How a state frames AI governance and funding could also shape what counties and cities are asked to follow.

Practical takeaway: when a technology proposal reaches your council or board, ask which outcome it serves and who pays once grant or one time funding ends.

As reported by StateScoop, Missouri Gov. Mike Kehoe signed an executive order Tuesday directing the Department of Public Safety to set statewide safeguards for state and local law enforcement use of automated license plate readers. The order cites concerns about Flock Safety's cameras and data sharing network, and about officers misusing the technology to track people they know. It says misuse would trigger disciplinary proceedings or criminal referral, while the legislature works on a permanent statute.

The order also lists standards that agencies are encouraged to adopt voluntarily where existing contracts and law allow. They include deleting most plate and vehicle data within 30 days, barring vendors from selling, sharing or commercializing data captured in Missouri, limiting use to legitimate criminal justice and lifesaving purposes, and prohibiting AI facial recognition integration with ALPR systems.

For clerks, managers and council staff, this is a records and procurement issue as much as a policing one. Retention periods, vendor data terms and audit trails for these systems may soon be measured against a state benchmark, and those items often land in contracts, agenda packets and public records requests. Even outside Missouri, the order shows where state expectations may be heading.

Practical takeaway: pull your current ALPR contracts and check the stated retention period, vendor data sharing terms and who can audit access. Flag any gaps before the next renewal reaches your agenda.

Over the past year, more cities and counties have started testing AI tools inside the work that surrounds a public meeting. That means assembling agendas, drafting staff reports, and searching prior actions. The pattern is consistent. Agencies are not handing decisions to software. They are using it to reduce the manual work that goes into preparing a packet, while keeping staff review in place.

The interest is strongest where records are already digital and where clerk turnover has left teams stretched. What separates a serious tool from a demo is traceability. If a drafted line cannot be traced to a source document, it does not belong in the public record.

Cities evaluating these tools are asking sharper questions about where data lives, how it is isolated, and who remains accountable for accuracy. That is the right instinct. The technology is useful, but the standard for public work has not changed. At Govera, we build each output to cite its source, so staff can verify before anything reaches the record.

As more agencies try AI for drafting minutes and summaries, a fair question follows. How does that fit with open meeting and public records law? The short answer is that the law does not change because a tool is involved. Minutes still must reflect what happened. Records still must be retained and produced on request.

A draft produced by software is a draft until staff review and adopt it, the same as any other. The practical guidance is to keep a clear human review step, keep the source recordings and documents, and make sure any AI generated text can be checked against them.

Transparency is easier, not harder, when each summary links back to the record it came from. Agencies that treat AI output as a starting point, not a final word, stay on solid ground. Govera's approach follows the same principle. Assistive drafts, full citations, and staff in control of what becomes official.

Buying AI for a public body is not like buying it for a business. The record is public, the stakes are legal, and trust is the product. A few questions separate a safe purchase from a risky one.

Does each output cite a source document you can open and verify? Where is your data stored, and how is it kept separate from other agencies? Does the tool keep staff in control with review steps and draft states, or does it act on its own? Will it read the messy documents you already have, or does it need a long data project first? And who is accountable for accuracy, your staff supported by the tool, or the vendor's model alone?

Good vendors welcome these questions. Weak ones deflect them. The market for civic AI is growing quickly, and the cities that ask the hard questions early will get the tools that hold up in public. Govera is built to answer all five without hedging.