The Board Policy Mandate Is Live.  ·  Virginia HB 1186, Chapter 937, approved April 13, 2026 · Every School Board Must Adopt AI Policies Consistent With State Guidance
Virginia HB 1186  ·  State Legislation  ·  October 10, 2026

Every Virginia School Board Must Adopt AI Policies, and the Law Names the Standard

By Dr. Reginald Griffin  ·  Novo Innovative Pathways  ·  October 10, 2026

Virginia wrote the district AI policy mandate into the Code of Virginia and, unlike most states, said what the policy has to be consistent with. There is no countdown to manage. There is a standard to meet.

Status: In effect. Chapter 937, approved April 13, 2026. Virginia’s standard effective date for 2026 session laws is July 1, 2026; the act sets no later date.
In Effect
Board Policy Requirement Is Live Now
§ 22.1-20.2:1
New Code of Virginia Section
1 of 7
States With Binding District Mandates

What HB 1186 Actually Requires

House Bill 1186 adds a single section to the Code of Virginia and builds it in three layers. The first is state guidance: the Department of Education, consulting local divisions and stakeholders, must compile how artificial intelligence systems are already used for instruction and publish guidance on safe, ethical, and equitable use. The second is the mandate: subsection C reads, “Each school board shall establish, implement, and enforce policies” “consistent with the guidance developed by the Department pursuant to subsection B.” The third is money: an AIS Innovation in Education Pilot Program, subject to appropriations, to fund and evaluate safe uses in public schools, with annual reporting to the General Assembly and a sunset on July 1, 2030.

The operative word is consistent. A board policy is compliant only if it lines up with guidance the statute itself scopes. That guidance must address every item below, which means a compliant Virginia policy has to reach every item below too.

Virginia HB 1186 · What the Guidance, and Therefore the Policy, Must Cover

Student data privacy and security, including FERPA, COPPA, and other federal and state student privacy law
Resources and training for teachers
Transparency and explainability of how AI systems are used
Data privacy agreements that bar vendors from using division or student data to train or improve external AI models
Bias and discrimination best practices, embedded professional development, and a prohibition on relying solely on AI for certain high-stakes decisions as the Department defines them
Accessibility and equitable access, and alignment of approved uses with the Standards of Learning and high-quality instructional materials
Guardrails that favor division-managed AI platforms in division-managed environments: role-based access, administrative oversight, audit logging, configurable moderation
Teacher access to transcripts of student AI interactions, and monitoring through dashboards, automated alerts, and audit logs

Source: Virginia Acts of Assembly 2026, Chapter 937 (HB 1186), creating Code of Virginia § 22.1-20.2:1. Approved April 13, 2026. Subsection D expires July 1, 2030.

The Standard Question

Ohio told districts to adopt a policy by a date. Georgia set a graduation requirement and issued guidance. Idaho ordered a statewide framework first and district policies after. Virginia did something the others did not: it put the contents of the standard into the statute that creates the mandate. A Virginia school board cannot satisfy subsection C with a one-page acceptable-use statement, because the guidance it must be consistent with reaches vendor contract terms, decision boundaries, and classroom-level monitoring.

That turns compliance into three design questions. What are the division’s vendor terms, and do they bar model training on student data? Which decisions about students and staff may AI inform but never make alone? And who can actually see what students are doing with the tools, through what dashboard, with what alert, and on what record?

Consistent With Is a Standard, Not a Suggestion

The statute does not ask boards to consider the guidance. It requires policies consistent with it, and it requires boards to implement and enforce them. A policy that is silent on no-training vendor terms, on high-stakes decision limits, or on transcript access is not consistent with guidance that must address all three. The gap is a compliance gap on day one, not a best-practice gap for later.

Where Novo Works

Adopting the policy is step one. Making it consistent is the work.

HB 1186 hands every Virginia school board a policy obligation with a defined floor and leaves the design to the division. Novo works with cabinets on the three places a local policy and the state standard most often diverge: advisory, built from the statute, not off the shelf.

01
Vendor Terms
Data privacy agreements that bar training on division and student data, and the division-managed platform standard written into procurement criteria.
02
Decision Boundaries
Which high-stakes decisions AI may inform and which it may never drive alone, mapped across evaluation, discipline, placement, and special education.
03
Oversight Design
Transcript access, dashboards, alerts, and audit logs that run in practice, with the staff training the guidance requires alongside them.

Designing to the standard also answers what the statute leaves open: how the board documents consistency, how the policy reaches classroom practice, how pilot participation under subsection D is evaluated for student learning, teacher workload, and equity, and how the division reports back when the General Assembly asks.

Virginia in Context: The Mandate Now Comes With a Floor

HB 1186 is one of seven binding district AI policy mandates of this cycle, alongside Georgia SB 179, Ohio HB 96 (board policy deadline July 1, 2026), Idaho SB 1227, Maryland SB 720, and Oklahoma SB 1734. Florida’s State Board followed with Rule 6A-1.0957 in September, carrying a July 1, 2027 district policy deadline. The trend inside the trend is specificity: the newest mandates say what the policy must contain, not just that it must exist.

The Senate companion, SB 394, is the study-and-guidance bill. HB 1186 is the one that carries subsection C and the one that was chaptered. Districts reading the companion will miss the mandate.

What to watch next:

Common Questions on HB 1186

What does Virginia HB 1186 require of school boards?
HB 1186 (Chapter 937, approved April 13, 2026) creates Code of Virginia § 22.1-20.2:1. Subsection C states that each school board shall establish, implement, and enforce policies consistent with the guidance the Department of Education develops under subsection B. That guidance must address student data privacy and security under FERPA and COPPA, teacher resources and training, transparency and explainability, data privacy agreements that bar using division or student data to train external AI models, bias and discrimination, a prohibition on relying solely on AI for certain high-stakes decisions, accessibility and equity, and alignment with the Standards of Learning.
Is the Virginia AI policy mandate in effect now?
The act was approved April 13, 2026 and sets no later effective date of its own; Virginia’s standard effective date for laws passed in the 2026 regular session is July 1, 2026. The school board policy requirement in subsection C has no separate deadline: it is a standing obligation tied to the Department’s guidance. Only the AIS Innovation in Education Pilot Program in subsection D carries a date, and that is a sunset on July 1, 2030.
What makes Virginia’s mandate different from Ohio’s or Georgia’s?
Virginia does not just require a policy; it specifies what the policy must be consistent with. The guidance it points to must favor division-managed AI platforms in division-managed environments, give teachers access to transcripts of student AI interactions, and let administrators monitor use through dashboards, automated alerts, and audit logs. A district policy that is silent on those points is not consistent with the guidance.
How does Novo help Virginia districts comply with HB 1186?
Novo works with division cabinets on the three places where a policy and the state guidance usually diverge: vendor terms (no-training data privacy agreements and the division-managed platform standard), decision boundaries (which high-stakes decisions AI may not drive alone), and oversight design (transcript access, dashboards, and audit logs that actually run). The initial conversation is free.
Stay Current

The AI in Public Education Brief

Weekly analysis on state legislation, governance policy, and AI leadership for K-12 district leaders. Free. No noise.

Join district leaders across the country. Unsubscribe anytime.

Also for your district
Is your career guidance built for 2030 or 2020?
Download the free Futures-Ready Career Report: 40 AI-resilient careers mapped across 4, 5, 7, and 10-year horizons. Built for district leaders and guidance counselors navigating AI-era postsecondary planning.
Get the Free Report ›
Novo Innovative Pathways

How Novo Helps Virginia Districts

HB 1186 hands every Virginia school board a policy obligation with a defined floor. Novo works with division leaders to meet it: vendor terms that bar training on student data, decision boundaries for high-stakes uses, oversight that teachers and administrators can actually run, and board-ready documentation that shows consistency with the state guidance.

No cost for the initial conversation. Direct engagement with Dr. Griffin.