A Maryland School Board Banned AI for Every Student, Weeks After Piloting Gemini
AI & ML

A Maryland School Board Banned AI for Every Student, Weeks After Piloting Gemini

Frederick County voted 6 to 1 to bar AI use from pre-K through 12th grade just weeks into a Gemini pilot, and the reversal says more about how fast district trust in AI can collapse than any vendor contract ever will.

PublishedOctober 11, 2026
Read time5 min read
Share

What the board actually voted on

The Frederick County Board of Education voted 6-1 on October 7, 2026, to bar artificial intelligence use by students across every grade level, from pre-kindergarten through 12th grade. The board first proposed restricting AI for younger grades specifically, then extended that restriction to older students as the proposal moved through discussion, ultimately landing on the sweeping, all-grades ban that passed. The lone dissenting vote came from a board member who argued publicly that restricting AI access now could leave older students meaningfully less prepared for a college environment where AI tools are already in common use.

District officials have said enforcement details and how specific policy exceptions will actually operate inside classrooms are still being worked out, which means schools are implementing a board-approved ban before the practical mechanics of that ban have been fully defined. The policy carves out exemptions for classroom lessons specifically about AI itself, direct instruction on the technology, and accommodations for students with disabilities, but the board has not yet clarified how a teacher is expected to distinguish those permitted uses from the newly prohibited ones in daily practice.

The timing next to the Gemini pilot is the real story

The vote landed just weeks after Frederick County began piloting Google's Gemini for middle and high school students in September, and district officials have not publicly explained how that active pilot squares with a board-approved ban covering every grade level including the ones the pilot was actively running in. That gap between what the technology department was piloting and what the school board just banned is the detail every other district watching this story should sit with carefully, since it suggests the pilot and the policy decision moved through entirely separate institutional tracks without coordinating on timing or messaging.

Educators cited by local coverage pointed to concerns about cheating and about students relying on AI instead of building their own underlying skills as the primary drivers behind the ban, with some teachers reportedly already returning to paper-and-pencil assignments specifically to route around the problem. That reasoning reflects an instructional concern that predates this specific Gemini pilot by a wide margin, suggesting the ban was less a direct reaction to Gemini itself and more a long-simmering concern that finally reached a board vote at a moment the pilot happened to still be running.

Parents are split in a way that mirrors the board's own vote

Parent reactions captured in local coverage split in a pattern that closely tracks the board's own near-unanimous but not quite unanimous outcome. One parent, Ikea Bowie, argued AI can become a crutch and that students should rely on their own thinking rather than offloading it to a tool. Another, Eric Frierson, pushed back that AI can be genuinely useful in some situations and that students need to be prepared for a world already shaped by it, echoing almost exactly the reasoning behind the board's single dissenting vote.

A third parent, Justin Heid, raised a different and arguably more important criticism: that the district had sent families very few communications about how AI was already affecting classroom learning before this vote happened, leaving many parents to learn about the scope of AI's classroom presence only once the ban itself became news. That communication gap, more than the substance of the ban itself, is the kind of unforced error other districts can actually learn from and avoid in their own policy rollouts.

Maryland's own state law points in the opposite direction

Frederick County's ban sits in direct tension with Maryland's own SB 720, a state law that requires every district to adopt a formal AI policy and build AI literacy directly into K-12 standards, rather than restricting student AI access outright. Other Maryland districts have taken meaningfully different approaches under that same state mandate, which makes Frederick County's blanket ban one of the most restrictive responses to SB 720 adopted anywhere in the state so far, even though the district is nominally complying with the same underlying law that other, far more permissive districts are also operating under.

That divergence under a single shared state mandate is worth watching closely, because it shows how much discretion individual districts actually retain even under a state law explicitly designed to standardize AI policy across a state's public school system. Districts, vendors, and policy advocates should expect Frederick County's approach to become a reference point, cited either as a cautionary example of federal and state AI-literacy goals undermined at the local level, or as a legitimate, locally appropriate response that SB 720's framework was always flexible enough to accommodate.

What this means for edtech vendors and other districts

Any edtech vendor currently running a pilot inside a district, Gemini included, should treat this reversal as a concrete reminder that an active pilot provides no real insulation against a sudden board-level policy reversal once cheating concerns and parent frustration accumulate past a certain threshold. Vendors should be proactively coordinating communication with district leadership well before board meetings where AI policy is on the agenda, rather than learning about a ban through the same local news coverage parents and students are reading.

For other districts watching this specific case unfold, the clearest actionable lesson is Justin Heid's communication complaint, not the substance of the ban itself: districts that fail to proactively explain how AI is already present in classrooms before a formal policy debate begins are setting themselves up for exactly the kind of parent backlash and board whiplash Frederick County is now experiencing in real time. A pilot program running quietly alongside a board slowly building toward a ban is a genuinely avoidable governance failure, not an inevitable one, and the districts paying close attention now have a real chance to get ahead of it before their own board reaches a similar breaking point.

Tagged#news#edtech#education#learning#lms#ai-education#frederick-county#maryland#ai-ban#k-12#gemini-pilot#sb-720#academic-integrity