Your Board Adopted an AI Policy for Ohio HB 96. Will It Hold Up?

The July 1, 2026 deadline in House Bill 96 has passed. If your board adopted an AI policy to meet it, the compliance box is checked. The harder question is whether that policy holds up the first time it is tested.

It will be tested by ordinary events: a teacher starts using an AI grading tool that is on no approved list, a vendor arrives with a product tied to grant funding, a parent questions AI-generated content in an IEP, or a data breach runs through an AI integration no one tracked. In each case, the board-adopted policy is where the district’s response starts.

This page covers what HB 96 requires, where adopted policies most often fall short, and a six-point check you can run against your own policy in five minutes.

What HB 96 Requires

House Bill 96, passed as part of Ohio’s FY2026 to 2027 budget, required every local education agency in the state to adopt a formal policy governing the use of artificial intelligence by July 1, 2026. The policy must address AI use in instructional settings and in district operations. It must be adopted at the board level, not simply drafted by a curriculum coordinator or IT director.

That is the floor. The law does not specify the content of the policy in granular detail. It does not mandate a particular framework or vendor approval process. What it creates is accountability: if something goes wrong with an AI tool in your district after July 1, the question is whether you had a policy, whether that policy addressed the situation, and whether staff were trained on it.

A policy that was written in a hurry, approved without stakeholder input, and filed in a drawer does not create a governance structure. It creates a document that can be used against you.

The Accountability Gap Most Districts Are Missing

The instinct in a compliance crunch is to move fast: find a template, adapt it, get it to the board before the deadline. That response is understandable and in some cases appropriate. But it misses what HB 96 is actually creating.

Ohio is almost certainly not the last state to require this. Maryland’s SB 720 was signed into law on May 26, 2026. Idaho, Utah, Georgia, and at least 27 other states have active AI education legislation in 2026. The pattern is clear: what begins as a recommendation becomes a requirement within two to three legislative cycles. Ohio is acting now. The question is whether districts respond with a document or with a governance infrastructure.

Real governance infrastructure requires four elements that a policy document alone does not provide:

• A designated coordinator or committee with decision authority over AI tool adoption, not just a point of contact for vendor questions
• A procurement standard that requires vendors to demonstrate efficacy evidence before adoption, not after
• An assessment framework that distinguishes between task completion and durable learning outcomes
• A policy review cycle with a defined frequency, not a static document that expires the moment a new tool enters the market

The Stanford SCALE Initiative reviewed more than 800 academic papers on AI in K-12 education and found exactly 20 that meet the threshold for rigorous causal evidence. Not one was conducted inside a U.S. K-12 classroom. Districts developing policies around vendor efficacy claims are building on a foundation that does not yet exist. A board-adopted policy that requires independent evidence before adoption is one of the few governance tools available right now that simultaneously protects students and accountability systems.

What the July 1 Deadline Does Not Cover

Adopting a policy by July 1 is a compliance action. It is not the same as being ready for what comes after July 1.

After the deadline, the following situations arise in districts that have a policy document but no governance infrastructure: a teacher begins using an AI grading tool not on any approved list; a vendor approaches the district with a new product tied to federal grant funding; a parent files a complaint about AI-generated content in a student’s individualized education plan; a data breach occurs through a third-party AI integration that no one in the district tracked.

In each of those situations, the board-adopted policy is the starting point for the district’s response. If the policy is specific enough to address the situation, the district has legal and operational cover. If it is not, the district has a document that raises more questions than it answers.

This is why what happens after July 1 matters more than the filing itself. The districts that treated the deadline as an opportunity to build real governance architecture are in a materially different position than those that produced a document and moved on. If your district is in the second group, the gap is auditable, and closable.

Three or more “no” answers means your district is document-compliant but not governance-ready. That distinction is what gets tested now.

What Novo Helps Districts Build

Novo Innovative Pathways works with district leadership teams to design AI governance structures that are built ahead of adoption, not retrofitted after something goes wrong. Dr. Griffin spent 22 of his 28 years in education as a principal at the elementary, middle, and high school levels.

For Ohio districts working through HB 96 compliance, our engagement includes:

• A policy audit or first draft aligned to HB 96 requirements and current best practices in AI governance
• A coordinator role definition with reporting structure and decision authority
• A procurement standard that districts can apply immediately to vendor conversations
• A board presentation framework that explains the policy to trustees in terms of accountability and legal exposure, not just technology

We work with superintendents, curriculum directors, and board chairs. Adoption was the starting line. The work now is making your policy operational and defensible.

Related analysis: Ohio HB 96: What the AI Policy Deadline Requires