From the K–12 edition of October 7, 2026
Utah State Board of Education draft rule R277-334 (Draft 1, 5 Oct 2026): districts must keep approved AI tool inventories, bar student generative AI unless an educator authorises it, notify parents and certify compliance
Utah State Board of Education (USBE) · State K-12 rulemaking on classroom technology and AI · Utah, United States
- Publisher
- Utah Public Notice Website (USBE October 2026 committee materials)
- Original publication
- 2026-10-05
- Source retrieved
- 2026-10-08
What happened
Draft 1 of R277-334, Classroom Technology and Artificial Intelligence Governance, dated October 5, 2026, implements H.B. 273 (2026). LEAs must adopt the Board's model AI use policy or a compliant local policy before July 1, 2027, keep an inventory of approved student-facing AI tools, ban biometric surveillance and psychological profiling, and prohibit student generative AI for academic work unless an educator authorises it for a specific purpose. Educators may not use generative AI to independently grade work or make high-stakes determinations. Parents get written notice with a metadata-dictionary link when generative AI is used. High-risk AI interactions may not be used with students. LEAs must train staff, keep records and certify compliance to receive certain state technology funds.
Why it matters
A new state rule draft turns AI policy into auditable operating duties for every Utah LEA, as Utah districts diverge on student Gemini access. Several duties, such as tool inventories, parent notice, educator authorisation and training records, mirror requirements already in the archive for Florida, Oklahoma and Maryland.
Evidence and measured results
Primary-source draft rule text with tracked changes, plus the Board memo and draft model policy posted for the October 2026 committee meeting. It is a proposal at first reading; it reports no outcomes.
Limitations and uncertainty
Draft at first reading; text may change before final adoption. The draft defines 'high-stakes artificial intelligence interaction' but its prohibition refers to 'high-risk', a drafting inconsistency to watch. No fiscal or workload estimate in the materials opened.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Utah LEAs face new statewide AI and classroom technology duties with a July 1, 2027 deadline and funding conditions.
- Stakeholders
- superintendent
- LEA board
- technology director
- teaching and learning director
- student data privacy manager
- charter school leaders
- Discovery questions
- Do you have an inventory of approved student-facing AI tools?
- How will teachers record when they authorise student AI use?
- Can you produce training records for every educator?
- Which tools might involve biometric or profiling features?
- Value hypothesis
- Early inventory and policy work reduces the risk of non-compliance findings and withheld technology funds once the rule is final.
- Potential engagement
- Six-to-eight-week R277-334 readiness review: tool inventory, policy gap analysis, parent notification templates and training plan.
- Unsupported claims
- That the draft will be adopted unchanged
- That compliance improves student outcomes
- Any specific cost of compliance
Pre-sales engineering
Role takeaway
- Fit
- Directly relevant to Utah districts and charters; a template for other states with similar rules.
- Architecture and integration
- Approved-tool registry tied to the student data metadata dictionary, filtering by grade band, and parent-facing tool lists and monitoring access.
- Prerequisites
- current edtech and AI tool inventory
- metadata dictionary under Utah privacy law
- filtering and device management by grade
- Constraints
- draft text may change
- applies to Utah LEAs
- grade-level device and screen-time limits affect where AI tools can run
- Security
- Exclude tools with biometric surveillance or psychological profiling; confirm vendor compliance with Utah student privacy law before adding a tool to the inventory.
- Proof of value
- Produce the approved-tool inventory with metadata links for a sample school
- Demonstrate parent notice for one generative AI activity
- Show training completion records for one staff group
Delivery
Role takeaway
- Work
- Implement R277-334 duties: policy adoption, approved AI tool inventory, educator authorisation practice, parent notice, training and compliance records.
- Dependencies
- final rule adoption
- USBE model policy
- vendor privacy agreements
- Ownership
- Policy office owns adoption and submission; IT owns inventory and filtering; teaching and learning owns educator authorisation and training.
- Skills and adoption
- Educators need training on approved tools, assignment-level AI expectations and not using generative AI to grade independently.
- Governance checkpoints
- public meeting before policy adoption
- submission to the Superintendent
- biennial policy review
- Acceptance criteria
- Proposed: 100% of student-facing AI tools in the inventory with privacy review
- Proposed: training records for all educators before rollout
- Proposed: parent notice issued for each generative AI use
- Risks
- rule text changes late
- inventory goes stale
- funding withheld for non-compliance
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?
Districts need a maintained registry of approved student-facing AI tools linked to the metadata dictionary, device filtering by grade band, and a parent-accessible monitoring system referenced in the rule.
Governance
Who approves, reviews and stays accountable for outcomes?
Policy adoption needs a public meeting, submission to the Superintendent and review at least every two years; non-compliance can bring corrective action or withheld funds.
Security and privacy
What data, permissions and controls need testing?
Explicit bans on biometric surveillance and psychological profiling; AI tools must comply with Utah student privacy law and LEA data governance.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Mandatory staff training on AI tools and integrity; LEAs must plan for students with technology-related learning difficulties and keep IEP and 504 exemptions.
Procurement
What should contracts, pricing and exit terms secure?
Vendors must fit the approved-tool inventory, privacy law and metadata dictionary, and avoid biometric or profiling features to be usable with students.
Operating model
Which teams own the service once it runs?
AI governance becomes a recurring compliance function with records, reporting and funding consequences.
Publication history
- 2026-10-07K–12 · Issue 315 resources
Stable resource ID: usbe-utah-r277-334-draft-classroom-technology-ai-rule-20261005