Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the State Government edition of October 21, 2026

Government auditCautionaryNew this fortnight

GAO finds DOD's Responsible AI working council lapsed for about nine months without a charter and its Responsible AI Division had 3 of 10 positions filled

U.S. Government Accountability Office; Department of Defense Chief Digital and AI Office · Federal AI governance and oversight capacity (transferable evidence) · United States (federal)

Publisher
U.S. Government Accountability Office
Original publication
2026-10-14
Source retrieved
2026-10-22
Read original source

What happened

GAO surveyed 10 DOD components on 10 selected AI use cases and found most took initial steps to set up Responsible AI oversight. But the CDAO's Responsible AI Working Council did not meet from late 2024 until August 2025, and four components said they faced implementation challenges in that period that collaboration would have helped. The council still lacks a charter defining roles and meeting frequency, so it could lapse again. As of February 2026 only three of 10 authorized Responsible AI Division positions were filled, which officials said hindered further actions. GAO recommends a charter and addressing staffing; DOD concurred.

Why it matters

Why now: released Oct 14 and covered in trade press on Oct 21, it is audit evidence that AI governance bodies without charters and staff stop functioning, which bears directly on state AI councils and cabinets, such as Illinois' unstaffed AI Cabinet. Transferability is limited by DOD's scale and mission, but the governance mechanics (charter, cadence, staffing) apply to states.

Evidence and measured results

GAO audit: document review, a survey of 10 components on 10 selected use cases, interviews. Quantified: council inactive late 2024 to August 2025; 4 components reported challenges; 6 of 10 said shared resources would help; 3 of 10 division positions filled as of February 2026. Survey covers selected use cases, not all DOD AI.

Limitations and uncertainty

Federal defense context; staffing and organizational scale differ sharply from states. Findings rely partly on component self-reporting in a survey of selected use cases.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-21; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
AI governance bodies are created but under-resourced, leaving agencies without consistent guidance as adoption speeds up.
Stakeholders
  • State chief AI officer
  • State CIO
  • AI council chair
  • Legislative audit staff
  • Agency AI leads
Discovery questions
  • Does your AI council have a written charter and meeting cadence?
  • How many staff support AI governance centrally?
  • Have meetings lapsed, and what happened to approvals then?
  • Do agencies interpret AI guidance consistently?
Value hypothesis
A governance capacity review may reduce the risk of stalled or inconsistent AI oversight; GAO evidence shows the risk in a federal setting.
Potential engagement
Four-week AI governance capacity assessment: charter review, staffing analysis, meeting history and guidance consistency across three agencies.
Unsupported claims
  • That state councils are failing
  • That staffing alone fixes oversight
  • Direct transfer of DOD findings to states
  • Cost or speed benefits of governance

Pre-sales engineering

Role takeaway
Fit
States with multiple agencies adopting AI under one central governance body with limited staff.
Architecture and integration
Shared governance tooling (use-case inventory, risk assessment templates, approval tracking) used across agencies.
Prerequisites
  • AI use-case inventory
  • Standard risk assessment template
  • Defined approval workflow
  • Named governance owners
Constraints
  • Small central teams
  • Agency autonomy
  • Advisory bodies without authority
  • Federal context of evidence
Security
Ensure security review steps are captured in governance tooling so they continue when councils pause.
Proof of value
  • Share of AI use cases with completed risk assessments
  • Time from proposal to governance decision
  • Consistency of decisions on similar use cases across agencies

Delivery

Role takeaway
Work
Establish or strengthen a chartered, staffed AI governance council and its supporting processes.
Dependencies
  • Executive sponsor
  • Central AI office staff
  • Agency representatives
  • Legal counsel
Ownership
State chief AI officer or CIO as council owner.
Skills and adoption
Train agency AI leads on shared templates so guidance is applied consistently when central staff are scarce.
Governance checkpoints
  • Written charter approved
  • Meeting cadence set and tracked
  • Staffing plan funded
  • Annual review of council effectiveness
Acceptance criteria
  • Proposed: charter defines roles and meeting frequency
  • Proposed: no lapse longer than one scheduled cycle
  • Proposed: authorized governance positions filled or a mitigation plan in place
Risks
  • Council lapses during leadership change
  • Vacant governance positions
  • Inconsistent agency interpretation
  • Governance seen as overhead and cut

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?

Limited relevance: not a technology finding. Interpretation: governance capacity, not tools, can be the constraint on scaling AI responsibly.

Governance

Who approves, reviews and stays accountable for outcomes?

Working-level AI governance needs a charter with roles and meeting cadence, and a staffed central office. States should check whether their AI councils have both, and whether gaps in meetings leave agencies interpreting guidance inconsistently.

Security and privacy

What data, permissions and controls need testing?

Not addressed directly; inconsistent interpretation of guidance during council lapses is the stated risk.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

AI workforce shortfalls in the oversight office itself, not only in delivery teams, limited progress; GAO also flags unaddressed prior recommendations on defining the AI workforce.

Procurement

What should contracts, pricing and exit terms secure?

Not addressed in the audit summary.

Operating model

Which teams own the service once it runs?

Central responsible-AI office plus a working-level council of components; without a charter and staffing the council stopped meeting.

Publication history

  1. 2026-10-21State Government · Issue 444 resources
Read preserved resource versions (JSON)

Stable resource ID: gao-dod-responsible-ai-council-lapse-division-3-of-10-staffed-20261014