From the Local Government edition of October 14, 2026
Stanislaus County, California puts an employee GenAI policy on its Oct 13 consent agenda, barring public-tool uploads of confidential data and AI-made decisions
Stanislaus County Board of Supervisors, California · County government workforce AI policy · Stanislaus County, California, United States
- Publisher
- Stanislaus County
- Original publication
- October 13, 2026 (agenda date)
- Source retrieved
- 2026-10-15
- Event date
- 2026-10-13
What happened
The Chief Executive Office recommended the board adopt Personnel Manual Tab 16, an AI policy developed by a staff workgroup. It bars entering non-public information into public GenAI tools, asking GenAI to find facts or make decisions without expert human review, concealing GenAI use (including listening, transcription or translation tools), and using GenAI for employment decisions. It requires written IT approval before integrating GenAI with county systems, lets IT block risky tools, treats prompts as potentially subject to public records requests, cites HIPAA, CJIS, IRS and CCPA obligations, and exempts CIO-approved "Trusted GenAI" from some rules. No immediate fiscal impact; existing staff administer it.
Why it matters
Mid-size California county policy that is practical and specific (disclosure of listening tools, records treatment of prompts, employment-decision ban), useful as a comparison template for other counties.
Evidence and measured results
Board agenda item 5.B.11 PDF opened in full with pdftotext, including the attached September 2026 policy. Search reporting indicated approval; the opened document is the staff recommendation, so final board action was not verified from minutes.
Limitations and uncertainty
Agenda recommendation, not confirmed minutes; Trusted GenAI exemption is undefined in scope; training is voluntary; no inventory or monitoring mechanism described.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-14; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- County needs consistent, enforceable staff GenAI rules without new staff or budget.
- Stakeholders
- Board of Supervisors
- Chief Executive Office
- CIO/ITC
- CEO Human Relations
- Department heads
- Discovery questions
- What criteria will make a tool Trusted GenAI?
- Which departments handle CJIS or HIPAA data?
- How will prompt records be retained for public records requests?
- Is training going to become mandatory?
- Value hypothesis
- Clear approval criteria and training may speed safe adoption under the new policy; no adoption metrics exist.
- Potential engagement
- Short engagement to draft Trusted GenAI criteria, an approved tool list, and staff training aligned to Tab 16.
- Unsupported claims
- That the policy reduced data exposure
- Productivity gains from GenAI in the county
- That the board adopted it unchanged (not verified from minutes)
Pre-sales engineering
Role takeaway
- Fit
- Enterprise GenAI tools that can meet no-training, retention and records requirements.
- Architecture and integration
- ITC written approval gate for any integration with county software; trusted tools separated from public tools.
- Prerequisites
- Defined Trusted GenAI criteria
- Data classification by department
- Records retention guidance for prompts
- Constraints
- CJIS, HIPAA, IRS and CCPA obligations
- No dedicated staffing
- Department-specific stricter rules
- Security
- Public tools barred from confidential data; trusted-tool controls undefined.
- Proof of value
- Test that an enterprise tool meets no-training and retention terms
- Prompt logging retrievable for records requests
- Blocking of unauthorized tools verified
Delivery
Role takeaway
- Work
- Define approval criteria, publish tool list, create training, run integration request process.
- Dependencies
- Board adoption
- ITC capacity
- HR training channels
- Ownership
- ITC with CEO Human Relations.
- Skills and adoption
- Employees learn to verify AI output and disclose AI listening or transcription tools.
- Governance checkpoints
- Board adoption confirmation
- Trusted GenAI designation reviews
- Periodic CIO/CEO policy review
- Acceptance criteria
- Proposed: published Trusted GenAI criteria
- Proposed: approved tool list available to all staff
- Proposed: training completion tracked by department
- Risks
- Shadow use of public tools
- Undefined trusted-tool exemption
- Voluntary training gaps
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?
Distinguishes public GenAI from CIO-approved Trusted GenAI; any integration with county systems needs ITC written approval, implying a review path for enterprise tools.
Governance
Who approves, reviews and stays accountable for outcomes?
CIO and CEO review the policy periodically; departments may add stricter rules; GenAI training is encouraged, not required.
Security and privacy
What data, permissions and controls need testing?
Prohibits credentials, PHI, personnel and confidential material in public tools; names HIPAA, CJIS, IRS and CCPA; treats prompts as public-record-like.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Bans GenAI in hiring, discipline and other employment decisions; employees bear full responsibility for AI output accuracy.
Procurement
What should contracts, pricing and exit terms secure?
Covers acquiring GenAI software but sets no procurement review criteria beyond ITC approval.
Operating model
Which teams own the service once it runs?
Policy administered by existing CEO and IT staff with no added resources.
Publication history
- 2026-10-14Local Government · Issue 395 resources
Stable resource ID: stanislaus-county-employee-genai-policy-board-item-20261013