From the K–12 edition of September 28, 2026
Virginia Code §22.1-20.2:1: division-managed AIS, transcript monitoring, training bans, and evaluated pilots
Commonwealth of Virginia (Code of Virginia) · State statute / education governance · United States — Virginia
- Publisher
- Virginia Legislative Information System
- Original publication
- 2026 (Acts of Assembly cc. 937, 943)
- Source retrieved
- 2026-09-29
What happened
Virginia’s 2026 statute directs VDOE to compile instructional AIS uses and post guidance covering FERPA/COPPA privacy, teacher training, transparency, DPAs that prohibit using division or student data to train external AIS models, bias/accessibility practices, and SOL/HQIM alignment. Guidance must favor division-managed AIS platforms in division-managed environments and ensure teachers can access transcripts of student–AIS interactions with administrator dashboards, automated alerts, and audit logs. School boards must implement consistent policies. An AIS Innovation in Education Pilot Program (expires July 1, 2030) funds/evaluates instruction, tutoring, engagement, operations, and teacher-support uses, prioritizing diverse/high-poverty/rural/under-resourced divisions, requiring PD plus evaluation plans for student learning, teacher workload, and equity, with annual legislative reporting.
Why it matters
Concrete statutory control stack—managed platforms, no external training, transcript supervision, workload/equity evaluation—that other states and vendors will be measured against.
Evidence and measured results
Primary statutory text from LIS; implementation details depend on VDOE guidance and appropriations.
Limitations and uncertainty
Guidance content and pilot funding not fully specified in the statute section alone; effective dates/appropriations need local confirmation; not outcome evidence.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-28; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Virginia divisions need student AI uses that are monitorable, privacy-bounded, curriculum-aligned, and evaluable—not opaque consumer tools.
- Stakeholders
- school boards
- division IT
- instructional leaders
- teachers
- VDOE
- vendors
- Discovery questions
- Can teachers export full transcripts of student–AIS interactions today?
- Does the DPA forbid external model training on division/student data?
- Are dashboards, alerts, and audit logs available to administrators?
- For pilots, how will you measure learning, teacher workload, and equity?
- Value hypothesis
- If vendors deliver division-managed, transcript-visible AIS with no external training on student data, Virginia divisions can meet statutory guardrails while piloting instruction/tutoring uses.
- Potential engagement
- Readiness assessment mapping current AI tools to division-managed criteria and drafting a pilot evaluation plan template.
- Unsupported claims
- That any education chatbot automatically qualifies as a division-managed AIS platform
- Guaranteed pilot funding without appropriation/selection
- That monitoring alone ensures developmental safety
Pre-sales engineering
Role takeaway
- Fit
- Virginia public school divisions and vendors targeting VDOE’s AIS pilot; informative for other states writing monitoring mandates.
- Architecture and integration
- Deploy AIS inside division-managed tenancy; RBAC; transcript store accessible to teachers; admin dashboards/alerts/audit logs; SOL/HQIM content alignment.
- Prerequisites
- Board policies consistent with VDOE guidance
- DPAs banning external training
- Teacher PD on AIS literacy
- Evaluation instrumentation
- Constraints
- Pilot expires July 1, 2030
- Guidance details set by Department
- High-stakes decisions cannot rely solely on AIS
- Security
- FERPA/COPPA compliance; prohibit external model training on student/division data; audit logging and moderation controls.
- Proof of value
- Teacher can open a student transcript within minutes
- Pen-test shows no student data leaving for vendor training
- Pilot eval plan covers learning, workload, equity
Delivery
Role takeaway
- Work
- Align board policy to VDOE guidance, migrate student AI to division-managed platforms, enable transcript/monitoring, and prepare pilot evaluation designs.
- Dependencies
- VDOE guidance publication
- vendor roadmap for transcript APIs
- funding for Pilot Program
- PD calendar
- Ownership
- Board owns policy; IT owns platform controls; instruction owns SOL alignment; evaluation owns impact measurement.
- Skills and adoption
- Train teachers to review transcripts and use dashboards as formative supervision, not only after incidents.
- Governance checkpoints
- Guidance gap analysis
- DPA renegotiation
- Pre-pilot eval plan approval
- Annual Dec. 1 reporting inputs
- Acceptance criteria
- 100% student AIS tools provide teacher transcript access
- Contracts ban external training
- Monitoring dashboards live for admins
- Risks
- Legacy tools cannot export transcripts
- Vendors resist training bans
- Monitoring creates privacy/labor disputes if poorly scoped
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?
Division-managed tenancy, RBAC, transcript storage, monitoring/alerting, and contractual training prohibitions are mandatory design constraints.
Governance
Who approves, reviews and stays accountable for outcomes?
Board policies must track VDOE guidance; pilots need pre-registered learning/workload/equity measures.
Security and privacy
What data, permissions and controls need testing?
Explicit ban on external model training with student/division data; FERPA/COPPA called out; audit logs required.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Guidance must address equitable access and accessibility of AIS resources; pilots prioritize under-resourced divisions.
Procurement
What should contracts, pricing and exit terms secure?
Prefer platforms that can operate as division-managed with transcript/monitoring APIs and training bans in DPAs.
Operating model
Which teams own the service once it runs?
Teacher supervision via transcripts/dashboards becomes an operational duty, not an optional analytics upgrade.
Publication history
- 2026-09-28K–12 · Issue 235 resources
Stable resource ID: virginia-ais-instructional-safety-statute-2026