What's moving in local government tech

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.

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, 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.

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 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, 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 Route Fifty, New York City Council Speaker Julie Menin issued a rarely used subpoena on Monday to Elon Musk's SpaceXAI to compel public testimony at the council's Oct. 5 oversight hearing on AI risks. A council spokesperson said SpaceXAI was the only invited company that did not respond and commit to sending a representative. Per a council press release, Meta simply agreed to attend, while Google, OpenAI and Anthropic confirmed only after explicit threats of subpoenas.

Menin said the firms owe it to the public to answer questions and give input on proposed legislation under oath. The council says it would seek judicial enforcement in the New York State Supreme Court if SpaceXAI does not comply, and could pursue civil contempt sanctions after that.

For clerks and council staff, the episode shows that compelled testimony is a real tool for a legislative body, and one that brings its own procedural load. Witness lists, confirmations, sworn testimony and a clean record of every invitation and response all become part of the official file. Most local bodies will never face a case like this, but the same questions can arise on a smaller scale with a vendor or utility that declines to appear.

Practical takeaway: check what subpoena authority your governing body has under state law or charter, who signs, and how service and enforcement work, before you need it.

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 Route Fifty, local leaders speaking at the Granicus Government Experience Virtual Summit said the technology side of modernizing services is the easier part. Marcus Townsend, a solutions architect for Fayetteville, North Carolina, said residents will find a way to reach the city, whether by email, a 311 call center, a mobile app or a chatbot.

The harder work, speakers said, is telling residents clearly what is changing, what works and what does not. They also warned that elected officials need to stay in the loop, especially because they may take the brunt of public criticism when a project stumbles. The article notes that many state and local agencies have embraced artificial intelligence and report some early success.

For staff who prepare meetings and records, this is a useful reminder. New agenda portals, public comment tools or chatbots reach residents and council members at the same moment, and surprises tend to land on the dais. Council members who understand a change before residents ask about it are better placed to explain it.

Takeaway: before launching a new resident facing tool, brief the governing body in plain language. Share what will change, what may go wrong and where residents can get help.

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, 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, 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, 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 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, 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 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 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, 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 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, 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.

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.

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 cut the hours that go 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 every 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 every 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 every 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.