From the K–12 edition of November 10, 2026
Texas 2036: In Ctrl of AI in Schools, a Texas policy report on AI governance, student safety, learning evidence and AI literacy
Texas 2036 · K-12 education policy · Texas, United States
- Publisher
- Texas 2036
- Original publication
- 2026-11-10
- Source retrieved
- 2026-11-11
What happened
The report finds AI is already in Texas classrooms but largely unguided: in fall 2025, 86% of school and district leaders reported teacher AI use and 61% student use, yet only 29% reported a district policy on student AI use and 20% one on teacher and staff use. It argues FERPA obligations fall on schools rather than vendors, that student PII includes indirect identifiers, and that learning evidence is genuinely mixed. It recommends a state baseline for responsible use, pre-classroom vetting of tool safety and efficacy, educator AI literacy and student AI literacy.
Why it matters
Directly useful for district governance and procurement: it turns privacy law, tool design risks and mixed learning evidence into vetting requirements, and shows a state-level standard-setting gap that districts must otherwise fill individually.
Evidence and measured results
Policy report synthesizing the March 2026 Stanford evidence review, two meta-analyses (generative AI feedback; higher-order thinking), individual studies, and national and Texas surveys. Literature search ended August 2026; survey and policy data current to October 2026. The adoption and policy figures come from a Texas AI in Education Task Force report cited by the authors.
Limitations and uncertainty
Advocacy-oriented policy report from a Texas organization, not a primary evaluation. It states that most underlying evidence comes from outside the United States, reviews draw more on higher education than K-12, causal studies are few and some not peer reviewed, and findings are early signals. Adoption and policy percentages are self-reported leader survey figures. Legal statements are the authors' interpretation, not legal advice.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Districts use AI widely but few have policies, and vetting duties for student data fall on the school.
- Stakeholders
- Superintendent
- Chief technology officer
- Privacy officer or counsel
- Curriculum leaders
- School board
- Discovery questions
- Do you have written policies covering student and staff AI use?
- Which AI tools are teachers using that were never vetted?
- How would you inspect or correct an AI-generated student record?
- Value hypothesis
- A structured tool inventory and vetting process can reduce unmanaged privacy exposure and give principals a consistent baseline.
- Potential engagement
- Bounded AI tool inventory, vetting framework and policy baseline for one district.
- Unsupported claims
- Legal compliance certification
- That policies improve learning outcomes
- That Texas findings apply uniformly to other states
Pre-sales engineering
Role takeaway
- Fit
- Relevant where districts need a technical vetting checklist for AI tools touching student data.
- Architecture and integration
- Map data flows from classroom tools to vendors, including identifiers created by accounts and any generated records, and align with existing data-privacy agreements.
- Prerequisites
- Inventory of AI tools in use
- Data privacy agreements
- Account and identity management visibility
- Constraints
- Report is policy analysis, not product testing
- FERPA points are interpretation
- Texas-specific laws
- Security
- Check indirect identifiers, vendor training on student data, and record access and correction; do not treat school-email accounts as de-identification.
- Proof of value
- Inventory shows percentage of tools vetted
- Sample tool data-flow review
- Test whether a generated record can be inspected and corrected
Delivery
Role takeaway
- Work
- Run inventory, set policy baseline, stand up vetting workflow, then train educators and students.
- Dependencies
- Counsel review
- Board policy process
- Teacher time for training
- Ownership
- District technology and privacy office with curriculum partners.
- Skills and adoption
- Educators need baseline AI knowledge to recognize risks even if they do not use AI themselves.
- Governance checkpoints
- Policy adoption
- Vendor vetting sign-off
- Periodic tool re-review
- Acceptance criteria
- Proposed: written policies for student and staff AI use adopted
- Proposed: all in-use AI tools inventoried and tiered
- Proposed: vetting completed before new tool approvals
- Risks
- Unvetted consumer tools persisting
- Policy not matched by training
- Legal interpretation errors
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?
Because a tool's output may create or alter education records, districts need visibility into what student data flows to tools and whether records can be inspected and corrected; black-box tools make this hard.
Governance
Who approves, reviews and stays accountable for outcomes?
Districts, not vendors, carry FERPA compliance duties, so vetting must ask whether the district can use a tool compliantly; Texas leaders lack consistent policy, supporting state baselines and pre-classroom safety review.
Security and privacy
What data, permissions and controls need testing?
Student PII is broader than names: indirect identifiers and school-email accounts do not de-identify data. The report also flags sycophantic design and developmental risks of consumer chatbots for students.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
The report stresses educator AI literacy, noting the research base on it is thin, and recommends foundational training whether or not educators use AI themselves.
Procurement
What should contracts, pricing and exit terms secure?
Vetting should ask whether the district can use the tool compliantly; no product can be FERPA-compliant on its own, so contracts need data-use, retention and record-access terms.
Operating model
Which teams own the service once it runs?
Without state standards, vetting varies by district and classroom; districts need a named owner and a common baseline.
Publication history
- 2026-11-10K–12 · Issue 653 resources
Stable resource ID: texas-2036-in-ctrl-of-ai-in-schools-governance-safety-learning-20261110