Oklahoma SB 1734 School AI Requirements and Parent Opt-Out

Current status: Last reviewed August 17, 2026 against the enrolled act and official bill history. This is educational information, not legal advice.

Oklahoma SB 1734 requires public school districts to put safeguards around student-facing AI, disclose covered tools and data practices annually, honor a written parent opt-out at any time, provide an alternative path to core instruction, and adopt a district AI policy before the 2027-2028 school year. The act took effect July 1, 2026.

The parent-choice provision is operational, not merely a notice requirement. An opted-out student may not be academically penalized or denied core instructional content. A district therefore needs a reliable way to record the choice, apply it to covered student-facing tools, notify the right educators, and provide an equivalent instructional path.

The requirements at a glance

Topic	What the enrolled act says	District implementation record
Effective date	July 1, 2026	Legal review and implementation timeline
Human oversight	Educator or authorized employee reviews output before it is used for instruction, feedback, assessment, or a student-affecting decision	Named reviewer, workflow, exception path, and retained approval evidence
High-stakes decisions	AI may not be the primary basis for grading, discipline, placement, promotion, retention, or another high-stakes educational decision	Decision-owner matrix and human sign-off standard
Student-facing suitability	Tool must be age- and developmentally appropriate and serve a defined educational purpose	Approved-use record by grade, purpose, account, and feature
Data minimization	District takes reasonable steps to minimize student data shared with AI systems	Data map, field-level minimization, technical test, and owner
Annual disclosure	Identify tools, vendors, data categories, sharing extent, and educational purpose	Family notice, publication date, distribution evidence, and current inventory
Parent opt-out	Written notice may be provided at any time for student-facing AI participation	Choice record, effective date, covered uses, owner, and change history
Alternative instruction	No academic penalty or denial of core content	Equivalent non-AI workflow, materials, grading path, and educator notice
Board policy	Adopt before the 2027-2028 school year	Adopted policy, board record, version, effective date, and review calendar

This table is an implementation aid. District teams should work from the enrolled act, current Oklahoma law, agency guidance, board policy, and counsel.

Which AI uses are covered?

SB 1734 centers its classroom safeguards and parent-choice provision on student-facing AI tools used for instructional or educational purposes. That is narrower than every possible use of AI by a district.

A practical inventory should distinguish:

a student directly interacting with a chatbot or AI feature;
an educator using AI to prepare materials before students see them;
AI generating feedback, an assessment, or a recommendation about a student;
a district-built application calling an AI model in the background;
administrative or operational AI with no student interaction; and
an AI feature embedded inside an otherwise approved application.

The legal and operational controls can differ across those categories. Do not apply a student-facing label to everything simply because an AI model appears somewhere in the system. Do not exclude an embedded chatbot merely because the district originally approved the host application for a different purpose.

Use the AI application register template to record the purpose, users, data, vendor, model, decision owner, and current status of each use.

How to build a usable parent opt-out workflow

An opt-out checkbox is only the beginning. The full workflow should answer seven questions.

1. Who can submit and revoke the choice?

Define how the district verifies the parent or legal guardian, how a student is matched, when the choice becomes effective, and how a later change is handled. Avoid storing more identity data than the workflow needs.

2. Which uses does the choice control?

Map the choice to student-facing AI participation, not to a vague global flag that nobody can interpret. The record should identify which products, features, classes, or instructional workflows are affected and who maintains that mapping.

3. How do educators learn that an alternative is required?

The district needs a role-appropriate signal that reaches the responsible educator before the activity. A choice that remains inside an administrative system while a student is assigned the AI activity is not operational.

4. What is the alternative?

Design the non-AI activity before the AI activity is assigned. It should preserve access to the core instructional content and a fair path to demonstrating the same objective. The alternative should not publicly identify or stigmatize the student.

5. How does grading remain fair?

Document how both paths are evaluated. The parent choice cannot quietly produce a lower participation grade, reduced access, or a more burdensome assessment without a defensible instructional reason.

6. What happens when AI is embedded in another product?

Maintain a feature-level inventory. A product may add a writing assistant, tutor, or conversational interface after procurement. The district needs a way to detect the changed surface, re-evaluate it, and determine whether the parent-choice rule applies.

7. What evidence is retained?

Retain the choice, effective period, covered uses, educator notification, alternative offered, and resolution of exceptions. Avoid storing student prompts or responses merely to prove the control exists.

Human review must be a real control

The act requires review before AI output is used for instruction, feedback, assessment, or a decision affecting a student. A general statement that “a human remains in the loop” is not enough.

For each covered workflow, record:

the qualified human role;
what the reviewer can see;
what the reviewer must check;
whether the reviewer can reject or revise the output;
what happens if the reviewer is unavailable;
what evidence is retained; and
which decisions AI may never control as the primary basis.

This matters most when a tool appears to save time. A one-click approval screen can become a rubber stamp if the reviewer lacks context, time, authority, or a practical way to correct the output.

Annual disclosure needs a maintained inventory

The required disclosure cannot be accurate if tool ownership is scattered across technology, curriculum, schools, and individual classrooms.

At minimum, the working inventory should include:

product and vendor;
specific AI feature or model route;
educational purpose;
covered users and grades;
student-data categories;
whether and how data is shared;
approved accounts and configurations;
parent-choice applicability;
human-review owner;
approval date and next review; and
retirement or suspension status.

Pair the inventory with the AI tool vetting and approval template and vendor and DPA review questions. A contract review and a point-of-use data-minimization control solve different problems.

How Tenet may support an Oklahoma implementation

Tenet by TrueMadeAI is K-12 AI governance software. Tenet Edge applies district and classroom policy on supported direct-use AI surfaces on managed Chrome. Tenet Gateway is a founding-district program for approved backend AI operations.

A district implementation could use Tenet to help:

present role-, class-, subject-, and schedule-aware rules on supported surfaces;
block supported unapproved AI chat and writing interfaces;
apply supported on-device data-loss-prevention controls before content leaves the device;
route approved backend AI operations through defined application, purpose, data, and failure boundaries; and
retain bounded operational evidence without treating raw student conversations as analytics.

TrueMadeAI is preparing an administrator-managed parent opt-out setting. It is not described here as a shipped capability. Before release, it needs an authoritative source of parent choice, clear scope, propagation to the relevant enforcement points, educator-visible alternative-workflow support, tests, and auditable change handling. A district should not buy or represent a planned control as current functionality.

Tenet does not replace legal review, policy adoption, procurement, educator judgment, alternative instruction, or the district’s responsibility to determine which uses SB 1734 covers. Review the dated capability matrix before relying on a specific product surface.

If your district wants to map one Oklahoma policy and parent-choice workflow to supported controls, request a scoped Tenet District conversation.

A 90-day implementation sequence

Days 1-30: establish scope

Confirm the current legal text and responsible counsel.
Assign a district owner and board-policy workstream.
Inventory student-facing AI tools, embedded features, and vendors.
Identify current high-stakes and AI-assisted decision workflows.
Document how parent choices are received today.

Days 31-60: design controls

Define approved purposes and age or grade boundaries.
Build the annual disclosure from the maintained inventory.
Create the parent opt-out, educator notification, and alternative-instruction workflow.
Specify human-review standards and prohibited primary-basis decisions.
Test data minimization at the actual point of use.

Days 61-90: validate and govern

Test representative student, educator, parent-choice, and exception scenarios.
Train the people who own approval, review, alternatives, and incidents.
Correct gaps before broad rollout.
Prepare the board record and policy implementation evidence.
Set review triggers for new features, vendors, laws, incidents, and school-year changes.

What this guide does not establish

This guide does not determine:

whether a particular district use is legally student-facing;
whether written notice must use a particular form;
whether another state or federal law creates additional consent, privacy, accessibility, or records duties;
that a contract, DPA, approved list, or technical product alone creates compliance;
that every Tenet control applies to every AI product or data path; or
the legal consequence of a missed deadline or failed implementation.

Those conclusions require the current official sources, the district’s facts, and qualified review.

Sources

Frequently asked questions

When did Oklahoma SB 1734 take effect?

The enrolled act states that it became effective July 1, 2026. Its district-board policy requirement applies before the beginning of the 2027-2028 school year.

Does Oklahoma SB 1734 give parents an AI opt-out?

Yes. A parent or legal guardian may provide written notice at any time to opt a student out of participating in student-facing AI tools. The student may not be academically penalized or denied access to core instructional content.

Does the opt-out cover every use of AI by a school district?

The cited provision is framed around participation in student-facing AI tools. Districts should not automatically restate it as a prohibition on every staff, administrative, security, or backend AI use without further legal analysis.

Can AI grade students under Oklahoma SB 1734?

The act says AI may not be used as the primary basis for grading or other listed high-stakes educational decisions. It also requires an educator or other authorized employee to review AI output before it is used for assessment, feedback, instruction, or a decision affecting a student.

What must Oklahoma districts disclose annually?

The annual disclosure must identify the AI tools and vendors used, the categories of student data collected or shared, the extent of data sharing, and the educational purpose for which each tool is used.

Does Tenet already provide the Oklahoma parent opt-out setting?

No claim is made that this setting is shipped today. TrueMadeAI is preparing an administrator-managed parent opt-out capability. It must be implemented, tested, and documented before it can be treated as a current Tenet control.