From the State Government edition of September 6, 2026
State AI assessment finds impact reporting trails experimentation
Code for America · State AI adoption and benefits administration · United States
- Publisher
- Code for America
- Original publication
- May 2026; exact day not established on inspected assessment
- Source retrieved
- 2026-09-07
What happened
The assessment finds widespread experimentation but limited impact reporting and continuous learning. It distinguishes readiness, piloting, implementation and impact.
Why it matters
Direct state-government portfolio evidence with a benefits-access lens. Use it to frame evaluation questions, not to infer any state's present performance.
Evidence and measured results
Research ended in March 2026. Methods combine public-document desk research, state feedback opportunities and advisory rubric review. This is a maturity assessment, not a controlled test of AI effectiveness.
Limitations and uncertainty
Public reporting can miss internal work. Rendered state totals were unavailable; no counts or rankings are asserted. Full PDF was email-gated and not accessed. Findings are not a September status census.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-07; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Ask agency executives, benefits directors and budget owners what counts as public value and who can supply the baseline. A bounded engagement could inventory selected pilots and design a measurable continuation decision. The value hypothesis is better allocation of implementation effort, not guaranteed savings from adding AI. Ask whether success means faster processing, fewer corrections, more completed applications or improved access. Keep those outcomes separate from license uptake. Do not use maturity language as a competitive ranking or claim a customer has weak performance merely because public reporting is sparse.
Pre-sales engineering
Role takeaway
Establish a common evaluation record containing workflow version, data boundary, human involvement, task outcome and costs. Map connectors and legacy interfaces before selecting a deployment model; this assessment supplies no local capacity specification. Prerequisites include baseline access, representative cases and consent or other approved handling for evaluation data. Test a limited workflow across ordinary and difficult cases, recording both system output and human corrections. Include accessibility failures and unauthorized disclosure attempts. Require reproducible comparisons across model changes. The proposed design addresses evidence gaps without treating a desk-research maturity rubric as technical assurance.
Delivery
Role takeaway
Put an agency service owner in charge of recurring evaluation, supported by analysts, frontline staff, accessibility specialists and security. First document the current process, then establish a test cohort and reporting cadence. Dependencies include reliable operational data and time for human review. Train staff to log corrections and route incidents without discouraging honest reporting.
- Proposed acceptance criteria
- each pilot has a baseline, named owner, cost report and explicit continuation threshold, with a completed review before expansion. Risks include measuring only usage, missing excluded residents, inconsistent metrics and losing institutional knowledge when pilot staff leave.
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Require reusable evaluation telemetry and inventory identifiers across platforms; do not equate a shared data platform with safe integration.
Governance
Who approves, reviews and stays accountable for outcomes?
Link each use case to outcome measures, review dates and decisions to continue, change or retire.
Security and privacy
What data, permissions and controls need testing?
Collect minimal evaluation data and restrict access to benefits records and sensitive employee prompts.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Measure outcomes for users with disabilities and language needs; include reviewer learning and correction workload.
Procurement
What should contracts, pricing and exit terms secure?
Contracts should preserve measurement access, portability and ability to stop an ineffective pilot.
Operating model
Which teams own the service once it runs?
Give service owners recurring responsibility for performance review rather than making evaluation a one-time launch task.
What changed
New canonical source URL in searched archive. Adds a methodological counterweight to unarchived deployment announcements; older research is explicitly dated and not presented as a fresh event.
Publication history
- 2026-09-06State Government · Issue 013 resources
Stable resource ID: code-for-america-ai-landscape-2026-impact