What SB 720 Actually Requires
The Artificial Intelligence Ready Schools Act amends Maryland’s Education Article on two levels at once. It obligates the state — the Maryland State Department of Education must publish AI guidance through an online platform and develop guidelines, best practices, and evaluative tools districts can use to assess the AI products they select. And it obligates every local school system — most visibly, by requiring each one to designate a non-instructional, central-office coordinator responsible for managing AI use.
Because the law is already in effect, these are not items on a future to-do list. Every Maryland school system must now account for each of the following:
Maryland SB 720 — Core Requirements
The bill passed with near-unanimous margins — 45 to 0 on final passage in the Senate and 129 to 8 in the House — and carries a sunset provision, signaling the legislature intends to revisit the framework as evidence accumulates. That combination matters: the mandate is bipartisan, durable, and designed to evolve rather than expire quietly.
Source: Maryland General Assembly, SB 720 (Education — Artificial Intelligence — Guidelines, Professional Development, and Collaborative; Chapter 634, approved by the Governor May 26, 2026); legislative history and roll-call record via mgaleg.maryland.gov and legiscan.com, as documented in Edition 19 of the AI in Public Education Brief.
The Coordinator Question
For two years, the hardest question in K-12 AI governance has been ownership: who, inside the district, is actually accountable for AI — for the policy, the tools, the data, and what happens when something goes wrong. Most districts answered with a committee, or with nobody. Maryland answered it by statute. AI governance now has a name, a desk, and a reporting line in every school system in the state.
That makes the operative question for Maryland leaders a design question, not a compliance question. The law tells you to name a coordinator. It does not tell you where the role sits, what it controls, or what it owes the board. Those choices determine whether SB 720 produces governance or paperwork.
The mandate can be satisfied two ways: add “AI coordinator” to an existing job description and move on, or design the role as a real governance seat. The difference is written authority over procurement and policy, standing to evaluate tools against criteria the district controls, and the resourcing to function. A district that chooses the first path will be technically compliant and operationally exposed — the same gap that follows a one-page AI policy with no infrastructure behind it.
Naming the role is step one. Designing it is the work.
SB 720 hands every Maryland school system a new governance seat and leaves the design open. Novo works with district cabinets on the three questions the statute does not answer — advisory, not off-the-shelf, built around your system’s size, structure, and the person or office you name.
Designing the seat well means answering questions the statute leaves open: how vendor review works, what the role owes the board, how its work reaches classroom practice, and how the coordinator connects to the MSDE guidance and the Maryland AI Education Collaborative as both come online. Those design choices — not the designation itself — determine whether the mandate becomes a governance capability or a line on an org chart.
Maryland in Context: The Standard of Care Is Moving
SB 720 is the fourth signed state K-12 AI mandate of this cycle, following Georgia SB 179, Ohio HB 96 (board policy adoption deadline July 1, 2026), and Idaho SB 1227. It is also a different kind of law. The earlier mandates regulate documents — policies and frameworks districts must adopt. Maryland regulates the org chart.
That distinction travels. When a state with Maryland’s policy influence converts the AI coordinator from a best practice into a legal requirement, vendors, counsel, and neighboring legislatures begin to treat the named district AI owner as the expected standard of care — whether or not their own statutes require it yet. Superintendents outside Maryland should read SB 720 as a template, not a local development: name the office now, define its authority in writing, and absorb the mandate before it arrives.
What to watch next:
- MSDE’s guidance platform and evaluative tools, now in development under SB 720
- The standup of the Maryland AI Education Collaborative
- New Mexico’s legislative consideration of a formal AI oversight body ahead of the 2027 session
- The full K-12 AI State Legislation Hub — every signed mandate, deadline, and what districts must build to comply
Featured in the Brief The full analysis of SB 720 — including the New Mexico oversight-body recommendation and the peer-reviewed research on which AI-literacy dimensions actually predict academic performance — is in Edition 19 — Maryland Mandates a District AI Coordinator, with primary-source citations.
Common Questions on SB 720
What does Maryland SB 720, the Artificial Intelligence Ready Schools Act, require of school systems?
Is the Maryland AI coordinator mandate in effect now?
Does adding “AI coordinator” to an existing job description satisfy SB 720?
Why should districts outside Maryland pay attention to SB 720?
The AI in Public Education Brief
Weekly analysis on state legislation, governance policy, and AI leadership for K-12 district leaders. Free. No noise.
Join district leaders across the country. Unsubscribe anytime.
How Novo Helps Maryland Districts
SB 720 hands every Maryland school system a new governance seat. Novo works with district leaders to design it — written role authority, procurement and tool-evaluation criteria, role-based AI literacy for staff, and the board-ready documentation that makes the coordinator a real governance function instead of a title on an org chart. If your system is in Maryland — or watching the standard of care move — we should talk before the 2026-27 school year.