Ohio Just Required Every District to Have an AI Policy. Here’s What It Means for Edtech Companies.
By July 1, 2026, every traditional public school district, community school, and STEM school in Ohio has to adopt a formal policy governing the use of artificial intelligence. This isn’t a suggestion — it’s written into the state budget. House Bill 96 directed the Ohio Department of Education and Workforce to publish a model policy by the end of 2025, and directed every district in the state to adopt a policy of their own — the state’s model, or one they write themselves — by mid-2026.
For edtech companies selling into Ohio, or watching Ohio as a bellwether for what other states will do next, this is worth understanding in some detail. Not because it changes what districts can buy — it doesn’t ban or restrict any particular tool — but because of what it tells vendors about how districts will now be expected to evaluate what they buy.
What Does Ohio’s New AI Policy Requirement Actually Say?
Ohio’s approach traces back to February 2024, when InnovateOhio and The AI Education Project (aiEDU) released an AI Toolkit for the state’s K-12 districts. That toolkit was explicit about its own limits: it was designed as a trusted and vetted resource, not a mandate to use AI in the first place. Its central contribution is a five-step method for turning high-level goals into concrete policy — take stock of the current landscape, identify core values, derive principles from those values, translate principles into actionable policy, then implement and monitor.
Building on that groundwork, Ohio’s AI in Education Coalition — convened under then-Lieutenant Governor Jon Husted — released a statewide AI strategy in November 2024 recommending that local policies address several specific things: clearly defined uses of AI by students and staff, privacy and data protection standards, ethical guidelines, and teacher-specific use cases. Two items on that list matter most for vendors: “considerations for evaluation of purchased resources and vendor agreements” and an outlined process for evaluating AI tools from third-party vendors.
That last piece is the one edtech companies should sit with. Ohio isn’t just asking districts to decide whether teachers can use a chatbot. It’s asking them to formalize how they evaluate any AI-enabled tool before it enters a classroom — which means a documented process, not a gut call from whichever administrator happens to see the demo.
Why Does This Pattern Look So Familiar?
If you’ve been through an ESSA evidence conversation with a district procurement team, this will feel familiar. Districts are being pushed — by state law, in Ohio’s case — toward documented, defensible evaluation criteria rather than ad hoc adoption decisions. That’s precisely the shift LXD Research has built its practice around for the last several years, just applied to a new category of tool.
It also tracks with what we’ve heard directly from educators, specifically about AI. In a 2025 survey of over 200 K-12 educators across 37 states, LXD Research found that adoption has clearly passed a tipping point — but that the reasons for caution have shifted underneath it.
Ethical concerns (54%) and data privacy risks (53%) have now overtaken cost (35%) as the top barriers to adoption. Educators were also candid about their skepticism of vendor-funded research. As one technology coordinator we surveyed put it:
“Vendor research isn’t, I don’t wanna say it isn’t trustworthy, but we give it a grain of salt because we know that the people who are doing the research do have an interest in making sure that the research is favorable for the company.”
K-12 Technology Coordinator, LXD Research survey of 200+ educatorsA Structural Response to an Old Instinct
Ohio’s push toward a formal, outlined vendor-evaluation process is a structural response to exactly that instinct. Districts have always been a little skeptical of a vendor’s own claims about its own product — that’s not new, and it isn’t unique to AI. What’s new is that the state is now giving districts a documented process to point to instead of relying on a vendor’s word, and writing the expectation that such a process exists into law.
None of this means Ohio is banning or even discouraging AI adoption — the toolkit says as much directly. What it means is that the burden of proof is shifting toward companies that can show, in terms a school board or IT director can point to, that their tool works, that it was evaluated by someone other than the vendor, and that its data practices hold up under scrutiny.
Companies that already have third-party research, transparent data documentation, and a clear account of how a tool was piloted and validated will move through whatever evaluation process a given Ohio district adopts. Companies relying only on internal marketing claims will find that process considerably harder to clear.
Is Ohio an Outlier, or a Preview?
It’s a preview, not an outlier. Ohio is one of a growing number of states formalizing evidence and evaluation requirements into procurement and policy — Michigan now scores curriculum submissions on a points system tied directly to ESSA tiers, and Massachusetts’s CURATE bid splits its entire evaluation 50/50 between standards alignment and documented efficacy. Different states, different mechanisms, same direction: formal, documented evidence is becoming the expectation rather than the exception, and AI tools are simply the newest category being pulled into that expectation.
For a product leader watching this from outside Ohio, the useful question isn’t whether your state will pass something identical. It’s whether your evidence base would already hold up if it did. The districts writing these policies aren’t inventing a new standard from scratch — they’re formalizing a version of the same question ESSA has been asking edtech companies for years: not just does it work, but who checked, and how.
The companies with a documented, third-party evaluation already in hand won’t need to scramble when the next state writes its own version of House Bill 96. The ones without one will be building that evidence base under a deadline instead of ahead of one.
Not Sure What Level of Evidence Your Product Has?
Get a research-path recommendation for your product, timeline, and procurement goals.
Book an ESSA Evidence Review View Our Services