Ohio HB 96 — Deadline: July 1, 2026
All Ohio traditional public school districts, community schools, and STEM schools must adopt a formal AI policy by this date. Non-compliance may affect district standing with the Ohio Department of Education and Workforce.
Rachel Pauley · Ohio Edition
v1.0 — May 2026
Jul 1
2026 deadline
Everything Ohio K–12 leaders need to meet the HB 96 deadline and close the AI companion gap — in one document, ready to adapt.
HB 96
Ohio mandate — formal AI policy required
Jul 1
Adoption deadline for all Ohio public districts
30
Days to adopt, train, and communicate
The Law
Ohio HB 96 requires every traditional public school district, community school, and STEM school to adopt a formal policy on the use of artificial intelligence by July 1, 2026. The law does not dictate the content of the policy — it requires districts to have one and to develop it with community input.
What the law requires
What the law does not specify
Ohio DEW Model Policy
The Ohio Department of Education and Workforce has published a model policy at education.ohio.gov/Topics/AI-in-Ohio-s-Education/Model-Policy. Districts may adopt it as-is or adapt it. This kit adds a critical section the model policy does not include: AI companion / character chatbot language.
The Gap
The Ohio DEW model policy is a strong starting point. It defines AI, establishes expectations for instructional use, and addresses data privacy. But it treats "AI" as a single category. That means it misses the fastest-growing student risk: AI companion and character chatbot use.
Add this to the Ohio model policy
This single paragraph closes the companion AI gap. Add it as a new section in your adaptation of the Ohio model. Have legal counsel review for local context.
Section __ — AI Companion and Character Chatbot Use. The District distinguishes "AI companions" — persona-driven, relational, or character-based chatbots designed for emotional or social interaction (including but not limited to Character.AI, Replika, Janitor AI, and similar products) — from instructional and productivity AI tools approved through the District's vendor review process. Students and staff may not access AI companion services on District-owned devices or through the District network. Staff who become aware of student use of AI companions involving signs of emotional reliance, distress, self-harm, or unsafe content shall follow the District's standard student welfare and mandated reporting protocols. This section is in addition to, and does not replace, the District's general policies on AI use, internet safety, and acceptable use of technology.
Ohio Timeline
| By date | Action | Why it matters for HB 96 |
|---|---|---|
| June 2 | Draft policy language using Ohio DEW model + AI companion addendum from this kit | Gives legal counsel + superintendent time to review before board window closes |
| June 6 | Community input process — email to staff, families, students with a simple feedback form (3 questions, 2-week window) | HB 96 requires community input. Document responses for your audit file. |
| June 9 | Legal counsel review of final draft | Standard for policy adoption; flag any state-specific language concerns |
| June 16 | First reading at regular board meeting | Most districts require two readings. First reading on June 16 = second reading on June 23 or June 30. |
| June 23–30 | Second reading and adoption vote | Must be adopted by June 30 at the latest to meet July 1 deadline. |
| July 1 | HB 96 deadline — policy must be in effect | Statutory deadline. |
| July 7 | Brief all staff at back-to-school admin meetings | Policy only works if people know it exists. |
| July 14 | Send parent advisory and post policy on district website | Community awareness + defensible record of transparency. |
⚠ If your board has a July-only meeting schedule, you may need an emergency special meeting or resolution before July 1. Check your board meeting calendar now.
Community Input (Required by HB 96)
HB 96 requires districts to seek input from community members, district employees, students, families, and professionals when developing AI policies. Use these templates to document your process.
Staff + family input email
Subject: Help us shape our AI policy — your input requested by [Date]
Dear [Staff / Families],
Our district is developing a formal policy on the use of artificial intelligence in our schools, as required by Ohio HB 96 (effective July 1, 2026). We want your input before the policy is finalized.
This takes 3 minutes. Please share your perspective by [Date, 2 weeks out]: [Form link]
Three questions:
Your input will be reviewed by our leadership team and incorporated where appropriate. Thank you.
[Superintendent name and signature]
Document your process
Keep a simple log: who was invited to give input, how (email, meeting, survey), how many responded, and how responses influenced the final policy. This log is your audit trail if the district is ever asked to demonstrate compliance with the community input requirement.
Board Meeting
Motion for second reading and adoption:
"I move that the Board of Education of [District Name] adopt Policy [Number] — Artificial Intelligence Use in Schools, as presented, to satisfy the requirements of Ohio HB 96 and to establish district guidelines for the responsible, equitable, and safe use of artificial intelligence by students, staff, and administrators."
If adopting by emergency resolution prior to July 1:
"I move that the Board of Education of [District Name] adopt the attached Resolution on Artificial Intelligence Use in Schools as an emergency measure, effective immediately, to meet the July 1, 2026 deadline established by Ohio HB 96. This resolution will be replaced by a permanent policy following the standard two-reading adoption process at the [Month] regular board meeting."
Ohio Resources
Ohio Pre-Adoption Checklist
Ohio District AI Policy Kit · v1.0 · May 2026
Rachel Pauley · rdpauley@gmail.com
Free for district internal use. Not legal advice. Always review with your district's counsel and consult ODE for the latest guidance on HB 96 compliance.