From the Local Government edition of October 6, 2026
Los Angeles County AI Policy 6.106 bans fully automated high-impact decisions and unapproved AI tools, but Board vote is continued to Nov. 10
County of Los Angeles (Chief Executive Office / Office of the CIO; Board of Supervisors) · County AI governance policy · Los Angeles County, California, United States
- Publisher
- County of Los Angeles Board of Supervisors (board letter and enclosed policy)
- Original publication
- October 6, 2026 (board letter); supplemental agenda posted October 2, 2026
- Source retrieved
- 2026-10-07
- Event date
- 2026-10-06
What happened
The county's CEO asked the Board to adopt Board Policy 6.106, which the Audit Committee approved Sept. 16. It sets eight principles, requires disclosure of AI-generated work product, and prohibits fully automated decisions that substantially affect people without meaningful human review, covert tracking or social scoring, manipulation, and the use of unapproved AI tools to upload non-public data, make official decisions, replace staff or produce authoritative work without human verification. It allows no exceptions. A supplemental agenda shows Supervisor Mitchell asked to continue the item to Nov. 10.
Why it matters
The largest U.S. county is codifying a prohibited-use list and named security and privacy roles, yet adoption has been deferred; this is a concrete template and a reminder that board timing is not guaranteed.
Evidence and measured results
Primary board letter and policy text, plus the supplemental agenda continuance entry; no implementation data.
Limitations and uncertainty
Reasons for continuance not stated; printed sunset date 'September 31, 2030' is not a real date; Board minutes not inspected.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Departments are using AI without an adopted countywide rulebook, and the proposed policy's prohibitions will require visible controls once approved.
- Stakeholders
- Board of Supervisors and deputies
- Chief Executive Office
- County CIO
- CISO
- Chief Privacy Officer
- Department CIOs
- Discovery questions
- Why was the item continued, and what changes are expected?
- Which AI tools are approved today?
- How will departments prove human review for high-impact decisions?
- How is AI-generated work product disclosed now?
- Value hypothesis
- Readiness work could shorten the time from adoption to compliance; no measured benefit is reported.
- Potential engagement
- A department-level gap assessment against the proposed prohibited-use list, delivered before the Nov. 10 hearing.
- Unsupported claims
- The policy has been adopted
- Any tool guarantees compliance
- The text will remain unchanged
Pre-sales engineering
Role takeaway
- Fit
- Fits policy-driven controls for approved tools, data classification and output disclosure; does not by itself define technical standards.
- Architecture and integration
- Approved AI catalogue linked to identity and data classification, egress monitoring for unapproved AI services, output labelling and decision logs with reviewer identity.
- Prerequisites
- Data classification under Policy 6.104
- Inventory of department AI uses
- Central logging
- Identity and access management
- Constraints
- Board approval pending
- Decentralised department IT
- Criminal justice and health data rules
- Possible text amendments
- Security
- Keep PII, PHI and CJI out of unapproved services, enforce access controls, and route AI incidents through the CISO's incident process.
- Proof of value
- Sample audit of one department's AI tool use against the prohibited list
- Test egress monitoring for unapproved AI domains
- Check that high-impact decisions record a named human reviewer
Delivery
Role takeaway
- Work
- Prepare departments to comply with Policy 6.106 if adopted: inventory, review evidence, disclosure templates and training.
- Dependencies
- Board adoption on or after Nov. 10
- Department CIO participation
- CISO and privacy office capacity
- Final policy text
- Ownership
- Chief Executive Office / Office of the CIO, with department CIOs.
- Skills and adoption
- Staff training on prohibited uses, disclosure of AI-generated work and when human verification is required.
- Governance checkpoints
- Board vote
- Corrected sunset date and final text
- First department compliance review
- Acceptance criteria
- Every department reports AI uses in a common inventory within a set period after adoption
- Each high-impact AI-assisted process documents a human reviewer
- Unapproved AI service use is measured and reported
- Risks
- Further delay or amendment
- Departments treating 'no exceptions' as unworkable and bypassing it
- Training lag
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?
The ban on unapproved AI sites and models for non-public data implies an approved-tool catalogue, data-classification enforcement and egress controls tied to existing Policy 6.104.
Governance
Who approves, reviews and stays accountable for outcomes?
A no-exceptions policy with CIO, CISO and Chief Privacy Officer roles centralises accountability, but the continuance means departments operate under the earlier framework until at least Nov. 10.
Security and privacy
What data, permissions and controls need testing?
Explicitly covers PII, PHI and Criminal Justice Information and assigns incident response to the CISO.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
A workforce-empowerment principle favours retraining over displacement and bars using unapproved AI to supplant staff or contractors.
Procurement
What should contracts, pricing and exit terms secure?
Policy applies to AI that is developed, procured or accessed through third-party platforms, so vendor terms must meet transparency and privacy requirements.
Operating model
Which teams own the service once it runs?
Department CIOs carry compliance duties under a central CIO-led AI Governance Framework.
Publication history
- 2026-10-06Local Government · Issue 316 resources
Stable resource ID: la-county-board-policy-6106-ai-continued-20261006