From the K–12 edition of November 5, 2026
Houston ISD AI Guidebook v3 (Nov. 4) sets teacher-directed AI below grade 6 and parental consent plus teacher permission for older students
Houston Independent School District · K-12 district AI policy · Houston, Texas, United States
- Publisher
- Houston ISD
- Original publication
- November 4, 2026
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-04
What happened
Houston ISD's AI Guidebook Version 3, last updated November 4, 2026, allows students below 6th grade to use only district-approved generative AI in teacher-directed learning, while students in grade 6 and above need written parental consent and prior teacher permission for each approved educational task. Students must disclose AI assistance and may need to produce chat histories; the district says it does not promote AI detectors because of accuracy and bias limits. Classroom-approved tools listed are Google Gemini, Microsoft Copilot, Microsoft Reading Coach and Adobe Creative Cloud Suite; other student-facing tools require AI Support Team vetting. Staff must not enter PII into AI tools, must verify consent, and grades 3-5 generative AI chats are teacher-modeled only without individual student chat access.
Why it matters
Provides a concrete large-district operating model for grade-gated consent, teacher permission, vetted-tool lists and anti-detector guidance that other K-12 systems can compare to their own AI policies.
Evidence and measured results
Primary district guidebook PDF stating rules and approved tools. No compliance or learning-outcome data.
Limitations and uncertainty
Policy text only; consent uptake and classroom adherence unknown; living document may change after Nov. 4.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Large district needs enforceable student AI rules that differentiate elementary and secondary use with consent.
- Stakeholders
- CTO / IT
- Curriculum leaders
- Campus principals
- Teachers
- Parents
- Discovery questions
- How is parental consent captured and checked before Gemini/Copilot access?
- Which grades currently have individual AI chat?
- What is the intake path for MagicSchool or similar tools?
- Value hypothesis
- Matching console access to guidebook gates could reduce unauthorized student AI use.
- Potential engagement
- A policy-to-configuration alignment sprint and campus rollout checklist.
- Unsupported claims
- Learning gains from approved tools
- That detectors are unnecessary in every context
- Statewide transfer without Texas/policy localization
Pre-sales engineering
Role takeaway
- Fit
- Grade-banded controls on Gemini, Copilot, Reading Coach and Adobe with consent/permission checks for grade 6+.
- Architecture and integration
- Interpretation: link SIS grade and consent flags to IdP/app assignments; keep 3-5 in teacher-mediated modes.
- Prerequisites
- Authoritative grade roster
- Consent store
- Teacher permission workflow
- DLP/PII guidance
- Constraints
- Only listed tools approved for student classroom use
- Living document may change
- Monitoring reserved on district devices/networks
- Security
- Prohibit PII in prompts; vet any additional student-facing AI through the AI Support Team.
- Proof of value
- Sample student accounts by grade for correct app access
- Confirm unvetted tools blocked for students
- Verify consent required before grade 6+ chat enablement
Delivery
Role takeaway
- Work
- Deploy guidebook rules campus-wide, collect consent, train teachers and staff the AI Support Team queue.
- Dependencies
- Parent communication
- Teacher PD
- IT app assignment changes
- Ownership
- AI Support Team with teaching and learning and IT.
- Skills and adoption
- Teachers need routines for granting per-task permission, requiring disclosure and modeling chats in grades 3-5.
- Governance checkpoints
- Consent audit before enablement
- Approved-tool list review
- Misuse consequence calibration
- Acceptance criteria
- Consent on file for enabled grade 6+ students
- Published approved-tool list matches console
- Teachers can state disclosure expectations
- Risks
- Incomplete consent
- Shadow AI tools
- Inconsistent teacher permission practices
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?
Identity, consent records and teacher-permission workflow must gate which students can open Gemini/Copilot chats; grades 3-5 need teacher-mediated modes.
Governance
Who approves, reviews and stays accountable for outcomes?
Parental consent and per-use teacher approval become control points; AI Support Team vetting is the path for tools beyond the short approved list.
Security and privacy
What data, permissions and controls need testing?
Staff barred from entering PII into AI tools; district reserves right to monitor student generative-AI use on its devices and networks.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Teacher-directed and teacher-modeled requirements increase adult mediation load in elementary grades.
Procurement
What should contracts, pricing and exit terms secure?
Student-facing tools beyond Gemini, Copilot, Reading Coach and Adobe Creative Cloud need formal AI Support Team vetting.
Operating model
Which teams own the service once it runs?
HISD treats generative AI as a gated instructional resource with consent and permission workflows, not a default student utility.
Publication history
- 2026-11-05K–12 · Issue 603 resources
Stable resource ID: houston-isd-ai-guidebook-v3-parental-consent-teacher-permission-20261104