From the K–12 edition of September 23, 2026
California releases adaptable TK–12 AI model policy rejecting detector-only discipline and mandating privacy-by-design
California Department of Education · K-12 state education agency standards and guidance · California, United States (TK–12 LEAs and charter schools)
- Publisher
- Model Policy: Artificial Intelligence In Education
- Original publication
- June 25, 2026 (model policy posted; superintendent letter July 6, 2026; page last reviewed June 26, 2026)
- Source retrieved
- 2026-09-24
- Event date
- 2026-06-25
What happened
CDE’s SB 1288 model policy (posted June 25, 2026; Thurmond letter July 6) gives LEAs a ready-to-adapt template: disclose AI use; ban detector-only discipline/grade penalties; authorize only district-approved tools; privacy-by-design with no training/advertising on student data; FERPA/EC 49073.1 compliance; annual guardian consent for autonomous AI student tools; parent human-review rights; pre-deployment evaluation; enforceable vendor clauses (breach notice, audit, deletion); educator-of-record grading authority; AI literacy as core competency; biennial strategy review. Newly relevant on 2026-09-23 because LAUSD’s student GenAI moratorium and nationwide pause/boundary debates leave California LEAs drafting fall policies against a concrete SEA checklist—without making compliance mandatory (EC 33308.5).
Why it matters
California LEAs now have an explicit sales/engineering checklist: detectors cannot be sole evidence; contracts need audit/deletion/training bans; literacy and human grading authority are policy defaults.
Evidence and measured results
Opened the CDE model-policy page via WebFetch (26 principles) and the July 6 release letter confirming June 25 posting under SB 1288; cross-checked themes against CDE AI Guidance PDF downloaded the same session (human-centered AI, literacy, privacy sections).
Limitations and uncertainty
Non-mandatory exemplary policy; not an effectiveness study; LAUSD local moratorium may be stricter than the model’s permission structure; full DOCX template not re-downloaded beyond HTML page.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- CA LEAs need adaptable AI policy language covering integrity, privacy, literacy, and vendor contracts without treating CDE text as a mandate.
- Stakeholders
- superintendent
- board counsel
- privacy officer
- curriculum
- teachers association
- parents
- Discovery questions
- Have you adapted CDE’s SB 1288 model policy locally?
- Do vendor contracts ban training/advertising on student data with audit rights?
- Are AI detectors used as sole discipline evidence today?
- Is guardian consent required for autonomous student AI tools?
- Value hypothesis
- Vendors whose DPAs already match CDE privacy-by-design and audit/deletion clauses shorten CA legal review.
- Potential engagement
- Policy-to-DPA crosswalk against the 26 model principles and a detector-use compliance check.
- Unsupported claims
- That adopting the model policy is legally mandatory
- That the policy proves any tool improves learning
- That detector avoidance alone stops AI cheating
Pre-sales engineering
Role takeaway
- Fit
- Fit for CA LEAs building approved-tool catalogs and consent workflows; weaker for consumer-chat classroom norms.
- Architecture and integration
- Approved-vendor SSO gate; consent registry; human-review workflow for AI-informed decisions; logging without automatic detector discipline hooks.
- Prerequisites
- board policy adaptation
- privacy officer capacity
- approved-vendor process
- Constraints
- non-mandatory status
- local bargaining
- LAUSD-style stricter pauses
- Security
- No student PII in unauthorized tools; encryption and breach notice per contract; deletion on termination.
- Proof of value
- Show personal ChatGPT account blocked from student-data use
- Demonstrate consent capture before autonomous student AI
- Confirm detector output cannot alone change a grade in the SIS
Delivery
Role takeaway
- Work
- Adapt model language, run vendor evaluations, train on disclosure and AI literacy progressions, and set biennial review.
- Dependencies
- legal
- IT
- curriculum
- communications
- bargaining units
- Ownership
- Superintendent/board for policy; privacy officer for contracts; curriculum for literacy.
- Skills and adoption
- Educator AI literacy PD; student claim-check and source triangulation skills per model language.
- Governance checkpoints
- First board reading
- Vendor addendum executed
- Consent process live
- Biennial strategy scheduled
- Acceptance criteria
- Local AI policy posted
- At least one vendor contract with audit/deletion/training-ban clauses
- Detector-only discipline prohibited in written regulation
- Risks
- LEAs treat exemplary text as optional and stall
- Stricter local pauses conflict with literacy pilots
- Consent fatigue
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?
Approved-vendor lists with wellbeing monitoring; consent workflow for autonomous student AI; human review queues for AI outputs affecting decisions; no personal AI accounts for student data.
Governance
Who approves, reviews and stays accountable for outcomes?
Local boards adapt exemplary language; biennial multistakeholder strategy review; instructional discretion per assignment with family communication.
Security and privacy
What data, permissions and controls need testing?
Privacy-by-design, training/advertising bans, breach notification, audit rights, and deletion-on-termination become contract norms; confidential records barred from learning tools unless authorized.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Model ties AI deployment to ongoing PD in AI literacy, data fluency, and learning science so access is not license-only; equitable access to institutionally approved tools is explicit.
Procurement
What should contracts, pricing and exit terms secure?
Pre-deployment evaluation and contractual safeguards (breach, audit, deletion, unauthorized-use liability) become the CA procurement checklist even though the model itself is non-mandatory.
Operating model
Which teams own the service once it runs?
Human-centered operating model: educator discretion per assignment, educator-of-record grading, biennial multistakeholder strategy—not automated high-stakes decisions.
Publication history
- 2026-09-23K–12 · Issue 185 resources
Stable resource ID: cde-model-policy-ai-education-20260625