Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the K–12 edition of November 6, 2026

Standards or public-body guidanceEmergingNew this fortnight

Michigan DOE uses CCSSO Digital Excellence grant to launch multi-state AI Together on AI, screens, privacy, integrity and well-being

Michigan Department of Education · K-12 state education agency AI and digital learning · Michigan and partner states (Delaware, Kentucky, Nebraska, New Mexico, North Carolina, Wyoming), United States

Publisher
Michigan Department of Education
Original publication
November 6, 2026
Source retrieved
2026-11-07
Event date
2026-11-06
Read original source

What happened

On Nov. 6, 2026, MDE announced $53,000 in second-round CCSSO Digital Excellence Collaborative Community funding (Ballmer Group) to begin multi-state work with Delaware, Kentucky, Nebraska, New Mexico, North Carolina and Wyoming. AI Together: Connecting States, Schools, and Families will develop engagement strategies on AI, screen time, data privacy, academic integrity and student well-being; a companion Student Voice project will surface student and educator barriers to equitable digital learning. Materials are intended for sharing with all states. A prior $40,000 mini-grant produced multilingual parent tech-support videos in GoOpen Michigan.

Why it matters

Shows SEAs coordinating shared family-facing AI/screen/privacy resources rather than leaving every district to invent engagement strategies alone—transferable for states seeking cross-jurisdictional playbooks without mandating a single classroom tool.

Evidence and measured results

Primary SEA press release with named grant amounts, partner states and project scopes. No student outcome metrics.

Limitations and uncertainty

Announcement of work beginning; deliverables, evaluation methods and timelines not specified; $53,000 budget is limited relative to statewide need.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Districts and SEAs need shared family engagement strategies on AI, screens, privacy and integrity without each inventing materials alone.
Stakeholders
  • State superintendent
  • SEA digital learning leads
  • District family engagement
  • Partner SEAs
  • Multilingual families
Discovery questions
  • Which AI Together artifacts will be public versus SEA-only?
  • How will partner-state legal differences be handled in shared templates?
  • How do first-round multilingual video workflows carry into AI Together?
Value hypothesis
Shared multi-state engagement kits could cut duplicated local drafting on AI/screen/privacy messaging.
Potential engagement
A short localization workshop mapping AI Together drafts to one district’s parent portal and policy stack.
Unsupported claims
  • That the $53,000 grant will improve student learning outcomes
  • That partner-state resources satisfy every local privacy statute
  • Guaranteed statewide adoption timelines

Pre-sales engineering

Role takeaway
Fit
Shared communications and guidance artifacts integrated into existing district portals and translation pipelines.
Architecture and integration
Interpretation: reuse GoOpen/multilingual publishing patterns; do not assume a new AI platform procurement.
Prerequisites
  • Inventory of current family AI/screen notices
  • Translation/localization workflow owner
  • Partner-state contact map
Constraints
  • Modest grant funding
  • Deliverables not yet published
  • Cross-state legal variance
Security
Any templates mentioning student data must align with FERPA/COPPA and local vendor contracts before district reuse.
Proof of value
  • Publish at least one localized family AI/privacy notice from shared draft
  • Confirm accessibility and language coverage for target communities
  • Track which partner SEAs reuse the same artifact

Delivery

Role takeaway
Work
Coordinate multi-state drafting of AI Together engagement materials and field-test with districts.
Dependencies
  • CCSSO grant administration
  • Partner SEA staff time
  • District pilot sites
Ownership
Michigan Department of Education digital teaching/learning leadership with partner SEAs.
Skills and adoption
District communicators and principals need briefing on how to adapt—not copy-paste—shared AI/screen guidance.
Governance checkpoints
  • Shared draft legal review per state
  • Public release criteria
  • District feedback loop
Acceptance criteria
  • Public shared AI Together resource package
  • Documented localization checklist
  • At least one partner SEA reuse example
Risks
  • Under-resourced delivery
  • Uneven partner participation
  • Districts misreading drafts as mandates

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?

Expect shared templates for family AI/screen/privacy communications that districts still must map to local SIS, LMS and filter stacks.

Governance

Who approves, reviews and stays accountable for outcomes?

Multi-state collaboration frames AI alongside screen time, privacy, integrity and well-being as a governance bundle, not a standalone chatbot policy.

Security and privacy

What data, permissions and controls need testing?

Project scope includes data privacy engagement strategies but does not publish vendor controls or DPIA templates in this release.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

First-round multilingual parent videos signal equity focus; AI Together workforce implications for teachers are not sized in the press release.

Procurement

What should contracts, pricing and exit terms secure?

No new classroom AI product is procured here; value is shared guidance rather than a vendor award.

Operating model

Which teams own the service once it runs?

SEA operating model is shifting toward multi-state collaborative resource production on AI bundled with screen/privacy/well-being, not solely district-by-district chatbot rules.

Publication history

  1. 2026-11-06K–12 · Issue 613 resources
Read preserved resource versions (JSON)

Stable resource ID: michigan-mde-ai-together-ccsso-digital-excellence-multistate-20261106