Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the K–12 edition of September 28, 2026

Independent reportingEmergingNew this fortnight

WOSU: Central Ohio districts operationalize Ohio’s first school-year AI policy mandate with literacy frameworks and use tiers

WOSU Public Media · K-12 education journalism / district operations · United States — Central Ohio (Hilliard City Schools; Columbus City Schools)

Publisher
WOSU Public Media
Original publication
September 28, 2026
Source retrieved
2026-09-29
Event date
2026-09-28
Read original source

What happened

Izza Haq reports that in Ohio’s first school year under a statewide AI-policy requirement, districts are implementing unevenly: Hilliard City Schools launched an AI Readiness Framework introducing AI concepts from kindergarten through high school and teacher guidelines that define AI-use levels for assignments (including a 'full AI' path where students draft on paper then use AI for feedback before revision), while Columbus City Schools has not created supplemental AI programs but has teachers ask students to compare their work with AI to surface inaccuracy. Officials stress embedding AI literacy in curriculum, gathering stakeholder feedback, and staying agile as the technology changes; Olentangy, Westerville, and Dublin officials were unavailable for comment.

Why it matters

Shows how a state 'adopt a policy' mandate translates into concrete district operating models—useful for Ohio LEAs and other states watching statutory AI-policy requirements.

Evidence and measured results

Local public-radio reporting with on-record CTO/CIO quotes dated the research day; not an outcome evaluation.

Limitations and uncertainty

Journalistic snapshot of two districts; no learning-outcome measures; several districts did not comment; Ohio-specific statute.

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
Districts under Ohio’s AI-policy statute must show classroom-ready literacy frameworks and use tiers without defaulting to unsupervised generative chatbots.
Stakeholders
  • CTO/CIO
  • curriculum leaders
  • principals
  • teachers
  • board
  • parents
Discovery questions
  • Do you publish assignment-level AI-use tiers (none/bounded/full) in syllabi?
  • Which student AI tools are approved and age-banded for K–5 versus secondary?
  • How do teachers capture AI-feedback revision without grading AI-authored drafts as mastery?
  • What teacher/parent feedback loop updates the AI framework mid-year?
Value hypothesis
If districts operationalize literacy-first AI frameworks with explicit use tiers and feedback loops, they can meet Ohio’s mandate while limiting accuracy and offloading risks.
Potential engagement
4–6 week AI-readiness workshop producing a graded-use continuum, approved-tool list, and classroom exemplars for one secondary and one elementary grade band.
Unsupported claims
  • That kindergarten AI literacy requires student use of generative chatbots
  • Guaranteed learning gains from adopting any AI readiness framework
  • Uniform implementation quality across all central Ohio districts

Pre-sales engineering

Role takeaway
Fit
Strong fit for Ohio and similarly mandated states needing classroom-operational AI policies beyond board adoption paperwork.
Architecture and integration
Map AI-use tiers to LMS assignment settings; route student AI feedback through approved education tenants; retain draft-before-AI workflow artifacts.
Prerequisites
  • Adopted board AI policy
  • Approved-tool inventory
  • Teacher PD on AI literacy and accuracy critique
  • Family communication channel
Constraints
  • Mandate requires a policy, not prescribed classroom content
  • Rapid model change requires agile controls
  • Uneven district capacity across suburbs vs urban
Security
Keep student work in contracted education environments; forbid pasting PII into consumer chatbots; log tool approvals.
Proof of value
  • Sample syllabi show AI-use tiers
  • Teachers can disable student AI features without vendor tickets
  • Parent FAQ documents approved tools and alternatives

Delivery

Role takeaway
Work
Stand up AI workgroup, publish use-tier guidance, pilot draft-then-AI-feedback assignments, and schedule mid-year policy review.
Dependencies
  • board policy calendar
  • LMS configuration
  • vendor DPAs
  • PD time
Ownership
CTO/CIO owns tool controls; curriculum owns literacy frameworks; principals own classroom fidelity.
Skills and adoption
Coach teachers to use AI for critique/feedback after student drafts and to teach inaccuracy explicitly.
Governance checkpoints
  • Pre-pilot privacy review
  • Quarterly workgroup review
  • Family feedback session each semester
Acceptance criteria
  • Published AI-use continuum for core subjects
  • ≥1 elementary and ≥1 secondary exemplar live
  • Documented non-AI alternative path
Risks
  • Framework becomes literacy theater without classroom change
  • Full-AI assignments credit assisted work as mastery
  • Shadow consumer AI bypasses approved list

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?

Need assignment-level AI-use controls, approved-tool lists, and draft-before-AI workflows rather than open student chatbot access.

Governance

Who approves, reviews and stays accountable for outcomes?

Board policy alone is insufficient; districts need continua, PD, and feedback loops in the first mandated year.

Security and privacy

What data, permissions and controls need testing?

Approved-tool boundaries and limits on student exposure to unvetted AI remain operational concerns as models evolve.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Kindergarten-through-high-school AI literacy framing must remain age-appropriate and not force generative tool use on young learners.

Procurement

What should contracts, pricing and exit terms secure?

Buy tools that support teacher-set AI-use levels and non-AI alternatives rather than only open generative chat.

Operating model

Which teams own the service once it runs?

First-year mandate compliance is a continuous improvement cycle across curriculum, IT, and family engagement—not a one-time board vote.

Publication history

  1. 2026-09-28K–12 · Issue 235 resources
Read preserved resource versions (JSON)

Stable resource ID: wosu-ohio-district-ai-policy-implementation-20260928