From the K–12 edition of September 20, 2026
Maryland SB720 AI Ready Schools Act: SEA guidance, local AI policies in 120 days, coordinators, and procurement rubrics
Maryland General Assembly / Department of Legislative Services · K-12 state AI governance, professional development, and procurement · Maryland, United States (local school systems statewide)
- Publisher
- SB 720 Fiscal and Policy Note (Enrolled – Revised): Artificial Intelligence Ready Schools Act
- Original publication
- 2026 Session Fiscal and Policy Note — Enrolled Revised (bill effective June 1, 2026)
- Source retrieved
- 2026-09-21
- Event date
- 2026-06-01
What happened
Enrolled SB 720 (Artificial Intelligence Ready Schools Act) requires MSDE to publish AI guidance for systems, educators, parents, and students; local school systems must adopt an aligned AI policy within 120 days of guidance release, designate a central-office AI coordinator, and procure AI tools consistent with DoIT requirements. MSDE must publish a rubric/evaluative tools for local AI-tool selection, incorporate AI literacy into workforce-preparation and K–12 computer science standards by June 1, 2027, provide educator/leader PD, and staff a Maryland AI Education Collaborative. The bill takes effect June 1, 2026 (collaborative provisions terminate May 31, 2028). DLS projects GF expenditure increases beginning FY2027 (~$610k) and notes local boards may face significant staffing costs for AI-experienced personnel.
Why it matters
Shows a second U.S. state model—SEA guidance plus mandatory local coordinators, 120-day policy adoption, and procurement rubrics—distinct from Florida’s internet-safety AI rule and California’s operator training ban, useful for multi-state operating comparisons.
Evidence and measured results
Opened the official Maryland General Assembly fiscal/policy note PDF via curl and pdftotext; verified enrolled-revised status, effective date June 1, 2026, AI coordinator and 120-day policy requirements, MSDE rubric duties, PD/collaborative provisions, and fiscal summary figures.
Limitations and uncertainty
Fiscal note summarizes enrolled bill requirements; local implementation depends on MSDE guidance publication timing; not an impact evaluation of learning outcomes. Why now: unarchived enrolled Maryland AI operating model, newly relevant beside California training bans and Florida floors as states diverge on control architectures.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-21; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Maryland systems must operationalize SEA AI guidance quickly—policy, coordinator, and rubric-based procurement—without a ready internal playbook.
- Stakeholders
- Superintendents
- Board counsel
- CTOs
- Curriculum leads
- HR / central office
- Discovery questions
- Has MSDE published the AI guidance and rubric yet?
- Who will be designated AI coordinator at central office?
- Which AI tools are in use without rubric review today?
- What DoIT procurement constraints already apply?
- Value hypothesis
- A bounded policy, inventory, and rubric-scoring engagement can meet SB720’s 120-day local duties and reduce ad hoc AI sprawl.
- Potential engagement
- 90-day AI Ready compliance package: policy draft, coordinator charter, and first-wave rubric evaluations.
- Unsupported claims
- That SB720 guarantees improved student outcomes
- That rubric scores replace instructional quality review
- Fixed statewide staffing costs for every district
Pre-sales engineering
Role takeaway
- Fit
- Fit for Maryland LEAs building governed AI inventories; patterns transfer where SEA rubric/coordinator mandates exist.
- Architecture and integration
- AI-tool registry → rubric scoring fields → procurement/DoIT status → roster of approved classroom uses; coordinator dashboards for exceptions.
- Prerequisites
- Complete shadow-IT / filter-log inventory
- Board policy drafting capacity
- Central-office FTE for coordinator role
- Security review path with DoIT-aligned controls
- Constraints
- Clock starts on MSDE guidance release
- Local budget for AI-experienced staff may be material
- Collaborative reporting duties are time-limited
- Security
- Gate new AI tools through privacy/accessibility checks encoded in the rubric and DoIT requirements before classroom enablement.
- Proof of value
- Adopted local AI policy within 120 days of guidance
- Named AI coordinator on org chart
- Rubric scorecards for top N tools
- PD completion for priority educator cohorts
Delivery
Role takeaway
- Work
- Watch SEA releases, draft/adopt policy, stand up coordinator function, score existing tools on the rubric, and schedule PD.
- Dependencies
- MSDE guidance and rubric publication
- Board meeting calendar
- HR approval for coordinator role
- Vendor questionnaire responses
- Ownership
- Superintendent/board own policy adoption; central-office AI coordinator owns ongoing inventory; CTO owns technical procurement gates.
- Skills and adoption
- Coordinator and curriculum leads need rubric-scoring practice; teachers need PD on ethical classroom AI use aligned to local policy.
- Governance checkpoints
- Guidance-release day zero briefing
- Day-60 draft policy review
- Day-120 adoption and inventory freeze
- Acceptance criteria
- Board-adopted AI policy on file
- AI coordinator designated and resourced
- Rubric evaluations completed for in-use GenAI tools
- PD plan funded for educators/leaders
- Risks
- Guidance delay compressing the 120-day clock
- Unfunded coordinator mandate
- Rubric becoming paperwork without procurement teeth
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?
Districts need an owned AI-tool evaluation workflow mapped to the MSDE rubric and DoIT procurement constraints, with coordinator-accessible inventories rather than ad hoc teacher downloads.
Governance
Who approves, reviews and stays accountable for outcomes?
Policy adoption clocks start when MSDE guidance posts; boards should pre-draft AI policies and coordinator job descriptions to meet the 120-day window and document rubric-based procurement decisions.
Security and privacy
What data, permissions and controls need testing?
Guidance must address state/federal privacy and accessibility standards for instructional AI; procurement alignment with DoIT adds a security review gate before classroom deployment.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Creates new central-office AI coordinator roles and educator PD expectations; accessibility standards are explicitly in scope of SEA guidance, so tool selection must consider equitable access—not only novelty features.
Procurement
What should contracts, pricing and exit terms secure?
Local procurement must use MSDE rubric/evaluative tools and align with DoIT requirements—raising the bar for vendor questionnaires and security reviews before purchase.
Operating model
Which teams own the service once it runs?
Shifts AI from optional innovation projects to a standing coordinator-led operating function with policy refresh and collaborative reporting cycles.
Publication history
- 2026-09-20K–12 · Issue 154 resources
Stable resource ID: maryland-sb720-ai-ready-schools-enrolled-2026