{"resourceId":"vcu-merc-virginia-ai-policy-comparative-2026","versions":[{"version":"external-b1ff4488bd54c3289493bdde6da036eb3c000c0abb84f540d2f38c34c6fc1acb","resource":{"id":"vcu-merc-virginia-ai-policy-comparative-2026","title":"VCU MERC: staff AI use is thinnest VA division domain—only 2 of 10 had explicit staff provisions","organization":"Metropolitan Educational Research Consortium (MERC), Virginia Commonwealth University School of Education","sector":"K-12 research-practice partnership policy analysis","geography":"Virginia, United States (10-division comparative sample; state policy context)","publishedAt":"2026 MERC research and policy review (citation year 2026; analysis timed to spring 2026 / June 2026 framing)","publicationDate":"2026-06-01","eventDate":"2026-07-01","sourceName":"AI Policy in Virginia Public Schools: A Comparative Analysis (VCU Scholars Compass PDF)","sourceLabel":"University research-practice consortium comparative policy review","sourceUrl":"https://scholarscompass.vcu.edu/cgi/viewcontent.cgi?article=1159&context=merc_pubs","evidenceClass":"independent-research","outcomeClass":"cautionary","topics":["governance-procurement","data-security","accessibility-workforce","operating-model"],"finding":"MERC analyzed publicly available AI-related policies across Virginia divisions against six domains (student use, academic integrity, staff use, approved tools/procurement, data privacy/security, training/literacy) as Virginia’s SB394/HB1186 (signed April 2026; effective July 1, 2026) requires VDOE guidance and eventual local board policies. At data collection, six of ten studied divisions had no AI-explicit language. Staff Use of AI had the least existing governance infrastructure—only two divisions had explicit staff AI use provisions—with no reliable Acceptable Use Policy equivalent for teacher AI. Three divisions had AI procurement/vetting language; only one tied procurement to privacy agreements and a ban on using division data for model training. Every division had some privacy framework, but FERPA-era policies were not designed for AI model-training risks. Training/literacy was stronger at state level than in local requirements. Why now: documents the staff-use/procurement gap LEAs must close as binding state AI mandates (VA and FL) land—unarchived and newly relevant to Sept 2026 compliance work.","sledRelevance":"Gives SEAs/LEAs a domain checklist and empirical gap map—especially staff-use and procurement—usable when translating new state AI laws into board policy and vendor contracts.","evidence":"Opened full VCU Scholars Compass PDF (recommended citation, executive findings on six-of-ten and staff-use domain, procurement and privacy bullets). Cross-checked July 8, 2026 VCU News interview summarizing the same gaps and the July 1 law’s compliance shift.","architectureImplications":"Divisions need staff AI allowlists and procurement gates that block model-training on district data—not only student AUP plagiarism rules.","governanceImplications":"Boards should prioritize staff-use and training policies alongside student integrity rules when aligning to VDOE guidance under SB394/HB1186.","securityPrivacyImplications":"Existing FERPA/privacy policies are insufficient for AI vendor training-data risks; contracts need explicit prohibitions and vetting.","caveats":"Ten-division comparative sample, not statewide census; publicly posted documents only—may miss internal drafts; June/spring 2026 snapshot precedes full VDOE guidance issuance. Companion GMU 50-division preliminary (38% with formal policies) not used as primary to avoid double-counting Virginia gap narratives.","streamIds":["k12"],"roles":{"sales":"Sales framing: Virginia divisions must move from patchwork AUPs to staff-use and procurement AI policy under new state law. Lead with staff allowlists, vendor no-training-on-district-data clauses, and training requirements—not student chatbot pilots. Ask whether teacher AI is governed at all today and whether procurement can veto model-training uses. Position a six-domain policy gap assessment as the engagement before VDOE guidance finalizes.","engineering":"Engineering framing: separate student AUP controls from staff AI entitlements; implement procurement metadata for vetted tools and contractual blocks on training on district data. Privacy stacks need AI-specific DPA fields beyond legacy FERPA exhibits. Prove staff features can be disabled pending policy adoption, and that allowlist changes propagate through IdP groups without shadow SaaS sprawl.","delivery":"Delivery framing: run a six-domain document review, draft staff-use and procurement policy language aligned to forthcoming VDOE guidance, stand up training, and brief the board. Acceptance is adopted staff-use provisions, a vetted-tool list, and signed vendor clauses prohibiting model training on division data. Schedule a post-guidance alignment check so early drafts do not drift from state requirements."},"roleDetails":{"sales":{"customerProblem":"Most studied Virginia divisions lack AI-explicit staff-use rules while state law now forces policy alignment.","stakeholders":["School boards","Superintendents","CTOs","General counsel","HR","Teacher associations"],"discoveryQuestions":["Do you have explicit staff AI use provisions today?","Does procurement ban vendor training on district data?","Is AI training required before staff access?","How will you align to forthcoming VDOE guidance?"],"valueHypothesis":"Structured six-domain policy builds (staff use + procurement + privacy) will satisfy compliance mandates faster than student-integrity addenda alone.","potentialEngagement":"3–5 week MERC-domain gap assessment and draft board policy package for staff use and AI procurement.","unsupportedClaims":["That policy adoption changes classroom AI practice immediately","Statewide generalization from a 10-division sample","Guaranteed privacy compliance without contract remediation"]},"engineering":{"fit":"Fit for divisions ready to inventory staff tools and centralize procurement vetting; weak fit where shadow AI is unmanaged.","architectureIntegration":"Staff IdP groups → vetted AI allowlist → DPA/training-data controls → usage logging; student AUP remains separate control plane.","prerequisites":["Public/internal policy corpus","Vendor contract inventory","Identity-managed staff AI access","Board policy calendar"],"constraints":["VDOE guidance timing","Ten-division evidence limits","Posted-document undercount risk"],"security":"Add AI-specific privacy clauses (no model training on district data; breach/incident terms) atop FERPA exhibits.","proofOfValue":["Domain gap scorecard published","Staff-use policy text adopted","At least one vendor contract amended for training ban","Training completion gate before staff AI enablement"]},"delivery":{"work":"Collect policies, score six domains, draft staff-use/procurement language, negotiate vendor clauses, launch training, and schedule board readings.","dependencies":["Legal","Procurement","IT","VDOE guidance release","Board clerk"],"ownership":"Superintendent and board own adoption; CTO/procurement own vendor controls; HR owns staff training.","skillsAdoption":"Required AI literacy for staff before tool access; optional deeper instructional modules later.","governanceCheckpoints":["Domain gap briefing to board","First reading of staff-use policy","Vendor clause remediation milestone","Post-VDOE guidance alignment check"],"acceptanceCriteria":["Explicit staff AI provisions in board policy","Procurement vetting checklist live","No-training-on-district-data clause in active AI contracts","Training requirement documented"],"risks":["Guidance delay stalls local adoption","Internal drafts missed in public review","Teachers continue unmanaged consumer AI"]}},"retrievedAt":"2026-09-20T03:04:20Z","enrichedAt":"2026-09-20T03:10:38Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Staff training/literacy gaps mean AI rollouts without PD will hit teachers unevenly; prioritize required awareness training before instructional AI expectations.","procurementImplications":"Only sparse divisions already tie AI procurement to privacy agreements and model-training bans—make those clauses standard RFP language.","operatingModelImplications":"Move from student plagiarism AUPs to a dual operating model: staff AI governance plus student integrity, refreshed when VDOE guidance lands.","sourceVerification":{"openedUrl":"https://scholarscompass.vcu.edu/cgi/viewcontent.cgi?article=1159&context=merc_pubs","referenceExcerpt":"Only two divisions had explicit staff AI use provisions.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}