From the OpenAI edition of October 29, 2026
ABA analysis: government ChatGPT and other AI chatbot prompts and outputs are likely public records, but retention and cost barriers block access
American Bar Association Forum on Communications Law · State and local government (records and transparency) · United States
- Publisher
- American Bar Association, Communications Lawyer
- Original publication
- September 10, 2026 (Fall 2026 issue)
- Source retrieved
- 2026-10-30
What happened
The article argues AI prompts and outputs used for public business are public records under state law and agency records under FOIA, though no court has ruled. It reports researchers found agencies often claim no responsive records or impose high fees (Colorado quoted $9 million), cites Colorado Springs and HUD withholding, and notes the Army requires retention of prompts while DHS contracted with OpenAI to keep communications as federal records.
Why it matters
Every state and local ChatGPT Enterprise rollout, including those under the new OneGov terms, creates records-retention and disclosure obligations that procurement and configuration must address.
Evidence and measured results
Legal analysis with cited reporting and a preliminary Stanford-led study of 105 records requests; examples include Washington cities and TxDOT producing ChatGPT conversations under state public records laws.
Limitations and uncertainty
Commentary by a media-law attorney, advocacy-oriented toward access; not OpenAI-specific; cited study findings are preliminary.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies adopting AI chat tools lack retention and disclosure processes for prompts and outputs.
- Stakeholders
- Agency records officer
- General counsel
- CIO
- Public information officer
- Discovery questions
- Do your retention schedules cover AI prompts and outputs?
- Can you export conversations for a records request today?
- Who decides exemptions for AI-assisted drafts?
- Does your contract address retention and vendor-held data?
- Value hypothesis
- Planning records handling up front may reduce legal risk and request costs.
- Potential engagement
- A bounded records-readiness assessment for an AI rollout, covering retention, export and legal review.
- Unsupported claims
- That courts have settled the question
- That vendor defaults meet state records laws
- Specific OpenAI product retention features
Pre-sales engineering
Role takeaway
- Fit
- Applies to any agency deploying ChatGPT or similar tools for public business.
- Architecture and integration
- Export or compliance API into agency records or archiving systems.
- Prerequisites
- Records schedule update
- Export capability
- Legal review
- Constraints
- State-by-state records law variation
- Unresolved case law
- Security
- Disclosure may include personal data in prompts; apply redaction and minimum-data rules.
- Proof of value
- Retrieve a sample user's conversations through admin export
- Map retention settings to schedules
- Dry-run a records request
Delivery
Role takeaway
- Work
- Update records schedules, configure retention, train staff on capture and run a test request.
- Dependencies
- Legal counsel
- Platform export tools
- Records system
- Ownership
- Agency records officer with legal counsel.
- Skills and adoption
- Staff training on which AI interactions are records and how to save them.
- Governance checkpoints
- Records review before rollout
- Annual retention audit
- Exemption review process
- Acceptance criteria
- Test request fulfilled within statutory deadline (proposed)
- Retention policy documented (proposed)
- Risks
- Litigation over withheld AI records
- High retrieval costs
- Personal data exposure
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?
Agencies need conversation export, retention settings and search for records requests; vendor-held history alone may not satisfy obligations.
Governance
Who approves, reviews and stays accountable for outcomes?
Records schedules, legal review of exemptions and contract terms on retention should be set before rollout.
Security and privacy
What data, permissions and controls need testing?
Disclosure of prompts can expose personal data entered by staff; redaction processes are needed.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Staff need training to recognize AI interactions as records.
Procurement
What should contracts, pricing and exit terms secure?
Contracts should specify retention, export and handling of AI interactions as public records, as DHS reportedly did with OpenAI.
Operating model
Which teams own the service once it runs?
Records management becomes part of AI operations, not an afterthought.
Publication history
- 2026-10-29OpenAI · Issue 016 resources
Stable resource ID: aba-government-ai-chats-public-records-foia-20260910