Some Maryland districts will miss the state’s AI policy deadline

Maryland’s first statewide deadline for district-level AI rules is exposing a basic but consequential reality of school governance: writing about artificial intelligence is easier than getting a board to adopt policy on time. Three days before the Oct. 22 compliance date described in summer reporting on the new law, The Baltimore Sun reported Monday that four Maryland districts will miss the deadline. The immediate problem is procedural, but the stakes are practical for superintendents, teachers, procurement officials, and families who now need to know what rules actually govern AI use in classrooms and school operations. (baltimoresun.com)

What changed is not Maryland’s interest in AI, which has been building for more than a year, but the state’s decision to turn guidance into a local mandate. The Artificial Intelligence Ready Schools Act requires the Maryland State Department of Education to publish statewide AI guidance and requires local school systems to adopt an aligned AI policy within 120 days of that release, designate an AI coordinator, and follow state procurement expectations for AI tools. The law took effect June 1, 2026. (mgaleg.maryland.gov)

MSDE’s framework is also much broader than the narrow public debate over whether students should use chatbots to write essays. The state’s own materials tell districts to cover instructional use, operational use, data privacy, academic integrity, and human oversight, while also building governance structures for vetting tools, monitoring equity effects, and making sure AI systems comply with laws covering privacy, accessibility, and civil rights. (marylandpublicschools.org)

That breadth helps explain why the deadline is now turning into a compliance story rather than a culture-war story. A district cannot meet the state’s expectation just by telling teachers to “use AI responsibly.” It needs a board-approved policy, someone formally responsible for coordination, and local procedures for things like vendor review, pilot approval, staff training, incident response, and student-data protection. Those are slow-moving central-office and board-office tasks, even in systems that are not philosophically opposed to AI. (marylandpublicschools.org)

When the calendar becomes the policy problem

Anne Arundel County offers the clearest documented example of why some districts are about to miss. The district said Friday that its board would hold a first reading of a new AI policy on Oct. 21. But Anne Arundel’s own policy-adoption timeline calls for a 30-day public-comment period after first reading, followed by second and third readings. In other words, once the district reached first reading, missing the Oct. 22 deadline became unavoidable under its standard process. (aacps.org)

Harford County appears to be in a similar bind. Official board materials show the district has been working from a drafted policy titled “Use of Artificial Intelligence and Emerging Technologies,” but Harford’s board schedule lists Oct. 12 as its latest business meeting and Nov. 9 as the next one. Absent a special meeting or some other accelerated action not visible in the public schedule, that calendar would put final board action after the state deadline. That is an inference from the public documents, but it illustrates the governance bottleneck Maryland is now facing. (hcps.org)

The pressure is not uniform across the state. Frederick County Public Schools says its board adopted Policy 124 on Oct. 7, and that policy takes one of the state’s most restrictive approaches so far by prohibiting student AI use in grades pre-K through 12 except for specific curricular, AI-literacy, or disability-related uses. Carroll County, by contrast, told its board last week that it had already completed student, educator, staff, and family AI guidelines and a security-and-ethics procedure before the 2026 mandate, leaving the district in a stronger position to align with the state framework. (fcps.org)

Those contrasting examples matter because they show Maryland’s law is not producing one statewide AI policy. It is forcing each district to reveal what kind of institution it already is: one that had governance capacity and cross-functional planning in place, one that moved quickly toward restriction, or one that is still translating a state framework into something a local board can actually vote on. (marylandpublicschools.org)

The real work starts after adoption

Even districts that meet the deadline should not confuse adoption with implementation. MSDE’s documents make clear that the local policy is only the front end of a much larger operating system. Districts are expected to evaluate tools before use, review vendor disclosures on training data and limitations, document why tools were approved or rejected, protect student data, and monitor whether AI systems create disparate impacts across student groups. For teachers, that translates into more explicit rules about when AI can support brainstorming or tutoring, when it crosses into academic dishonesty, and when a human must stay firmly in charge of grading, counseling, or decision-making. (marylandpublicschools.org)

That is why missed deadlines matter beyond optics. In the absence of a finalized local policy, schools often fall back on a patchwork of older technology rules, classroom-level discretion, and vendor promises. That can leave principals and teachers with uneven expectations, while procurement and privacy staff are asked to judge rapidly evolving tools without a board-approved framework behind them. A late policy does not stop AI from showing up in classrooms or operations; it mostly means the governance arrives after the practice. (marylandpublicschools.org)

There is also a tension built into Maryland’s approach. MSDE’s guidance is intentionally human-centered and preserves local autonomy in tool selection and implementation, but the statute also converts that flexibility into a deadline. That tradeoff may be sensible policy: the state sets guardrails, local boards customize. Still, October is showing the cost of that design. The more comprehensive the framework becomes, the harder it is for districts with ordinary board calendars, comment periods, and legal review cycles to turn it into enforceable local policy on short notice. (msde.maryland.gov)

What remains uncertain now is less about whether AI will be present in Maryland schools than about how the state responds when local adoption slips. The public documents reviewed for this story show why districts can miss even when work is underway, but they do not yet show whether MSDE will treat late boards as out of compliance in a formal way, whether districts will call special meetings, or whether interim guidance will be enough for staff already using approved tools. For educators and school leaders, that is the next phase to watch: not the rhetoric of AI readiness, but whether Maryland can turn a statewide framework into local rules before the technology outpaces the policy again. (baltimoresun.com)