From the K–12 edition of October 14, 2026
Oklahoma SDE updated model board AI policy (Oct 2026): approved-tool review, AI inventory, annual parent notification, opt-out rights and full compliance by 2027–28
Oklahoma State Department of Education (OSDE) · State education agency / K-12 district board policy · United States (Oklahoma)
- Publisher
- Oklahoma State Department of Education
- Original publication
- Updated October 2026 (PDF created October 1, 2026)
- Source retrieved
- 2026-10-15
What happened
OSDE posted an updated model board policy, 'Artificial Intelligence (AI) Use in Schools', in October 2026 for districts implementing the 2026 Oklahoma Responsible Technology in Schools Act (70 O.S. § 11-120). The four-page template defines classroom, student-facing, administrative and third-party vendor AI and requires human-in-the-loop review. It assigns roles (board, superintendent, technology department approval of tools, educators, students) and lists approved and prohibited educator uses; prohibited uses include AI as the primary basis for grades, discipline or placement, deepfakes, and entering sensitive student data into consumer-grade tools. It requires data minimisation, district-approved tools only, a current AI tool inventory, vendor FERPA/COPPA compliance, annual parent notification of tools, vendors, data and purpose, 30-day notice for new data-collecting tools, opt-out from any student-facing AI tool with non-AI alternatives, annual review, a public AI Impact Report, and full compliance by the start of 2027–28. Why now: the October update follows Oklahoma Watch's archived Oct 5 report on uneven district implementation and gives the primary template districts are adopting.
Why it matters
A concrete U.S. state template that turns AI governance into board-adoptable obligations with a compliance date. Gives vendors and districts a checklist (inventory, notification, opt-out, impact report) likely to recur in other states.
Evidence and measured results
Primary policy template, not an evaluation. Requirements are stated obligations; there is no data on adoption or effectiveness. Bracketed fields indicate districts customise it.
Limitations and uncertainty
Model template only; districts may alter it. Not evidence that policies are implemented or effective. The liability clause's enforceability is not established. Retrieved PDF metadata shows October 1 creation; the agency page labels it updated October 2026.
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
- Oklahoma districts must adopt and operationalise AI governance (inventory, notices, opt-out, impact reporting) by 2027–28 with limited staff.
- Stakeholders
- Superintendent
- School board
- Technology director
- Privacy / data officer
- Principals
- Parent liaison
- Discovery questions
- Has the board adopted the OSDE model or a variant?
- Do you have a complete AI tool inventory including embedded features?
- How will you deliver opt-out alternatives for student-facing tools?
- Who will produce the annual AI Impact Report?
- Value hypothesis
- Structured readiness work could reduce compliance risk and parent complaints by producing the required artefacts on time; no measured outcome is available.
- Potential engagement
- Compliance-readiness package: inventory build, vendor data register, parent notice template, opt-out workflow and first AI Impact Report outline.
- Unsupported claims
- The template does not show learning or workload benefits.
- No evidence that the liability clause shields districts.
- Adoption rates are unknown.
Pre-sales engineering
Role takeaway
- Fit
- Fits ed-tech management, SSO and data-privacy platforms that can track apps, data flows and per-student settings.
- Architecture and integration
- Link the AI inventory to app approval and SSO catalogues, maintain vendor data-flow records, propagate opt-out flags from the SIS to student-facing tools, and collect usage logs for audits.
- Prerequisites
- Board-adopted policy
- App approval workflow
- SIS field for AI opt-out
- Vendor DPAs covering AI features
- Constraints
- Oklahoma statute and OSDE guidance specific
- Vendors may not support per-student AI disablement
- Embedded AI in suites complicates inventory
- Security
- Approved tools only, data minimisation, vendor FERPA/COPPA and state cybersecurity compliance, incident response, and blocking sensitive data in consumer AI.
- Proof of value
- Inventory reconciled against SSO and network logs
- Opt-out flag verified to disable AI in sample tools
- Parent notice generated from vendor data register
- Usage audit export tested for impact report
Delivery
Role takeaway
- Work
- Adopt the model policy and build inventory, notification, opt-out and impact-reporting processes before 2027–28.
- Dependencies
- Board approval
- Vendor cooperation on data disclosures
- SIS changes
- Committee staffing
- Ownership
- Superintendent's designee chairing the District AI Governance Committee; technology department for tool review.
- Skills and adoption
- Teacher training on approved and prohibited uses and opt-out alternatives; front-office staff on parent notices.
- Governance checkpoints
- Board policy adoption
- Tool approval before classroom use
- Annual parent notification
- Annual policy review and public AI Impact Report
- Acceptance criteria
- Policy adopted with dated approval
- Inventory covers all approved AI tools
- Annual parent notice issued
- Opt-out alternatives documented for each student-facing tool
- First AI Impact Report published
- Risks
- Shadow AI outside inventory
- Opt-out burden on teachers
- Vendor non-disclosure
- Liability clause over-relied upon
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?
Requires a maintained AI tool inventory, district-approved tools only, and the ability to give opted-out students non-AI alternatives. Interpretation: districts need an inventory linked to app approval workflows and per-student opt-out flags that downstream tools respect.
Governance
Who approves, reviews and stays accountable for outcomes?
Board approves the policy; superintendent oversees governance and periodic audits; a District AI Governance Committee updates the inventory, audits usage and publishes an annual public AI Impact Report. The template includes a liability-protection clause for good-faith use that districts should review with counsel.
Security and privacy
What data, permissions and controls need testing?
Data minimisation, approved tools meeting security standards, vendor FERPA/COPPA and state cybersecurity compliance, incident response, and a ban on entering sensitive student data into consumer-grade AI tools.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Approved educator uses include differentiation and accessibility supports; opt-out requires non-AI alternatives, which adds teacher workload; educators remain responsible for instructional decisions.
Procurement
What should contracts, pricing and exit terms secure?
Vendors must comply with FERPA, COPPA, state law and cybersecurity requirements and disclose data for parent notices; only district-approved tools allowed.
Operating model
Which teams own the service once it runs?
Creates a standing AI Governance Committee with annual inventory updates, usage audits and public reporting.
Publication history
- 2026-10-14K–12 · Issue 385 resources
Stable resource ID: osde-model-ai-use-policy-update-202610