{"resourceId":"maryland-sb720-ai-ready-schools-enrolled-2026","versions":[{"version":"external-a161c872bd38bf2b4dfd88259a278333208b055e693d3443101036004a4c4f7c","resource":{"id":"maryland-sb720-ai-ready-schools-enrolled-2026","title":"Maryland SB720 AI Ready Schools Act: SEA guidance, local AI policies in 120 days, coordinators, and procurement rubrics","organization":"Maryland General Assembly / Department of Legislative Services","sector":"K-12 state AI governance, professional development, and procurement","geography":"Maryland, United States (local school systems statewide)","publishedAt":"2026 Session Fiscal and Policy Note — Enrolled Revised (bill effective June 1, 2026)","publicationDate":"2026-06-01","eventDate":"2026-06-01","sourceName":"SB 720 Fiscal and Policy Note (Enrolled – Revised): Artificial Intelligence Ready Schools Act","sourceLabel":"Official Maryland enrolled-bill fiscal and policy note","sourceUrl":"https://mgaleg.maryland.gov/2026RS/fnotes/bil_0000/sb0720.pdf","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["governance-procurement","accessibility-workforce","operating-model","data-security"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"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.","governanceImplications":"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.","securityPrivacyImplications":"Guidance must address state/federal privacy and accessibility standards for instructional AI; procurement alignment with DoIT adds a security review gate before classroom deployment.","caveats":"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.","streamIds":["k12"],"roles":{"sales":"Sales framing: Maryland districts need help standing up AI coordinators, 120-day policies, and rubric-aligned procurement—not another chatbot pilot. Lead with SB720’s enrolled duties and ask whether MSDE guidance and rubric releases are on the calendar. Offer a policy-plus-inventory engagement with clear staffing implications; do not sell the statute as proof of student learning gains from any product.","engineering":"Engineering framing: build an AI-tool registry with rubric scores, DoIT and security gates, and coordinator workflows for exception handling. Architecture should capture which tools are approved, pending, or blocked, attach evidence packs for board adoption within 120 days of SEA guidance, and keep teacher GenAI requests auditable against the rubric instead of allowing shadow installs.","delivery":"Delivery framing: sequence SEA-guidance watch, local policy drafting, coordinator onboarding, rubric scoring of the current tool stack, and professional development rollout for educators. Acceptance is an adopted local AI policy, a named and resourced coordinator, and rubric-documented procurement decisions for in-use tools—not awareness training alone or a static PDF nobody maintains after board adoption day."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["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?"],"valueHypothesis":"A bounded policy, inventory, and rubric-scoring engagement can meet SB720’s 120-day local duties and reduce ad hoc AI sprawl.","potentialEngagement":"90-day AI Ready compliance package: policy draft, coordinator charter, and first-wave rubric evaluations.","unsupportedClaims":["That SB720 guarantees improved student outcomes","That rubric scores replace instructional quality review","Fixed statewide staffing costs for every district"]},"engineering":{"fit":"Fit for Maryland LEAs building governed AI inventories; patterns transfer where SEA rubric/coordinator mandates exist.","architectureIntegration":"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.","proofOfValue":["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":{"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.","skillsAdoption":"Coordinator and curriculum leads need rubric-scoring practice; teachers need PD on ethical classroom AI use aligned to local policy.","governanceCheckpoints":["Guidance-release day zero briefing","Day-60 draft policy review","Day-120 adoption and inventory freeze"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-09-21T03:15:40Z","enrichedAt":"2026-09-21T03:24:38Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"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.","procurementImplications":"Local procurement must use MSDE rubric/evaluative tools and align with DoIT requirements—raising the bar for vendor questionnaires and security reviews before purchase.","operatingModelImplications":"Shifts AI from optional innovation projects to a standing coordinator-led operating function with policy refresh and collaborative reporting cycles.","sourceVerification":{"openedUrl":"https://mgaleg.maryland.gov/2026RS/fnotes/bil_0000/sb0720.pdf","referenceExcerpt":"The AI coordinator designated by each local school system must be employed at the central","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}